Bjoern K

Seems to work for me as well. Even if the FG session itself hangs (upon loading) and needs to be closed (which happened after the third or fourth repeated "launcher -> run session -> quit session -> launcher, etc." loop), the launcher reopens. Good work, James!

Still getting crashes. Aerostar 700 at BIKF. Multiple resets at the location were okay, but changing the airport to EDAH and then resetting crashed FG. P.S: Do you know how to pass that "handle SIG32 nostop" command at startup? Having to look it up and copy and paste it for each debugging session is highly annoying.

Still getting crashes. Aerostar 700 at BIKF. Multiple resets at the location were okay, but changing the airport to EDAH and then resetting

The primary "Linuxisms" I can think of is differing directory separators for paths and too strict handling of folder naming (as in capitalization). Or it's an OSG bug. I've got all FG files with me this week, so I can build it on my laptop to rule our graphics driver related issues (laptop: NVidia, desktop: AMD).

Alright then. Did my log files yield anything useful?

OS: Arch Linux SG HEAD: a49619fa6c23bf7ad8839de63d8454291cb29cf3 FG HEAD: 083d364f9c2e809716f4cceb634ed41b836ac725

The top of my "installed aircraft" list when using the normal launcher:

Aircraft Center: Missing default aircraft and custrom folders