Margoth

(0.2.1) I'm encountering this randomly with Dawn. E.g. I have a number of identical very light probes (sample return pods), one of them bugged out in the above described way after escaping Eve SOI - worked fine while within SOI. Another probe escaped Eve and did a 90min burn just fine under time warp. Reloading and quitting game don't seem to help. Don't know if related, but the AP/PE reported in lower left seem to be bugged too (reported 0m/0m or -2,088km/20,567m)

I noticed that 0.2.1 should (once again) fix this issue. Just wanted to drop an observation. Launching the return capsule from my test craft seems to always result in orbital velocity dropping to zero after switching vessels. I noticed in Tracking Station that the capsule is reported as "landed", even if it high in orbit. If, after launching, I first land the capsule nearby and then go for orbit, the anomaly seems not to happen. So somehow the "landed" state was sticky and got reset when landing again?

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: AMD Ryzen 7 5800X | GPU: GeForce RTX 3080 | RAM: 32 This should probably be merged with the Orbital Decay - I'm submitting here to attach a workspace. The attached workspace contains a Sample Return Rover (intended for Moho) that for me seems to trigger orbital decay every time, whether flying it to destination manually or by cheat. It seems that the rover must be landed, after which the return capsule is launched towards orbit. I have encountered orbital decay on every attempt so far. Launching from Mun orbit before landing didn't seem to trigger decay. Further observations: Decay visible by slowly changing AP/PE and speed. Orbital speed resets to (near?) zero when switching to another craft and back. No trajectory lines visible. This craft tested only on Mun, but I have observed this behaviour on other crafts when launching from at least Duna and Gilly. Didn't notice decay after escaping Mun SOI. Trajectory was altered drastically after escaping Mun SOI. In the screenshot attached the craft had barely escaped Mun and was on a decent stable orbit around Kerbin (lines not visible but AP/PE around 9-16Mm). After swithcing to another vehicle and back it was shooting out of Kerbin SOI at 4,2km/s Included Attachments: SampleReturnRoverTest.json .ipsImage { width: 900px !important; }

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: AMD Ryzen 7 5800X | GPU: GeForce RTX 3080 | RAM: 32 I haven't been able to reproduce this yet, but it was a curious one-time bug. The return vehicle (pictured) had a Mk1 pod with Mk16 parachute, stacked with heatshield, Science Jr. and a FL-T100. Yes, I forgot the decoupler! Most of the vehicle blew up on re-entry, but IIRC somehow the Science Jr. exploded while the FL-T100 survived, although remaining a bit separated from the heatshield and the pod. From that point on no deceleration took place, even though the new beautiful visuals were showing. No more orbital degredation, even on subsequent atmospheric entries. I hope I can reproduce this at some point. Not really much to work on before that... Included Attachments: .ipsImage { width: 900px !important; }

I think I have encountered something like this a few times when accidentally trying to (un)deploy during time warp. Movement doesn't happen and the the part manager status becomes confused about the actual status. Now I'm very careful not to activate anything durin time warp. I should probably focus on reproducing rather than avoiding. :-D

A nice Christmas present, thank you!

Simple: loss of attitude control at side booster separation, resulting in slowly spinning fireworks. Hence why I want to try reproduce one more time, provide logs etc.

Thanks for the nice big bugfix update! After a quick test I couldn't reach orbit due to bugs so I'm still calling the game unplayable. I will submit a proper report on the worst ones a bit later.

I guess these are all related as they appeared around the same time. Clicking Launch in VAB does nothing. No autosaves, quick saves or manual saves are stored. Starting a new campaign doesn't proceed from filling in the names, colours etc. Saving workspace designs DOES work. Checking game files integrity (Steam) didn't find anything. Re-install didn't have an effect. Removing "Kerbal Space Program 2" in AppData/..../ seems to have resolved the problem. System: CPU: AMD Ryzen 7 5800X Mem: 32GB GPU: GeForce RTX 3080 10GB Monitor: Samsung G9, native resolution 5120x1440 If attachments had been allowed here (as suggested elsewhere), I would have attached a zip with the whole KSP2 folder from AppData. Inside there is also a log file from game directory, from a previous save attempt. Let me know if I can drop it somewhere. I hope you nail this one, it's a pretty sad method for recovering.