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

ETA:TRANSITION is broken #7

Closed
tsbockman opened this issue Mar 14, 2014 · 0 comments
Closed

ETA:TRANSITION is broken #7

tsbockman opened this issue Mar 14, 2014 · 0 comments
Assignees
Labels
bug Weird outcome is probably not what the mod programmer expected.

Comments

@tsbockman
Copy link

This stat seems like it should be really useful for predicting SOI changes, but as far as I can tell the number it returns is always too high - sometimes by quite a lot.

To demonstrate: manually set up an encounter with the Mun, then run the following command in the KOS terminal:

add node(time:seconds + ETA:transition, 0, 0, 0).

Go to map view and focus on the Mun. Compare the ETA reported by the stock UI for the encounter to that of the new maneuver node, and you will see that they do not match as they should.

When I tried this a second ago, the node was placed about 5 minutes after the actual transition; that is the closest I have seen it. Earlier tests averaged a separation of more like 20 minutes, but sometimes it is off by hours.

@marianoapp marianoapp added the bug label Mar 16, 2014
@marianoapp marianoapp self-assigned this Mar 16, 2014
erendrake pushed a commit that referenced this issue Apr 9, 2015
Pulling development branch updates
erendrake pushed a commit that referenced this issue May 13, 2015
Pulling changes from the main repo
erendrake pushed a commit that referenced this issue May 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Weird outcome is probably not what the mod programmer expected.
Projects
None yet
Development

No branches or pull requests

2 participants