Project

General

Profile

Bug #25227

Surprise SOI encounters

Added by StopIteration almost 4 years ago. Updated about 3 years ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
Map and Planetarium
Target version:
-
Start date:
04/29/2020
% Done:

0%

Version:
Platform:
Linux
Expansion:
Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

While bringing an asteroid to Kerbin orbit, I had two separate instances when the game failed to show an upcoming encounter with the Mun.

I attempted to reproduce the issue in sandbox with highly elliptical and inclined orbits like the ones I had with the asteroid, but was unable to reproduce it after a couple attempts, so ultimately I just copied over the orbital parameters from the asteroid mission and got the same bug after a few orbits.

To ensure there wasn't anything unnatural about these orbital parameters, I performed an orbital rendezvous with the ship (keeping out of physics range just to be safe), but the second ship also failed to show the encounter, despite also being on a collision course with the Mun.

I found that by enabling "Always Show Closest Approach for Target", I was able to see how close the encounter would be, and I could even adjust the orbit so that this closest approach was minimized to 0.0 km. However, the SOI change still did not appear on the map, only the closest approach. Additionally, after the ship passes some point about 5 minutes before the ascending node, the closest approach marker switches to showing the closest approach for the next orbit. Adjusting other conic settings did not seem to have any effect. For the screenshots, conic patch limit was set to 3, draw mode relative.

This may be related to #24415, but I'm not sure because I am completely unable to get the encounter to appear, even by the workaround that issue mentions of placing a maneuver node after closest approach.

The bug occurs on stock KSP with no DLCs. I am using 64-bit Steam version of KSP 1.9.1 on Linux.

mun-0km.sfs (64.3 KB) mun-0km.sfs The sandbox save: a vessel on a surprise collision course with the Mun StopIteration, 04/28/2020 10:29 PM
no-markers.png (1020 KB) no-markers.png "Always Show Closest Approach for Target" disabled StopIteration, 04/29/2020 12:51 AM
closest-approach.png (950 KB) closest-approach.png "Always Show Closest Approach for Target" enabled StopIteration, 04/29/2020 12:52 AM
next-orbit.png (1.08 MB) next-orbit.png Closest approach marker switches to next orbit sometime before ascending node (near Kerbin periapsis) StopIteration, 04/29/2020 12:52 AM
still-nothing.png (1.04 MB) still-nothing.png Right outside Mun SOI, still no encounter StopIteration, 04/29/2020 12:53 AM
surprise.png (1.04 MB) surprise.png Surprise encounter! Brace for extreme lithobrake maneuver! StopIteration, 04/29/2020 12:53 AM
52258
52259
52260
52261
52262

History

#1 Updated by StopIteration almost 4 years ago

  • Description updated (diff)

#2 Updated by StopIteration almost 4 years ago

  • Description updated (diff)

#3 Updated by StopIteration almost 4 years ago

  • Version changed from 1.9.1 to 1.10.0

Bug still exists in 1.10.0

Also available in: Atom PDF