blackshe3p Posted October 20, 2018 Report Posted October 20, 2018 (edited) Hi! I cant figure out why there is no map displayed on the MFD and also there is the fault "XPDR fail". Can't find anything in the docs and got no sim faults enabled. Happens with fresh airframe as well. From watching some tutorials I would consider this a bug. Is it? Edited October 20, 2018 by skiselkov Quote
Cameron Posted October 20, 2018 Report Posted October 20, 2018 Certainly looks like a bug! @skiselkov will look at this soon after he wakes up in a couple of hours. Quote
skiselkov Posted October 20, 2018 Report Posted October 20, 2018 Can you please check if you have a Saitek switch panel if - always put the AVIONICS switch to ON. Otherwise it kill the background G1000 systems. Or unplug the panel. Quote
blackshe3p Posted October 20, 2018 Author Report Posted October 20, 2018 Reloading the plane in the sim seems to have fixed it. I have no Saitek switch panel. Thanks Quote
skiselkov Posted October 20, 2018 Report Posted October 20, 2018 41 minutes ago, blackshe3p said: Reloading the plane in the sim seems to have fixed it. I have no Saitek switch panel. Great to hear, thanks for letting us know! Quote
Mike Cameron Posted October 21, 2018 Report Posted October 21, 2018 (edited) This is happening on my system also. I do not have a Saitek panel and reloading does not work. It worked when I first purchased but does not work now. Could it be navigation database related. I updated to latest Navigraph Database for XP11 and thats when it started happening. How to I revert back to default XP NAV database to test. Removed custom data and also discovered that my GO Flight avionics switch is needed just like the Saitek. Strange because none of my other Go Flight buttons work. Thanks, Mike Edited October 21, 2018 by Mike Cameron Updated results Quote
2Fat2Fly Posted October 23, 2018 Report Posted October 23, 2018 (edited) Hello devs, I have the same issue too. Every time I start XP and load the aircraft, the MFD map is not showing up and the map display on the PFD is corrupted and unreadable. Reloading the aircraft via the debug menu DOES WORK. However the next time I start XP the very same issue will happen again, so I have to manually reload the aircraft every time. I don't have the Saitek panel nor have the plugin installed. I wonder if the issue can be fixed so I can save up the effort to reload the aircraft? Thank you! Fengyu Edited October 23, 2018 by 2Fat2Fly typo Quote
mctxpilot Posted October 23, 2018 Report Posted October 23, 2018 I have the same problem. The PFD and MFD images are not correct. The MFD shows a portion of an attitude indicator and no map. Both the PFD and MFD are discolored. Quote
Seamaster Posted October 23, 2018 Report Posted October 23, 2018 (edited) I don’t see on MFD charts and checklist menu also the engines gauges and alarm are displayed on right part of screen Edited October 23, 2018 by Seamaster Quote
piper2102 Posted October 24, 2018 Report Posted October 24, 2018 I could reload but once ahrs aligns it goes dead again. Quote
fireone Posted October 24, 2018 Report Posted October 24, 2018 In order to aid the developers ( and all who might be able to help ) its standard procedure to attach the log.txt file and gizmo.txt file to posts asking for help solve problems. The log.txt file among others is in the main X-Plane folder. Copy it as a file then attach to your post Don't copy the text and paste it in your post or it'll make the post physically long. Its worth opening the text file and reading it for oneself. Some of it is jargon , but a lot of it is easily understood and offers immediate problem solving solutions. Quote
2Fat2Fly Posted October 24, 2018 Report Posted October 24, 2018 (edited) 2 hours ago, fireone said: In order to aid the developers ( and all who might be able to help ) its standard procedure to attach the log.txt file and gizmo.txt file to posts asking for help solve problems. Oops I've forgotten that. Sorry. Here's the Log.txt and the GizmoLog.txt. The aircraft is the latest v1.0.5. When I started X-Plane, loaded the aircraft, push the crash bar up and selected the batt source, the PFD and MFD looked like this: The missing map and menus on the MFD, and the miscolored gauges on the PFD is obvious in the picture. Also may you notice that the backup gauges on the PFD is not supposed to be there when the MFD is alive, and the "XPDR FAIL" message is in place instead of the normal transponder code and mode. Then I reloaded the airplane via the developer menu, everything is back to normal: And below are the flight log files which seems to be useful for the analysis: log_181024_152234_LGKR.csv log_181024_152448_LGKR.csv If there is any other files that will help for the analysis, please let me know! Edited October 24, 2018 by 2Fat2Fly Quote
fireone Posted October 24, 2018 Report Posted October 24, 2018 2Fat2Fly , I'm not an expert by any means . I've had a very quick look at your log.txt . My observations which may or may not mean anything . You have a fair few plugins and the Terrain Radar Utility isn't always behaving , have a look at .txt the file to see what I mean about 1/ 3 and again 2/3 of the way down. Not every error message ,or failure to load ,causes problems but if you want to try before the devs find a solution for you I would disable all plugins unrelated to the TBM via the plugin menu as a starting point and see how it goes. 1 Quote
2Fat2Fly Posted October 24, 2018 Report Posted October 24, 2018 (edited) 5 hours ago, fireone said: I've had a very quick look at your log.txt . Thank you! In fact I myself haven't taken a look at them yet! xD I've removed literally EVERY plugin except for the necessary ones. Nothing had changed and here's the log files for the fresh run: Log.txt GizmoLog.txt log_181024_220013_LGKR.csv log_181024_220157_LGKR.csv Edited October 24, 2018 by 2Fat2Fly Quote
strumpy Posted October 24, 2018 Report Posted October 24, 2018 I am having the very same problem with the TBM900, but my problem stays the same even after a restart aircraft, through the developers menu. Log.txt Quote
2Fat2Fly Posted October 25, 2018 Report Posted October 25, 2018 On 10/20/2018 at 8:00 PM, skiselkov said: Great to hear, thanks for letting us know! Could you please have another look at this? It seems that the issue still persists in some cases. Quote
skiselkov Posted October 25, 2018 Report Posted October 25, 2018 3 minutes ago, 2Fat2Fly said: Could you please have another look at this? It seems that the issue still persists in some cases. Can you please try without additional plugins loaded? I suspect some of them are messing with the electrical datarefs and are shutting part of the avionics off. Quote
2Fat2Fly Posted October 25, 2018 Report Posted October 25, 2018 Just now, skiselkov said: Can you please try without additional plugins loaded? I suspect some of them are messing with the electrical datarefs and are shutting part of the avionics off. I've done a run with only gizmo in my plugin folder: 22 hours ago, 2Fat2Fly said: I've removed literally EVERY plugin except for the necessary ones. Nothing had changed and here's the log files for the fresh run: Log.txt GizmoLog.txt log_181024_220013_LGKR.csv log_181024_220157_LGKR.csv The issue persists and it seems that someone else suffers from being completely inaccessible to the MFD maps. Quote
strumpy Posted October 25, 2018 Report Posted October 25, 2018 I have also removed all of my plugins but still the same problem persists. Please see attached X-Plane log. Log.txt Quote
2Fat2Fly Posted October 30, 2018 Report Posted October 30, 2018 (edited) Deleting the output folder solved this issue on my side. However I've yet to find which particular file that cause the issue. Edited October 30, 2018 by 2Fat2Fly 1 Quote
Hoekstes Posted February 13, 2019 Report Posted February 13, 2019 (edited) I have this same problem. Do I need to delete my entire Output folder?! EDIT: I did delete the entire contents of by Output folder and restarted X-Plane. This did in fact solve my problem. Edited February 13, 2019 by Hoekstes Resolved problem Quote
Goran_M Posted February 13, 2019 Report Posted February 13, 2019 @HamSammich I knew there was another topic about this. Can you try this out? Quote
HamSammich Posted February 13, 2019 Report Posted February 13, 2019 (edited) I have not yet deleted my entire output folder, but I have discovered another workaround, and it may be helpful diagnostically. Reloading the plane and art fixes the problem for me--which I'm beginning to think has something to do with load-order or synchronization with XP's underlying G1000 code as it loads or perhaps as it's invoked by the TBM. It's just my dumbass gut instinct. The reload even fixes a corrupted PFD/MFD once it's happened, but it also seems to prevent it if done BEFORE flipping on the batteries on the TBM. Still broken, but now at least fixable. I'll also try the output folder fix and report back. Best, Marshall Edited February 13, 2019 by HamSammich Quote
HamSammich Posted February 13, 2019 Report Posted February 13, 2019 Okay, deleting the entire output folder fixes the problem. I have no idea why. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.