Fix ottd_display_speed to reflect changes done in OpenTTD #35
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Since checks are enabled, a rebase to master is required to include workflow file. |
planetmaker
reviewed
Dec 9, 2019
This was referenced Dec 20, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
736f034 fixed rounding errors with nml->nfo conversion, however the ottd_display_speed function has not been updated to reflect changes done in OpenTTD/OpenTTD@7634416. Specifically, the display value should be divided only after all other conversions have been done. The updated version of the function fixes the many off-by-one rounding errors currently present with nml coded vehicles.