Jump to content

Manipulating a maneuver node causes the wrong trajectory or broken trajectory


Hartrule

Recommended Posts

  • KSP Version 0.1.1.0.21572
  • Operating System  Windows 10

Got a vessel that uses xenon engines in an normal orbit around kerbin and when adding a maneuver node then adding some prograde to it looks like the the trajectory can't calculate it an turns into strange collision course. 

Don't know whether its the vessel as its using 4 xenon engines and a lot of xenon or it thinks it has over 27k deltaV, that it can't path a normal route out?

Took a pic:?imw=5000&imh=5000&ima=fit&impolicy=Lett

Wanted to flag it up, can still carry though, just manually plotting a course and doing it by eye should work, in theory

Edited by Hartrule
Link to comment
Share on other sites

41 minutes ago, Hartrule said:
  • KSP Version 0.1.1.0.21572
  • Operating System  Windows 10

Got a vessel that uses xenon engines in an normal orbit around kerbin and when adding a maneuver node then adding some prograde to it looks like the the trajectory can't calculate it an turns into strange collision course. 

Don't know whether its the vessel as its using 4 xenon engines and a lot of xenon or it thinks it has over 27k deltaV, that it can't path a normal route out?

Took a pic:?imw=5000&imh=5000&ima=fit&impolicy=Lett

Wanted to flag it up, can still carry though, just manually plotting a course and doing it by eye should work, in theory

Look how long your burn is.  It is longer than the period of your orbit by an order of magnitude at least.  You don't have enough thrust to weight ratio to perform that burn quick enough to maintain the burn vector without colliding with Kerbin.  The display is doing its best to communicate this situation

41 minutes ago, Hartrule said:
  •  

You need to split the burn up over multiple orbits

Edited by darthgently
Link to comment
Share on other sites

 

11 hours ago, darthgently said:

Look how long your burn is.  It is longer than the period of your orbit by an order of magnitude at least.  You don't have enough thrust to weight ratio to perform that burn quick enough to maintain the burn vector without colliding with Kerbin.  The display is doing its best to communicate this situation

You need to split the burn up over multiple orbits

Thanks for the info, the burn duration is exaggerated wanted to see if it would eventually exit the orbit. Will try the burns after each orbit. Next time I'm on, thanks again. 

Link to comment
Share on other sites

×
×
  • Create New...