pckbls

Are you using the command line argument workaround to disable the new Private Division launcher? I re-enabled the latter and suddenly SoundTrackEditor Forked would play music again on the latest KSP version.

Do you have TUFX or KS3P installed? If so, try disabling Ambient Occlusion.

I was able to solve this issue by disabling Dithering in Scatterer's settings.

Could someone elaborate why some of the engines offer the possibility to switch between pure LH2 and LOX consumption? I assumed the former provides less thrust but higher efficiency thus more Delta V. In reality the LOX mode provides more thrust AND almost twice as much Delta V than the LH2 mode (with the corresponding fuel tank configured that it only stores LH2). Is it supposed to work like that? If so, why? If not, how could I fix this? UPDATE: I totally get it now, lol. The tank variant with embedded Oxidizer weighs about 50t more!

In fact, I'd HIGHLY recommend to install this mod along Spectra. Especially when using a rescaled solar system, it'll fix all the washed out textures when in high orbit. Just look at that Mun for reference: Duna is also more beautiful than ever:

Yes, I have attempted to quickload and reland the vessel. Always getting the same results. I have purposely disabled both Terrain Scattering and Tesselation as both massively impact the performance on my system. With both enabled I get less than 10 FPS near celestial bodies vs. 30-50 with both disabled. Also with Tesselation disabled, landing legs do not clip through the surface (at least on my system), proof: Regarding my issue: It's hard to see on a screenshot, but it's not just some weird visual glitch but there's definitely something wrong the the landing legs physics on Voss here. It seems that when in the extended state, they are "falling through" the surface. Hard to explain. Thus I have recorded a short video that shows the landing of my Vessel on both Voss and it standing on the Launching Pad on Rhode. Hope that helps to get an understanding of what is happening: *UPDATE* Appears to be a known Kopernicus issue, see: https://github.com/Kopernicus/Kopernicus/issues/459 *UPDATE2* I was able to resolve this issue by uninstalling the Making History expansion. *UPDATE3* I have figured out that this issue not only occurs on Voss but on other celestial bodies, too. Kohm is also affected. However I found a solution that works without having to remove the Making History expansion. Turns out that I have to manually tweak the Terrain Quality settings in KSP's settings.cfg. For a more technical details head over to this particular comment in the corresponding issue on Github. Proof:

Hi there, after having played Vanilla KSP for about 700 hours, I got kinda bored. Hence I've decided to start another Science mode play through with some content mods once again: Restock/Restock+, Near Future Technologies, Beyond Home and the usual visual/audio enhancements. I cannot express, how beautiful Beyond Home is! Here's my favorite shot so far! Refer to my Imgur gallery for some more impressions: https://imgur.com/a/O0OP8nN So far, I was able to visit several planets and moons without any issues. However today I've encountered the first annoying bug: I've landed on Voss with an near empty Vessel in an ore rich Biome to do some refueling. Unfortunately the landing legs to not touch the ground and instead simply clip through it. The vessel stands on its engines. I can get out of the Vessel into EVA and plant a flag, the latter however is not visible on the surface immediately after. I wouldn't mind those issues if it didn't affect the surface harvester's functionality: I cannot mine ore as the harvester complains about "no ground contact". I'm running: KSP 1.10.1 Parallax 1.0.1 Beyond Home 1.5.0 https://github.com/R-T-B/Kopernicus/releases/tag/UBE-release-58 Is this a known issue? Any chance to resolve it? Kind regards, Patrick