Printable View
@Asessa: others seem to have the backlight working correctly with cockpitsonic modules and latest updateed version?
Regarding the radio spacing, if you want to use 8.33kHz spacing, in your FMGS server\PERF\PA320\aircraft.ini look for the Spacing833 line and change it to
Spacing833=yes
or add the line if it does not exist.
@Netserv: maybe graphics card drivers? ATI or nvidia chipset?
JL
Thank you for the radio (on vatsim there are many station on 8.33Khz spacing).Quote:
Originally Posted by jeehell
For the backlight i don't know if there are someone using Cockpit Sonic ....
some peope have some modules from cockpitsonic. Leonidas and Tcane have ECAMp and/or radio modules from them. There was a little bug in a previous release, but the last update has fixed it (check a few posts earlier).
JL
i checked it... so, i can try to reinstall a full 38.8 maybe...
Hello, has anyone had issues with Approach phase not auto-activating in the last few betas?
Thank you.
I have not noticed yesterday because i aciveted it manually, sorryQuote:
Originally Posted by OmniAtlas
ps.
Do you have CockpitSonic hardware?
@JL
Thanks for the tipps, but no success. Tried 3 other adapters, all with correct drivers. Also onboard VGA. White displays are coming as soon as the WideFsServer starts and data is sent.
I returned to B38.6, and guess what?
It worked again properly. Anywhere in the blog i read about white displays, but those were standby instruments as far as I remember. So if I am the only one with this behavior, just forget it.
Okay, I cannot solve it, I change the Motherboard, I have some spare boards on the shelf.. ;-)
greetings, Guenther
All ok now. The problem ended up being a faulty download of 38.8
Finally discovered the problem and a new update and all seems well.
Will post all my findings on the new WideView setup when I finish all the testing.
Cheers..................Brian W.
Hello JL,
I hope you can help me!
What is the right way to install two MCDUs? In the JeehellWare.txt I have the following registered:
Var 1, name key, Link USB_KEYS, Device 2
Var 2, name keyfo, Link USB_KEYS, Device 4
I have no chance to configure the second MCDU with Sioc Creator.
When I push a Button to configure (example LSK1) the Software jumps next to Button LSK5 or RSK2.
With the first MCDU is the configuration no problem.
Must I change something in the Key.ini?
best regards
Micha
Micha,
The CPT and FO MCDU use exactly the same code for the key detection, so I think you should first try to check if you hardware MCDU does not have any issue... You may try the CPT MCDU as the FO MCDU to cross check that.
Regards,
JL