-
Notifications
You must be signed in to change notification settings - Fork 39
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
tr2: migrate to common BOUNDS_16 #2255
Conversation
This replaces TR2's BOUNDS_16 to use the same as TR1, so we have two XYZ16s rather than individual values for each component.
TR2 frame bounds can now be assigned in the same way as TR1.
Download the built assets for this pull request: |
Found an issue with smashable windows and bells, they're a bit awkward to shoot now. Investigating. |
The original approach relied on the layout of BOUNDS_16 to check smashables, so this updates the checks to use exactly the properties we need.
Fixed. Would appreciate a glance over and test to confirm. Will squash the separate commit into the main one later. The original code relied on the layout of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The windows/bells behaviour is working as expected. LGTM.
Checklist
Description
This replaces TR2's
BOUNDS_16
to use the same as TR1, so we have twoXYZ16
s rather than individual values for each component. No logical changes, this is pretty much just renaming properties.TR2 frame rot expansion next, which should get us to equal handling for both games.