kbjackson

Yeah, I love x-camera. Thanks for the info on ortho4k scenery. I will give that a go as well. Since my last post I have flown to Dallas from SAT and back with no problems. The TBM900 seems to be working great on my MacOS. On WinOS I couldn't turn on Synthetic view without major FPS sink and severe stutters. On MacOS Synthetic view has literally no impact on FPS. That tells me that there's something wrong with video drivers on my WinOS. Now that things seem stable I will try to add some weather and scenery addons to see how far I can get. Thanks for sharing. Happy simming.

Thanks for the feedback Robert. After posting to this thread I took a closer look at the errors in the logs and found several lines of 'malformed data' that repeats throughout the flight. Example: "2019-08-23 23:02:16 TBM900[navaiddb.c:512]: Error parsing /Users/kbjackson/X-Plane 11//Custom Scenery/Global Airports/Earth nav data/earth_nav.dat: malformed data on line 643" This is the TBM900 log file as well as the X-Plane log file. Not sure why this occurs with a clean install of X-plane with on the TBM900 and x-camera installed. I would think this existed before TBM900. I also found references to the default AI aircraft communicating with ATC and having trouble playing a wave file that is non-existent (sample below). On a whim I removed the AI aircraft and restarted the sim. To my surprise I was able to complete a 1hr, 30min flight from KSAT to KDFW in the TBM900 without incident. Of course this could be pure coincidence and speculation on my part but I will continue testing with one and only change to a pristine install of X-Plane. 1:06:35.812 D/ATC: p=1 (N43XS): Cleared IFR 1:06:35.812 I/FLT: Init dat_p1 type:loc_specify_lle lat:30.426821 lon:-98.680847 ele(ft):17000.000450 psi:135.723053 spd(kts):169.500011 1:06:35.812 D/ATC: p=1 (N43XS): Fly Heading: 87 1:06:35.812 D/ATC: p=1 (N43XS): Maintain 16998ft 1:06:35.812 I/ATC: Aircraft p=1 (N43XS) started airborne as an overflight at 30.426821, -98.680847, 5181.600098 1:07:14.992 I/ATC: BEECH 90 (A90 King Air) 3XS, KDZB altimeter 2 9 9 5. 1:07:14.992 E/ATC: Tried playing a wave file that doesn't exist: 'King' 1:07:14.992 E/ATC: Tried playing a wave file that doesn't exist: 'Air)' 1:07:14.992 E/ATC: Tried playing a wave file that doesn't exist: 'apt_KDZB.opus' 1:07:19.998 I/ATC: KDZB altimeter 2 9 9 5, BEECH 90 (A90 King Air) 3XS. 1:07:19.998 E/ATC: Tried playing a wave file that doesn't exist: 'apt_KDZB.opus' 1:07:19.998 E/ATC: Tried playing a wave file that doesn't exist: 'King' 1:07:19.998 E/ATC: Tried playing a wave file that doesn't exist: 'Air)' My current plan is to keep a clean install of X-plane with TBM900 only and continue flying around the southwest region for a while. I typically will perform 1 to 2 hour IFR flights in daytime and night. To make life easier I have 5 copies of X-Plane installed so that I can continue to enjoy the TBM900 as is and other addons as well. Copy 1: Clean X-Plane install with TBM900 only Copy 2: Clean X-Plane install with addons of all sorts, including TBM900, Zibo, PMDG, Carenado, Orbx scenery, AVItab and pushback addons, etc. Copy 3: Clean X-Plane install for testing 11.40 alpha Copy 4: A backup copy of Copy 1 Copy 5: A backup copy of Copy 2 just in case I mess up my current environment With a 2TB SSD drive this is easy to maintain.

I have been experiencing this problem with the TBM 900 and watching the posts daily for the past few weeks. I think I may be in a unique position to offer some help in troubleshooting as I have 2 different OSes with clean XP/TBM900 installs. A little history from my perspective. I initially installed TBM900 on my Windows 10 OS with the latest version of XP (11.35r1) and experienced the 'exception handler, replaced it with 0000000000000000' CTD issue as widely reported. I tried various method of troubleshooting as suggested in your forum with no joy. As I am a RW pilot and going through instruments training I use XP quite a bit. My Windows OS is dedicated to only XP with very modest addons/plugins. So I had no problem simply removing XP completely and reinstalling a fresh copy. I then installed TBM900 as my one and only addon product and repeated my normal IFR flight from KSAT to KDFW using G1000. Same results with 'exception handler, replaced it with 0000000000000000' CTD. I also run XP on a late mode iMac with 8GB GPU and 24GB memory. This system has a 2TB SSD so I have no problems installing more than one instance of XP. On this OS I installed a fresh copy of XP and TBM900 only. Same IFR flight from KSAT to KDFW using G1000 with similar CTD. I say similar because the logs on the MacOS does not show the exception handler error. Still, CTD with a clean install of XP/TBM900. I have since installed x-camera which I cannot live without but the results are always the same on the same route flown. The kicker here is that both OSes are running on the same hardware. Win10 running on bootcamp formatted disks and MacOS running on journaled disks. The fact that the same CTD occurs on both OSes rules out a lot of things and brings into focus the GPU which is about all that both OSes share other than memory or disks. Since I run other addons on the WindowsOS such as Zibo, PMDG777, 737, Carenado PC-12 and others with RealityXP GNS750 with Garmin trainer and addons as well, without problems then there must be something happening with the TBM900 that my system is just not able to handle. I can afford a new state-of-the-art system but want to make sure that this issue is fixable in a known way. There are a few more logs of interest in the MacOS that are not present with WinOS but this may not be relatable to the issue at hand. I am willing to test any configuration on either or both of the OSes. I love the TBM900 with excellent G1000 so much that I'm will to wait for a solution for as long as it takes. This fits so closely to my RW flying and makes my ground school training so much more richer. I have learned things using this config that I haven't been able to easily grasp in RW training. I will stick with small flight from San Antonio to Corpus and Houston as they are shorter and seem to work fine. It's the longer flight to Dallas that always causes the CTD. Hope you get this sorted out. I'm here to help in any way I can. Here are my logs from the MacOS. I will post the WinOS logs soon but I'm sure they look exactly like everyone else's. Note: Yes, I am aware of the hypoxia alerts that show in the logs. I stupidly took off with the cargo door not properly secured and the LFE went crazy at about FL150. I recovered quickly though which shows just how deep the TBM900 is. Well done. Cycle Dump.txt Data.txt GizmoLog.txt Log.txt Macintosh HD:Users:kbjackson:X-Plane 11:GizmoLog.txt TBM900_Log.txt