CL650 CTD when restoring a saved situation

[cwjohan]

With version 1.6.1 and a new airframe, restoring a saved state in the Airframe Manager, I get a crash to desktop very early on after the restore.

The saved state was a ready to taxi situation at KDEN created from version 1.6.1 (not an old version).  I start up at KDEN and fix a few restore errors (like GEN1 OFF).  Within 1 minute, it crashes. In one case, the crash was within the first three seconds (let's say instantaneous). All I'm doing is looking around the cockpit for anything else that needs fixing to really be ready to taxi.

In the Airframe Manager:
1.) I click the saved state name (KDEN-KASE taxi)
2.) I leave "Restore Position and Trajectory" ticked
3.) I click ">>>>> FLY! <<<<<"
4.) I click ">> Confirm? <<"

The second attachment below (the instantaneous crash) contains a backtrace, which ought to be helpful.

Log_ctd_2022_06_29_a.txt Log_ctd_2022_06_29_b.txt

[Pils]

One log doesn’t really identify the cause, the other says it was SAM that crashed.

Edited June 30, 2022 by Pils

[richjb]

On 6/29/2022 at 7:43 PM, cwjohan said:

With version 1.6.1 and a new airframe, restoring a saved state in the Airframe Manager, I get a crash to desktop very early on after the restore.

The saved state was a ready to taxi situation at KDEN created from version 1.6.1 (not an old version).  I start up at KDEN and fix a few restore errors (like GEN1 OFF).  Within 1 minute, it crashes. In one case, the crash was within the first three seconds (let's say instantaneous). All I'm doing is looking around the cockpit for anything else that needs fixing to really be ready to taxi.

In the Airframe Manager:
1.) I click the saved state name (KDEN-KASE taxi)
2.) I leave "Restore Position and Trajectory" ticked
3.) I click ">>>>> FLY! <<<<<"
4.) I click ">> Confirm? <<"

The second attachment below (the instantaneous crash) contains a backtrace, which ought to be helpful.

Log_ctd_2022_06_29_a.txt 266.68 kB · 1 download Log_ctd_2022_06_29_b.txt 1.37 MB · 1 download

I have had the same issue, same flight DEN to ASE.  I also had it on a DEN EGE run.  It was always the memory error message, access violation as explained here:

Access Violation C0000005 | Microsoft Docs

Last night, I did a flight from MRY to STS.  No issues.

Each of these flights as started with a saved configuration file where all the items prior to taxi were completed and the TAXI checklist was ready to begin.  I did have change the FMS location to the current location and re-do the flight plan, performance, etc. 

Not sure if this helps, but you were not alone...

Rich Boll