Implement MxDisplaySurface::VTable0x24
#1261
Merged
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
|
One sec. Checking something in the beta, where we do have |
|
Nice! Two to go 😄 |
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.
As noted in the comments: almost a direct copy of
MxDisplaySurface::VTable0x28.Edit: I thought I found a difference between this and
VTable0x28near the check on thestrideandlengthvariables. We have 28 in the beta and it turns out that function had it backwards, so now they both match. Accuracy increase for beta and retail. I hand checked the diff and it looks ok, but it might be worth an in-game test.