Flight Ship "Stuck" Stationary above Mun [Uncontrolled Vessel Stuck In Stationary Landed State Above Celestial Body]

[PicoSpace]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 10 Professional | CPU: AMD 5800x | GPU: Zotec 3070 with improved fans. | RAM: 64GB CL14

 

I strongly expect this is an expansion of the false landing bug but when doing an Apollo style landing Rescue mission my lander on accent got the trajectory-line bug and then when I switched to the orbiter the lander basically got stuck at 11m/s (which I'm assuming is the rotation of the surface of mun) and basically my orbiter fly right past it rather than rendevous. Kerbal jumped out and fell like normal but the lander is still floating in space above Mun.

Series of Events:
1. Initial Mission crashed a lander on Mun (whoopsie)
2. Send an semi-apollo style mission to rescue and then attempt to re-land at waypoint (arc)
3. Undocked the Lander from the orbiter, the lander at this point is under probe control as I needed to first pick up the stranded Kerbnaut.
4. Landed by crashed ship, Kerbal transferred, lander ascend (after a time warp to ensure orbiter ideal position for rendezvous).
5. Trajectory Lines Missing, Targeted Orbiter anyways in hopes of 1A/1B intercept alignment as I wasn't too far off having used the surface features to guide lift-off trajectory. But failed to get an intercept.
6. ReBooted the Game in an attempt to get trajectory lines back - no luck
7. Swapped to Orbiter as it still had its trajectory lines, but when I did the lander wasn't movinge (well 11m/s) but it wasn't falling etc. Status indicated "Landed" on Tracking Station despite it still being up in the air.
8. Tried to dock with the NOW stationary lander, swapped back and forth but no go.
9. Decided to Jump the Kerbal to from the Lander to the Orbiter, missed and the Kerbal fell to mun as if it was under normal phsyics (once it let go).
10. Several Kerbals were lost to bring this bug report (as the orbiter dV and trajectories failed to escape Mun's gravity as well).

Image: Shows the Status of the Lander that's "Floating" its not falling nor is it accelerating/decellerating
Other Attachment: Orbiter and Lander Image (Not Sure you need this but again, pretty basic crafts)

 

Included Attachments:

Edited February 1 by The Space Peacock

[Spicat]

@dya, merged your bug report.

[dya]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 11 Home | CPU: AMD Ryzen 7 5800X3D 8-Core Processor 3.40 GHz | GPU: GeForce 2070 Super | RAM: 32 GB

I'm limited currently to only running single vehicle/launch missions because of a bug where vehicles I send up will seemingly randomly be flagged as landed from what seems to be the point of launch. It's happening to at least 2 of every 3 launches.

The vehicle will operate normally, but have no orbit line, making any rendezvous nearly impossible, meaning I can't establish a station or have multi-vehicle missions.

When re-loading on these vehicles, they're sitting at their last position in space, but with velocity zero. So they just drop from the sky.

I've been able to edit my saves to put the vehicles back to orbit, but I can't calculate (with any reasonable level of ease) their velocities. So I'm pretty much stuck.

 

 

I'm attaching the json for a vehicle that seems to suffer the issue with some regularity.

Included Attachments:

KerbinRefuel.json

[Anonymous Bug Reporter]

Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Win 11 | CPU: AMD RYZEN 7 5700X 8 CORE | GPU: geforce RTX 3060 | RAM: 32 GB

Severity: Med

Frequency: High

Desc: as of 1/8/24 I've been encountering an issue with every flight where while launching to orbit the trajectory line on the map disappears and even if orbit is then achieved, rockets will inevitably stop and fall back to kerbin. I've reloaded my save file multiple times, reverted flights, recovered vessels and re launched, and closed and reopened the game multiple times. but once the bug occurred once, it occurred every flight after that.

 

specifically, once stage separation has been enacted atleast once, regardless of whether the map has been opened yet for that flight or not, the only path projection line on the map will be for one of the separated debris parts, and not the vehicle or command part. that line will after a moment disappear. if I managed to get my rocket into orbit anyway and go to KSC, tracking station, any other facility or combination of in any order, or save and exit/reload, the map will still not display a path line for the vessel in the tracking station or in flight map. and regardless of any previously mentioned things done or not done to get the path line back, the vessel will eventually stop in orbit and fall back to kerbin.

Included Attachments:

[brobiwan]

Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes 
OS: Windows 11 Home 22621.3007 | CPU: Intel(R) Core(TM) i7-12800H 2.40 GHz | GPU: NVIDIA GeForce RTX 3070 Ti | RAM: 64GB DDR5

 

straight away, since it's probably just another variant of the landed state bug.

Basically, I had previously done some rendezvous between 3 craft to do some fuel exchange, etc., and I wanted to undock to split up the vessels.  I first wanted to undock one of the vessels, which was essentially dead weight, and crash it into Kerbin.  The entire merged vessel was in LKO of ~100km.  After undocking and executing a burn to get "(COMBINED)-14" on a crash course with kerbin, the unfocused vessel ("DEFAULT NAME-11"), originally still in its 100km LKO, suddenly flipped into a landed state, and its speed changed to 204m/s.  It's also worth noting that a "Vessel Recoverable" notification popped up at the time the issue occurred.  "DEFAULT NAME-11" seemed to be frozen in the same position, despite showing a non-zero velocity, although "(COMBINED)-14" and other in-flight vessels continued to move on their trajectories.  When I switched to control "DEFAULT NAME-11", it began to fall more or less straight at Kerbin, although as it fell, it still showed up as "Landed" state from the tracking station.  From the time "DEFAULT NAME-11" flipped into a landed state, no orbital lines for that vessel showed up in the map view (orbital lines for other vessels showed up correctly).  See attached video.

The issue seems reproducible, starting from the attached save ("Kraken.json"), undocking, and performing a retrograde burn.  I'm not sure if this matters, but I think in most of the cases where I've reproduced it, the issue occurred while I was in map view.  I've reproduced it 5 or more times at this point, starting from the same save.

One weird thing:  Given that the issue seemed very similar to the previously reported ones, I tried the workaround posted by The Space Peacock:

However, after reloading a save where I manually changed the situation from "Landed" to "Orbiting", it did not fix the issue.  I'm not sure if the changed velocity (from  ~2245 m/s to 204 m/s) created problems for the vessel even after its situation was fixed, or what.

 

Included Attachments:

 

Kraken.json

Edited February 1 by The Space Peacock

[The Space Peacock]

@brobiwan merged your report, think this one describes it better than the landed state bug. it sounds like it might be a variation of it, but best to keep them seperate for now. also a quick heads up: please make sure the video files you submit for bug reports arent too large, that prevents us from viewing them/embeding them in your report
@PicoSpacemoved your report out of the archive

Edited January 31 by The Space Peacock

[brobiwan]

@The Space Peacock thanks for merging this!

About the video size -- the bug report submission page said the limit was 500MB, and the video I submitted was 200MB if I'm not mistaken.  Is there a lower limit I should adhere to to make things easier for you in future?

[The Space Peacock]

18 hours ago, brobiwan said:

About the video size -- the bug report submission page said the limit was 500MB, and the video I submitted was 200MB if I'm not mistaken.  Is there a lower limit I should adhere to to make things easier for you in future?

Yeah, it's a bit liberal in that regard; mostly for the purpose of allowing long videos if those are needed. Your size is actually not that outrageous for the length of the video, but it still makes it hard for us to embed it into the forum so other people dont have to download it (for files that large that can take up to 15 minutes). 

Don't know if you've ever heard of Handbrake? its an amazing tool for condensing large video files into smaller ones without losing quality. I was able to bring your video down from 200mb to just 30mb with it