I have searched for an answer to why any plane of mine fitted with the Garmin 1000 has a total Garmin screen blackout after circa 5 minutes flight or even sat on the runway. I haven't used it for perhaps 6 months so unsure how I (or MSFS) have messed this up. When Asobo started integrating the Working title version I deleted the mod to use the new MSFS version, so that is not the problem.  I have started MSFS with ALL mods disabled via Addon Linker and the problem remains. Looking in the Content Manager and searching for Garmin I see there are two entries. The first shows a logo pfd screen shot and is called V0.14.0 the second shows the MSFS logo and is version 1.0.4

I have tried deleting both and of course the V1.0.4 is added back automatically on loading MSFS, but the problem remains, I again allowed Content Manager to download the V 0.14.0 and the problem remained. I have run out of ideas, can anybody help please?

In order for the new version of the WT NXi to work with all compatible aircraft I learned that both versions have to be active in the Content Manager (and yes, you would have no older mods active in your Community folder).

One version is installed automatically as it is now the default.  The other is necessary to work with some add-on aircraft and mods.

I had some issues with the NXi immediately following the SU10 install, but these disappeared after I had rebooted.

12 hours ago, RandallR said:

I had some issues with the NXi immediately following the SU10 install, but these disappeared after I had rebooted.

Thank you for confirming that BOTH versions need to be there, that is one possibility I can cross off the list, sadly even after multiple rebootings my problem still rears its ugly head in any of my aircraft using the G1000. The only point I forgot to mention in my original post is that quite often circa 5 minutes after both PFD and MFD go black, they often reappear for just a few seconds again. Very frustrating 😞

Cockpit refresh rate?

3 hours ago, Nemo said:

Cockpit refresh rate?

Thanks for the idea so just tried from High to Medium then Medium to Low and all three offer no change even after cold restarts.

48 minutes ago, Espana Pete said:

Thanks for the idea so just tried from High to Medium then Medium to Low and all three offer no change even after cold restarts.

Check for a key binding conflict with your controls/periphals.  Unplug all of them at once, start the sim and sit there and see if it still occurs. If not, plug them in again one-by-one.  You may need to restart the sim at each step.

Edited November 4, 20223 yr by fppilot

On 11/4/2022 at 4:34 PM, fppilot said:

Check for a key binding conflict with your controls/periphals.  Unplug all of them at once, start the sim and sit there and see if it still occurs. If not, plug them in again one-by-one.  You may need to restart the sim at each step.

Thanks for that tip Frank, I unplugged my Airbus TAC and tried my old Thrustmaster Hotas and voila, the G1000 was back to normal. Goodness knows which binding was conflicting as the Airbus TAC bindings were never changed and used to work OK with the G1000.

13 hours ago, Espana Pete said:

Thanks for that tip Frank, I unplugged my Airbus TAC and tried my old Thrustmaster Hotas and voila, the G1000 was back to normal. Goodness knows which binding was conflicting as the Airbus TAC bindings were never changed and used to work OK with the G1000.

We've seen a number of users report this lately. It appears there is a binding on some controllers that holds the starter in the start position forever, which is enough battery draw that the alternator cannot keep the battery charged. This leads to a battery drain and eventually no more avionics. There's no code handling aircraft systems in the NXi so this is an issue between the sim and the controller.

I would check all the bindings on those controllers and remove any related to engine start.

Edited November 14, 20223 yr by MattNischan