[Merged by Bors] - Add MSAA to new renderer #3042
Closed
cart wants to merge 2 commits intobevyengine:pipelined-renderingfrom
Closed
[Merged by Bors] - Add MSAA to new renderer #3042cart wants to merge 2 commits intobevyengine:pipelined-renderingfrom
cart wants to merge 2 commits intobevyengine:pipelined-renderingfrom
Conversation
This was referenced Oct 28, 2021
superdump
approved these changes
Oct 29, 2021
Member
Author
|
bors r+ |
bors bot
pushed a commit
that referenced
this pull request
Oct 29, 2021
Adds support for MSAA to the new renderer. This is done using the new [pipeline specialization](#3031) support to specialize on sample count. This is an alternative implementation to #2541 that cuts out the need for complicated render graph edge management by moving the relevant target information into View entities. This reuses @superdump's clever MSAA bitflag range code from #2541. Note that wgpu currently only supports 1 or 4 samples due to those being the values supported by WebGPU. However they do plan on exposing ways to [enable/query for natively supported sample counts](gfx-rs/wgpu#1832). When this happens we should integrate
Contributor
|
Pull request successfully merged into pipelined-rendering. Build succeeded: |
bors bot
pushed a commit
that referenced
this pull request
Nov 3, 2021
Add an example that demonstrates the difference between no MSAA and MSAA 4x. This is also useful for testing panics when resizing the window using MSAA. This is on top of #3042 . Co-authored-by: Carter Anderson <mcanders1@gmail.com>
bors bot
pushed a commit
that referenced
this pull request
Nov 3, 2021
Add an example that demonstrates the difference between no MSAA and MSAA 4x. This is also useful for testing panics when resizing the window using MSAA. This is on top of #3042 . Co-authored-by: Carter Anderson <mcanders1@gmail.com>
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.
Adds support for MSAA to the new renderer. This is done using the new pipeline specialization support to specialize on sample count. This is an alternative implementation to #2541 that cuts out the need for complicated render graph edge management by moving the relevant target information into View entities. This reuses @superdump's clever MSAA bitflag range code from #2541.
Note that wgpu currently only supports 1 or 4 samples due to those being the values supported by WebGPU. However they do plan on exposing ways to enable/query for natively supported sample counts. When this happens we should integrate