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

Speed values are slightly off when using metric units #74

Closed
Andrew350 opened this issue Dec 20, 2019 · 1 comment
Closed

Speed values are slightly off when using metric units #74

Andrew350 opened this issue Dec 20, 2019 · 1 comment

Comments

@Andrew350
Copy link

@Andrew350 Andrew350 commented Dec 20, 2019

Note: I'm using the (very) old NML executable for Windows to make an NRT roadset, if that makes a difference. I don't think anything has been changed to this effect lately, but just in case, I wanted to mention it.

Expected Result

When defining speeds for some feature in km/h or m/s, the in-game speeds should be exactly as defined.

Actual Result

The displayed speeds in-game are slightly different than what is defined by the NewGRF. As an example, I've attached a simple NewGRF (and NML file) which clearly defines a roadtype with a speed of 50 km/h; however in-game the speed is reported as 49 km/h. A similar effect is observed with m/s.

This feels like some kind of rounding error or something, perhaps due to the weird units OpenTTD uses internally, but that's just an uneducated guess 🤷‍♂ Whatever the case, this probably affects other things as well, but I haven't tested that to find out.

speedbug.zip

@planetmaker
Copy link
Contributor

@planetmaker planetmaker commented Dec 20, 2019

This probably is a duplicate of #35 or solved by that

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

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.