Stuck on "loading part upgrades 1.12

[Starslinger999]

Just now, linuxgurugamer said:

Still, something is left over.  Just make a brand new install and proceed from there.  Make sure it works before you add any mods

Ill try that trick where I delete everything and verify and see if adding my modlist in slowly works

[linuxgurugamer]

3 minutes ago, Starslinger999 said:

Ill try that trick where I delete everything and verify and see if adding my modlist in slowly works

No, don't do that.  Make a new install, that way you know nothing is there in the wrong places

[Starslinger999]

1 minute ago, linuxgurugamer said:

No, don't do that.  Make a new install, that way you know nothing is there in the wrong places

Ill use ckan to make a new modpack with the same mods that should do it?

[linuxgurugamer]

Just now, Starslinger999 said:

Ill use ckan to make a new modpack with the same mods that should do it?

That should be ok, but test it first before you add the mods

[Starslinger999]

On 7/6/2021 at 3:47 PM, linuxgurugamer said:

That should be ok, but test it first before you add the mods

Managed to narrow it signifcantly mainly mods that require ToolbarController as a dependency in CKAN
  
(for refrence removing these managed to fix it)

[Ladak2009]

On 6/25/2021 at 9:30 PM, maddog59 said:

I had the same problem, and found that not only KIS, but also Surface Lights and Warp Plugin mods caused the same problem.  

I'm curious ... what happens if you have a ship in action and the mod that supplies some of it's parts (such as Surface Lights and Warp Plugin) is no longer present? I see the warning message when loading that particular game, but I've not had the courage to proceed. Does the ship disappear? Explode? Have a whole where the part was?

 

On 6/25/2021 at 2:38 PM, Lanzelet said:

Found out, it was the "Kerbal Inventory System (KIS)" Mod. Without it, Startup works fine.

A have same problem, and I deleted mod RSSDateTime for 1.2.0.0 and game run fine now :-)

[linuxgurugamer]

3 hours ago, Starslinger999 said:

Managed to narrow it signifcantly mainly mods that require ToolbarController as a dependency in CKAN
  
(for refrence removing these managed to fix it)

Given that there are thousands of players using those mods, I tend to doubt it's those.  These are among the most popular mods in use.

But it sounds like you are still working on removing mods, rather than starting fresh and adding them slowly, a few at a time.

[Starslinger999]

19 hours ago, linuxgurugamer said:

Given that there are thousands of players using those mods, I tend to doubt it's those.  These are among the most popular mods in use.

But it sounds like you are still working on removing mods, rather than starting fresh and adding them slowly, a few at a time.

I managed to fix it somehow by uninstalling and reinstalling stuff idk what I did lol but ye one of those mods was giving me problems lol

Edited July 8, 2021 by Starslinger999

[linuxgurugamer]

8 minutes ago, Starslinger999 said:

I managed to fix it somehow by uninstalling and reinstalling stuff idk what I did lol but ye one of those mods was giving me problems lol

Then something wasn't installed properly or had gotten corrupted.

Glad you got it figured out

[Starslinger999]

Just now, linuxgurugamer said:

Then something wasn't installed properly or had gotten corrupted.

Glad you got it figured out

Ye I can finally play JNSQ 1.12

[Tacombel]

I also had this problem and with advice from another thread solved it. The problem is with miniAVC.dll. Removing all copies (I had five) of it from your gamedata folder allows KSP to load correctly.

I have zerominiAVC installed.

[Zexion]

On 7/9/2021 at 6:13 AM, Tacombel said:

I also had this problem and with advice from another thread solved it. The problem is with miniAVC.dll. Removing all copies (I had five) of it from your gamedata folder allows KSP to load correctly.

I have zerominiAVC installed.

Had the same issue and doing this resolved it for me as well!

[pleroy]

(Principia author here.)

PSA: Since 1.12 the mods that have DLLs with an empty "File Version" will fail to load and the game will be stuck on "loading part upgrades".

Details: the 1.12 change log has the sentence:

Quote

When multiple versions of the same assembly are present, KSP now makes sure only the most recent one is loaded.

To do this, it seems that KSP parses the file versions of the DLLs it finds in GameData.  Unfortunately, if the file version is empty (which may be the default depending on details of how the DLLs were built) an exception gets raised during parsing.  Error handling is hard so this exception seems to bubble up to a place where it confuses the loading process and KSP gets stuck.

Advice to modders (including @linuxgurugamer who has been active on this thread): add file versions to all your DLLs.  The exact value probably doesn't matter as long as it can be parsed by the System.Version constructor.

[rangerrenze]

I currently have the same issue, already tried reinstalling all my mods. Was there a sole cause figured out that caused this with a fix? I tried the miniAVC trick and didn't work either.

[Tacombel]

1 hour ago, rangerrenze said:

I currently have the same issue, already tried reinstalling all my mods. Was there a sole cause figured out that caused this with a fix? I tried the miniAVC trick and didn't work either.

Are you completely sure that you found all of them? Or could be the difference is ZerominiAVC. Install it if you haven't.

I would try doing a copy of your current game directory and deleting all subdirectories in gamedata except Squad and Squadexpansión and see what happens.

[rangerrenze]

Apperently it worked on the 3d time reinstalling, 3d times is the charm

[Starforge Aerospace]

i got the same problem too. I use alot of mods and some are pretty old. Any help would be appreciated! 

[releansol]

 

On 7/11/2021 at 9:33 PM, pleroy said:

(Principia author here.)

PSA: Since 1.12 the mods that have DLLs with an empty "File Version" will fail to load and the game will be stuck on "loading part upgrades".

Details: the 1.12 change log has the sentence:

To do this, it seems that KSP parses the file versions of the DLLs it finds in GameData.  Unfortunately, if the file version is empty (which may be the default depending on details of how the DLLs were built) an exception gets raised during parsing.  Error handling is hard so this exception seems to bubble up to a place where it confuses the loading process and KSP gets stuck.

Advice to modders (including @linuxgurugamer who has been active on this thread): add file versions to all your DLLs.  The exact value probably doesn't matter as long as it can be parsed by the System.Version constructor.

indeed this miniavcs.dll s caused the problem.. thanks for pointing it out @pleroy and @Tacombel

On 7/9/2021 at 12:13 PM, Tacombel said:

I also had this problem and with advice from another thread solved it. The problem is with miniAVC.dll. Removing all copies (I had five) of it from your gamedata folder allows KSP to load correctly.

I have zerominiAVC installed.

[Rasip]

Removing KIS/KAS and patch manager from my gamedata lets the game boot up.

[Celuta]

On 7/11/2021 at 3:33 PM, pleroy said:

(Principia author here.)

PSA: Since 1.12 the mods that have DLLs with an empty "File Version" will fail to load and the game will be stuck on "loading part upgrades".

Details: the 1.12 change log has the sentence:

To do this, it seems that KSP parses the file versions of the DLLs it finds in GameData.  Unfortunately, if the file version is empty (which may be the default depending on details of how the DLLs were built) an exception gets raised during parsing.  Error handling is hard so this exception seems to bubble up to a place where it confuses the loading process and KSP gets stuck.

Advice to modders (including @linuxgurugamer who has been active on this thread): add file versions to all your DLLs.  The exact value probably doesn't matter as long as it can be parsed by the System.Version constructor.

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

[DarkLord76865]

On 6/30/2021 at 7:33 AM, theleg said:

For me, 

is causing the problem.

I can confirm this mod was also the only problem for me (and I'm using 20 mods). 

Thanks for saving me a ton of time. 

[linuxgurugamer]

2 hours ago, DarkLord76865 said:

I can confirm this mod was also the only problem for me (and I'm using 20 mods). 

Thanks for saving me a ton of time. 

Did you notice that that user @thelegnever followed instructions, and never posted the complete log? 

If you are having problems with a mod, please post the COMPLETE log file, not a snippet.   I seriously doubt that the mod itself  is a problem, but I can't help without the full log file.  And, if there IS a problem, that is what I need to fix it.

Edit:   Note that, according to the OP, this mod is in beta and is not available on CKAN for 1.12 so you may have installed an incompatible mod.  The last version of this mod available through CKAN is for  KSP 1.9. 

 

So without the log file, I have no way to know if you are even using my version of the mod

Edited July 26, 2021 by linuxgurugamer

[linuxgurugamer]

Following up on this, I've made some time and investigated.  Seems that there is a new feature in 1.12 which causes this bug if there isn't a "AssemblyFileVersion" setting in the file, and for this mod, there wasn't.

For all of you,  and especially @theleg I could have fixed this weeks ago IF the proper log files had been provided.  I don't have time to investigate every single report, especially when requested information is not provided.

I've also taken [x] Science out of beta and added it to CKAN for 1.12

A more general comment is that I have about 260 mods to support.  I'm slowly going through all of them to make these changes needed for 1.12, but it's going to take about 2 months to finish, assuming nothing interferes.  So if you come across a specific problem, please provide ALL the requested information, start off with the COMPLETE log file (Player.log is preferred).  Snippits are fine to point out something you feel might be significant, but many times the needed information is buried in the rest of the log file.

Edited July 26, 2021 by linuxgurugamer

[Unsoar]

Same problem here but I have deleted all outdated mods and it still is stuck on the screen, can someone help?

[Gotmachine]

@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

Edited August 14, 2021 by Gotmachine