@azieba I guess any multisystem contains a root frame without a physical body ( BodyType::TYPE_GRAVPOINT).

P.S. Sorry, hit the button by accident.

I have a 20230203-level savegame that when I hyperspace to Sirius (1, 0, -1), a multi-star system:

• 20230203 release: works fine
• 20230213 master b4894e6: Crashes to desktop upon arriving at Sirius (A or B)
• 20230213 master b4894e6 + PR Fix autopilot crash, when no mass in frame of reference #5551: works fine

Environment:
Windows 10 Enterprise 22H2
Compilations performed using Visual Studio 2019 16.11.24 using CMake instructions and x64-Release configuration

• 20230213 master b4894e6 + PR Fix autopilot crash, when no mass in frame of reference #5551: works fine

So I guess we have an independent verification. Thank you!

You're welcome 😄

I am still getting occasional crashes to desktop with this PR applied, typically when autopilot is engaged inbound to a starport - i.e. not immediately upon arriving at the system as previously described. This can occur in single-star systems also, e.g. my last occurrence was returning to Los Angeles, Sol (journey from arrival point to starport about 75% complete).

I'm not sure but the CTD could be occurring when the frame of reference changes..?

I'd like to supply a backtrace / call stack, but I cannot currently compile a debug version (issue #5545).

I'd like to supply a backtrace / call stack, but I cannot currently compile a debug version (issue #5545).

Debug versions have asserts active so they crash much more often even though release works fine. If such assert is in a way I comment it out to proceed.
EDIT: This is not an assert issue.
Save file would be actually more useful if you have one.
EDIT2: I could not reproduce with the journey to Los Angeles.

Apologies on waiting so long to merge this PR - it slipped my mind that this was already in-progress and waiting on review/merge.