Nazfib
commented
6 months ago Oh dear.
Apparently, something in Kopernicus triggers a bug in the Unity Engine, where it uses the external zlib library incorrectly. The original zlib library handled this, mostly by accident, correctly anyway. However, Fedora 40 (on which Bazzite Linux is based) has replaced zlib by zlib-ng, which crashes when it is mis-used in this way.
A fix is in the works, but it will take a while before that is released, then makes its way into Fedora, and then Bazzite.
Known workarounds include:
- Compiling your own zlib, and placing it in the game's library directory (https://github.com/Kopernicus/Kopernicus/issues/615#issuecomment-2042405147)
- Compiling a patched copy of
libMonoPosixHelper.so, one of the core components of Unity, and replacing the version included with the game (https://github.com/zlib-ng/zlib-ng/issues/1708#issuecomment-2044631491)
There's nothing the RP-1 team can do about this, I'm afraid.
References:
tuliom
Running a decently large pack, please advise me on the information needed to diagnose the root cause: Running Linux Bazzite (Latest), KSP 1.12.5, RP1 3.6.0
Game has been running fine up until most recent launch. When the booster stage hit the ground, the game froze. The previous launch, the game had a large lag spike just after explosion.
Repeated testing has shown the freeze/crash occurs between Tiny Tim solid motors hitting the ground and exploding, and a sepatron hitting the ground to explode. Same behaviour also occurs just before a fairing hits the ground to explode.
Nothing happens to the game if the parts are not destroyed.