Stone Blue

@Manul Nice!!... looks like you may have some props in there, that I didnt get copies of...

Also, @kerbmario is there any chance to get this (and any source model/texture files) up on a github repo, like neistridlar had, here? https://github.com/neistridlar/Neist-Airliner-Parts

yeah.. that got fixed awhile back... i only mentioned them, because a couple seem to be MM patch files themselves, by the naming.... The log is quite long, and there seem to be a bunch of other issues, so i didnt poke very deep @dangaffa you could look & see if you have in you main KSP folder, a /Logs/ModuleManager/MMPatch.log file, and try posting that... that might give an idea of what bad patch is causing issues... vOv

yeah.. what Jonny said... looking at your log, right off, near the beginning, you have a ton of empty cfg files being reported, and some seem to be related to MM patching... If something is expecting some patches or there are errs in patches, *or* the patches are not present, due to empty cfg files... MM wont create the cache file, and if stuff/patches are missing, *that* could be a problem... I would suggest going thru your install, and verifying everything is installed correctly, including any mod dependencies

@dangaffa can you link to your ModuleManager.ConfigCache file?... Should be at the bottom of /GameData somewhere And its *ONLY* the Stail aerospike?... if so, that should help narrow it down quite a bit, as there several other parts targeted by the same patch, from what I can tell EDIT: oh, wait!... uhh... you do realise, you have a different part selected in the PAW, right?

You three are PHENOMINAL!!

HOW HAVE I NEVER SEEN THIS MOD?!?! :O Awesome sauce!

it *IS* on github... *all* three OPT mods are in the same repo, here: https://github.com/StoneBlue/OPT_Streamlined "Continued" is the /OPT/ folder

Looking guud!

Well, the first thing i would suggest, is updating ModuleManager to the latest 4.2.2 version, and deleteing all the others. Also, delete all 4 of the other ModuleManager files that arent the .dlls... (The next time you run the game, with the updated 4.2.2 MM, those files will all be freshly re-created. Then makke sure *all* your installed mods are updated versions. Other than that, it would help if you posted your KSP.log for peeps to look at... (AFTER you have done the above steps with updating MM, of course ) If its only certain IVAs, and not ALL of them, I would guess there is a mod(s) that arent quite installed correctly, *or*, you could possibly be missing some dependency mods. (Chec to make sure all your mods have dependencies installed, also)

Wot?... I could say the same about the Player.log KSP.log seems to be moar useful for troubleshooting stuff happening at game load, ModuleManager stuff, part compiling issues (models/textures/cfg problems), and other stuff... Player.log may have this stuff, idk... its much harder to understand if you dont seem to be a coder... I know this log seems much moar useful for troubleshooting plugin mods, and stuff happening in-game, *after* loading... I would not say either is worthless... each seems to be quite useful, depending on the type of mod, and moar specifically, the type/timeline of the issue you're looking at. Just to cover all bases when posting bug reports, its prolly best to provide *both* logs... Some devs *do* prefer one over the other, but seems easier to provide both from the start.... vOv But yes, I can see in the case of Principia, (basically a plugin mod), and most of its "stuff" happens *after* loading/in-game, I can see where Player.log is moar prefereable in this case... So I guess I'm just saying you should maybe have clarified you statement, "...*in the case of Principia*, KSP.log is generally worthless..."

Idk... ALL the old versions are still there, for me to grab... vOv (be aware, the oldest version that has ever been up on the KSP Store, is 1.0.5... which *is* still up)...

Taniwha has this: not sure if it is adjustable or not, tho vOv... maybe worth poking?

Nope.. just moved it: https://imgur.com/5igtEXihttps://imgur.com/5igtEXi Altho, when I change *any* of the settings in the launcher window... *NONE* of them seem to actually apply

nevermind.. nothing to see here... move along

So, yes... The site seems to be down right now for everyone... I've let @VITAS kknow via Discord as well

hmm... then you need to also define the replacement Item node properly, withits own brackets, too: @Scatterer_planetsList:AFTER[Scatterer] { @scattererCelestialBodies { !Item[Kerbin]{} Item { ... etc etc etc... } } } OK.. this seems to be the original: Scatterer_planetsList { scattererCelestialBodies { Item { celestialBodyName = Kerbin transformName = Kerbin loadDistance = 100000000 unloadDistance = 200000000 hasOcean = True flatScaledSpaceModel = True usesCloudIntegration = True mainSunCelestialBody = Sun sunColor = 1.0,1.0,1.0 eclipseCasters { Item = Mun Item = Minmus } planetshineSources { Item { bodyName = Mun color = 1,1,1 intensity = 0.0799999982 isSun = False } } } Are you *only* trying to delete Kerbin? or trying to delete/replace with something? If delete *only*, you *should* just need: @Scatterer_planetsList:AFTER[Scatterer] { @scattererCelestialBodies { !Item[Kerbin]{} } } At least as far as the *syntax* goes... I have no idea what the *results* of straight up deleteing, or deleting/replacing that node, will be... I'm not familiar with Scatterer/EVE/Kopernicus...

Mebbe this might be an option? vOv or better yet... this one?

Two posts up from yours

From your example, what is "Item..etc, etc"? Anything added would need to be properly defined as a proper node{}.... Also, there are no closing brackets in your example. ie, you need the last two brackets @Scatterer_planetsList:AFTER[Scatterer] { @scattererCelestialBodies { !Item[Kerbin] {} Item... etc etc etc... } }

Not on the KSP Store, it seems...

@Jovzin No, that folder structure is correct... all three should be their own folder in GameData As to question #1, there may be a deeper issue youre seeing, but make sure you have Community Resource Pack installed, as well.... It is a dependency for OPT Reconfig.

Pretty sure...yes Somehwere in the UI, there should be a button to get to where you can setup the UI layout. Somehwere in there, you can customize an MJ dropdown menu, to add/remove different "modules" of MJ. I dont believe it "enables/disables" anything... It just allows you to customive what shows up in the menu. You can also customize the size and position of where you want it on screen. IIRC, you can even "snap it" to the any edge of the screen, and where-ever you want it.

... or HullcamVDS Continued... Pretty sure it now has Neptune Camera support added. I forgot to mention that in my post

@ColdJ You may want to update the BforArtists info in the 2nd & later posts. Taniwha's Mu Plugin *does* work with all versions of BFA v3.x.x+, so far. I (and a couple other people I know), have used it on every version post-v3.0 to the current v3.3.1 I would also link to the BFA releases page, instead of a specific version, here: https://www.bforartists.de/download/