-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Make ClearColorConfig::None work correctly (esp in the presence of MSAA)
#23844
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
Merged
+85
−56
Merged
Changes from 4 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
8630cca
Cache ping pong atomics for view targets.
tychedelia 554eeb1
Writeback when loading.
tychedelia c2593a4
Ci.
tychedelia ac26219
Ci.
tychedelia c9a15f7
Clean-up old entries.
tychedelia 71bc8b6
Use entry API.
tychedelia e770b3c
Merge branch 'main' into view-target-fixes
tychedelia 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 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
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
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.
Can use
HashMap.entryIs it correct to use
Weak<AtomicUsize>, won’t it be dropped at the start of each frame?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.
Basically, we re-insert the
ViewTargetevery frame. As long as the configuration doesn't change, this is just replacing the effective same component over and over again. So there is an existing strong handle on the component, which we will replace here. I forgot to add the clean-up at the top of the system, but it's basically a cheap way to see if an entry is actually being used. I also just switched to using the actual entry api here, thanks!