Jump to content

Stuck on "loading part upgrades 1.12


Recommended Posts

58 minutes ago, Gotmachine said:

@linuxgurugamerNote that in addition to plugin assemblies having a mandatory AssemblyFileVersion attribute, the KSP 1.12 AssemblyLoader.FlagDuplicatedPlugins() method is completely borked  (and still not fixed in KSP 1.12.2).

Basically, having 2 mods that package the same dll  (for example miniAVC) will trigger that issue. There is no workaround (beside making sure all installed mods packaging the same dll use different file names, because ironically this piece of crap use the file name instead of something reliable like the AssemblyTitle attribute to check if two assemblies are the same)

See related Squad bugtracker issue : https://bugs.kerbalspaceprogram.com/issues/28036

I am aware, but for some reason I’ve seen multiple MiniAVC.dll files in an install with the same file version without any problem.

I saw this while working on fixing the ZeroMiniAVC mod, by adding a dummy KSP-AVC.dll, I had to change the version because it conflicted with an old version someone had installed.

‘The bug only happens when two DLLs have both the same name AND the same version, other than that, it is kind of ok.

Link to comment
Share on other sites

1 minute ago, linuxgurugamer said:

for some reason I’ve seen multiple MiniAVC.dll files in an install with the same file version without any problem.

The ArgumentOutOfRangeException doesn't always happen, in some cases the AssemblyLoader.FlagDuplicatedPlugins() method will just remove random assemblies from its internal list without further noticeable consequences.
It depends in which order the plugins are added to that list, itself dependent on the folder/file composition/naming inside the GameData folder.

Link to comment
Share on other sites

11 hours ago, Gotmachine said:

The ArgumentOutOfRangeException doesn't always happen, in some cases the AssemblyLoader.FlagDuplicatedPlugins() method will just remove random assemblies from its internal list without further noticeable consequences.
It depends in which order the plugins are added to that list, itself dependent on the folder/file composition/naming inside the GameData folder.

Right, but the only times I've seen it is when there are duplicated plugin DLLs with identical versions (using the AssemblyFileVersion)  When not duplicated, the FlagDuplicatedPlugins seems to not have issues.  Have you seen any issues where they weren't identical versions?

Link to comment
Share on other sites

Ran into this as well. Tried a clean install of KSP and it booted fine, so I know it's one of my mods. I'm having a hard time nailing down which one though, short of uninstalling them one by one; is there a way I can take the hex ID that player.log blames and convert that to a mod's name? I've tried doing searches but it's not particularly helpful.

My player.log file: https://easyupload.io/7g112o

I can also upload a .ckan of my mods if that will help.

Link to comment
Share on other sites

3 hours ago, delcera said:

I've tried doing searches but it's not particularly helpful.

Search you whole GameData folder using a wilcard search : "*.dll".
You will find at least two dlls with the same name. Rename them so they don't have the same name, and the issue should disappear.

Link to comment
Share on other sites

  • 2 weeks later...
On 7/24/2021 at 8:39 PM, Celuta said:

Principia doesn't work with 1.12.  It does the infinite Loading Part Upgrades thing.

I can second this. I play with a number of mods, but because I didn't want to go through the headache of finding out which had become incompatible with 1.12.2, I created a fresh install with just the squad folder and principia (Grothendieck) in GameData. I encountered this loading issue only when the principia folder was present (the stock game loaded just fine).

Link to comment
Share on other sites

I was having the same issue.

18 Hours of work and I finally figured it out. Libraries and dependencies.

Multiple mods I had shared the same dependences, so I ended up having multiple instances of them. For me the issue was TACLifeSupport. As for some odd reason, i had a TACLifeSupport folder with all of the dependences included and a separate ThunderAerospace folder. I remove the former and everything works. So here is what I found KSP is doing.

First of all it checks for duplicates. If duplicates are found, then KSP will look for the version associated with each of the duplicated files (it goes first to config files, but if nothing is found, it goes to DLL files. If both end up with nothing, the result is "null"), If the version number is existent then the one with the highest version number (in the order of xx.**.** , **.xx.** , **.**.xx) is loaded and the rest is ignored. If all duplicates have either the same or no version number, it produces a null result. 

When the result is "null", it causes a NullErrorException, which the ErrorHandler attempts to resolve by running the process again, this causes multiple ErrorHandler processes as the NULL result causes a new instance of the Error Handler. Which causes a loop.

I don't exactly know why or how it eventually loads but either; Until the ErrorHandlers all realise that the attempts have failed and they all request to ignore the mod, or Until the ErrorHandler realises that it has taken too long to long and ignores the mod.

When there are no duplicates found, the files are loaded, the version number is not checked.

 

Now I'll provide the logs and a zip file of my current (and fixed) gamedata folder Along with a second zip file of my (broken) gamedata folder (if the folders aren't there at first, please @ me so I can check that they are there). Because I might have misunderstood a few things or whatever and I may be wrong, but what I said above is what I believe is occurring based on how I resolved the issue and what the logs show.

 

Link to comment
Share on other sites

  • 2 weeks later...
  • 8 months later...
  • 2 months later...

At 24th August the problem is still there.

 

Basically the game will crash if and only if it has to load DLLs from mods. If it doesn't, it won't be stuck.

I've tried everything, even only 1 mod, even just a simple part pack...

Results: if there's no DLL to load it'll work fine, else it won't.

Therefore, the problem seems to be with DLLs.

 

For the last KSP boot I had this Gamedata folder:

-.png

And here's the corresponding log:

Player.log

 

I don't really know what to do, even if a lot of stuff has been said there.

Link to comment
Share on other sites

  • 5 months later...
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...