bpcw0001

I may add that the log was generated when I reloaded the situation after the first crash, and I tried the direct to in the reloaded situation with exactly the same outcome. That may also indicate that this behavior was not just some random fluke.

Full log file attached. Log_DIRECT_TO.txt

Hi, generally, I enjoy a pretty stable experience with the Hot Start Challenger and X-Plane 12. I see no crashes or other issues at all on my system, except for occasional CTDs that happen when using DIRECT-TO in the FMS. It does not matter if I use the "DIR" button in the FMS, or I do it "Boeing-Style by copying a flight plan waypoint into the scratchpad and LSKing it to the active waypoint on the LEGS page). As soon as a waypoint is chosen as direct to, the sim crashes. I've had this on some occasions now, interestingly always when flying east-to-west routes (may be coincidence though). The latest one happened on this route: LEBL/20 N0459F390 SENI2J SENIA UZ596 NEXAS UN975 CCS DCT EXONA EXON9A LPPT/02 Shortly before NEXAS, I was given a direct to CJN. The crash log says: 2023-07-22 21:59:24 CL650[gps4000s.c:2940]: WAAS data download successful 0:07:06.454 I/ATC: Airport flow changed at LECH! CurFlow: W wind NewFlow: E wind 2023-07-22 22:00:30 CL650[fpl_path.c:1840]: Internal error Backtrace is: 0 00007FF8F3B44B2C C:\Windows\System32\KERNELBASE.dll+0000000000064B2C () 1 0000000080375AE1 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000385AE1 (cstr_alt_at_leg+151) 2 000000008037ABDE C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000038ABDE (guess_leg_alt_lnav+79e) 3 0000000080389E03 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000399E03 (solve_lat_path_leg+763) 4 000000008038B74B C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000039B74B (fpl_path_rebuild+4cb) 5 000000008045297A C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000046297A (rebuild_fpl_paths+4ca) 6 0000000080456065 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000466065 (fpl_mgr_main+2515) 7 00000000803DCCC4 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000003ECCC4 (fmc_main+1a4) 8 0000000080573360 C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000583360 (runpool_worker+11f0) 9 0000000080569E1F C:\X-Plane 12\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000579E1F (_lacf_thread_start_routine+f) 10 00007FF8F51626AD C:\Windows\System32\KERNEL32.DLL+00000000000126AD () 11 00007FF8F65AAA68 C:\Windows\SYSTEM32\ntdll.dll+000000000005AA68 () --=={This application has crashed!}==-- --=={UUID: c12d07a6-0e15-476d-af13-e236a5cf102c}==-- FMA at the time of the crash was: LNV1 AP VALTS 0.80M, 39000ft I am on Windows 11 Pro. I use Navigraph navdata (for this case: 2307 rev2)

Same on arrival / approach into LEVC RWY 12: Arrival SAURA.SAUR4D, approach ILS Z RWY 12 via OPERA Autotune and ghost needles happened at around OPERA only. Like I said, still sufficient, but a bit late for comfort. Many other approaches give me autotune and ghost needles way before the actual approach.

Hm ... ok. Strange then. Then I am not even doing anything wrong as it seems. Also right now, I was going along this route: LIRA/15 N0466F390 ESI5V ESINO Z924 ABIDU DCT EPIKU DCT GINOX UM601 BCN UN975 CCS DCT ELVAR DCT EXONA EXON9A LPPT/02 On approach to LPPT, I came along the EXON9A arrival, the ILS starting at PESEX. The ghost needles appeared very late, between PT422 and PESEX, where the ILS glide commences. So the auto tune happened, but a bit too late for comfort, basically seconds before the capturing the glide slope of the ILS. Had this happen on other occasions as well, when the ghost needles and the auto tune happened very late.

Oh boy ... I missed the radios no longer being set to "AUTO" tune after manually tuning in some VOR. Thanks for the heads-up though. Good video in the link. A lot of things to learn with this marvellous bird, our Challenger.

Hi, I've come across some occasions where the autotune of an ILS just would not happen. I had to disengage and make a visual approach last second. Among those where: EGGW ILS 07 (VECTORS) and LIRA ILS Y 15 (via LOCRI). Navigraph data, the charted ILS frequencies definitely work when tuned in manually. Capt nav sources were FMS1, preselected LOC1, and FO nav sources were FMS2, LOC2 preselected at all times (since I've read that not having this may cause issues with autotune). Autotune usually works for me, but then, there are these occasions when it just doesn't. What's the deal here? What might I have overlooked?

Thanks for providing this information. Much appreciated!

Cool. Thanks for the info! I wonder how many operators have that option.

Hi, after flying the Challenger for a while now, I keep wondering about the behavior of the flight director. The format does not matter, i. e. X-shape or V-shape is irrelevant, I tried with both. Scenario: On an approach (ILS for example), hand-flying, and drifting slightly of course laterally (like 1/4 dot). The deviation clearly shows on the rose CDI needle, but the FD does not command any course correction. According to the FD, I am perfectly on course. If I flew the FD only, I'd end up next to the runway! The FD commands a correction only when the deviation gets larger. I don't know if that is a limitation of screen resolution that indicating small corrections would not translate into a visible change or if this is how the system generally works. Any insights for me here?

Yep. Same with me. I usually try to squeeze in 2 legs after work and chores are done. More on weekends, other duties permitting. It's an addictive and time-consuming passion. But at least I can set things up and get going a lot faster than I could when I was still flying rw.

Hi, occasionally the SVS on the PFD drops out temporarily (MSG: SVS INOP), but comes back shortly. Happens during turbulence or turns, or sometimes even when just parked and going through the checklists. No big deal, but interesting nevertheless. A quirk/intricacy of the real system, or an issue in the sim?

That's obvious .We're talking interim/stop-gap here in case the X-Plane guys take too long to get the WX radar relevant API sorted. Not the final thing. It seems we don't even have an ETA for the respective APIs yet.

Nevermind. I found it by playing around. But is it documented somewhere?

Hi, due to excessive flying with the Hot Start Challenger, I had to replenish the engines with oil several times. Now, the replenishment tank is empty. How is the replenishment tank refilled?

Imho the Hot Start Challenger is a major pull factor for X-Plane. I hope that the X-Plane guys have weather radar relevant APIs high on their prio list. Depending on how long that is going to take, it might be worth into looking for a "non-perfect", cheap stop-gap solution, like at least getting a top-down weather view when the WXR button is used. As a first step, it might be better than having nothing at all, before we finally get the X-Plane APIs and then all the radar modes, tilt/gain and what not.

I tried that out. Doesn't work really well in my case. If I put 4 pax in the front 4 seats, 200lbs in the baggage compartment and load about 7.000-8.000lbs of fuel, this tool calculates a CG of 27% with a TO trim setting of 5.0 If I use that in the sim (and loading the pax/baggage stations via X-Plane according to the calculation made), I end up with a nose-heavy aircraft for takeoff that I can barely lift off the ground. Has someone tried that out, and finds the calculation to match the actual sim behavior?

I am happy to hear that. Really. One of the things that drove me away from MSFS.

Thanks for the explanation. Not certain if other simulators do this correctly, but it grabbed my attention in X-Plane more than in other sims.

Too bad. Weather radar is one of the very few really big things still missing in this fantastic simulation of the Challenger 650. I have no idea if it would be an option for X-Plane, but on other sim platforms there was a time when missing weather data was worked around by providing WX radar in conjunction with ActiveSky. I have it for X-Plane 12, and based on their map, they seem to know about precipitation (it's what I use as a kind of "workaround" weather radar). Is there any ETA for the required SDK functionality in X-Plane?

I see. So the overlay is supposed to show up at the right time. Thanks. I shall look closer at this. You guys have thought of everything

That's what I ended up doing, so as to have precise control over actual pax number, pax weights and cargo/baggage. Works fine. I just let the fuel truck refuel, so as to make sure that the tanks get filled in the right order and with the correct internal flow logic.

Ok. Thanks. Too bad. Might have helped prevent a sudden power surge or loss on ATS disconnect if one doesn't get the hardware throttle pos entirely right just by sight.

Hi, is it possible to bring up the "ghost throttles" on demand, e. g. before manually disconnecting the ATS, in order to sync the hardware throttles? Thanks

I thought as much