-
Notifications
You must be signed in to change notification settings - Fork 432
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
--[PBR Update 1 of 3] Map materials' extension/layer data to Drawables cache #2112
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
f2b204b
--initial commit for mapping extensions to pbr drawable cache.
jturner65 404e71a
--improve flags comparison
jturner65 c17bc64
--cleanup debug spam
jturner65 b5456be
--structs for layers in cache
jturner65 cf1a98c
--improve material access
jturner65 9e9e2ad
--remove unnecessary check for normaltexture scale
jturner65 4d545cc
--add anisotropy extension support
jturner65 fced5cb
--reviewer suggestions; cleanup
jturner65 16947e0
--reviewer suggestions
jturner65 558cf72
--remove check for non-zero
jturner65 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Why do we compare flags with >=? Isn't flags basically a bitfield?
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.
that's how magnum compares multi-bit flags
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.
Docs for reference,
>=
is chosen because it looks close to a ⊇, a symbol for a superset.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.
Ok so, what the heck do these lines mean? :) Is it testing whether
flags_
includesInstanceObjectId
?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.
Yes. It's a shorthand for
(a & other) == other
, as the docs say. It does exactly what it did before -- checking if one set of bits is a superset of the other set -- just in a more concise way.