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
BiomeTracker.OnLoad can sometimes throw an exception, preventing any ScenarioModule after it from being initialized #258
Comments
I've seen the post and the user report that he has removed OPM before of this. So that should be the problem because, Tekto is a OPM planet. |
I got this when using the Base Construction pack and the outer planet mod. Upon reloading the save, without touching either, I got a similar exception and all my contract history was nuked. |
Correction: the tracking center is having a seizure. Seems I have to reinstall now. Sheesh. |
mmm well my Base Construction pack uses a parameter system to support OPM and other planet packs. This look for all the planets, then make a list, after that I put a lot of parameters for orbit using that list (20 planets max). I look only for the celestials bodies that have surface so I dont know why is throwing an exeption. |
The tracking center seemed unrelated, in hindsight:
|
The tracking center might be related - depends on whether the NRE is due to a bad ScenarioModule. Give me an hour or two and I should be able to get a fix done. And the way it is supposed to behave is that it should silently remove planets that are invalidated from uninstalling planet packs. At least, that's the theory. 😉 |
Okay, @skymarshal, give the pre-release dll here a shot. If the issue is due to the same issue as was reported originally, it should resolve it in your save. If not, then post the entire KSP.log and I'll take a closer look. |
Closing as fixed - will re-open if necessary. |
I'll test it in the morning. Thanks for the quick work! |
I've got a user that reported this one. The stack trace should be informative enough:
In this user's case, it prevents ScienceAlertProfileManager (and some of your own -- teehee!) from running due to reasons you already know
User's Post
User's Log
The text was updated successfully, but these errors were encountered: