[SOLVED] Came back to my save from a year ago and a ship is in a bizarre situation I don't understand

[VasimrVasimrovich]

As the title says. This ship was supposed to go to Eve, but I'm not seeing an intercept or even a closest approach. I tried setting up some manouvers but I can't seem to fix the situation. Also, it has a weird manouver node (from a year ago) and I don't know what that's supposed to do. If I remember right, I did launch this at the transfer window.

Please tell me if this ship can still get to Eve and what do I need to do.

 

The situation

Spoiler

The manouver node

Spoiler

 

Edited February 22, 2021 by VasimrVasimrovich

[VoidSquid]

Hmm... are you playing directly via Steam, i.e. your active KSP installation is in the \Steam\steamapps\common\Kerbal Space Program folder? If yes, Steam probably did an auto update and with that, ruined your KSP installation.

Solution in that case: revert to the KSP version you had when playing last time.

Never play KSP directly from the Steam folder and have Steam running. Instead, copy your KSP folder to a location outside any "special folder (like C:\Program Files (x86)", and only play from there.

The three rules when working with computers:

1. Always have a backup copy.
2. Always have a backup copy.
3. And most important rule: always have a backup copy.

Edited February 22, 2021 by VoidSquid

[VasimrVasimrovich]

This is version 1.2.2 that I'm playing outside of the Steam directory. I played on this version a year ago, then some time later made a separate install (of the newest version) in a different folder through Steam and played that for a while. Now I went back to the old copy. This copy has never been launched through Steam or from the Steam directory.

[Guest]

I can only think of 2 possible solutions.

1) KAC stores the original maneuver node I think so remove that weird node and warp to alarm then restore node from the alarm pop up (don't save or backup in case it doesn't work)

2) check conics mode on precise node.

[VoidSquid]

1 hour ago, VasimrVasimrovich said:

This is version 1.2.2 that I'm playing outside of the Steam directory

Oh... now I'm almost out of my wits. The very same installation you used earlier, no changes (updates, mods, ...), right?

Either try to delete and recreate the node, what @FruitGoose suggested. Or, if that doesn't work, we'll have to go deeper to try to analyze this, for that we'll need log files, see here 

 

[king of nowhere]

well, that node clearly is not an eve manuever. it won't intercept eve's orbit. you can see that apoapsis and periapsis are wrong. also, plane inclination.

you are better off planning the manuever again. it's just an eve intercept, with a plane change manuever to set inclination to 0. easy to make anew.

 

on second analysis, there is indeed something very wrong with that orbit. it says periapsis in 3 yers and apoapsis in 7 years. that's an 8 years orbit, for staying inside kerbin's orbit. it should not be possible to have an orbit longer than one year. but the problem then is not the manuever node. unless the time is the result of some other mod i'm not aware of, you certainly have plenty of popup mod windows on your screen. but for now try to replot the manuever

Edited February 22, 2021 by king of nowhere

[VasimrVasimrovich]

Thanks for the replies everyone. The solution was much simpler though, and I made a stupid mistake. I turned on hacked gravity while testing some other vessel and forgot to turn it off when switching to this one. I just launched the game again and the orbit is mostly right, with a closest approach that needs some fine tuning.

Sorry for wasting your time with my dumbness

[VoidSquid]

3 minutes ago, VasimrVasimrovich said:

and I made a stupid mistake

What idiot told you to repeat my silly mistakes?  

Glad you could sort this out, happy flying then  

Edited February 22, 2021 by VoidSquid

[lemon cup]

5 minutes ago, VasimrVasimrovich said:

I turned on hacked gravity while testing some other vessel and forgot to turn it off when switching to this one

I made the exact same mistake yesterday  tried flying a newly redesigned Mun rocket on a mission and thought I had grossly over budgeted dV.