Project

General

Profile

Bug #24415

Planetary Encounters Not Showing

Added by MistyShadows over 4 years ago. Updated about 3 years ago.

Status:
Confirmed
Severity:
Low
Assignee:
-
Category:
Map and Planetarium
Target version:
-
Start date:
11/23/2019
% Done:

10%

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

Description

Planetary or moon encounters aren't showing if the game thinks there is a different close encounter sooner.

I discovered this bug during a recent trip to Gilly.I was following a few online guides showing how to get an easy encounter with Gilly, notably Matt Lowne's guides. I had planned to capture at Eve in a highly elliptical orbit, then raise my periapsis so it intersected with Gilly's orbit, then at periapsis burn retrograde a bit so that I'd get an encounter. This "easy" encounter refused to show and I spent quite awhile trying to figure out what seemed to be an easy idea, until I by happenstance added another maneuver node past the "close encounter" which then showed my intended close encounter. I also experienced this when returning to Kerbin. This problem is also not just inherent to the maneuver nodes, but also to the actual trajectory, and I didn't see my Gilly encounter appear until a third of my way through my orbit.

My game this happened in originally is modded, so I used my other computer to install a clean version of KSP and the identical thing happened. I'm going to link to a video showing the bug, this video will be using my modded install, but note that the bug appears to be in stock KSP too.

Workaround: Add another maneuver node past the first encounter that the game shows.
Despite this workaround showing the encounter, it is difficult to tell if an encounter has actually been achieved, and makes fine-tuning it difficult.

Bug in action: https://www.youtube.com/watch?v=st-rQg1L2-g

KSP.log (460 KB) KSP.log Hopefully the log you want MistyShadows, 11/24/2019 12:02 AM
quicksave #38.sfs (368 KB) quicksave #38.sfs Quicksave displayed in my video MistyShadows, 11/24/2019 12:03 AM
quicksave (2020_02_24_14_21_36).sfs (266 KB) quicksave (2020_02_24_14_21_36).sfs boolybooly, 02/24/2020 02:27 PM
20200224142131_1.jpg (327 KB) 20200224142131_1.jpg boolybooly, 02/24/2020 02:28 PM
51517

History

#1 Updated by Anth12 over 4 years ago

I have experienced a similar issue, however the issue seems intermittent.
Any way you can supply a quicksave and ksp.log? (thats in the main ksp folder)

#2 Updated by Kirk over 4 years ago

Also, what is your conic patch limit setting?

#3 Updated by MistyShadows over 4 years ago

Anth12 wrote:

I have experienced a similar issue, however the issue seems intermittent.
Any way you can supply a quicksave and ksp.log? (thats in the main ksp folder)

Sure! I hope this is everything you need. The issue seems very reliable for me, at least regarding this particular encounter. Can't speak so much for other encounters, though as I said I did encounter it elsewhere.

#4 Updated by MistyShadows over 4 years ago

Kirk wrote:

Also, what is your conic patch limit setting?

My conic patch limit is 4. I don't think this is the problem, because as shown in my video, when I get an actual encounter with Gilly it doesn't show until halfway through my orbit.

#5 Updated by Anth12 over 4 years ago

I kind of see what you are saying, but its hard to explain it.

The log file was correct, and showed that your bug is different to the one I am investigating.

#6 Updated by boolybooly about 4 years ago

51517

Just want to say I am seeing this kind of problem in 1.9, e.g. trying to leave Mun SOI and intercept Minmus the intercept prediction suddenly gets ADHD and leaps to predict a miss 2 orbits ahead instead of following the current orbit to intercept, while adjusting the node. Even when I achieve a defacto intercept, it will not show it unless I place a zero velocity node just before the intercept.

This isnt just a one off, it happens all the time. I made a bug report about this kind of problem several years ago.

I include an f5 quicksave in case anyone is interested and a screenshot showing Minmus in an impossible predicted location, just for fun, to demonstrate how this is not working as intended. :)

#8 Updated by RafaHdz about 3 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

Also available in: Atom PDF