alstr

At the start of my latest flight from RJTT (using payware scenery), the fuel truck never arrived, despite requesting it at the EOB and again over the phone. I am wondering if it is an issue with the scenery stopping it from coming and/or AI aircraft nearby (Traffic Global)? I don't really remember it happening in the past, but it might have. In the end I used the refuel panel via the menu. Edit: Weirdly it showed up at the end of manual fuelling.

Okay, that's good I guess... but is there a way of resolving it if it happens again? I thought the door close switch wasn't engaged when trying to remove it.

I've been enjoying the latest update for the last few days and just encountered my first real problem. It was impossible to remove one of the pins from the nose door area. I tried reloading the game and trying to modify the relevant dataref and it still wouldn't be removed. As I couldn't shut the nose door I therefore had to abandon the airframe and create a new one. It looks like it was clipping through the aircraft but don't know if that was the problem. It was the 'middle' one of the three in that area.

Man am I happy about this, thank you for the great work.

Is this how it is in real life? I find the relaxed tone at odds with the urgency of the situation, but that's just based off having heard the warnings in other aircraft. terrain.mp4

Having flown the Toliss A319 recently, which has no tooltips, I just want to say how much I appreciate the tooltips provided in the Challenger. I noticed this small error a while ago but have never reported it. Chances are you already know. If you hover the outer selector on the CRS knob it says barometer.

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.

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.

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

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 will take a look, thanks. Side note, another weird camera issue has started the last couple of flights. These last two times just before takeoff the camera has gone really janky, where any joystick input or braking makes the camera shake around like crazy. Again there’s a chance this is just X-Plane rather than the aircraft. I couldn’t get it to stop despite switching views multiple times, so I had to restart (which then turned my engines off for some reason). I’m currently mid way through a flight where this juddery movement started and I didn’t want to restart so we’ll see how landing goes. Also I just discovered the fuel guy bangs on the door if you lock him out. Nice touch.