Spicat

@Vl3d, moved your bug report out of the archive.

@All_Hail_Autostrut, does the bug behave like this one (if you remember if you were paused while F5/F9)? And do spamming pause/unpause fix it?

@Mushylog, merged your bug report.

@Vl3d, moved your bug report out of the archive.

This seems to be a bug, use the appropriate form: https://forum.kerbalspaceprogram.com/forms/2-ksp2br/ You can put all the information (you can still put imgur in the message) as well as a craft file at the bottom of the form.

@Scarecrow71, merged your bug report

It's planned but not anytime soon (This was posted on the ksp2 modding discord server)

@margual56, merged your bug report, it seems like it's happening when you disengage timewarp and not when you cross 20km of height and you seem to have landing legs as well which cause phantom forces.

@Dragonld, merged your bug report.

Here, it’s due to some AMD hardware it seems:

No, this one we are in is for deploying landing legs, the one you linked is when disengaging timewarp. There are also the ones on reload and on undocking (see below). They are likely to have the same cause but their reproduction steps are not the same so we didn't merge it because it's potentially not the same bug.

@HammerTyme, merged your bug report.

Anth did a good job on this bug report not so long ago. Now that he's hired, he might push it to the devs. We'll see.

Is this similar? See the message from Anth where he explains the steps to see if it's what happened to you. If this is still the case I will suggest to send a bug report with the link of the one above saying it's still present in 0.1.5.0. You're not forced to do so though.

Yes the change from unity version in this patch broke every mods. Modders are working on it

It's due to the strut, here the bug report I made about it (it's on the kerb):

He was just answering some random questions because he had time due to him being on the plane and unable to work:

Reported Version: v0.1.4.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 10 | CPU: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz | GPU: NVIDIA GeForce RTX 2070 | RAM: 16GB Steps to replicate: Go to launchpad with a pod with any parachute on it Deploy the parachute Repack the parachute and observe the animation Second steps to replicate (to see the bug longer): Go to launchpad with a craft with a parachute and an engine&tank to fly Deploy the parachute Wait for him to deploy Cut the parachute Repack the parachute Additional informations: The bug seems to only appear on ascent where the parachute is not deployed in the intended way (to land). Included Attachments: 2023-10-2215-27-30.mp4 2023-10-2215-26-06.mp4 .ipsImage { width: 900px !important; }

Looks like the same bug as this:

For the fonts

Still happening in 0.1.4.1: https://imgur.com/a/d6M2axI

The second game is also supposedly on Unreal Engine (source: the same job offers) So it’s very unlikely that Unity devs switch to Unreal (Besides it has been confirmed by Dakota that they didn’t move development away from ksp2 but you believe them or not):

They never said anything about reentry vfx being in patch 5, don’t get your hopes up. And it’s a new version of the game engine, not a new game engine (Unity 2020.3.33f1 => Unity 2022.3.5f1). Which is still great, especially for modders!

There is a small difference during the animation of landing legs and the final result as seen in this video: https://imgur.com/a/Oiz4zLs The most severe one is the smallest landing legs.