![]() When you notice you're at the closest point to your target (the target is starting to get further away again), fire your engines and get the relative velocity to near zero. The retrograde marker now points out the relative velocity between you and the target ship. Before you reach the same intersection point again (a few minutes before, with the target ship hopefully now nearby within 10-50km and getting closer), make sure the reference of the navball is set to "Target" (I think it changes automatically when you're close enough to your target) and aim towards retrograde velocity. Getting separation to be less than 100km might be "good enough", but with a little more effort you can probably bring it to less than 10 km, which makes the next phase a lot easier. A good way to do this is to pass the intersection point by a few seconds (so that you can see the future prediction after one orbit), and then do the prograde/retrograde burn to match the target position to the intersection position. You would usually want fire prograde or retrograde at one of these intersections to change the period of your orbit, so that you can get the separation (target position at intersection) as close as possible for the next time you intercept. Not sure if we are talking of the same thing but the intersect markers often shows 2 intersections and the relative target positions at the time of the intersection. Send us a message with proof, and we'll give you some flair to show it! Disable header animation Enable header animation Δ | Support/bug reports | KerbalAcademy | ConsoleKSP Last contest's winner: forteefly1998! Have you developed a mod? See this page for more infoĬommunity Teamspeak Server Refrain from submitting images that involve real life space disasters that resulted in loss of lifeĭon't post/discuss mirrors or torrents of any version of KSP ![]() See the discussion on misc posts for more info No posts unrelated to KSP or memes and image macros. Please remain kind and civil at all times
0 Comments
Leave a Reply. |