CTD when using DIRECT-TO

[bpcw0001]

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)

Edited July 23, 2023 by bpcw0001

[Pils]

25 minutes ago, bpcw0001 said:

The crash log says

Please also attach full log file.

[bpcw0001]

Full log file attached.

Log_DIRECT_TO.txt

[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. 

[bpcw0001]

Hi,

I had some more of these crashes, now also when collapsing waypoints in a route in the FMC when under VNAV.

It seems that there is an issue under certain circumstances when

1. VNAV is active

2. Waypoints are skipped or deleted, as it happens in a DIRECT-TO, or by just removing/skipping them in the FMC. For the latter, I had a route segment with fixes A-B-C-D-E ahead of me, and I LSK'ed E to come right after A, so that the resulting route would be just A-E. This crashed under VNAV, but works just fine after I reloaded and did the same without VNAV enabled.

 

For now, I shall not use VNAV except when not planning to modify the route, and use V/S with the VNAV advisory only instead.

Edited August 21, 2023 by bpcw0001

[bpcw0001]

Well, my assumption about this CTD somehow being connected to using VNAV proved wrong.

I got the very same CTD with exactly the same backtrace and error message in a situation that did not involve VNAV usage.
Nevertheless, the crash seems to indicate some issue with altitude calculations, which is no surprise since the TOD and other data need to be recalculated on flight plan change.

I remember having deleted an altitude constraint at some fix in the arrival procedure before, which left the fix without any calculated altitude, just with a "---" displayed in the FMS where the altitude would be displayed otherwise.
Might that have upset the calculation?