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
Fast-forward speed limit is stored as 16-bit integer instead of 32 bits. #8768
Comments
I would be impressed if you could find a computer where you could actually manage 655x speed |
This is fully intended. You can always set it to 0 to go as fast as you can, but having the limit to 655x is already not a useful value to have. Soon there will be a GUI (I hope :P), which limits the speeds to something like 2x/4x/8x/16x/32x .. but not much more. It simply doesn't become useful from that moment on. If you have a good argument why faster than, say, 128x is useful, I would love to hear. But I am going to close this ticket for now, as we consider this "working as intended" :) Sorry :) |
What did strike me odd about your story, that the value overflowed. This was unintended, and fixed with #8769. If you meant to say that, sorry, I did not pick up on that from this ticket :) you reported a solution, so it was a bit hard to backtrack to a problem :D |
Version of OpenTTD
1.11.0-beta2
Expected result
Fast-forward speed limit is stored as a 32-bit unsigned integer, allowing for game speeds of several in-game years per second.
Actual result
Fast-forward speed limit is stored as 16-bit unsigned integer, limiting game speed to 655.35x normal if the fast-forward speed limiter is enabled.
Steps to reproduce
The text was updated successfully, but these errors were encountered: