alstr

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/

Hi, I have a variety of noob questions relating to ATS I was hoping someone could shed some light on to help me further understand this wonderful aircraft. 1. I've encountered a few scenarios, usually on approach, where ATS fails and I can't reconnect it. I want to better understand the reasons for this. I'm assuming it's because the aircraft can no longer maintain the speed selected, or because of some manual intervention. How can I rectify it? 2. I also want to clarify the colour of the speed on the PFD. Is this correct; Pink - ATS active and following speed in VNAV setup; Blue with ATS illuminated - speed set at number dialled in by speed knob; Blue with ATS not illuminated - ATS disengaged, power set by throttle position. Sometimes I'm not sure whether ATS is active or not. 3. What is the meaning of the throttle sliders that appear in the bottom right hand corner of the screen, indicating that they should be moved to the position shown? 4. Sometimes when climbing out with a heavy fuel load the speed plateaus at around 200kts and then starts to fall backwards. ATS fails here also as the aircraft appears to be climbing too steeply to meet the speed asked of it (presumably partly answering my first question). I usually set speed to 231 before takeoff then after the packs transition engage VNAV climb at 250 kts. What is the best procedure here? (I am sure the real world detail is much more complex than can be distilled here but a general overview is helpful). Thanks.

That is what I thought. Since I created a new airframe it has actually stopped. So the old airframe must have become weirdly corrupt or something.

The 'terrain, terrain' warning in this aircraft sounds like it is spoken by some text to speech engine. It sounds a bit odd, though I can't say what the real deal sounds like either, so I'm just guessing here. Just wondering what the situation was and if it can be improved. (Yes I know you can just not fly near terrain).

I'm guessing TorqueSim is aware of this. Will it be fixed in the next release?

I can cope with it, but that's good news about the update. It periodically crashed under the same circumstances with older versions anyway, just not as much.

Here. It always crashes at the same time. Log.txt

Hmmm... the crashing has returned. Is anyone able to elaborate on what 2026-01-21 14:40:23 CL650[cabin.c:322]: assertion zone->T_air < ((2500) + 273.15) failed (128882698720.679611 < 2773.150000) relates to exactly, so I can maybe experiement with ways to avoid it? I've tried checking datarefs for crazy values.

Not sure if this is the aircraft or X-Plane, but it's a bit weird. You can load up a save on final approach and get warnings about 100kt winds (as below).

Update: I have had no crashes since removing Traffic Global, when they were previously a frequent occurrence, so there is a problem somewhere related to that. Whether it’s TG directly or how it interacts with this aircraft I don’t know.

Yes, I believe so. It looks like there’s a ridge at the top of the runway that seems to trigger these warnings unless you go over it at reduced speed. I think most of these issues, bar the loading issue, are mesh related. Shame because the default X-Plane airport has many problems and visually this payware one looks great. It has been relayed to the developer. I'm still not sure whether any tyre was actually blown, because like I said the aircraft landed fine.

The tyres blowing I do believe is particular to this airport's mesh. Going over a ridge in the runway seems to set off a chain reaction. It doesn't happen with any other aircraft I've tried though, and the Challenger doesn't show it as a failure.

That's what I've done. So far no crashing. But also no traffic obviously, and I would ideally like to keep it. I've already been through the support process with Just Flight and the logs always reference the Challenger so thought there must be something on that side causing it.

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.