Fix libretro frontend bug #147
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
…55 and libretro will expect RGB565 This involved some more fixes as Im really confused between RGB and BGR I hope Im correct with the comments and names but im not sure. Now Pixel is a RGB565 since this format is more popular. Also fixed some typos
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.
The problem is the core outputs the data as RGB555 and libretro will expect RGB565 (it can accept ARGB1555 but it is not recommended)
This involved some more fixes as Im really confused between RGB and BGR I hope Im correct with the comments and names but im not sure.
Now Pixel is a RGB565 since this format is more popular.
Also fixed some typos