Gordon Dry

@HansAcker for heaven's sake - that was not my question. I DID NOT install RP-0 aka RP-1 but the result of the MM patching is if I would have. Come on.

yelp! I use MM 4.1.1 which only got one small change about Firespitter warning message. So besides that it should be the same as MM 4.1.0, right? Now I got something weird, I guess my game is borked because of this (and other still unrecovered ones): I got NOT RP-0 (aka. RP-1) installed I got the part Utility_InfoDrive installed (solo, extracted from B9_Aerospace, worked for long time this way) I got a patch in my zFinal folder: @PART[Utility_InfoDrive]:NEEDS[B9_Aerospace,RP-0] { @TechRequired = unlockParts %RSSROConfig = true %RP0conf = true } @PART[Utility_InfoDrive]:NEEDS[B9_InfoDrive,RP-0] { @TechRequired = unlockParts %RSSROConfig = true %RP0conf = true } This patch worked until I went on hiatus 3 months ago. Now without RP-1 in my setup, the MM cache tells me this: UrlConfig { parentUrl = B9_InfoDrive/Parts/Utility_InfoDrive/Utility_InfoDrive.cfg PART { name = Utility_InfoDrive module = Part author = Snjo + bac9 mesh = model.mu scale = 1 node_attach = 0, 0.0, 0, 0.0, -1.0, 0.0 TechRequired = unlockParts ... RSSROConfig = true RP0conf = true ... So, what is wrong? Is the MM syntax logic totally changed? Does a comma in a NEEDS is no more an AND but an OR now?

So this is an alternative to https://forum.kerbalspaceprogram.com/index.php?/topic/156017-18x-kerbal-nrap-procedural-test-weights/

I tried it last night with KSP 1.8.1 and no launch parameters (so DX11). All VAB part icons were borked so I removed it again.

@blowfish I just missed any hint that makes me believe the mod/config is allright. Some info like in R&D it says when the unlock will be available.

How have the IDCSP been positioned? They got no fuel for translation or maneuvering themselves and the Transtage got not enough Delta-V to settle them all. Or did I miss a small part like a tiny Monopropellant engine?

@kcs123 I will check that. This "way of doing it" does confuse me because I was used to the RO/RP-1/TestFlight way of doing it. @kcs123 nope, so you did not know it, you just assumed it This means, my question ist not answered.

I'm not exactly sure where to post this, Bluedog_DB thread or here. I decided here @CobaltWolf So, when or how can I switch the part config? Or is it "later" with some tech tree unlock? If yes, why is this information not provided?

RocketSoundEnhancement updates for Bluedog_DB - please check and give feedback: https://github.com/Gordon-Dry/RocketSoundEnhancement/tree/additional-effects -> https://github.com/Gordon-Dry/RocketSoundEnhancement/commits/additional-effects which is https://github.com/ensou04/RocketSoundEnhancement/pull/5

@Zorg allright, I will commit those changes into my branch first - when they are okay I can move them to a BDB PR later and remove them from the RSE branch.

^^ additional configs batch 6 - Bluedog_DB done: https://github.com/Gordon-Dry/RocketSoundEnhancement/commit/cf3c806fde9c54dd2430265755dcce0e7eac6e66

@Aspira See here - could need a new thread or whatever, @Frylovespi https://github.com/Frylovespi/History-of-Spaceflight/releases or even here for the freshest stuff: https://github.com/Frylovespi/History-of-Spaceflight/branches

Yesterday I got a lot of bad stuff in my log as I was looking for something else - a lot of IFS stuff. Yes, I did not dare to open an issue whatsoever - because I already removed TweakScale before that. So I was not sure if those exceptions came because of the lack of TweakScale. After I removed IFS (and still got B9PartSwitch and Firespitter) everything was sane again. I did a check and found only two part packs that really would need IFS at all - and I already had commited patches for those that they also can use Firespitter. Example: MODULE { name:NEEDS[Firespitter,!InterstellarFuelSwitch] = FStextureSwitch2 name:NEEDS[InterstellarFuelSwitch] = InterstellarTextureSwitch2 ... This means, Firespitter comes first and then - if installed - is replaced by IFS. Just for those two part packs I don't need the whole IFS "suite"

see https://github.com/Gordon-Dry/RocketSoundEnhancement/tree/additional-effects which is https://github.com/ensou04/RocketSoundEnhancement/pull/5 I will add more for GameData\Bluedog_DB\Compatibility\RealPlumes\ @CobaltWolf

^ updated the branch with the last commit for now - feel free to fiddle with the cloned configs to make them more realistic

RocketSoundEnhancement lacks a lot of configs. Months ago I already created a branch with new effects - which are in fact clones of existing effects but better than nothing. The problem was that I mislead the people with the name of the branch - it made people think it's only intended to be used with RealismOverhaul. That is not true. It's intended to be used by everyone. So here is the new branch and PR which also contains new additions from just today. (WIP - I'm in the process of creating the configs as I post this) Branch: https://github.com/Gordon-Dry/RocketSoundEnhancement/tree/additional-effects PR: https://github.com/ensou04/RocketSoundEnhancement/pull/5

Still the old bugs. Outside it says "1 strategy", inside it says "2" I spend 150.000 to update, it still says "1" outside and "2" inside. The same behaviour as 2 years ago.

Quick search, hit: GameData\LightsOut\Plugins\LightsOut.dll

I have a weird issue. I DO NOT use this mod at all (I even never downloaded it), but I got this: This is definetely the "not-my-fault-but-the-game-is-borked" issue of the day. So I guess there is some other of your mod updates that went wrong ... Full log and stuff: https://www.dropbox.com/s/ytkxhdwa5uxqrjz/player.log and stuff 2019-11-06-04.zip?dl=1

@Aspira @Yeet_TheDinosaur expecially when using the dev repo, which is the default branch and got commits for KSP 1.8

@mid0r fair enough

Any planet pack is dependent of Kopernicus - which is not updated yet. So this question is not really helpful.

@kcs123 please quote or mention, it's easier to track replies. "zzzUnKerballedStart" does not need to have a folder. It just needs a FOR. I got CTT. I also learned "something" about MM syntax the last years.

I got that, but it just still does not work. As the version for KSP 1.6.x did not work on KSP 1.6.x. Button there, button clickable, but does nothing.

There is a syntax flaw that makes this whole mod not work at all. I see a lot of AFTER[zzzUnKerballedStart] and BEFORE[zzzUnKerballedStart] The MM syntax logic is that these only work if there is a FOR[zzzUnKerballedStart] So I searched for it and only found two files which contain them: GameData\UnKerballedStart\Mod Support\MakingHistory.cfg GameData\UnKerballedStart\Mod Support\Snacks.cfg Because I neither got MH nor Snacks it looks like the mod is totally ignored. Is this intended?