Mitchel James

With the latest TBM update, (1.1.7), I now cannot even load a flight on x-plane. After configuring a flight, and x-plane is loading, I see the: Loading Aircraft/X-Aviation/TBM-900/TBM900.acf. appear on the bottom left loading bar, then after about 5 seconds, x-plane stops responding until I get a crash or I have to manually use CTRL+ALT+DEL to end the program...... Only happens with the TBM, no other aircraft. Has this been reported? I haver attached my Log file, I assume it shows enough as I am technically closing x-plane as I have a full Windows freeze. With all due respect, this is starting to get ridiculous. A $70 aircraft should not have so many problems on every single version. I have 10+ purchased planes from other developers, and I don't recall a single CTD, freeze, error or similar with any of them. This TBM (again the most expensive one I have purchased by over $40), has crashed on me in excess of 20 times in, from memory, about 60 hours of flying time. LogTBMerror_again.txt

More crashes recently. I cant pinpoint anything specific I'm doing when they occur. Each CTD is just randomly whilst in cruise, not touching anything, not playing with the Garmin etc. I was starting to think it was something to do with approaches / arrivals being loaded into the Garmin (after a prior post from Goran re the Garmin possibly causing issues with scenery errors loading into it) and crashes we were getting in the previous TBM version, but on my latest flight, I purposely had not added my destination airport to my flightplan, nor had I selected an airport as a waypoint. No procedures etc were loaded in at all, it was simply VORs. This latest CTD, departed KSNA, passed PDZ VOR, passed DAG VOR, then enroute on around a 340 degree course up to KTPH at FL280, about 30 min away from reaching KTPH when I got the sudden CTD. Hadnt touched the screen or aircraft, or changed a view or anything in about 3-4 minutes. Log is attached. Re plugins, Im virtually running no plugins at all. Im not getting any CTD with any default or custom purchased aircraft at all, except for in the TBM. Of note, I probably went around 4-5 hours without a CTD in the TMB prior to this flight, all flying very similar areas (KSNA up to KOAK and around california and Nevada border on others) TBMLog_27feb.txt

Nope, I haven’t downloaded any of the ortho scenery packages.

Hi @Goran_M, Firstly please forgive my ignorance as I don't know the first thing about these logs and lines of computer text - but I can see all the custom scenery errors you are talking about. How can I tell which custom scenery they are referring to? The only actual custom scenery I have personally installed is KSNA and KLGB (and the MisterX Library). I have absolutely no other scenery plugins. (the other custom scenery folders listed near the start of the log are put there by x-plane itself I believe?) Whilst Ive had probably 6 total CTD since downloading the original version of the TBM900, I don't think a single one of them has been anywhere near my custom scenery of KSNA Todays CTD occurred with the following entered into the FLPN; depart KROW>BWS>SSO>TFD>GBN>VICKO>BLH>KPSP I was in cruise at FL280 and around halfway between SSO and TFD, got the CTD. I have previously done many flights in/around this route - most of mine originate in KSNA and branch out to anywhere from San Francisco area, Utah to New Mexico or West Texas (or the subsequent return trip). As in my original post, version 1.1.3 of the TBM and 11.26 of x-plane worked for months and many hours without a single hitch with the TBM or any of my other default and extra aircraft, so its strange that the same CTD error that was occurring in prior versions has returned?

Just updated to x-plane 11.30r3 (Windows). Then, updated TBM900 to V1.1.4. About 2hrs into flight, again getting the same error. '2019-01-15 15:35:12 TBM900[except.c:282]: Something reinstalled our exception handler, replaced it with 0000000000000000' I previously got this CTD exception handler error numerous times on prior TBM versions, but it was perfectly stable for around the 30hrs of flight time in version 1.1.3. Now with the x-plane update and TBM update, same errors occurring again. Extremely frustrating to say the least. Has any progress been made to find the cause? It seems not? It seems like updates are just 1 step forwards, 2 steps back. TBM-error-Log.txt