All Activity

Just keeping this thread and my hopes alive...

Oh, thanks! We were worried you wouldn't come back. ...but the answer hasn't changed.

Hi all, Just dropping in for my annual reminder that the TBM 900 “update” is still… somewhere. Every year we get the same beautifully crafted PR message about a massive rewrite, unparalleled quality, and how it’ll “definitely be worth the wait.” At this point I think the rewrite might actually be longer than the lifespan of the real TBM. If there’s actual progress, fantastic. If not, maybe it’s time to retire the yearly inspirational speeches and give us something concrete.

Crashing has definitely escalated recently. It crashed twice again today in a short flight. Both times seemed to be triggered when changing or moving the camera. I would post the crash log but it's the same kind of thing as above so I never saved it. I'm not sure if there's a conflict with Traffic Global somewhere. I've read of others having issues under the same circumstances. Since I added that things have gotten worse (though it still crashed before).

New one today. I started up the battery and APU and I got nothing on the cockpit displays, despite the pop out one working fine. It could be a brightness bug, as it went overcast dark outside, but I cranked the brightness and still nothing. The AviTab brightness was definitely darker than normal but I could still see it on max. Everything else though was impossible to see. I reloaded and the exact same problem. In the end I had to create a completely new airframe.

Incredibly weird series of events today. What should have been a short hop on a Saturday afternoon between KCRW and KDCA turned into hours of restarting and weird bugs. First, when I loaded up the sim I noticed the landing gear looked very strange, with the nose gear at a 90 degree angle and the main gear twitching. I didn't leave it like that. This was a new scenery I had loaded, Yeager, which has quite a detailed custom mesh, but I don't know if that was the problem. I think the aircraft seemed to think it was in flight. gear.mov I tried reloading the aircraft, but when you reload aircraft, it is impossible to spawn because the button is greyed out? So I had to completely quit X-Plane. In any case, I created a completely new airframe, that must solve it surely, and I spawned at different location in the same airport. Again the gear was screwed up. When I started taxiing I had a 'steering INOP' message and nose wheel steering didn't work until I re-toggled that switch. On takeoff, I blew every tyre, losing control quite a bit, and X-Plane produced about 100 popup windows to tell me, which took about 3 minutes to clear off the screen. I reloaded it to before takeoff and the exact same thing happened so I just had to takeoff. I checked failures and there was nothing listed... takeoff.mov (The front gear missing was just X-Plane's replay mode not showing it for some reason). When I landed the tyres were fine. I am not saying all of these are the fault of the CL650, but it was odd.

It looks like this update isn't going to get pushed. Is anyone here using the Sundowner with the Honeycomb Bravo or Bravo LITE? If so, is the flaps lever working? I'm thinking about purchasing it.

This is expected behaviour at this time.

I have uninstalled your highly recommended $70 aircraft. X-Plane 12 now works fine, as before. Thank you for your help. It was worth the purchase price.

Are there any known bugs about state-saving? For me the saving and loading works good, but it is exactly the same state as when I last flew it, so engines still hot etc. Is there any setting for enabling the real-time based things like ice accumulation or engine cooldown? It works like 10% of the time for me if at all, most of the time the plane is in the same state as when I shut down. Engines are off and Battery switch is off most of the time and I always use time synced to realtime.

And 12.4.0 b3 is available and bug free, several flights made, no issues

Maybe it's got worse on Tahoe. Sorry for the trouble.

Using the search function here, it doesn't appear I need to explain the trash situation over there on the "other" forum. Just thought I'd say hello and see how much activity was happening over here. Currently flying XP12 with a pretty substantial cockpit setup. Usually on PilotEdge and I do some streaming when I can. Terribly upset with the state of payware aircraft for XP12 and how these devs are selling garbage flight models. Went to criticize a vFlyteAir product at the org and got the hammer. As you can imagine nobody actually helped. Just denied a problem exists. I have switched to the default Cessna 172 and I must say, I should've went back to a default aircraft much sooner. It flies BEAUTIFULLY in the latest BETA with a FFB yoke. Very good GA bones there for sure.

I had it happen again just now before taking off, I've attached a log. The first time was maybe a rounding error but the differences being referenced here are absurdly large: 128882698720.679611 < 2773.150000 Log.txt

What Mac is this? Can you post a full Log.txt, please?

Sadly, yes.

https://discord.gg/Qjm8jxKQ

Another crash when getting ready to taxi for takeoff; X-Plane 12.3.3. Presumably same diagnosis. 2026-01-21 14:40:23 CL650[cabin.c:322]: assertion zone->T_air < ((2500) + 273.15) failed (128882698720.679611 < 2773.150000) 2026-01-21 14:40:23 CL650[except.c:120]: Caught SIGABORT: abort (0x18203b5b0) Backtrace is: 2 libsystem_platform.dylib 0x000000018207f744 _sigtramp + 56 3 libsystem_pthread.dylib 0x0000000182075888 pthread_kill + 296 4 libsystem_c.dylib 0x0000000181f7a850 abort + 124 5 systems.xpl 0x00000003543da494 asn1_check_version + 335736 6 systems.xpl 0x000000035363024c XPluginReceiveMessage + 241644 7 systems.xpl 0x0000000353630f4c XPluginReceiveMessage + 244972 8 systems.xpl 0x000000035362feb8 XPluginReceiveMessage + 240728 9 systems.xpl 0x000000035398c27c XPluginReceiveMessage + 3764252 10 systems.xpl 0x0000000353c9b98c wfETC1_DecodeImage + 341304 11 libsystem_pthread.dylib 0x0000000182075c08 _pthread_start + 136 12 libsystem_pthread.dylib 0x0000000182070ba8 thread_start + 8 --=={This application has crashed!}==-- (Art controls are modified.) 2026-01-21 14:40:23 CL650[except.c:117]: Caught SIGSEGV: segmentation fault (0x1e0) Backtrace is: 2 libsystem_platform.dylib 0x000000018207f744 _sigtramp + 56 3 systems.xpl 0x000000035372545c XPluginReceiveMessage + 1245692 4 systems.xpl 0x00000003537255c4 XPluginReceiveMessage + 1246052 5 libsystem_c.dylib 0x0000000181f2942c __cxa_finalize_ranges + 480 6 libsystem_c.dylib 0x0000000181f291ec exit + 44 7 systems.xpl 0x0000000353c71490 wfETC1_DecodeImage + 167996 8 libsystem_platform.dylib 0x000000018207f744 _sigtramp + 56 9 libsystem_pthread.dylib 0x0000000182075888 pthread_kill + 296 10 libsystem_c.dylib 0x0000000181f7a850 abort + 124 11 systems.xpl 0x00000003543da494 asn1_check_version + 335736 12 systems.xpl 0x000000035363024c XPluginReceiveMessage + 241644 13 systems.xpl 0x0000000353630f4c XPluginReceiveMessage + 244972 14 systems.xpl 0x000000035362feb8 XPluginReceiveMessage + 240728 15 systems.xpl 0x000000035398c27c XPluginReceiveMessage + 3764252 16 systems.xpl 0x0000000353c9b98c wfETC1_DecodeImage + 341304 17 libsystem_pthread.dylib 0x0000000182075c08 _pthread_start + 136 18 libsystem_pthread.dylib 0x0000000182070ba8 thread_start + 8 --=={This application has crashed!}==-- (Art controls are modified.)

I am fairly convinced that if you delete (not disable, delete!) Better Pushback, FlyWithLua, LiveTraffic and especially Volanta, things will work again.

Please find attached Log.txt

Wello, can I get a Discord Link to follow the TBM dev please?

Hydraulic temperature changes aren't simulated at this time.

I noticed that the HYD fluid temperatures remain at exactly 15c for all three systems, is this normal?

@Coop So, What can I do to solve this problem ?

Maybe try with the g-loaded camera disabled?