[SOLVED] Massive UI bugs using Kopernicus

[Guest]

Pics: https://imgur.com/a/ALxrhTl

Reproduction steps:

Not exactly sure. At some point during almost all my missions to Kerbin orbit and beyond, the right-click menu would stop working. Right clicking on any part during flight would display an empty menu, and it would get stuck like that on the screen. Right clicking on any other part after this would do nothing. Various buttons on the app launcher to the right would also duplicate, including countless instances of MechJeb (MechJeb is not the cause for this. I removed it and the bug persisted), which would tank FPS harder the longer the bug went on. All buttons on the UI would also become completely unresponsive, including the ALT+F12 menu. I tried clearing input locks through a mod which didn't fix anything. Once this bug started, reloading a save would not work. Restarting the game would restore it to normal but loading back to the affected vessel would bring the bug back, effectively locking me out of that mission.  This would also bug out the settings menu, in which case Esc-ing out of the pause menu would freeze the game. The game is still "alive", but the game is still frozen as if it were in the pause menu, without the actual pause menu. The only mod removal that has had a good success rate has been Kopernicus, though I really don't want to let that go. Hopefully this is not something intrinsic to Kopernicus since I want to keep playing JNSQ. I can't seem to find many other instances of this bug being reported, so I'm really out of ideas.

KSP: 1.11.2 Windows 64-bit

Mods:

- [x] Science v5.26
- Click Through Blocker v0.1.10.15
- Toolbar Controller v0.1.9.4
- Atmosphere Autopilot v1.5.17rc1
- BetterSRBs v1.2.4
- CameraTools Continued v1.16.2
- Community Resource Pack v1.4.2
- Community Tech Tree v3.4.3
- Contract Configurator v1.30.5
- Custom Barn Kit v1.1.20
- Distant Object Enhancement v2.0.2.0
- Environmental Visual Enhancements v1.8.0.2
- Eve Optimized Engines v3.0.1
- Hide Empty Tech Tree Nodes v1.3.0
- JNSQ v0.9.0
- JX2 Antenna v2.0.5
- Kerbal Engineer v1.1.8.3
- Kopernicus v1.11.1-40
- MechJeb v2.12.0.0
- MechJeb and Engineer for All v1.3.0.6
- Memgraph v1.2.0
- Module Manager v4.1.4
- Near Future Aeronautics v2.1.0
- Near Future Construction v1.3.1
- Near Future Exploration v1.1.1
- Near Future Solar v1.3.1
- PlanetShine v0.2.6.2
- Rational Hydrodynamics v1.1
- RealPlume v4.0.7
- Reentry Particle Effect Renewed v1.9.1.1
- ReStock v1.3.1
- ReStock Plus v1.3.1
- SCANsat v20.4
- scatterer v0.0770
- Science-Full-Reward v4.1
- Sigma Suits v0.5.1
- Strategia v1.8.0
- Surface Mounted Lights v1.18
- SXT Continued v0.3.29.5
- Texture Replacer v4.4
- TUFX v1.0.2.3
- Universal Storage 2 v1.9.1.2
- Waypoint Manager v2.8.2.7

Log: https://www.mediafire.com/file/eywzuhi08yj54em/Player.log/file

Edited June 8, 2021 by Guest

[jimmymcgoochie]

It's almost certainly not Kopernicus causing this.

The first thing I saw when I opened your log file could be the key- you've added mods to the KSP instance that Steam controls. Don't do this, ever! Steam is notorious for meddling with stuff especially with mods in the mix. If it broke something inside Kopernicus then that could be the cause.

Create a modpack in CKAN for easy mod reinstallation and back up your save games somewhere outside of Steam's folders (desktop will do), then completely uninstall KSP through Steam, reinstall it, disable cloud syncing then verify the game files- this will check all the files to make sure nothing has been corrupted and fix anything that has. Once that's done, copy KSP out of steam/steamapps/common and put that somewhere else, then add that instance to CKAN and reinstall your mods using the modpack. Add save game, boot up KSP and see if the problem persists.

I see many, many exceptions in the log file but a few things stand out- Kopernicus Expansion causes a few early exceptions, double check you don't have that; and MiniAVC causes some errors too so try adding ZeroMiniAVC to disable that. You could also try uninstalling and reinstalling Kopernicus.

[Guest]

6 minutes ago, jimmymcgoochie said:

It's almost certainly not Kopernicus causing this.

The first thing I saw when I opened your log file could be the key- you've added mods to the KSP instance that Steam controls. Don't do this, ever! Steam is notorious for meddling with stuff especially with mods in the mix. If it broke something inside Kopernicus then that could be the cause.

Create a modpack in CKAN for easy mod reinstallation and back up your save games somewhere outside of Steam's folders (desktop will do), then completely uninstall KSP through Steam, reinstall it, disable cloud syncing then verify the game files- this will check all the files to make sure nothing has been corrupted and fix anything that has. Once that's done, copy KSP out of steam/steamapps/common and put that somewhere else, then add that instance to CKAN and reinstall your mods using the modpack. Add save game, boot up KSP and see if the problem persists.

I see many, many exceptions in the log file but a few things stand out- Kopernicus Expansion causes a few early exceptions, double check you don't have that; and MiniAVC causes some errors too so try adding ZeroMiniAVC to disable that. You could also try uninstalling and reinstalling Kopernicus.

Thanks for the response. Will try this and report back

[Guest]

1 hour ago, jimmymcgoochie said:

It's almost certainly not Kopernicus causing this.

The first thing I saw when I opened your log file could be the key- you've added mods to the KSP instance that Steam controls. Don't do this, ever! Steam is notorious for meddling with stuff especially with mods in the mix. If it broke something inside Kopernicus then that could be the cause.

Create a modpack in CKAN for easy mod reinstallation and back up your save games somewhere outside of Steam's folders (desktop will do), then completely uninstall KSP through Steam, reinstall it, disable cloud syncing then verify the game files- this will check all the files to make sure nothing has been corrupted and fix anything that has. Once that's done, copy KSP out of steam/steamapps/common and put that somewhere else, then add that instance to CKAN and reinstall your mods using the modpack. Add save game, boot up KSP and see if the problem persists.

I see many, many exceptions in the log file but a few things stand out- Kopernicus Expansion causes a few early exceptions, double check you don't have that; and MiniAVC causes some errors too so try adding ZeroMiniAVC to disable that. You could also try uninstalling and reinstalling Kopernicus.

Thank you! I've got all my original mods running and things seem normal for now. I'm pretty new to this CKAN thing, since I've been installing mods manually without much regard for the whole Steam issue for many years, so forgive me for my ignorance on that end

CKAN automatically added ZeroMiniAVC, so that might have helped. I also opted to not install Kopernicus Expansion for now. Maybe I'll install it again later if I feel confident in it again

Thanks once again

[Terminal Velocity]

On 6/8/2021 at 6:03 PM, jimmymcgoochie said:

you've added mods to the KSP instance that Steam controls. Don't do this, ever! Steam is notorious for meddling with stuff especially with mods in the mix. If it broke something inside Kopernicus then that could be the cause.

 

How to prevent and disable?

[Curveball Anders]

21 minutes ago, Rocketry101 said:

How to prevent and disable?

Leave the Steam controlled instance untouched.

Copy it to somewhere on your disk(s) outside Steams control.

Then add whatever mods you want and play on that copy.

When steam one is automagically updated so you can create a new copy, install modes and test if it works and if so move your save(s).

Once you're sure that the newest instance is ok, you can remove the previous copy (if low on disk).

[Terminal Velocity]

3 hours ago, Curveball Anders said:

Leave the Steam controlled instance untouched.

Copy it to somewhere on your disk(s) outside Steams control.

Then add whatever mods you want and play on that copy.

When steam one is automagically updated so you can create a new copy, install modes and test if it works and if so move your save(s).

Once you're sure that the newest instance is ok, you can remove the previous copy (if low on disk).

I created a copy on my desktop will report how that works 

[Terminal Velocity]

4 hours ago, Rocketry101 said:

I created a copy on my desktop will report how that works 

not work reinstalling...