Fix #5249: No collision detection when building ride entrance at heights > 85.5m #10473
+3
−2
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
IntelOrca
approved these changes
Dec 30, 2019
… at heights > 85.5m
Gymnasiast
force-pushed
the
fix/10468
branch
from
f9820db
to
ad00f14
Compare
XplosiveLugnut
pushed a commit
to XplosiveLugnut/OpenRCT2
that referenced
this pull request
Apr 27, 2020
… at heights > 85.5m (OpenRCT2#10473)
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.
When doing #10468 , I remembered a similar bug, so I decided to look into that one as well. As I expected, it was caused by an overflowing 8-bit signed integer.