Joker58th

With RocketSoundsEnhancement and its default config, WaterFall and Stock Waterfall Effects installed, the jet engines have both stock sounds and RSE sounds. Can someone help me out? Log File

I can't quite put my finger on it yet, but yeah, there are some inconsistencies here with the burn bar. Sometimes the dots do not line up with the burn bar. Do I follow the dots or the burn bar? Sometimes the burn bar turns red from the left side. Sometimes there is no burn bar at all. If I can narrow it down, I'll post more details.

Yes please! I also used this a lot in KSP1.

I'm experiencing the same. It seems the default spring tension is not high enough. What's working for me is to disable auto suspension and increase spring strength to max.

Continuing the ISS build, I added the Quest airlock. Afterwards, I noticed the station starting to wobble so I decreased some of the reaction wheel strength which seemed to help but we'll see. Next up would be the PIRS docking compartment.

Today I added the Destiny module to the ISS. Nothing too exciting. I decided not to follow the exact build order of the real ISS as I'm not interested in moving stuff around after it assembled. Next up looks like the Quest airlock module.

I noticed that some people have asked for procedural or adjustable landing gear, but I haven't seen anyone mention @Shadowmage's amazing mod Kerbal Foundries2. This mod has everything that people have suggested and more. I always used this mod and its dependency KSP Wheel when I played KSP1 with space planes or aircraft contract packs. It would be great if this could be part of the stock KSP2 in the future. Especially, the feature that aligns the wheel to the ground would be very useful.

Tried the Z1 truss a second time and still had the jitter issue even after setting all docking ports to 0%. Enabling time warp worked! Thanks @stephensmat!

I usually do set my docking ports to 0% and I just double checked and found I forgot to set the one on the delivery ship. I'll fix that and try again. Fingers crossed! Thanks for the suggestion! Good suggestion, I totally froze while my station flew apart. If something like that happens again, I'll try this.

Welp, I tried to add the Z1 truss to the ISS. Failed due to bug and blew up my whole station. Thankfully, I just reverted to VAB. Overall, it was a pretty lousy flight any way. My docking control was awful.

Is more info still needed on this? I was working on an ISS build and lost over half of the station. Notice in the top right of the load window the thumb nail shows the entire station I had up to this point. Now it's gone. Some part of it is in the floor.

I added the Zvezda module to the ISS.

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: i7-12700K | GPU: Nvidia RTX 2080 | RAM: 32GB I discovered this issue on an orbital class spacecraft but simplified it to just an issue with the sepratron engine. Steps to replicate: Add sepratron to a probe core Move launch clamp to top of staging order Launch Fire the engine on the pad Exit game to menu being sure to save on exit Load the game you just saved A sound continues to play but does not seem to be the sepratron exactly Video Evidence: Ksp2soundbug.mp4 Craft File: TestBug.json .ipsImage { width: 900px !important; }

Nice work around. Thanks!

Reported Version: v0.1.5 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: i7-12700K | GPU: Nvidia GeForce RTX 2080 | RAM: 32GB The borderless setting does not seem to save to the settings.json file. Steps to reproduce: Note FullScreenMode in settings.json file. (Unless you are already in Windowed mode, it will be ExclusiveFullScreen) Launch game. Set Game Screen Mode to Borderless and exit settings. Note settings.json file still says ExclusiveFullScreen. Exiting the game after making the change does not work either. Note: Windowed mode does save and work as expected. If I edit the settings.json file with the "Borderless" setting, it does work the first time the game is launched. It will then revert back to ExclusiveFullScreen after the game is loaded. I wonder if the problem is related to my monitor's native resolution, which is higher than the max 2560x1440 in settings?