-
Notifications
You must be signed in to change notification settings - Fork 114
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
New kopernicus + OPM fails to load (1.4.5-1) #300
Comments
Seems to be sigma binary related, although there are no errors related to that in the log. |
seeing this is a new release of kopernicus and both OPM and SB have not been updated yet I would not be surprised if one or both mods have some issue working with the new kopernicus when you say it seems to be sigma related, do you mean OPM loads fine when SB is not installed? |
Removing only the SB mod makes the scary error message go away. I have ~60 mods. |
yeah, it's probably due the fact that SB is not designed to work with this version of Kopernicus you can either wait for a new SB release or just drop SB for the time being (should not affect your game much to remove SB as long as everything else work properly) |
Thank you. Closing issue. |
Small note, this combination produced duplicates for karen and karen-orbit in the config, triggering an IOException in Kopernicus (multiple bodies, same name, see #302). Thus the scary warning and the OPM planets not loading. The pull request makes this config work as is on my machine with KSP1.4.5, without a newer version of SB. Haven't travelled to karen in-game but it seems to be there and the log indicates [LOG 00:10:18.986] [SigmaLog]: Binary System Completed |
There should be no duplicates using sb, |
logs-Kopernicus.zip
KSP-log.zip
ModuleManager-configcache.zip
Hi, getting a scary message not to load my save and lots of exceptions in the log. Following instructions, here's the information.
BTW thanks for the update mid-summer. Now if we can get it to work with OPM it'd be great.
The text was updated successfully, but these errors were encountered: