SomeName

Short circuiting the DC BUS 2 via the failure menu results in a reproducible CTD. Clean / newly spawned airframe with just the APU started beforehand. Log.txt

Same error as as discussed on discord. Beta v1.7.1 Airport: EDDN Approach: ILS 28 Z Happens if you activate the approach again that you're currently on, before sequencing to the missed approach. And go to the LEGS page. CTD.mp4 Log.txt

It's a universal thing, not specific to any procedure. The example in the video was a hold over some random fix. Just pick any procedure that contains a hold with a speed restriction and you'll be able to reproduce it.

So do I. This isn't about what you should do, but what the correct behavior is.

Showed a maximum holding speed of 230 KT. But still should have maintained 180 KT because it's the lesser of the two.

Emmen's (LSME) ILS 22 via RONIX has a hold encoded into the approach. Arming exit of said hold, either automatically via the FMS or manually, results in a CTD. 2022-06-07 14:13:16 CL650[fmc_subsys_ap_ctl_vnav.c:1262]: assertion "leg != ((void *)0)" failed: Backtrace is: 0 00007FFFD85E4FD9 C:\WINDOWS\System32\KERNELBASE.dll+0000000000034FD9 () 1 00000000803D4971 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+00000000003E4971 (get_des_leg_dtg+121) 2 00000000803D797D E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+00000000003E797D (find_vnv_crz_des_alt_tgts+1a8d) 3 00000000803DA4FB E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+00000000003EA4FB (ap_ctl_update_vnav+1a2b) 4 00000000803C63EF E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+00000000003D63EF (ap_ctl_main+53f) 5 00000000803A1C84 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+00000000003B1C84 (fmc_main+1a4) 6 0000000080519913 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+0000000000529913 (runpool_worker+1223) 7 000000008051088F E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\Beta Challenger 650\plugins\systems\win_x64\systems.xpl+000000000052088F (_lacf_thread_start_routine+f) 8 00007FFFD9637034 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017034 () 9 00007FFFDAAC2651 C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000052651 () --=={This application has crashed!}==-- (Art controls are modified.)

The holding has a 180 KT speed restriction. The aircraft, however, accelerates past that when flying outbound of the holding fix. And then later on reduces to 180 KT again when turning inbound.

Sure thing. The one I've still got is from where I reproduced the error - that's why there's a IRS Debug align. Log.txt

Was simulating a dual engine fire at take-off. 2022-05-04 16:48:26 CL650[libfail.cc:298]: Failure /systems/fireprot/eng/1/zone/A/fire_non_ext transitioning from ARMED_ON_GEAR_UP to TRIG 2022-05-04 16:48:26 CL650[libfail.cc:298]: Failure /systems/fireprot/eng/1/zone/B/fire_non_ext transitioning from ARMED_ON_GEAR_UP to TRIG 2022-05-04 16:48:26 CL650[libfail.cc:298]: Failure /systems/fireprot/eng/2/zone/A/fire_non_ext transitioning from ARMED_ON_GEAR_UP to TRIG 2022-05-04 16:48:26 CL650[libfail.cc:298]: Failure /systems/fireprot/eng/2/zone/B/fire_non_ext transitioning from ARMED_ON_GEAR_UP to TRIG 2022-05-04 16:48:27 CL650[fo_actions.c:1340]: FO actions: gear up Left the engines running while I cycled to land. When both engines finally gave up and the APU generator took over, I hit the following assertion causing a CTD. 2022-05-04 16:52:31 CL650[fcc_fd_ctl.c:70]: assertion "((__builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (tgt), double), __fpclassify(tgt), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (tgt), float), __fpclassifyf(tgt), __builtin_choose_expr ( __builtin_types_compatible_p (__typeof__ (tgt), long double), __fpclassifyl(tgt), (__builtin_trap(),0)))) & 0x0100) == 0)" failed: Backtrace is: 0 00007FFFC9704F69 C:\WINDOWS\System32\KERNELBASE.dll+0000000000034F69 () 1 000000008037A9B5 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000038A9B5 (fcc_get_trk_or_hdg+2d5) 2 000000008037F486 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000038F486 (fcc_update_fd_tgt+896) 3 00000000803765B2 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000003865B2 (fcc_main+f22) 4 0000000080507937 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000517937 (runpool_worker+1207) 5 00000000804FFCBF E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000050FCBF (_lacf_thread_start_routine+f) 6 00007FFFCA837034 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017034 () 7 00007FFFCBC02651 C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000052651 () --=={This application has crashed!}==-- I tested if this was just a one off thing, but no, was able to reproduce the error.

Seems like this bug was never acknowledged - but is still valid as of 1.5r2. Trying to save "128.750/BREMEN RADAR" as a COM PRESET results in a CTD. 2022-05-01 14:26:42 CL650[labels.h:69]: assertion i < 8 failed (0x8 < 0x8) Backtrace is: 0 00007FFFC9704F69 C:\WINDOWS\System32\KERNELBASE.dll+0000000000034F69 () 1 00000000801F8443 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000208443 (do_preset_cmd+263) 2 00000000801F8E92 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000208E92 (com_cont_key_cb+f2) 3 00000000801E23D8 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000001F23D8 (cdu_push_key+208) 4 00000000801E359C E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+00000000001F359C (cdu6200_main+1fc) 5 0000000080507937 E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+0000000000517937 (runpool_worker+1207) 6 00000000804FFCBF E:\games\steam\steamapps\common\X-Plane 11\Aircraft\X-Aviation\CL650\plugins\systems\win_x64\systems.xpl+000000000050FCBF (_lacf_thread_start_routine+f) 7 00007FFFCA837034 C:\WINDOWS\System32\KERNEL32.DLL+0000000000017034 () 8 00007FFFCBC02651 C:\WINDOWS\SYSTEM32\ntdll.dll+0000000000052651 () 2022-05-01 14:26:44 CL650[fdr.c:465]: frame skipped 0-1 --=={This application has crashed!}==--

Expected behavior: The FCOM states: Observed behavior: Under the right condition the FMS seems to loose track of what page to show when pressing the MSG button. It is, for example, possible to get the FMS into a state where pressing the MSG button repeatedly cycles between the INDEX and PERF pages instead of showing the MESSAGES page. Steps to reproduce: I've recorded a small video that shows how to get into such a state.