Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warp fighting when GUI not displayed #76

Closed
TriggerAu opened this issue Nov 9, 2014 · 0 comments
Closed

Warp fighting when GUI not displayed #76

TriggerAu opened this issue Nov 9, 2014 · 0 comments
Labels

Comments

@TriggerAu
Copy link
Owner

Something I've noticed about KAC since I started playing in 0.23 and it's a minor niggle, but a niggle nonetheless.

KSP: 0.25 Winx86
Problem: Interaction between KAC and F2 (hide GUI) prevents on-rails timewarp behaving as expected
Mods installed:
KAC 3.0.1.0

Reproduction steps (ignore the A, B, C, D and bold for now):
Set KAC to automatically create alarms for manoeuvre nodes (say, a 3 minute margin, like mine now). Make a node on your orbit several minutes or hours ahead. A, Increase timewarp until B, KAC slows it down to trigger the alarm. Alarm triggers, you can C, increase timewarp to the node, whether you click the OK button on the alarm or not and KAC won't slow it down again - in other words, first, A will happen, then B, then C. This is expected. What is not expected is what happens when you hide the GUI with F2 - a continual loop of B->C->B->C etc etc. KAC and the user fight over whether the game should be increasing timewarp towards the node or decreasing it because the alarm has triggered. This only happens when you hide the GUI with F2.

It can be a little niggle if you have a long alarm margin (say, the default of 15 mins) or are trying to get a nice cinematic screenshot just before your burn and don't want "Time Warp x2(3,4,3,2,1,2,3,4 etc)" plastered across the screen. Granted, if Squad could hide that (and all the Transmitting Science and [F] Board texts) along with the rest of the GUI, that'd alleviate the problem somewhat, but there's still the fact that the user and KAC fight over timewarp when the GUI is hidden.

This can be more easily reproduced without user interaction with MechJeb and the node execution autopilot, specifically the Autowarp feature of it. MJ will increase timewarp until KAC slows it down to display the alarm, MJ increases timewarp, KAC immediately slows it down, MJ speeds it up etc etc.. I'l repeat, the GUI must be hidden for this to occur.

Source: ObsessedWithKSP at http://forum.kerbalspaceprogram.com/threads/24786-0-25-0-Kerbal-Alarm-Clock-v3-0-1-0-%28Oct-26%29?p=1530815&viewfull=1#post1530815

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant