-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CTD when installed together with Blueshift #3188
Comments
These are not the logs that we need, please read https://github.com/mockingbirdnest/Principia/wiki/Installing,-reporting-bugs,-and-frequently-asked-questions#reporting-bugs. |
The glog files. But both AppData Crashes folders are empty. Anything extra I need to do to get them to populate? |
An asteroid is being ill-behaved. I suspect this has something to do with the existence of code in Blueshift that messes with asteroid generation: https://github.com/Angel-125/Blueshift/blob/master/Source/Blueshift/SpaceAnomaly/WBICustomAsteroid.cs. In any case there is no chance of Blueshift working with Principia: it is an FTL mod, which means it operates by modifying orbits (or positions directly) without applying forces, which will immediately be undone by Principia. See https://github.com/mockingbirdnest/Principia/wiki/Installing,-reporting-bugs,-and-frequently-asked-questions#compatibility-with-other-mods. Closing this as it appear to be a compatibility issue with a mod that is incompatible by design for other reasons anyway. |
It's fair to decide not to support FTL mods, even if it's unfortunate, but it shouldn't cause a CTD. That is a poor user experience. If it's not fixable then I would suggest to at least add Blueshift to the list of known incompatible mods in the README with a warning about potential crashes. |
The CTD is not due to Blueshift being an FTL mod, it is due to Blueshift violating invariants that we expect from KSP. Violations of invariants result in an immediate crash, because otherwise they would instead result in broader save corruption and hard-to-diagnose bugs. This would be a bug that should be raised with Blueshift if Blueshift were compatible; it just happens that it isn’t, so there is no point in doing so. As for listing incompatibilities, this falls into the category
documented in the FAQ. To quote the next paragraph,
(to wit, we had never heard about Blueshift before this issue). |
Note that there is indeed a space anomaly, and I suspect that it is the part that's causing trouble:
This can be found here: |
KSP immediately crashes to desktop upon starting a new game when only Module Manager, Principia and Blueshift mods are installed.
Reproduction steps (Windows 10):
Install clean stock KSP 1.12.2 and both DLCs.
Install Module Manager version 4.2.1
Install Blueshift version 1.6.2
Install Principia Hadamard with October UI fixes from Google drive link in README.md
Start a new sandbox game with default settings.
I originally thought this may be related to how Blueshift spawns space anomalies (they are functionally similar to asteroids) and this may still be the case, but in my limited testing this issue happened even when space anomaly spawning was turned off in new game difficulty settings.
KSP log doesn't show anything interesting but Principia's stderr.log may hold a clue as it reports a failure from the Euler solver (both logs attached).
KSP.log
stderr.log
The text was updated successfully, but these errors were encountered: