The Space Peacock

@Meb Kat merged your report

@billyBobJoe merged your report with this one

Do you know if you lost all trajectory lines, or just the one for your craft? I’d like to try to replicate this

woah, never seen something like this before. it looks to be the same effect as viewing Kerbins atmosphere from inside Kerbin in map view/tracking station, except it's everywhere. Good find!

@nasafan2841 merged your report with this one

to anyone still running into this bug, here's a workaround: First, go to <<C:\Users\USERNAME\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Saves\SinglePlayer\CAMPAIGNNAME>> with 'CAMPAIGNNAME' the name of your campaign Find and open the .json file for your affected save file in any text editor program Locate your vessel data within the save .json. It should be next to "assemblyName": (tip: use CTRL-F) Scroll down a bit until you see the line "Situation": "Landed" (or "Splashed") Change the Situation from "Landed" to "Orbiting". Save the file, reopen the game and your craft should now have its trajectory back! See the images below for some clarification on each step.

Hi @ShadowZone, looks like you're experiencing a similar but different bug; The main difference is that with this bug, planets and other vessels will still have their trajectories, whereas the bug in this thread causes all trajectories to go missing. This one also cant be fixed by restarting the game, but there is a solution: First, go to <<C:\Users\USERNAME\AppData\LocalLow\Intercept Games\Kerbal Space Program 2\Saves\SinglePlayer\CAMPAIGNNAME>> with 'CAMPAIGNNAME' the name of your campaign Find and open the .json file for your affected save file in any text editor program Locate your vessel data within the save .json. It should be next to "assemblyName": (tip: use CTRL-F) Scroll down a bit until you see the line "Situation": "Landed" (or "Splashed") Change the Situation from "Landed" to "Orbiting". Save the file, reopen the game and your craft should now have its trajectory back! See the images below for some clarification on each step. Hope this helps!

@gishtag merged your report. also: the workaround for this bug is restarting the game

@mattihase merged your report with this one

@mattihase merged your report

K.E.R.B. is life, K.E.R.B. is love

@Tazmaniak merged your report with this one

This bug has been in the game for quite a while (possibly since release). I first noticed it on a craft pretty much identical to this one. You used to be able to abuse this bug to make a Kraken Drive in v0.1.2.0, but it was sadly patched out in 0.1.3.0

@Scarecrow71 merged your report with this one

thanks! added both into the report.

you've sufficiently convinved me that this should indeed be reported as a bug with that video i still think this is fine for pro/retrograde (since that basically allows you to do a continous launch without ever having to press a button), but it is a problem for up/radial and north/normal Also, a quick heads up: the forum cant embed .mkv files, so please submit any videos for bug reports either as a .mp4 file or youtube link if you can

want me to merge it? i left it as a standalone report because i've never seen the dawn do this before. and partially because the title was funny xD

i'm not nearly clever enough to figure that out

true, but its the closest thing there is to it and all the other surface SAS holds have an orbital counterpart. i'm just saying i get why they did it, not that i'm a fan of it :p

i'm pretty sure this isn't actually a bug, it sounds more like intended (but annoying) behaviour. in theory it makes sense to switch from 'up' to 'radial out', but in practice it almost never works out. having it switch to 'SAS hold' instead of 'radial out' when your SAS is set to 'up' when crossing the transition altitude is a great suggestion

6116

@142857 merged your report

@The Aziz have also merged your report into this one and updated the title to include reverting as a trigger

@Vl3d tried to merge your report (lets keep these as one report; there are technically multiple ways to trigger it, but the root cause is identical) it somehow took over the report tho, so moved my note on root cause from @ShadowZone's report to yours and edited the title to include all cases. the forums have their quircks

that lines up with what we've seen. we've been able to find a way to consistently replicate this, both for your craft and from scratch, and we're pretty sure we know whats causing it: for your craft, @Spicatdiscovered its the panels on the back that are to blame. in general, it seems like this bug is caused by copying a group of parts and connecting them using nodes that are not on the root. from here there are a few ways to trigger the bug; saving/loading twice, undoing something then doing a save/load, picking up a part of the assembly-placing it seperately-then undo+redoing, deleting a part and then hitting undo... this is a video of the bug happening in the most basic way i could get it to, using nothing but 4 panels: and here it is after undoing then reloading the craft: i dont know the full technical specifics of it, but i'm told it's caused internally by two parts getting assigned the same identifier due to the way they're copied and placed, then saved. As soon as you have parts that are connected this way in your craft, it basically becomes a ticking timebomb waiting to burry itself into the VAB floor. In any case, it's been reported internally and we should hopefully see a fix for this sooner rather than later