Phoenix-D

Does the ocean turn to a black void gradually, like an oil slick is being poured on to it? If so that's a TUFX problem. Turn off HDR.

Ah, ok, the config file in the mod folder made me think it was a default thing, and all the parts have scaling even with the patches out

Stupid question, how do we turn it off?

Grannus had a weird black ring around it in my install. I noticed that Circo had it's atmosphere commented out to avoid visual bugs, so I did the same to Grannus and that fixed it. If you're having the same thing, it's GPP/GPP_Planets/Grannus.cfg, just delete or comment out (//) the "Atmosphere" section. If you have GEP, do the same there

It'd pride month on SOME planet, let's go there!

Try the Memgraph mod if you haven't already. It improves garbage collection somewhat which can reduce memory usage. You could also try lowering texture quality. Also try installing those two mods alone and see if they cause the same issue.

1.123 is probably the last. Maybe one or two bugfix releases. Maybe.

Is there a way to ISRU FusionPellets? The resource files mentioned Pathfinder but I don't see it there or a patch in this. Also does Electro Plasma...do anything? Great mod .

We'll need the logs the report mentions to know.

You're missing a dependancy. [EXC 20:49:25.091] BadImageFormatException: Could not resolve field token 0x040001a7, due to: Could not load type of field 'KerbalConstructionTime.KCT_GameStates:toolbarControl' (26) due to: Could not load file or assembly 'ToolbarControl, Version=0.1.8.2, Culture=neutral, PublicKeyToken=null' or one of its dependencies. assembly:ToolbarControl, Version=0.1.8.2, Culture=neutral, PublicKeyToken=null type:<unknown type> member:(null) signature:<none> assembly:E:\My Games\Kerbal Space Program\GameData\KerbalConstructionTime\Plugins\KerbalConstructionTime.dll type:KCT_GameStates member:(null) signature:<none> Get and install the toolbar control mod (and clickthroughblocker)

There's a bug right now that reveals them all, and editing your save file won't help. Not sure what triggers it yet, and I haven't found a way to fix it aside from starting a new game. Oh, and once it happens you have to not open that save again. If you do, the bug spreads to your other saves.

Discovered that putting a docking port on the side of the rentry modules is a Bad Idea. Or a great simulation of being drunk (yes even with control from here on). Didn't help that I forgot SAS. No SAS + engineer driving + docking = AAAAAAAAAAAAAAAAARG.

Hi, I made a .cfg to place this in the stock system just past the orbit of Dres (with a high but lower inclination- 50% of real) Replace the socttmanly/planets/scott.cfg 's text with this I also made a ResearchBodies.cfg. Just put this in the scottmanly folder as scott_ResearchBodies.cfg. Both the same license as the original mod (currently listed as GPL3 on github), feel free to add them to the download or not as your leisure. No github account here to do a request with. I'd make the first one a non-RSS MM patch but I'm not confident enough with MM's syntax to do that to other people's saves.

Nah, not the helmet. Literally the inside of the kerbals eyes.

https://www.youtube.com/watch?v=30KSt4Iy9Q8 Static fires are common during development. Just not the kind you get with liquid engines where they fire the actual engine they're using right before takeover. For obvious reasons I do think the stock settings of the mod are kind of pessimistic on SRB reliability though. Once they're finished designing they're often more reliable than liquids.