Hello Everyone,
For some reason, the MFD screen on G1000 no longer works, not displaying MAP, engine parameters, etc. The issue occurs on SR22 & Cessna 172. It used to work while back.
Is this issue specific to my simulator setup or have others seen this problem as well? I would appreciate any feedback and thank you in advance.
Regards from across the pond.
Are you using the stock G1000?
Hi
The quick answer is I don’t know. I haven’t gone out of my way to upgrade to stock G1000 but it may have happened during routine simulator updates. How can I find out if I am using the stock G1000?
Regards
In case you are not using the Working Title G1000 mod, a manual download and install, you are using the stock version.
In any case, it’s odd the stock Nav Unit stops working. My thoughts are you may have added another Community Mod that is stepping on the Nav Unit display.
i have same issue on baron 58G as soon as i start take off both g1000 go blank,I been asking around ,nothing yet,let me know if you found something ,last i flew was 18/5/21 no issues
I just checked and looks like Working Title G1000 is installed. Well, it’s in the Community Folder anyway. The date on the files are March 2021 and although I can’t be sure, the problem may have started back then.
Latest WT G1000 release is 3.5 for April 14th. Do not use the Beta 0.4, lots of issues since WU4 with that one despite all the bells and whistles on it which I personally like.
Also - moving this to #third-party-addon-discussion:tools-utilities since WT code is not yet streamed into the sim core code yet. That’s coming in a later Sim Update cycle (not No. 4 schedule for this week).
My G1000 issue is different from yours as it’s aircraft independent. I tried Baron 58G just now and I have the same MFD issue but PFD functions OK after take off.
In the past unless the Avionics Masterswitch was switched on (or recycled) after BAT ON, MFD would sometimes not boot properly. Now, the MFD goes through the initialisation process and requests the far righthand softly to be pressed (as it did before), after which it does not display most of the functionality it is supposed to display, eg MAP, Engine Data etc. but displays the NAV/COM data some of the GPS buttons, eg Menu and Direct To seem to work.
I use SPAD.Next to connect to a number of hardware peripherals, eg Logitech FIPs & Radio NAV/COM panel.
i might of fixed mine by resetting crash settings, i got flybywire and custom livery for a320 but files in my comunity folder have pad locks on it,cant remove them