There is not. What you do is:
1. Start a flight in career mode
2. Create a new airframe
3. Run through the checklists until "all check lists done and verified and systems armed and ready for a flight"
4. Save the state through the airframe manager window
Then, next time you want to start "on runway threshold" you would:
1. Start a flight in career mode
2. Select the aforementioned airframe and saved state from the airframe manager, unchecking the "restore position" checkbox
3. Fly!
Any future questions please use the appropriate support forum: https://forums.x-pilot.com/forums/forum/266-challenger-650/
You could analyse the FDR files in \Output\CL650\FDR after every flight to build a log. Or use X-Plane's built-in logbook. Or, better, use an external flight tracker like Volanta.
https://discord.gg/tCver5En
You can try deleting the CL650 directory in Output. This’ll remove all airframes and settings. (However this doesn’t happen when uninstalling so not sure what’s happening there.)
You seem to be using the 2D panel display feature of XP. I recommend against this, this is not the intended use of the pop ups. Each secondary display should be set to Unused in XP graphics settings, and then each popup turned into an external window for placement by the default OS window manager (or some third party tool such as Sizer4 on Windows).
If you want to start over create a new airframe. Every airframe will restore its last state by default, it’s persistent. If you want it to be in a different state you have to put the plane in that state and save it for later use.
The key is to get at least the Max variant, with the most GPU cores available, and 24 GB of unified memory if possible. Anything less will likely struggle to get good X-Plane performance.
Network sync of aircraft state will never work properly for addon aircraft. I don’t know about your specific setup/issue, but TBM most likely needs to only be run once on the main computer with the controls and avionics displays.
Last backtrace isn’t similar, points more at the sim itself, which would require reporting to LR. However as you have many plugins you’ll need to remove all third party plugins except Gizmo64 in order to test on a “clean” system.
The SAM plugin is highly likely to crash X-Plane. This will need to be removed before we can troubleshoot reliably. There is an alternative available as SAM is no longer supported by its developer. https://forums.x-plane.org/index.php?/files/file/90865-opensam-an-open-source-replacement-for-sam/
Ah ok. If using Xsaitekpanels, or similar interface, plugin I suggest removing all the default functions, if they’re still in place.
Can be in basic function, there’s commands for all the FCP functions.