SUPPORT page for CriticalComponentsAbsent Fatal Error #17

Lisias · 2021-09-24T23:40:23Z

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

Very old KSPe artefacts left forgotten in your disk

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

Something else

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 · 2022-02-07T06:00:25Z

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 · 2022-02-20T11:14:09Z

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

Lisias · 2022-02-21T00:56:53Z

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 · 2022-02-21T07:49:19Z

@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 · 2022-02-21T09:49:59Z

@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 · 2022-02-21T10:37:34Z

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

AptemCat · 2022-02-21T11:04:32Z

@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 · 2022-02-21T11:07:18Z

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

AptemCat · 2022-02-21T11:16:46Z

@Lisias
Okay, which modulemanager should i download?

AptemCat · 2022-02-21T11:17:12Z

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

AptemCat · 2022-02-21T11:24:25Z

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 · 2022-02-21T14:28:49Z

@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 · 2022-02-21T15:36:32Z

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

Lisias · 2022-02-21T21:07:32Z

@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 · 2022-02-21T23:45:01Z

@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 · 2022-02-22T04:17:47Z

@Lisias It finally worked! Thank you very much.

davidgilson · 2022-05-13T16:47:52Z

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

Can you help?
KSP.log

Lisias · 2022-05-14T04:04:10Z

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:

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 · 2022-05-16T11:04:03Z

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

hendrack · 2022-09-02T14:13:04Z

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 · 2022-09-02T14:44:24Z

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 · 2022-09-02T15:05:12Z

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

TechnoCatza · 2023-01-07T09:57:21Z

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

TechnoCatza · 2023-01-07T10:01:20Z

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

Lisias · 2023-01-07T10:33:45Z

@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 · 2023-01-07T11:02:47Z

I cant find it...

TechnoCatza · 2023-01-07T11:03:06Z

Wait i did just find it

Lisias · 2024-10-30T08:23:18Z

@AviationNerd1 , please send me the KSP.log so I can diagnose the problem.

AviationNerd1 · 2024-10-30T13:44:16Z

Here you go, I hope this helps.
KSP.log

Lisias · 2024-10-30T16:29:54Z

@AviationNerd1 can you please describe me what did you did on your rig?

I found a stray DLL, C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\001_KSPe.dll that shouldn't be there, since no other of its "companions" are present. This file should be there only when the 000_KSPe.dll one is present, as well the directory 000_KSPe.

Deleting that DLL will solve your problem, but I need to understand how it happened at first place!

TheBigMacNerd · 2024-12-02T08:23:19Z

Can any black magic computer science wizards help me with this issue?
KSP.log

TheBigMacNerd · 2024-12-02T08:24:44Z

nvm i had the same issue as aviationnerd1

Lisias · 2024-12-03T06:22:34Z

Hi, @TheBigMacNerd !

nvm i had the same issue as aviationnerd1

How that DLL ended up there? Can you help on this? It's should not be possible to have the 001_KSPe.dll present without the other artifacts I mentioned...

abuss108 · 2024-12-03T21:42:16Z

KSP.log
This is the first mod I've had issues with so I'm confused. All of my other games have mods of various kinds in them. So I really screwed something up.

Lisias · 2024-12-04T01:44:14Z

KSP.log This is the first mod I've had issues with so I'm confused. All of my other games have mods of various kinds in them. So I really screwed something up.

The mod is not causing issues, it's warning you about issues on your rig. Something is broken in your rig:

[LOG 15:38:01.429] [AddonLoader]: Instantiating addon '_BuildManager' from assembly '_BuildManager'
[EXC 15:38:01.434] NotSupportedException: The invoked member is not supported in a dynamic module.
    System.Reflection.Emit.AssemblyBuilder.get_Location () (at <9577ac7a62ef43179789031239ba8798>:0)
    _BuildManager._BuildManager+<>c__DisplayClass2_0.<logVersion>b__0 (System.Reflection.Assembly x) (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    System.Linq.Enumerable+WhereSelectArrayIterator`2[TSource,TResult].ToList () (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
    System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
    _BuildManager._BuildManager.logVersion () (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    _BuildManager._BuildManager.Awake () (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler: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()

Usually, a Integrity Check would solve this problem - not rarely, it's some file from the game that got silently corrupted on the SSD (this essentially not happens on HDDs).

However, I also found this:

[LOG 15:38:03.523] MiniAVC -> Executing: MiniAVC - 1.0.3.0

This old version of MiniAVC was known to really play havoc in the past. The best solution is to remove all MiniAVC.dll files from your rig.

Well, try what follows:

Find and delete all files named MiniAVC.dll from your game. Check if the problem goes away.
Do an Integrity Check, or reinstall the binaries from the original distribution package if the Store you use don't have his feature.

If after these steps, you still have problems, send me a new KSP.log and I will see what else is happening.

abuss108 · 2024-12-04T03:59:55Z

I've got no results...
KSP.log

Lisias · 2024-12-04T10:11:44Z

@abuss108 , yep. The problem is still there:

[LOG 21:59:15.599] [AddonLoader]: Instantiating addon '_BuildManager' from assembly '_BuildManager'
[EXC 21:59:15.604] NotSupportedException: The invoked member is not supported in a dynamic module.
    System.Reflection.Emit.AssemblyBuilder.get_Location () (at <9577ac7a62ef43179789031239ba8798>:0)
    _BuildManager._BuildManager+<>c__DisplayClass2_0.<logVersion>b__0 (System.Reflection.Assembly x) (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    System.Linq.Enumerable+WhereSelectArrayIterator`2[TSource,TResult].ToList () (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
    System.Linq.Enumerable.ToList[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <351e49e2a5bf4fd6beabb458ce2255f3>:0)
    _BuildManager._BuildManager.logVersion () (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    _BuildManager._BuildManager.Awake () (at <8496beb9e4bc45c181392fb16a92ddee>:0)
    UnityEngine.DebugLogHandler:LogException(Exception, Object)
    ModuleManager.UnityLogHandle.InterceptLogHandler: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()

This _BuildManager thing is from EVE, and in all the circumstances I found it borking this way was due something else borking on it, or due a corrupted rig. We ruled out corrupted rigs, so I kept digging and...

[LOG 21:59:15.346] Load(Assembly): Mods/EnvironmentalVisualEnhancements/Plugins/_BuildManager
<....>
[LOG 21:59:15.360] Load(Assembly): Mods/ModularManagement-2024.04.24.3-CurseForge/000_KSPe

Oukey, I think we had found the problem. :) Things are installed wrongly in your rig!

This is how your GameData should be looking:

I suggest to watch this video, it explains how to install mods in your rig: https://www.youtube.com/watch?v=1_0PNkIyHrU

abuss108 · 2024-12-04T20:32:27Z

I've got my 000_KSPe file set up the same as you, unable to find a 999 KSP Recall file. ModuleManager.dll won't accept being put into the modulemanager file, I get an error saying it must be in the gamedata folder. Current setup is attatched.
KSP.log

abuss108 · 2024-12-05T04:14:12Z

It also won't accept 666Watchdog being in the 000KSP folder, it gives me the module manager.dll error again.

Lisias · 2024-12-05T11:55:28Z

There's a rogue Module Manager in GameData/Airplanes Plus/ModuleManager.4.1.3 .

As a matter of fact, the whole AirplanePlus thingy is wrongly installed!

[LOG 14:27:27.219] Load(Audio): Airplanes Plus/AirplanePlus/Sounds/109_idle

Remove the Airplane Plus directory and reinstall AirplanePlus properly. It should look something like this: https://github.com/net-lisias-ksp/AirplanePlus/tree/master/GameData

You will need to install this: https://github.com/net-lisias-ksp/KSP-Recall/releases

Please read the INSTALL instructions bundled on mentioned packages.

abuss108 · 2024-12-05T21:20:48Z

Oh, oh, we've made progress. Now it launches fine and just says there's one warning while loading the game. No more popup warnings. Thank you so much for helping with this. This was not supposed to be this big of a problem. Really appreciate it!!

Lisias · 2024-12-05T21:39:05Z

@abuss108 , send me the KSP.log later, so we can get rid of that warning too. We are already near a perfect installment, why stop here? :)

Cheers!

abuss108 · 2024-12-05T21:43:39Z

I just relaunched it again looking for the warning. It's working well except I think I deleted my kerbal engineer redux earlier in the process. IT RUNS FINE!!! WOOHOO. I'll attach a log so we can find the warning.
KSP.log

Lisias · 2024-12-06T06:36:48Z

@abuss108

It's a typo on a config file from GAP:

[LOG 15:40:40.553] [ModuleManager] WARNING: unrecognized trailer: '.' on: ContractPacks/GAP/Flights/Airline-Flight-30/CONTRACT_TYPE:NEEDS[SquadExpansion/MakingHistory].

And, yeah, I found the problem.

https://github.com/inigmatus/GAP/blob/f2a6c6867045fb3001bc93465aa4b8cb62dc17b1/Flights/Airline-Flight-30.cfg#L8

I will file a bug report later.

Until there, don't worry. This warning is really harmless, it's just littering the log file!

Cheers!

Lisias · 2024-12-06T13:48:06Z

Pull request on GAP issued. Hopefully next release the warning will be no more!

inigmatus/GAP#219

BeanMan1273 · 2024-12-07T14:49:09Z

what do you need to help me fix this error?

BeanMan1273 · 2024-12-07T15:22:36Z

what do you need to help me fix this error?

figured it out on my own, disregard

Lisias · 2025-01-06T17:09:00Z

Hi, @6FallenAngel666 !

There's a rogue 001_KSPe.dll file in your GameData. I'm puzzled, because it's plain impossible to have this file there without having the companion, 000_KSPe.dll.

How did you get this file there?

In a way or another, please delete GameData/001_KSPe.dll. I don't have the slightest idea how this file ended there, but by removing it, the problem will be gone.

MEMEKAISER · 2025-01-27T02:45:40Z

Hello again! decided to start fresh and uninstall all mods and got this.

KSP.log

Lisias · 2025-01-27T03:49:04Z

Hi, @MEMEKAISER

Hello again! decided to start fresh and uninstall all mods and got this.

KSP.log

You have a rogue 001_KSPe.dll in your GameData!

I don't have the slightest idea about how it was end there, because 000_KSPe.dll is missing and it should plain impossible to have the 001 and not the 000 there.

You also don't have anything that uses it, so I'm at lost about how it ended up there...

Can you, please, explain how this file ended there? What had you installed after the last time you ran KSP with success?

MEMEKAISER · 2025-01-27T14:16:27Z

@Lisias I hadn't installed any mods after the last time I ran it fine I only uninstalled all of them yesterday

Lisias · 2025-01-27T14:43:39Z

@MEMEKAISER

Thank you for the information! It strongly suggests that I need to inject a "kill switch" on 001_KSPe.dll so.

MEMEKAISER · 2025-01-27T14:53:45Z

What does that do? @Lisias

Lisias · 2025-01-27T15:11:13Z

What does that do? @Lisias

It's a toolbox of common routines that makes programming KSP easier, so all my add'ons can share these features. WIth the added benefit that if a bug is found, fixing on KSPe will have the bug fixed on all my add'ons at the same time without hassle to the user.

But it only "works" for my add'ons. It's useless for add'ons that don't use it.

MEMEKAISER · 2025-01-27T15:18:35Z

okay @Lisias what do I need to do?

Lisias · 2025-01-27T15:26:59Z

@MEMEKAISER

Just delete the 001_KSPe.dll . There's nothing installed in your rig that needs it.

I plain forgot to tell you that, sorry.

MEMEKAISER · 2025-01-27T15:31:21Z

Thanks @Lisias it worked

Lisias added the support support (no bug) label Sep 24, 2021

Lisias self-assigned this Sep 24, 2021

Lisias changed the title ~~SUPPORT page for CriticalComponentsAbsent~~ SUPPORT page for CriticalComponentsAbsent Fatal Error Sep 24, 2021

SUPPORT page for CriticalComponentsAbsent Fatal Error #17

SUPPORT page for CriticalComponentsAbsent Fatal Error #17

Comments

Lisias commented Sep 24, 2021 • edited Loading

Very old KSPe artefacts left forgotten in your disk

Something else

Lisias commented Feb 7, 2022 • edited Loading

AptemCat commented Feb 20, 2022 • edited Loading

Lisias commented Feb 21, 2022

AptemCat commented Feb 21, 2022 • edited Loading

Lisias commented Feb 21, 2022

AptemCat commented Feb 21, 2022

AptemCat commented Feb 21, 2022

AptemCat commented Feb 21, 2022

AptemCat commented Feb 21, 2022

AptemCat commented Feb 21, 2022

AptemCat commented Feb 21, 2022

Lisias commented Feb 21, 2022

AptemCat commented Feb 21, 2022 • edited Loading

Lisias commented Feb 21, 2022

Lisias commented Feb 21, 2022

AptemCat commented Feb 22, 2022

davidgilson commented May 13, 2022

Lisias commented May 14, 2022 • edited Loading

davidgilson commented May 16, 2022

hendrack commented Sep 2, 2022 • edited Loading

Lisias commented Sep 2, 2022

hendrack commented Sep 2, 2022

TechnoCatza commented Jan 7, 2023

TechnoCatza commented Jan 7, 2023

Lisias commented Jan 7, 2023

TechnoCatza commented Jan 7, 2023

TechnoCatza commented Jan 7, 2023

Lisias commented Oct 30, 2024

AviationNerd1 commented Oct 30, 2024

Lisias commented Oct 30, 2024 • edited Loading

TheBigMacNerd commented Dec 2, 2024

TheBigMacNerd commented Dec 2, 2024

Lisias commented Dec 3, 2024

abuss108 commented Dec 3, 2024

Lisias commented Dec 4, 2024

abuss108 commented Dec 4, 2024

Lisias commented Dec 4, 2024 • edited Loading

abuss108 commented Dec 4, 2024

abuss108 commented Dec 5, 2024

Lisias commented Dec 5, 2024

abuss108 commented Dec 5, 2024

Lisias commented Dec 5, 2024

abuss108 commented Dec 5, 2024 • edited Loading

Lisias commented Dec 6, 2024

Lisias commented Dec 6, 2024

BeanMan1273 commented Dec 7, 2024

BeanMan1273 commented Dec 7, 2024

Lisias commented Jan 6, 2025

MEMEKAISER commented Jan 27, 2025

Lisias commented Jan 27, 2025

MEMEKAISER commented Jan 27, 2025

Lisias commented Jan 27, 2025

MEMEKAISER commented Jan 27, 2025

Lisias commented Jan 27, 2025

MEMEKAISER commented Jan 27, 2025

Lisias commented Jan 27, 2025

MEMEKAISER commented Jan 27, 2025

Lisias commented Sep 24, 2021 •

edited

Loading

Lisias commented Feb 7, 2022 •

edited

Loading

AptemCat commented Feb 20, 2022 •

edited

Loading

AptemCat commented Feb 21, 2022 •

edited

Loading

AptemCat commented Feb 21, 2022 •

edited

Loading

Lisias commented May 14, 2022 •

edited

Loading

hendrack commented Sep 2, 2022 •

edited

Loading

Lisias commented Oct 30, 2024 •

edited

Loading

Lisias commented Dec 4, 2024 •

edited

Loading

abuss108 commented Dec 5, 2024 •

edited

Loading