PFD-MFD Map Corruption

[HamSammich]

Hiya Toto,

XP 11.31

Windows 10

TBM 1.14b

SYMPTOM: MFD map doesn't appear. PFD map insets are corrupted--Screenshot attached.

 DIAGNOSIS: Checking my TBM900_Log.txt (also attached) reveals lines along this pattern:

2019-02-03 22:15:35 TBM900[navaiddb.c:512]: Error parsing C:\Users\marsh\Desktop\X-Plane 11\\Custom Scenery\Global Airports\Earth nav data\earth_nav.dat: malformed data on line 1051

WORKAROUND: Deleting the Global Airports folder, pulling a fresh one with XP installer, removing and reinstalling the TBM, fixes the problem. Until it recurs.

Any ideas? Oh, and the plane CTDs when accessing the FPL, but I know this is a known bug and is being worked on.

Otherwise (seriously) I'm truly impressed. It's an amazing beast.

 

Marshall

 

 

TBM900_Log.txt

Edited February 6, 2019 by HamSammich
Typos

[Shinjo]

+1 to this. Happened to me last night, I think it was when I switched on the strobe lights, but it's happened other times as well. Wasn't sure if it was part of the 11.31 bug or not.

[HamSammich]

This is serious stuff. Why no reply from Goran or Saso? Understanding you're scrambling to deal with the CTD with 11.31, but this is a showstopper, too.

 

 

[Goran_M]

We're trying to deal with the 11.31 problem at the moment.  That problem is a blanket issue for, literally, everyone who updated to 11.31.  This one is an isolated case, limited to a few people.  

I'll get to it as soon as I can, but first thing I'll need is a log.txt file.  Not the TBM900 log file, but the one found in your root x-plane folder.  

You could also try, if possible, installing a complete bare installation of x-plane somewhere on another hard drive.  No scenery, and installing the TBM in that and see if the problem persists.  To me it looks like you have missing G1000 files.

Edited February 7, 2019 by Goran_M

[HamSammich]

Hi Goran,

I certainly appreciate your 11.31 nightmare. Did as you asked. Squeaky-clean XP install. Zero plug-ins. Then just my Brunner yoke plug-in. The problem manifested itself after several successful flights both clean and with the Brunner. Then, after having totally, utterly and properly shut down the plane, I restarted XP, only to have the TBM come up with the panel lit up and the Garmin broken. I promptly deleted the yoke plugin, removed and reinstalled the TBM, but the problem persisted.

Therefore I'm attaching three log.txt files. One is clean and working. The second is yoke plugin and busted. The third is, again, clean, reinstalled aircraft but still kaput.

Best,

Marshall

Log_Working_Clean.txt

Log_Broken_Yoke_Only.txt

Log_Broken_Clean.txt

[Goran_M]

Stupid question.  Did you check the maintenance manager to see if anything is broken?

[HamSammich]

Yup.

And reloaded the plane. And loaded new airframes. And done all the superstitious stuff. At first it seemed I could reproduce the problem by switching on battery power before the standby instruments were fully loaded, and curing it by waiting. Turned out to be random chance. It even happens in the tutorial, on a virgin install

[Goran_M]

This one is out of left field, but I've seen crazier stuff.  Have you installed the latest graphics drivers for your graphics card?

[HamSammich]

I did. And rolled it back one. I’m a former OS and newsroom computer system beta tester, so I’ve seen weird. But it’s an ambitious piece of software, with many interactions. This is bound to happen sooner or later.

BTW, the computer is pretty vanilla. Nvidia, intel 8700 and windows 10. The G1000 on the stock Cessna works fine

[Goran_M]

I'll get back to you.  I'm going to run some tests for this and the CTD's in 11.32 over the next 12-24 hours.

 

[HamSammich]

Good luck!

[walessa]

You may try deleting "../output/preferences/Miscellaneous.prf" (keep a backup). Possibly it's just the TBM entry in this file, but have not investigated further. Seems somehow related to the joystick/keyboard profile name ?

At least, solved the very same problem for me. Good luck !

 

[HamSammich]

Afraid it didn't work for me. Glad it did for you.

Marshall

[Hoekstes]

Exact same problem for me as well

[Shinjo]

This exact thing happens in the C172 when you have the battery on but not the avionics master. Is there some under-the-hood equivalent to this in the TBM? 

[Shinjo]

Bumping this back to the top. Still an issue.

[Goran_M]

If it's happening to some people with the default Cessna, as well as the TBM, this looks like some kind of combination between the users hardware and installation of X-Plane.  I cannot duplicate this at all on my system.

[Shinjo]

The point of highlighting the similar behavior in the Cessna was that it appears to be a normal reaction to flipping the avionics switch on and off? But the TBM has no avionics switch. 

So if you sit in the C172 G1000 with the master battery on but the avionics off you don't see what the OP's screenshots show (blank MFD, Xs on the PFD)?

 

Edited February 21, 2019 by Shinjo
Rewording

[HamSammich]

I get the problems still. However, reloading aircraft and art universally fixes it. Very annoying, though.

[skiselkov]

@HamSammich Are you running any kind of hardware switch panel (e.g. Saitek) that has an avionics master? This kind of look is a clear indication that something is messing with the G1000 datarefs underneath. If you do, try disconnecting that and testing to see if it has an impact.

Avionics dataref off:

Avionics dataref on:

[HamSammich]

Saso:

Aha! Now this is interesting. I have no hardware whatsoever that should affect that dataref. However I have had a similar problem with the LES SAAB and the G530 that was solved by manually turning the dataref on. Just wondering if there's something in common (Gizmo?) between the two planes that somehow farkles that particular dataref? In the meantime, I'll try flipping the DR manually to see if it fixes the MFD.

 

I've got a couple other questions about other hardware (Brunner and RealSimGear) to ask. Mind if I contact you directly?

Marshall

[skiselkov]

6 minutes ago, HamSammich said:

I've got a couple other questions about other hardware (Brunner and RealSimGear) to ask. Mind if I contact you directly?

No problem at all.

[Shinjo]

Thanks @skiselkov, how do you manually change datarefs?

Edited February 21, 2019 by Shinjo

[Shinjo]

Ok ... I think I've gotten to the bottom of it, at least in my case. My Saitek switch panel, which I partially use for lights only was setup with the default Spad profile, which includes Avionics On/Off commands for the Av Master switch. I didn't actually verify this by watching the datarefs and events, but I think when I flick the the strobe light on for the very first time Spad tries to sends some commands for all the switches to sync their state ... and since the Av Master switch is physically in the OFF state it must be sending an Avionics Off event.

So, basically flipping the Av Master switch on my panel flips between the low power state and normal state. Working as intended lol >.>

So for me the answer is to simply unbind the Av Master switch. I can't speak to @HamSammich since he/she says they're not running panels. It may be something Toto/Goran want to fix under the covers, but that's obviously up to them.

Thanks for the help with this guys.

 

[skiselkov]

Yeah it's definitely the avionics_on dataref. I'll be adding an override into the plane's code to make sure the dataref is set right and it will also detect when something external is messing with it.