Open
Conversation
Member
|
Thank you for identifying and providing a fix. I only have two concerns:
|
Author
Sorry, I don't have much test that cover all the case, I only test on the case of OriginUpperLeft and YAxisPointsDown which is the default case, with a project called Melonds on switch. I fix the rendering problem with source code compiled deko3d.
I can simplify it, but the reason I fix it in this way is for readability, since |
Author
|
Here is logic table:
|
This file contains hidden or 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
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.
Motivation
deko3d/source/dk_device.h
Lines 100 to 102 in 8cb7b4c
The implementation is not consistent with the comment. We intend to flip Y when
UpperLeft mode with Y pointing up. But in this case,!isYAxisPointsDown() = trueand!isOriginLowerLeft() = true,true ^ true = false. Same asLowerLeft mode with Y pointing down.Key Change
The fix is simple, I think the comment is the correct logic, so just add a
!before return.