orbit path is just gone.....

[Indig07]

Basically  the orbit path after loading into a save is just kinda gone so im not sure what to do also the camera is automatically and constantly switching. Lastly the final picture is just a simple spelling error in the settings menu of what should be VAB but instead is OAB

gone 

[Matt_In_Oz]

Yep, had this too after loading a quicksave. Had to guess how to de-orbit the mun... and when I got it right the SOI concentric circles appeared but still no orbit lines. Also no AP/PE markers etc.

[LameLefty]

Next time it happens, check the Tracking Station and see what it says under the Vessel Status. Each time I’ve had it happen, Tracking Station info shows the vessel as “landed” even with velocities of hundreds of feet per second around the Mun. 

There seems to be lots of glitches in vessel status data - even after landing a perfectly normal, uneventful mission, the final mission summary report that pops up show ridiculous, impossible maximum G-loading of like 138g’s. I strongly suspect there’s a vessel status data corruption bug that causes the incorrect G-load data for flights, along with getting confused about the vessel’s state as “Landed” or “In Oribt” or whatever. 

[Mopy]

Explanation

I have frequently encountered this bug within KSP 2's map view and I have realised how to fix it.

The current problem, if you look from the tracking station is that your craft is described as "landed" instead of orbiting, meaning that the game has no reason to display a orbital trajectory.  This can be seen in the save file when the craft's situation is described as "Landed" as the situation under "vesselState".

	"speedMode": "Orbit",
        "autoSpeedMode": "Orbit",
        "altimeterMode": "GroundLevel",
        "autopilotMode": "Retrograde",
        "autoPilotState": true,
        "isKerbalEVA": false,
        "isRCSEnabled": false,
        "flightControlsMode": "Normal",
        "actionGroupStates": null,
        "PhysicsMode": "RigidBody",
        "currentTargetID": {
          "Guid": "00000000-0000-0000-0000-000000000000",
          "DebugName": null
        },
        "launchLocation": "Launchpad_2",
        "SubVessels": [],
        "Situation": "Landed",
        "ControlState": "FullControl",
        "CommandModulesState": "None",
        "CurrentControlOwnerPart": {
          "Guid": "9e830c70-9d7b-45e5-a896-0e16f22d7994",
          "DebugName": null

This problem can be fixed by chaing the situation to "Orbiting"

	"speedMode": "Orbit",
                "autoSpeedMode": "Orbit",
                "altimeterMode": "SeaLevel",
                "autopilotMode": "StabilityAssist",
                "autoPilotState": false,
                "isKerbalEVA": false,
                "isRCSEnabled": false,
                "flightControlsMode": "Normal",
                "actionGroupStates": null,
                "PhysicsMode": "Orbital",
                "currentTargetID": {
                    "Guid": "00000000-0000-0000-0000-000000000000",
                    "DebugName": null
                },
                "launchLocation": "Invalid",
                "SubVessels": [],
                "Situation": "Orbiting",
                "ControlState": "FullControl",
                "CommandModulesState": "FullyFunctional",
                "CurrentControlOwnerPart": {
                    "Guid": "8917d299-e9f1-4f6c-a9c6-d83933060e85",
                    "DebugName": null
                }

I and many others have faced this issue, I hope this can help.

[James Kerman]

Welcome to the forum @Mopy, I have merged your potential solution into this thread where other members are reporting this bug.