Leaderboard

Hi, do you guys have a timeline on the update? I'm curious if I should buy the steam version so I can go back to 12.4.0.

Thanks. We know. A beta to fix will be out soon. (See numerous other threads.)

Laminar released the current stable version of X-Plane 12.4.1 today on which the current version 1.8 of HotStart Challenger 650 crashes with the error "Threading violation calling XPLMGetDatad". Loading the TorqueSim SR-22 crashes with the same error. The release notes of X-Plane even state the issue. I hope this gets fixed soon as there is no way of getting an older X-Plane version on new installations.

https://support.x-aviation.com/knowledgebase.php?article=7

Once Laminar Research releases its new documentation for users and devs, I believe you can expect renewed activity on the IXEG.

zzz....oh man...just woke up after a 18 month hibernation! Seriously....Nothing is forgotten, only life has happened. Here's a quick summary: Spent last 18-24 months in a significant life transition as I approach and prepare for retirement. Lots of loose ends to tie up and leave in the past. I now work full time for Laminar, a big change...and I have been positioning myself to stay in X-Plane work exclusively for the future. I'm wrapping up a 2-year private contract for the BETA ALIA production aircraft (which will be in X-Plane). I'll complete that work next month. Gizmo based code in all my products is nearing end of life and had complicated the update process due to the volume of code to rewrite......however AI has enabled a path to relearn concepts & rewrite the code as its become "X-Plane SDK aware" in the last year...This reduces the effort drastically and is a major catalyst. No fees for future updates on the MU2 or IXEG when they eventually go out. Updates will always be free for existing customers. They've earned that. After ALIA delivery, I'll return to push an update to the MU2 with the Gizmo code-base....I won't get OCD....I'll just push what I have, which is a good amount. After MU2 update, I begin code rewrites to serve as my future code platform for the MU2, IXEG and the forth-coming 717. This is foundational and absolutely required to guarantee long term compatibility for these products. Those aircraft will be the only three products I will maintain into retirement and beyond. That's the highlights. This gap in work has been all about my focus and preparation to sustain myself after retirement, and stay within the X-Plane ecosphere in the process.

It's not worth doing. Laminar can instruct you on how to downgrade if you contact them. We hope to have an update out on our end within the next week or two.

Every time I load a flight I get a CTD with 'threading violation' in the log. 2026-03-31 13:55:31 CL650[libsvs.c:4912]: libsvs(SVC): utilizing background rendering via IOSurface Threading violation calling XPLMGetDatai (/Users/administrator/.gitlab-runner/builds/5iac3Er_D/0/x-plane/design/SDK/COMMON/xplanesdk/Src/XPLM/XPLMDataAccess.cpp:327) Violation by Challenger 650 by Hot Start (hotstart.challenger650) 2026-03-31 13:55:31 CL650[except.c:120]: Caught SIGABORT: abort (0x1a049d5b0) Backtrace is: 2 libsystem_platform.dylib 0x00000001a04e1764 _sigtramp + 56 3 libsystem_pthread.dylib 0x00000001a04d7888 pthread_kill + 296 4 libsystem_c.dylib 0x00000001a03dc850 abort + 124 5 XPLM 0x000000012aba52c4 _Z26__XPLMValidateThreadSafetyPKcS0_i + 536 6 XPLM 0x000000012ab938ac XPLMGetDatai + 56 7 systems.xpl 0x000000037117028c wfETC1_DecodeImage + 130948 8 systems.xpl 0x0000000370ed55b4 XPluginReceiveMessage + 4031316 9 systems.xpl 0x0000000370edbed0 XPluginReceiveMessage + 4058224 10 systems.xpl 0x00000003711a6e78 wfETC1_DecodeImage + 355184 11 systems.xpl 0x00000003711a3840 wfETC1_DecodeImage + 341304 12 libsystem_pthread.dylib 0x00000001a04d7c08 _pthread_start + 136 13 libsystem_pthread.dylib 0x00000001a04d2ba8 thread_start + 8 --=={This application has crashed!}==-- In the X-Plane release notes it acknowledges that the Challenger 650 is not compatible: https://www.x-plane.com/kb/x-plane-12-4-1-release-notes/

Please don’t post whole log spams, rather attach the txt file to the post. Regardless: https://support.x-aviation.com/knowledgebase.php?article=7

Laminar released the current stable version of X-Plane 12.4.1 today on which the current version TorqueSim Sr22 crashes with the error "Threading violation calling XPLMGetDatad". X-Plane 12.4.0 worked fine. I hope this gets fixed soon as there is no way of getting an older X-Plane version on new installations. Log.txt

Wow, I must say Cameron was right. I switched back to XP version 12.4.0 and all my SR22s are working like a dream. Thanks.

Couldn't find much information online about audio issues with either the Motherboard or CPU, Updated my audio drivers but alas, no luck. I will update my BIOS some time over the weekend and see if that was an issue. After that im not sure what to do. The plane is great in all other ways - but this audio issue is really hampering it, I will let you know when I have more info, but I am not really sure what to do next.

Well, it seems you are completely right with it being a thing on my end. Tried it on my macbook, and my spouse's windows laptop - both of which are working fine. Id be curious to know what OP's computer specs were as it might be an issue with a specific hardware (for me an I5-12600kf and an msi b760m mobo) those two would be the culprits of a hardware audio problem, now time to see if these have any known issues with openAL.

This is the BN-2B Piston Channel but have the same issue.. could be XP12 12.4.1b1 and is applicable to the BN-2T as well. The image shows other issues. The plugin cannot be used as it crashes XP12.

Cameron, Glad to know my consistency matches yours. Maybe next year we can both surprise each other. Friendly banter aside, the lack of movement is the real concern. If the answer hasn’t changed in years, maybe the communication strategy should. Kind regards, Lucian Anghel

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.

Quite some time ago, but tried it as shown in your video and good enough for me

I couldn't start working before 12.1 went final. Beyond this, 1 person, me, working on 2 aircraft support and 2 aircraft under development. Moreover, I'm slowly moving the code from Lua to Cpp, which I'm learning as I'm doing things. Mostly, the update is almost done, needs final touches to be ready.

Xp13 will already be at version 13.5 and we will still waiting for the radar and the beta update... but don’t ask anything to the devs