Bug #786
Intercept points on map flickering
100%
Description
When setting up a coplanar orbit with 2 intercepts, the intercept points (intercept 1 & 2, target position at intercept 1 & 2) flicker very rapidly. hovering over them produces tooltips which also flicker between different points of interest. burning in any direction usually fixes this but makes rendezvous more difficult
KSP version 0.20.2.186
OS Win 7 64 bit
GPU: ATI HD 6870
The attached images were taken in quick succession but dont show "target position at intercept" points. flicker rate is high (like a bad flourecent lamp flickering)
History
#1 Updated by n00b1c1d3 over 11 years ago
Just noticed that placing a maneuver node sometimes stops the flickering
#2 Updated by doctorzuber over 11 years ago
this is normal for a circular orbit.
What is happening is the simple act of firing RCS to change your orientation is altering your orbit. The closer your orbit gets to a perfect circular orbit, the more jumpy the nav points get.
The only "bug" here is the fact that you can change your orientation with RCS turned off. This is a physics shortcut, and it does cause bouncing nodes even though they aren't actually changing at all. The game doesn't actually change the orbit for this free rotation, so the bouncing is a visual nuisance that maybe should be fixed for a final version, assuming that free rotation isn't simply removed entirely to increase realism.
#3 Updated by Ruedii over 11 years ago
This problem also ocurres on Linux with Ascending Nodes, descending nodes, planet intercepts, peripexes, and apopexes under various circumstances.
They flicker and twitch in various patterns. It is usually caused by close matching of the values being compared to create these points. However, I have not figured out what causes the planetary intercept points to flicker, but those tend to stop doing that once I move closer to them.
The flicker and twitching does not occur during time warp. This is likely because it is not recalculating the path during these times.
#4 Updated by Whitey04 about 10 years ago
- Status changed from New to Confirmed
- % Done changed from 0 to 10
In no condition should this be "normal". The GUI probably needs some hysteresis such that when intercept 1 & 2 keep swapping places it keeps one set rather than showing effectively neither.
When this happens it's impossible to use the interface to perform a rendezvous as none of the intercept markers are usable. Sometimes adding a node (and changing delta-V on it) will break the intercepts out to a usable state but it's only a workaround.
KSP 0.25
#6 Updated by Squelch over 9 years ago
- Platform Win32 added
- Platform deleted (
Windows)
#7 Updated by sal_vager about 9 years ago
- Severity changed from Normal to Very Low
This issue is caused by the limitation of numeric integration, and is not fixable.
#8 Updated by TriggerAu over 8 years ago
- Status changed from Confirmed to Needs Clarification
- % Done changed from 10 to 0
#9 Updated by TriggerAu over 8 years ago
- Status changed from Needs Clarification to Closed
- % Done changed from 0 to 100
Closing this report out for now. If you find it is still occuring in the latest version of KSP please open a new report (and this one can be linked to it.) For best results, the wiki contains really useful info for when creating a report http://bugs.kerbalspaceprogram.com/projects/ksp/wiki.
You can also ask questions about the bug cleanup in the forum here: http://forum.kerbalspaceprogram.com/index.php?/topic/143980-time-to-clean-up-the-bug-tracker/ and tag @TriggerAu to get my attention