[1.12x] RSMP (formally SWE)

[Neon_Twigman]

19 hours ago, Krazy1 said:

I'm not the expert here but I think you have the right dependencies installed. You exited the game after your ship crashed. It's a good practice to exit KSP entirely before uploading a log. There are a couple exceptions right at the end but that doesn't tell me much. Only guess is it might have some conflict with Deployable Engines or Eve Engines. I haven't used those before. 

If I recall, deployable engines is either a dependency or outright comes with Cryoengines. Eve Engines shouldn't do anything, but i guess i can try putting taking it out and see if that helps. Not like I'm good enough at the game yet to have a use for them. That said, my best guess, so far, is that for some reason the audio files are trying to load before Module Manager. That doesn't make much sense to me, but. It also says unnamed node, so that may have something do do with it. I could always reinstall it and see if that fixes the issue I suppose.

[Legolas5533]

I've been having a problem, solid motor plumes work well, but the smoke trail is gone.

[Quick_Nils]

Why are my SRB plumes transparent? I used this mod before and it worked fine then. Yes Stock SRBs have the same issue. Im using restock (thus waterfall restock) but since both stock and supported mods (in this case BDB) have the issue i dont think thats it. I checked every dependency. What could cause this?

[JonnyOThan]

15 hours ago, Quick_Nils said:

Why are my SRB plumes transparent? I used this mod before and it worked fine then. Yes Stock SRBs have the same issue. Im using restock (thus waterfall restock) but since both stock and supported mods (in this case BDB) have the issue i dont think thats it. I checked every dependency. What could cause this?

Do you have tufx and shabby?

[Quick_Nils]

38 minutes ago, JonnyOThan said:

Do you have tufx and shabby?

yes. I can try it without shabby. It worked with TUFX before. Will shaddy still work without shabby? (better looking habtech solar panels and parachutes)

[JonnyOThan]

1 hour ago, Quick_Nils said:

yes. I can try it without shabby. It worked with TUFX before. Will shaddy still work without shabby? (better looking habtech solar panels and parachutes)

No, I would have expected having tufx without shabby might have caused something like this.

[Quick_Nils]

39 minutes ago, JonnyOThan said:

No, I would have expected having tufx without shabby might have caused something like this.

Thats weird.  Heres my modlist. Any idea what could cause this problem?

yes, i like to mod any of my games till my pc yells at me

[Quick_Nils]

4 hours ago, JonnyOThan said:

No, I would have expected having tufx without shabby might have caused something like this.

I deinstalled everything thats not needed and its still happening

[Quick_Nils]

On 4/20/2024 at 11:45 PM, Quick_Nils said:

Why are my SRB plumes transparent? I used this mod before and it worked fine then. Yes Stock SRBs have the same issue. Im using restock (thus waterfall restock) but since both stock and supported mods (in this case BDB) have the issue i dont think thats it. I checked every dependency. What could cause this?

The issue seems to be fixed FINALLY  I deinstalled every mod, redownloaded RSMP and its dependencies and installed only those. My best guess is that the cause was the version of module manager. I had the problem with
version 4.2.3 (wich i believe is the newest). Waterfall comes bundled with version 4.1.4. No clue why the newest module manager version seems to bug out RSMP. Now i hope the game doesnt break after i reinstall all the other mods

[JonnyOThan]

8 hours ago, Quick_Nils said:

The issue seems to be fixed FINALLY  I deinstalled every mod, redownloaded RSMP and its dependencies and installed only those. My best guess is that the cause was the version of module manager. I had the problem with
version 4.2.3 (wich i believe is the newest). Waterfall comes bundled with version 4.1.4. No clue why the newest module manager version seems to bug out RSMP. Now i hope the game doesnt break after i reinstall all the other mods

That *really* shouldn’t be the case…why aren’t you just using CKAN?  99% of the time “I reinstalled everything and it works” just means it wasn’t installed correctly the first time.

You should verify the assumption about modulemanager.  Upgrade it to the newest version, changing nothing else, and see if the problem returns. For best results, copy your KSP.log and modulemanager.configcache files somewhere else first and then you can compare them to see what changed.

[Quick_Nils]

10 hours ago, JonnyOThan said:

That *really* shouldn’t be the case…why aren’t you just using CKAN?  99% of the time “I reinstalled everything and it works” just means it wasn’t installed correctly the first time.

You should verify the assumption about modulemanager.  Upgrade it to the newest version, changing nothing else, and see if the problem returns. For best results, copy your KSP.log and modulemanager.configcache files somewhere else first and then you can compare them to see what changed.

hm. ill do that when i have time

[Lisias]

On 4/22/2024 at 6:34 PM, Quick_Nils said:

My best guess is that the cause was the version of module manager. I had the problem with
version 4.2.3 (wich i believe is the newest). Waterfall comes bundled with version 4.1.4.

Never allow more than one ModuleManager to be present in your installment. Some older DLLs don't have enough meta-data to allow KSP 1.12.x (and only it, previous releases were a yet worst mess!) to try to figure out what to load.

Being not bad enough, I have evidences that some rigs are prone to fire up more than one instance of MM at once when this happens, and you end up having race conditions on the patching - this really screws up things. This appears to victimize MM 4.2.3 in special because, in the majority of the situations where a doppelgänger is also running, the most evident problem is the Localization's patches being screwed (with nodes copied inside themselves, really a mess). I could only detect this one by eye balling the ConfigCache - a very tedious task...

Since it's not feasible to determine in advance which DLL is safe to have as a doppelgänger and which is not, the safest and easiest way out of the mess is to avoid having more than one Module Manager DLL in your rig as it would be plague (what, in essence, ends up being sometimes).

As a matter of fact, I'm diagnosing some complex installments and decided to install MM 4.1.4 and 4.2.3 at the same time to see what happens with the patching on KSP 1.12.5 (MacOS).

This ended up allowing 4.1.4 to be ran instead of 4.2.3, as the following log excerpts demonstrates:

[LOG 21:50:19.605] ******* Log Initiated for Kerbal Space Program - 1.12.5.3190 (OSXPlayer) en-us *******
Kerbal Space Program - 1.12.5.3190 (OSXPlayer) en-us

<yada yada yada>

************************************************************************

Environment Info
Unix 7FFFFFFFFFFFFFFF  Args: KSP -crash-report-folder /Users/lisias/temp/ksp

Mod DLLs found:
Stock assembly: Assembly-CSharp v0.0.0.0
Scale_Redist v1.0.0.0 / v2.5.0.62
ModuleManager v4.1.4.0
ModuleManager v4.1.4.0     <----- doppelgänger!!!
<yada yada yada>

[LOG 21:50:48.120] [ModuleManager] version 4.1.4.0 at /Users/lisias/Workspaces/KSP/runtime/1.12.5/GameData/ModuleManager.4.1.4.dll won the election against
Version 4.1.4.0 /Users/lisias/Workspaces/KSP/runtime/1.12.5/GameData/ModuleManager.4.2.3.dll

So, and assuming that you just installed things by unzipping the whole contents without removing unwanted things after (the most usual M.O. on userland), it's pretty unlikely that MM 4.2.3 would be causing any trouble for you, because 4.1.4 would be the one being run, perhaps twice (I never managed to reproduce this MM being run twice behaviour on my rig, it appears to be tied to some CPU models).

So, in a nutshell, never, ever allow more than one Module Manager be present in your whole rig.

=== == = POST EDIT

On 4/21/2024 at 4:41 PM, Quick_Nils said:

I deinstalled everything thats not needed and its still happening

Well... I did this test: tried the GDLV3 stock craft on a test bed exactly like this one. In one test session, I used MM 4.2.3, and in another I used 4.1.4.

In both cases, the ConfigCache generated were identical (compared char by char). There's no way MM 4.2.3 would caused the problem you depicted.

In both cases, the image I got was:

Whatever is happening on your rig, changing to MM 4.2.3 must be a coincidence.

But, to be certain, I suggest you do what I did:

1. Install MM 4.2.3 on this test bed. Delete ConfigCache.
2. Fire it up, fly the GDLV3 and see what happens
3. Rename the ModuleManager.ConfigCache to ModuleManager.ConfigCache.mm423.
4. Remove MM 4.2.3, install 4.1.4.
5. Fire it up, fly the GDLV3 and see what happens
6. Rename the ModuleManager.ConfigCache to ModuleManager.ConfigCache.mm414.
7. Compare both ConfigCache for differences.

I think this may be related to VRAM (there are too many programs using video et all opened? On my old potato, I could not watch Youtube and play KSP at the same time!).  Perhaps deleting the Settings.cfg and the PartDatabase.cfg (on the same place where the EXE file is) would help?

If nothing helps, post your full KSP.log (quit KSP before copying the file, to prevent KSP from truncating it) after reproducing the problem again. I would like to see it to check if I find something on it that I recognize.

Edited April 24 by Lisias
Entertaining grammars made slightely less entertaining...

[NaviG]

On 4/14/2024 at 5:36 PM, Legolas5533 said:

I've been having a problem, solid motor plumes work well, but the smoke trail is gone.

Same here
edit: install the previous version, it should work fine again

Edited May 2 by NaviG