Stuck at an intermission loading screen (JNSQ-Modded) [RESOLVED]

[Erokoth]

I use JNSQ. I couldn't load a save/create a save/access settings, since I would just get stuck at the loading screen and have to force quit.

Additional Notes: I couldn't close the B9PartSwitch warning message anymore. Plus out of ~4 mods that showed up in my last playthrough only TUFX shows up in the main menu sidebar. I did upgrade Kopernicus from 223 to 224, the problem probably originated from that.

Player.log

Any help is appreciated!

 

Edited March 25 by Erokoth

[Lisias]

I!m on mobile now, so I couldn't check the log.  But the most common cause for this problem is a faulty file in some @thumbs directory.

These files are auto-generated so it's safe to hunt and delete all directories (and contents) called @thumbs and see if it fixes the problem.

Worst case scenario, I'll check the log later when I'll be back to my computer, if someone else didn't yet.

Edited March 22 by Lisias
Hit "Save" too soon.

[Erokoth]

Just tried that, it doesn't seem to work unfortunately.

[Lisias]

1 hour ago, Erokoth said:

Just tried that, it doesn't seem to work unfortunately.

Worst case scenario kicking in. I'm checking your KSP.log and will edit this post with the results.

---- POST EDIT

I found this:

MiniAVC -> System.IO.IOException: Sharing violation on path C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\KerbinSide
  at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32
  at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode) [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
  at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMode)
  at MiniAVC.AddonSettings.Load (System.String rootPath) [0x0001b] in <32daf95419734fac8d1e416d1f8be6d5>:0
  at MiniAVC.AddonLibrary.ProcessAddonPopulation (System.Object state) [0x0006c] in <32daf95419734fac8d1e416d1f8be6d5>:0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

In the past, similar expcetions from MiniAVC were associated to collateral effects on KSP. I suggest to search & destroy all instances of MiniAVC.DLL in your GameData.

The trigger for your borkage is this one:

[ParallaxScatter]        - [Exception] Unable to get the value of minimumSubdivision
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Uploading Crash Report
[ModuleManager] Exception while running a post patch callback: System.ArgumentNullException: Value cannot be null.
Parameter name: key
  at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior
  at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
  at Grass.ScatterLoader.LoadScatterNodes () [0x00041] in <f8c4be58fd694d77865148b1dd7ab67c>:0
  at Grass.ScatterLoader.Begin () [0x00051] in <f8c4be58fd694d77865148b1dd7ab67c>:0
  at ModuleManager.PostPatchLoader+<Run>d__16.MoveNext () [0x0046b] in <15a1f1ead20a4e7995346c905233ca64>:0
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Apparently Parallax is failing in a catastrophic way. But this can be collateral effect from MiniAVC. Remove all MiniAVCs from your GameData and see if he problem goes away.

If not you will need to reach Parallax maintainers for help.

--- POST EDIT ---

Nope! Something is different, I found another "uploading crash report" on your log!!!

DragCubeSystem: Creating drag cubes for part 'bluedog.Mariner3.TV.Camera'
(Filename: C:\buildslave\unity\build\Runtime/Export/Debug/Debug.bindings.h Line: 35)

Uploading Crash Report
NullReferenceException: Object reference not set to an instance of an object
  at ModuleDeployablePart.AssumeDragCubePosition (System.String name) [0x00088] in <4b449f2841f84227adfaad3149c8fdba>:0
  at DragCubeSystem+<RenderDragCubes>d__34.MoveNext () [0x001de] in <4b449f2841f84227adfaad3149c8fdba>:0
  at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00026] in <12e76cd

There'e dozens of 'Uploading Crash Report' in your log,  this looks very fishy on this log. Can you send me, please, the KSP.log too?

Anyway, check if removing MiniAVC will fix the problem first.

Edited March 23 by Lisias
Diagnosing... OR NOT!

[Erokoth]

Here's my most recent KSP.log.
 

2 hours ago, Lisias said:

Anyway, check if removing MiniAVC will fix the problem first.

Sure I'll let you know how it goes.

-EDIT-
Nope.

Edited March 23 by Erokoth
Giving a conclusion

[Lisias]

4 hours ago, Erokoth said:

Sure I'll let you know how it goes.

-EDIT-
Nope.

Oh, well.. At least on KSP.log I have some visibility about when and how things happen. Player.log omits some pretty good information that are only available on KSP.log.

Anyway, this is what I found:

[EXC 14:00:32.594] MethodAccessException: Method `UnityEngine.Texture..ctor()' is inaccessible from method `TextureReplacerReplaced.Reflections.setReflectionType(
    TextureReplacerReplaced.Reflections.setReflectionType (TextureReplacerReplaced.Reflections+Type type) (at <80f1396dc3cf43fd933ce44b5c40e267>:0)
    TextureReplacerReplaced.Reflections.load () (at <80f1396dc3cf43fd933ce44b5c40e267>:0)
    TextureReplacerReplaced.TextureReplacerReplaced.Start () (at <80f1396dc3cf43fd933ce44b5c40e267>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
    UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object)

TextureReplacerReplaced will just not work, no matter what you do.  I don't think this caused your immediate problem, but it will cause some problems for sure - anyone in need to have it working will bork.

What appears to had really screwed you is:

[LOG 14:00:13.951] [HighLogic]: =========================== Scene Change : From LOADING to MAINMENU =====================
<....>
[ERR 14:00:40.986] Exception handling event onLevelWasLoadedGUIReady in class <>c:System.NullReferenceException: Object reference not set to an instance of an obj
  at Kopernicus.RuntimeUtility.StarLightSwitcher+<>c.<Start>b__2_1 (GameScenes scene) [0x00005] in <9e43fe11c1b0456a81732a16b276154c>:0
  at EventData`1[T].Fire (T data) [0x000b0] in <4b449f2841f84227adfaad3149c8fdba>:0

[EXC 14:00:40.986] NullReferenceException: Object reference not set to an instance of an object
    Kopernicus.RuntimeUtility.StarLightSwitcher+<>c.<Start>b__2_1 (GameScenes scene) (at <9e43fe11c1b0456a81732a16b276154c>:0)
    EventData`1[T].Fire (T data) (at <4b449f2841f84227adfaad3149c8fdba>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object)
    UnityEngine.Debug:LogException(Exception)
    EventData`1:Fire(GameScenes)
    <FireLoadedEventGUIReady>d__47:MoveNext()
    UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

I.e.,Kopernicus. Something is missing/broken in your rig related to Kopernicus.

I suggest to first remove TextureReplacerReplaced to see if anything improves (it's not working anyway). If your KSP finally reaches the Main Menu, then you need to reach TextureReplacerReplaced maintainers for further help. Apparently you installed and version (I think this one) instead of the current one.

[LOG 13:46:44.716] AssemblyLoader: KSPAssembly 'Texture Replacer Replaced' V0.5.0 
                                                                           ^^^^^^^--- HERE!!

If by removing TRR your problem is fixed, then all you need to do is to install the newest one and you will probably be fine.

Otherwise, you will probably need to remove Kopernicus to see if it's really the problem. If the problems goes away, then it's something related to Kopernicus for sure. Are you sure you installed the latest one?

If by removing Kopernicus, you are still screwed, then Kopernicus is innocent. Send me again a new KSP.log (remember to quit KSP before copying it, to prevent it from bring truncated) and will see who is borking the Scene Change event this time.

[Erokoth]

I removed TRR, no change.

I just uninstalled Kopernicus & KopernicusExpansion along with JNSQ and some mods related to it (JNSQ Kerbinside+JNSQ Visuals). Surprisingly there's no problem! I can close the warning message and create a new save.

I also did a manual reinstall of Tweakscale and MechJeb2 because Tweakscale showed a warning.

Definitely Kopernicus related. So what now? I can't just switch to stock planets, what about my save?!

Quote

Are you sure you installed the latest one?

And as for your question, I did update Kopernicus to the latest version (224) using CKAN.

[arbsoup]

I am going to suggest you try something entirely different. Parallax and Kopernicus are likely not at fault.

You can put everything back (hope you have backups!); try removing solely JNSQ_ParallaxScatters from your install. I noticed a bunch of questionable Parallax scatter patches in the log coming from it; this might have to do with how it keeps using @ParallaxScatters{} instead of ParallaxScatters{}, and similar problems are known. If this and this alone is enough to fix it, I may have advice for you on how to keep it.

Edited March 24 by arbsoup

[Erokoth]

7 hours ago, arbsoup said:

I am going to suggest you try something entirely different. Parallax and Kopernicus are likely not at fault.

You can put everything back (hope you have backups!); try removing solely JNSQ_ParallaxScatters from your install. I noticed a bunch of questionable Parallax scatter patches in the log coming from it; this might have to do with how it keeps using @ParallaxScatters{} instead of ParallaxScatters{}, and similar problems are known. If this and this alone is enough to fix it, I may have advice for you on how to keep it.

That worked...
So what now? Where do I get a working version? (particularly the latest :p)

Edited March 24 by Erokoth
Note

[Lisias]

7 hours ago, arbsoup said:

You can put everything back (hope you have backups!); try removing solely JNSQ_ParallaxScatters from your install. I noticed a bunch of questionable Parallax scatter patches in the log coming from it; 

What I find interesting is how it utterly broke Kopernicus.

A mistake on JNSQ's Parallax Suppor breaks Parallax that by some reason throw Kopernicus under the bus... The one that diagnosed this one surely burnt some midnight oil...

[arbsoup]

There seem to be two types of files in JNSQ_ParallaxScatters. The first is for JNSQ bodies, which duplicate stock bodies' default Parallax configs and make minor tweaks. The second is for the stock bodies, to tweak their scatters a bit, and they all begin like this:

@ParallaxScatters:HAS[#body[Dres]]:NEEDS[JNSQ]:AFTER[ParallaxStock]

Somehow, in your log, this patch is not just getting applied to nodes with body=Dres; it is getting applied to every ParallaxScatters node for both stock and JNSQ bodies. And so on down for every single stock body patch in JNSQ_ParallaxScatters, which sums to over 200 patches.

I was wrong. I don't know how to fix this.

The worst-case approach might be to make do without JNSQ_ParallaxScatters, wait until Parallax Continued comes out (next month?), and use the corresponding JNSQ patch for that (this one?), which will be better-supported and more-discussed at least in the immediate aftermath of the release. (Maybe not discussed here, though, you might want to get a Github account ready.)

Edited March 24 by arbsoup