daid

yeah, I should avoid using the word "Station" it means 3 different things in the EmptyEpsilon context :D

Odd, I've been running a lot of debian linux without issues. Any chance you could get a stacktrace with a debug build? (`cmake -CCMAKE_BUILD_TYPE=Debug` and `gdb EmptyEpsilon`)

I didn't notice that this was changed. But, I like the `object object:setImpulseSoundFile(string)` form the best, so the old method with return data info added to it.

Odd, this code should handle that for ships vs nebula: https://github.com/daid/EmptyEpsilon/blob/master/src/screenComponents/radarView.cpp#L653 Did notice it with black holes myself.

I've made it an options.ini setting, so you can set it during debugging. Maybe once we know some sensible values we can also set a different default.

20 is really low, few 1000 is more what you most likely want

Yes

Not firing callbacks during teardown makes the most sense. As the game could be in inconsistent state during teardown.

I think the ship data translations are also only applied on startup.

Not being able to provide information during scanning is intentional. A good science officer knows when there is time to scan and when to not scan. There is a practical...