KSP-ModularManagement / KSPe

Extensions and utilities for Kerbal Space Program
http://ksp.lisias.net/add-ons/KSPAPIExtensions
Other
11 stars 6 forks source link

SUPPORT page for CriticalComponentsAbsent Fatal Error #17

Open Lisias opened 3 years ago

Lisias commented 3 years ago

Currently, we have two main reasons for this error to appear:

Very old KSPe artefacts left forgotten in your disk

Screen Shot 2023-03-13 at 10 06 17

Remove all KSPe files as explained on INSTALL.md and reinstall.

Something else

Screen Shot 2021-09-24 at 21 34 34

Something else is happening in your rig. Yell for help here (mention me by using @Lisias , it will make me notice your post faster)

Lisias commented 2 years ago

Hi, @AlgoNeuland

this is popping up and i don't know why so i'd really like to know how to solve it.

You need to attach the KSP.log on a post here, so I can inspect it and check who is borking on you.

What's happening is that some other add'on have a missing or faulty dependency, and when this happens it triggers a bug on a thingy called Assembly Resolver/Loader inside KSP. Once this bug is triggered, everything start to bork too while loading dependencies (no matter the dependency is sound or not!).

By inspecting the KSP.log, we can check who is the first add'on borking due an System.Reflection.ReflectionTypeLoadException - by fixing (or removing) this guy, everything should be back to rails.

AptemCat commented 2 years ago

Hi, @Lisias I have the same problem. KSP.log attached. It might have some text in russian, sorry about that.

Lisias commented 2 years ago

Hi, @Lisias I have the same problem. KSP.log attached. It might have some text in russian, sorry about that.

Hi @AptemCat ! This one is on me. From your log:

[ERR 14:26:03.013] [KSPe] ERROR: Fatal Error CriticalComponentsAbsent was shown. e = [The type initializer for 'KSPe.IO.Hierarchy' threw an exception.]

[EXC 14:26:03.015] Win32Exception: Не удается найти указанный файл.

        KSPe.Multiplatform.LowLevelTools.Windows32.GetFinalPathName (System.String path) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.Multiplatform.FileSystem.Reparse_windows (System.String path) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.Multiplatform.FileSystem.ReparsePath (System.String path) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.IO.Directory.RealPath (System.String path) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.IO.Directory.Exists (System.String path) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.IO.Path.EnsureTrailingSeparatorOnDir (System.String path, System.Boolean blindlyAppend) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.IO.Path.Combine (System.String path1, System.String path2) (at <67792739c4584a1897b06d874e1e20e6>:0)
        KSPe.IO.Hierarchy..cctor () (at <67792739c4584a1897b06d874e1e20e6>:0)
        Rethrow as TypeInitializationException: The type initializer for 'KSPe.IO.Hierarchy' threw an exception.
        KSPe.Util.SystemTools+Assembly+Loader..ctor (System.String namespaceOverride, System.String[] subdirs) (at <67792739c4584a1897b06d874e1e20e6>:0
        KSPe.Startup.Awake () (at <67792739c4584a1897b06d874e1e20e6>:0)
        UnityEngine.DebugLogHandler:LogException(Exception, Object)
        KSPe.Util.Log.UnityLogDecorator:UnityEngine.ILogHandler.LogException(Exception, Object)
        UnityEngine.Debug:LogException(Exception)
        KSPe.Util.Log.UnityLogger:logException(String, Exception)
        KSPe.Util.Log.Logger:error(Exception, String, Object[])
        KSPe.Log:error(Exception, String, Object[])
        KSPe.FatalErrors.CriticalComponentsAbsent:Show(Exception)
        KSPe.Startup:Awake()
        UnityEngine.GameObject:AddComponent(Type)
        AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup)
        AddonLoader:StartAddons(Startup)
        <LoadObjects>d__90:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        <CreateDatabase>d__71:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        GameDatabase:StartLoad()
        <LoadSystems>d__11:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        LoadingScreen:Start()

This means that you have the same problem I'm dealing here. Right now I don't have a solution neither a WorkAround for you, I think you will need to rollback KSPe and anything that depends on it for now.

Let me know if you need assistance on the task.

AptemCat commented 2 years ago

@Lisias, I'm pretty sure I do need help with that. I was using curseforge to manage mods, then switched to CKAN when found out what it was, if you need this info. Also, I read your thread you linked. You were talking about the path limit. I have this registry setting on. Do I also need to send a screenshot of process monitor like pokemoncrusher?

Lisias commented 2 years ago

@AptemCat ,

@Lisias, I'm pretty sure I do need help with that. I was using curseforge to manage mods, then switched to CKAN when found out what it was, if you need this info. Also, I read your thread you linked. You were talking about the path limit. I have this registry setting on.

it ended up that it was anything but what I spend the last week researching. Things ended up being extremely simpler, I just screwed up two small and hidden things that by some reason known only by the Krakens, affected Windows but not MacOS and Linux...

Right now, I have a Release Candidate where I hope expect :) to have things thigh again!

Try this release https://github.com/net-lisias-ksp/KSPAPIExtensions/releases/tag/PRERELEASE%2F2.4.1.11 and let me know if it works for you!

AptemCat commented 2 years ago

@Lisias Ok, thanks, will try when I'll get to my pc

AptemCat commented 2 years ago

@Lisias Deleted all mods, installed your version of Module Manager and your kspapiextensions, doesnt work. I read the KSP.log, seems like something is looping.

AptemCat commented 2 years ago

Will maybe try reinstalling the entire KSP, it seems like it's cursed.

AptemCat commented 2 years ago

@Lisias Okay, which modulemanager should i download?

AptemCat commented 2 years ago

I downloaded the ModuleManager-4.2.1.2-122.zip last time

AptemCat commented 2 years ago

Completely new install, downloaded ModuleManager-4.2.1.2.zip, KSPAPIExtensions-2.4.1.11.zip, installed, doesn't work. KSP.log GameData Screenshot I just don't know what to do anymore :(

Lisias commented 2 years ago

@AptemCat

Completely new install, downloaded ModuleManager-4.2.1.2.zip, KSPAPIExtensions-2.4.1.11.zip, installed, doesn't work.

Sorry. I was sleepy and didn't fixed the thing properly, my bad. I will publish a new release in the next few hours - if you live on the timezone I think you live, you will have it working by your morning.

AptemCat commented 2 years ago

I live on UTC(GMT)+3, it's 18:36 now, thank you anyway.

Lisias commented 2 years ago

@AptemCat , I think this will work now : https://github.com/net-lisias-ksp/KSPAPIExtensions/releases/tag/RELEASE%2F2.4.1.12

No obvious errors on MacOS (it shares 99.9% of the code now, and the 0.1% they don't, they are now coded to behave more or less the same).

If you use Steam on Linux and/or use Proton, you may find some problems (see https://github.com/net-lisias-ksp/KSPAPIExtensions/issues/21 and https://github.com/net-lisias-ksp/KSPAPIExtensions/issues/25 for details).

let me know either way! Cheers!

Lisias commented 2 years ago

@AptemCat another user confirmed that 2.4.1.12 solved the problem for him. I think it will do the same for you!

Cheers!

AptemCat commented 2 years ago

@Lisias It finally worked! Thank you very much.

davidgilson commented 2 years ago

Hello, Posting my KSP.log as requested, I got the error window shown that brought me here!

Can you help? KSP.log

Lisias commented 2 years ago

Hi, @davidgilson

Hello, Posting my KSP.log as requested, I got the error window shown that brought me here!

Can you help? KSP.log

You mistakenly installed the MM/L release for KSP 1.2.2 on KSP 1.12.3 - so things started to blow up everywhere due that nasty bug on the Assembly Resolver on KSP >= 1.8.0 (on KSP 1.7.3 and previous, a better diagnosing message would had been shown instead, good thing I always log the error messages on KSP.log too!)

Stock folder: SquadExpansion

000_KSPe.dll
ModuleManager.122.version
ModuleManager.CHANGE_LOG.md
ModuleManager.dll
ModuleManager.LICENSE
ModuleManager.NOTICE
ModuleManager.README.md

<yada yada yada>

[LOG 17:42:40.664] [ModuleManager] INFO: "Houston, we have a Problem!" about running MM on unsuppoted KSP was displayed

You need to install the correct ModuleManager/L package on your rig, as explained on the Release Notes of the thingy:

Screen Shot 2022-05-14 at 01 01 37

Remove completely all ModuleManager.* files from your GameData and install the correct one from

https://github.com/net-lisias-ksp/ModuleManager/releases/tag/RELEASE%2F4.2.1.3

davidgilson commented 2 years ago

Thank you - I'm a busy parent and I skim read too much. Thank you for your help and patience :)

hendrack commented 2 years ago

Oh boy, getting the KSPe screen of death again :)

Not been able to play for almost a year now, I updated everything. I deleted every instance of old KSPe, MM, MM-watchdog in GameData

used those files:

KSPAPIExtensions-2.4.2.1.zip KSP-Recall-0.3.0.1.zip ModuleManager-4.2.2.4.zip ModuleManagerWatchDog-1.1.0.2.zip

KSP.log

As always, cheers :D

Lisias commented 2 years ago

Hi, @hendrack !

Found the problem:

[LOG 16:07:21.451] [AddonLoader]: Instantiating addon 'Startup' from assembly 'KSPe.UI'
[EXC 16:07:21.455] Exception: Magic number is wrong: 542
        System.TermInfoReader.ReadHeader (System.Byte[] buffer, System.Int32& position) (at <9577ac7a62ef43179789031239ba8798>:0)
        System.TermInfoReader..ctor (System.String term, System.String filename) (at <9577ac7a62ef43179789031239ba8798>:0)
        System.TermInfoDriver..ctor (System.String term) (at <9577ac7a62ef43179789031239ba8798>:0)
        System.ConsoleDriver.CreateTermInfoDriver (System.String term) (at <9577ac7a62ef43179789031239ba8798>:0)
        System.ConsoleDriver..cctor () (at <9577ac7a62ef43179789031239ba8798>:0)
        Rethrow as TypeInitializationException: The type initializer for 'System.ConsoleDriver' threw an exception.
        System.Console.SetupStreams (System.Text.Encoding inputEncoding, System.Text.Encoding outputEncoding) (at <9577ac7a62ef43179789031239ba8798>:0)
        System.Console..cctor () (at <9577ac7a62ef43179789031239ba8798>:0)
        Rethrow as TypeInitializationException: The type initializer for 'System.Console' threw an exception.
        System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)
        System.Diagnostics.Process.Start () (at <ef151b6abb5d474cb2c1cb8906a8b5a4>:0)
        (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start()
        KSPe.Multiplatform.Shell.command (System.String command, System.String commandline) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.Multiplatform.FileSystem.Reparse_readlink (System.String path) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.Multiplatform.FileSystem.reparsePath (System.String path) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.Multiplatform.FileSystem.ReparsePath (System.String path) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.IO.Directory.RealPath (System.String path) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.IO.Directory.Exists (System.String path) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.IO.Path.EnsureTrailingSeparatorOnDir (System.String path, System.Boolean blindlyAppend) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.IO.Path.Combine (System.String path1, System.String path2) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.IO.Hierarchy..cctor () (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        Rethrow as TypeInitializationException: The type initializer for 'KSPe.IO.Hierarchy' threw an exception.
        KSPe.Util.SystemTools+Assembly+Loader.buildSearchPath (System.String[] subdirs) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.Util.SystemTools+Assembly+Loader..ctor (System.String namespace, System.String effectivePath, System.String[] subdirs) (at <f7bcfe7ae2a04457bed409
38e9f35fb8>:0)
        KSPe.Util.SystemTools+Assembly+Loader..ctor (System.String namespace, System.String[] subdirs) (at <f7bcfe7ae2a04457bed40938e9f35fb8>:0)
        KSPe.UI.Startup.Awake () (at <d4a9782c6adb4125a08f3d95f632d8ad>:0)
        UnityEngine.DebugLogHandler:LogException(Exception, Object)
        KSPe.Util.Log.UnityLogDecorator:UnityEngine.ILogHandler.LogException(Exception, Object)
        UnityEngine.GameObject:AddComponent(Type)
        AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup)
        AddonLoader:StartAddons(Startup)
        <LoadObjects>d__90:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        <CreateDatabase>d__71:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        GameDatabase:StartLoad()
        <LoadSystems>d__11:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        LoadingScreen:Start()

I may be wrong, but it appears to be the same problem from the last time (but I don't really remember if it was an issue from you).

You need to set the TERM environment variable to xterm, of Mono will bork with that enigmatic message!

Edit your ~/.profile file and add this on it:

export TERM=xterm

From that point, Mono will behave and will stop screwing up KSPe. :)

Cheers!

hendrack commented 2 years ago

Oh damn, I was that and I forgot about that >< Thanks, again :D

TechnoCatza commented 1 year ago

So is there a main solution to the problem? Cause i got the problem too

TechnoCatza commented 1 year ago

Also scrolling trough here made me realise i have to send a log file, where do i find that?

Lisias commented 1 year ago

@TechnoCatza

So is there a main solution to the problem? Cause i got the problem too

No. The solution for you will depend on who is the trouble maker in your case - there're many different ways to get bitten by it.

Also scrolling trough here made me realise i have to send a log file, where do i find that?

The KSP.log can be found in your KSP's root directory, the place where the KSP.exe file is. You need to quit KSP to make sure the KSP.log is not truncated (TL;DR: KSP bufferizes the output to make things faster, and so it may not had been updated yet).

Zip the KSP.log and paste it here and I will check it.

TechnoCatza commented 1 year ago

I cant find it...

TechnoCatza commented 1 year ago

Wait i did just find it

TechnoCatza commented 1 year ago

KSP.log

Lisias commented 1 year ago

@TechnoCatza

Found it!

[ERR 12:04:41.330] AssemblyLoader: Exception loading 'EVAFirstPerson': System.Reflection.ReflectionTypeLoadException: Exception of type '
System.Reflection.ReflectionTypeLoadException' was thrown.
  at (wrapper managed-to-native) System.Reflection.Assembly.GetTypes(System.Reflection.Assembly,bool)
  at System.Reflection.Assembly.GetTypes () [0x00000] in <9577ac7a62ef43179789031239ba8798>:0
  at AssemblyLoader.LoadAssemblies () [0x000e6] in <0435390348b6470d8166bd1c53b4b100>:0

Additional information about this exception:

 System.IO.FileNotFoundException: Could not load file or assembly 'HullCamera, Version=1.0.5100.39113, Culture=neutral, PublicKeyToken=nu
ll' or one of its dependencies.
File name: 'HullCamera, Version=1.0.5100.39113, Culture=neutral, PublicKeyToken=null'

There's a nasty bug on KSP that it's lingering for years on a thingy called Assembly Loader/Resolver. When it fails to load a DLL by any reason (being a missing dependency, being a corruoped or too old Assembly, etc), everything that needs it starts to get borked by it - and TweakScale makes heavy use of that thing.

In your case, you installed a thingy called EVAFirstPerson, but this thingy needs HullCamera installed, and you forgot to install it.

By removing EVAFirstPerson or installing HullCamera, you should be fine!

Cheers!

TechnoCatza commented 1 year ago

I first tried adding HullCamera, that didnt work. Then i removed Hullcamera and EVAFirstPerson and it still didnt work.

KSP.log

Lisias commented 1 year ago

@TechnoCatza:

I first tried adding HullCamera, that didnt work. Then i removed Hullcamera and EVAFirstPerson and it still didnt work.

Now I'm worried. Let me see what's happening…

[EXC 13:26:50.537] DllNotFoundException: 000_KSPAPIExtensions's DLL search path does not exists!
        KSPe.Util.SystemTools+Assembly+Loader.buildSearchPath (System.String[] subdirs) (at <282fa02f3b5c456b8fb9451e25b57f0c>:0)
        KSPe.Util.SystemTools+Assembly+Loader..ctor (System.String namespace, System.String effectivePath, System.String[] subdirs) (at <282fa02
        KSPe.Util.SystemTools+Assembly+Loader..ctor (System.String namespace, System.String[] subdirs) (at <282fa02f3b5c456b8fb9451e25b57f0c>:0)
        KSPe.Startup.Awake () (at <282fa02f3b5c456b8fb9451e25b57f0c>:0)
        UnityEngine.DebugLogHandler:LogException(Exception, Object)
        KSPe.Util.Log.UnityLogDecorator:UnityEngine.ILogHandler.LogException(Exception, Object)
        UnityEngine.Debug:LogException(Exception)
        KSPe.Util.Log.UnityLogger:logException(String, Exception)
        KSPe.Util.Log.Logger:error(Exception, String, Object[])
        KSPe.Log:error(Exception, String, Object[])
        KSPe.FatalErrors.CriticalComponentsAbsent:Show(Exception)
        KSPe.Startup:Awake()
        UnityEngine.GameObject:AddComponent(Type)
        AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup)
        AddonLoader:StartAddons(Startup)
        <LoadObjects>d__90:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        <CreateDatabase>d__71:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        GameDatabase:StartLoad()
        <LoadSystems>d__11:MoveNext()
        UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator)
        LoadingScreen:Start()

Apparently, KSPe** is not properly installed. Did you installed it as specifiec by the INSTALL.md file?

**edit: typo fixed

TechnoCatza commented 1 year ago

Idk, I just installed it via Epic games and then launched it via curseforge for the mods

Lisias commented 1 year ago

Idk, I just installed it via Epic games and then launched it via curseforge for the mods

My bad, the "e" was omitted. I was meaning "KSPe" is not properly installed.

Humm… Wait… Found this in your system:

[WRN 13:26:48.585] Config in file 'C:\Program Files\Epic Games\KerbalSpaceProgram\English\GameData\BiscuitfishMiniguns\License.cfg' contains no data.

Please confirm to me the full pathname of the directory where KSP_x64.exe is!! My understanding is should be C:\Program Files\Epic Games\KerbalSpaceProgram\English\ but I need confirmation!!

TechnoCatza commented 1 year ago

Yes it is in C:/Programm Files/Epic Games/KerbalSpaceProgram/English/

TechnoCatza commented 1 year ago

I will check if i installed it correctly later, currently far away from my Computer

mineralwater0 commented 1 year ago

@Lisias hey, can you help me with this, i already delete all the mod before i post this but the text said "000_kspe's DLL search path does not exist" KSP.log

Lisias commented 1 year ago

@mineralwater0 hey, can you help me with this, i already delete all the mod before i post this but the text said "000_kspe's DLL search path does not exist"

You have a ModuleManager infestation on your GameData!

Please remove the following files:

And install the latest Module Manager (4.2.3, IIRC). No matter if the Forum one or my Fork, both wlll do and I will support you the same.

Very old Module Managers not only are old, but they are buggy as hell - and some of these bugs screw up KSP internally in a way that makes everybody relying on two thingies called Reflection and Assembly Loader/Resolver completely screwed up (and I use both extensively).

mineralwater0 commented 1 year ago

@Lisias bro, thank you very much for saving my ksp, but when i installed the module manager it first didnt work but after i install the KSPAPIE it works, thank you very much for saving my ksp

yeetriceman commented 1 year ago

Hello, every time I want to play KPS this message comes 'This is a fatal error from KSPe! KSPe got a fatal error ''000_KSPe's DDL search path does not exists!'' while trying to load the KSPe.KSP subsystem.' I have verified the files in steam and I downloaded it again but the game still does not work. I had just deleted all of my mods and downloaded some new mods in CurseForge, after i did that this message comes up. KSP.log

Lisias commented 1 year ago

Hi @yeetriceman

Hello, every time I want to play KPS this message comes 'This is a fatal error from KSPe! KSPe got a fatal error ''000_KSPe's DDL search path does not exists!'' while trying to load the KSPe.KSP subsystem.' I have verified the files in steam and I downloaded it again but the game still does not work. I had just deleted all of my mods and downloaded some new mods in CurseForge, after i did that this message comes up.

Well, apparently you didnt' installed KSPe correctly. I found no 000_KSPe directory in your GameData.

Additionally, I didn't found any add'on on your rig that would need it, so I'm unsure about the reasons you decided to install it.

Check the INSTALL instructions about how to install the thing (if you really need it!).

yeetriceman commented 1 year ago

I would guess that KSPe has something to do with the modulemanager. I had the modulemanager installed for a few months and it all worked fine, so I think that 1 of the mods I installed was just a bit broken or that CurseForge was just doing some very weird stuff. If all of this KSPe stuff is not important for running the game I will just delete it and all of the other files that are not stock. I don't know anything about coding and files so I thought that it was something very important missing. Thanks for helping!

Lisias commented 1 year ago

@yeetriceman that's the strange thing, I didn't found anything else that would be installed with that file. On CurseForge, the thing is part of a package called Modular Management, and absolutely none of the many files that package would install were found on your KSP.log.

In a way or another, since I didn't found anything that would need it, you can safely delete the 001_KSPe.dll file and call it da day!

Cheers!

yeetriceman commented 1 year ago

Thanks for helping!

WolfyBobbo18 commented 1 year ago

@Lisias hey, I just had something like this pop up on my screen, how do I fix that? here's my ksp logs KSP.log

Lisias commented 1 year ago

@WolfyBobbo18 ,

@Lisias hey, I just had something like this pop up on my screen, how do I fix that? here's my ksp logs KSP.log

The file 000_KSPe.dll is missing from your GameData. Download this file and extract 000_KSPe.dll into your GameData and it should fix the installation.

EDIT

Alternatively… Are you sure you need to install KSPe at first place? You are using (Forum) Module Manager, and currently none of my Official Add'Ons (other than my MM fork) are linked against it - so chances are that you will be better served by removing anything related to KSPe from your GameData instead of trying to fix it.

74oshua commented 1 year ago

@Lisias Using KSPe, I get this popup every time I try to reload the database in-game with alt-F11, here's a screenshot of the error: Screenshot (309)

Aside from this, the add-on runs fine. Trying to install it as a dependency for the Ubio Welding mod. Using KSPe 2.5.3.3, KSP version 1.12.5

74oshua commented 1 year ago

Log as well: KSP.log

Lisias commented 1 year ago

@Lisias Using KSPe, I get this popup every time I try to reload the database in-game with alt-F11, here's a screenshot of the error: Screenshot (309)

THAT was a new! By some reason, KSPe is trying to load the same DLL twice, what can mean 3 things:

  1. I borked something while trying to load it
  2. KSPe is somehow installed twice
  3. You got hit by a race condition on KSP where it mistakenly fires up and run the same Assembly twice.

I will check the KSP.log to see what I find.

Aside from this, the add-on runs fine. Trying to install it as a dependency for the Ubio Welding mod. Using KSPe 2.5.3.3, KSP version 1.12.5

From the possible problems, the less worst of them. But don't trust too much this KSP installation - the same way KSPe may be being instantiated twice, others thing also may be - and most add'on authors are not paranoid as I am, leading to weird things happening late on the game (as two parts being added to the craft instead of one, or parts being chained wrongly when ReRooting, etc)

Lisias commented 1 year ago

@74oshua

Log as well: KSP.log

Found the problem - you forgot to remove the directory GameData/KSPAPIExtensions - very, very way behind I was thinking that KSPe would be just a small appendix to KSPAPIExtensions, but later I realised it ended up being exactly the other way around! :)

Usually, the KSPe.InstallChecker would yell about, but there can be only one Modal Window at a time, and the second copy of KSPe trying to load (again) the Unity2019 specific code was triggered first.

Bluntly remove GameData/KSPAPIExtensions and I think you will be fine. If not, send me the new KSP.log and I will dig on it!

Cheers!

74oshua commented 1 year ago

@Lisias Just tried removing the directory and restarting, same issue. Here's the new log: KSP.log