Anth

No worries, if its a problem for enough people I am sure others will report similar issues. Physics warp does disengage at 70000m, so its probably normal timewarp that caused the problem. Perhaps a phantom force from the landing gear?

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB I found the exact time that Time Warp Under Acceleration stopped working is between the following: Note with the changes to 0.1.4.0 Add 1 year 1 day to all times of the save files. Kerbin Orbit: Y15 D264 H4 M42 S7 and Y15 D264 H4 M42 S8 Save File: Y14D263H4M42S00.json Mun Orbit: Y15 D264 H4 M42 S5 and Y15 D264 H4 M42 S6 Save File: MOY14D263H4M42S1.json Solar Orbit: Y8 D132 H5 M21 S3 and Y8 D132 H5 M21 S4 Save File: SOY7D131H5M21S0.json Duna Orbit: Y15 D264 H4 M36 S29 Y15 D264 H4 M36 S30 Save File: DOY14D263H4M36S25.json Additional Information: The following bug that can break the rules of this bug report for solar orbit and have timewarp working after these times. Credit: @Turtle6 Helped by telling me about the bug, that it wasn't related to an engine using low thrust, (which is from another bug report).

@Justasimplepotato Merged your bug report with this one.

I think ladders will work eventually.

KSP1 did it.

Thanks for the bug report. Is there anyway you can supply the SSTO?

@Syltus They don't currently show up in map view or in the Tracking Station. You need to know exactly where you planted them or you may never find them again.

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Overview: A persistent issue where Kerbals, wheels and landing legs fail to interact properly with the ground in saves with a large number of flags planted, resulting in Kerbals freefalling in place indefinitely and wheels/landing legs clipping into the ground and not functioning, this issue seems to be independent of the location of planted flags in the save and also seems to be time dependant too (see below). Kerbal Floating Immobile Until using RCS Where She Looks like She's Skiing: Issue Gone with the Removal of the Flags: UT Time Is A Major Factor: Tylo: Laythe: The above issue happens within a range of UT times and not other times. Duna: Eeloo: Credit: @DibzNr Gave me his save files in relation to his bug report: @Moredice Gave me his save files in regards to Eeloo and I used his save to launch to Duna.

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Observed Behavior: If a strut is connected from a wing to another part then if that strut disconnects, all struts of a craft disconnect. Expected Behavior: If a strut is connected in anyway, when it disconnects it disconnects alone and all the other struts remain unless multiple struts have been stressed in exactly the same way. Strut from Wing To Tanks: All Struts Disconnecting Strut from Tank to Wing: Only Appropriate Struts Disconnecting

Personally I think its settings in the appdata folder that has something weird going on. Try that first is my recommendation. If that doesn't work. Reinstall from the file you already have first. I haven't had a corrupted direct download in a long time. I did post a suggestion of at least having appdata subfolders having their own versions. Everything in their same folder could be a problem for testing bugs over multiple versions. But no response as of yet. If it is the Intercept Games appdata folder, supplying that could help get to the bottom of the issue.

Career files do have some settings in them so that might help. Yes. I also recommend the following: First: Verify the KSP2 files. Second: Move the Intercept Games folder in the appdata folder to somewhere save. Location: %userprofile%\AppData\LocalLow\ (that exact line will work in windows explorer) The folder is Intercept Games Then restart KSP2 forcing it to create default folders and setting files.

@mattihase No problems in my testing. Craft in the VAB: Craft on the Launch Pad:

Oh. It's a craft file. Sorry. Brain Fart. I have only ever been given autosaves for outside the VAB. The json file is the only one necessary so I didn't even think to look at the little thumbnail.

Oh and can you supply the craft file as well? That would make for much quicker testing. I suspect the small parts might be the main cause. I would like to remove them and replace them with something else and see if the problem keeps happening.

Great Video but it is hidden in here where the developers might miss it. Could you please do a bug report for it via the form so the developers won't miss it? https://forum.kerbalspaceprogram.com/forms/2-ksp2br/

@CiberX15 Definitely not related to the strut bug. I moved your comment to here where its much more likely to be seen by the developers. And uploaded your video to the KSP Forum servers. Great Video by the way.

Reported Version: v0.1.3.2 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel i9 9900K | GPU: Nvidia 3070ti | RAM: 32GB Screenshot:

No. It's worse than that. For my testing of this bug for Laythe, the flag that was causing the issue was on Duna.

I Removed all the flags from your save file.

I am not sure the title is specific enough to the issue you are having. What about the following title: Various Rocket Engine's Thrust are Being Blocked When Clipped into Each Other.

@Stonks73 Thanks for posting this bug report. This bug report is about clipping engines together and there being no thrust?

That should correct your issue: AnthTerrainCorrection.json

@fvdief Merged your bug report with this one.

@mattihase Your autosave loaded into the KSC Screen and there was no apparent craft within the game even though there was evidence of a craft within the code itself. Here is a video showing how I am attempting to replicate your issue:

Thanks for the additional information. I will test and get back to you.