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.
Connections
Revival of #3966
Description
Enable some interop with native graphics APIs. I'm not convinced that this is in any way a good idea. Users have to be extremely careful about not accidentally taking locks on or destroying resources while using them from native dispatches. They also have to consider pipeline barriers and image transitions themselves, with no help from wgpu in tracking them. To work around this in Bevy, I plan to bind the resources to a dummy compute pass that does nothing, but that's run before+after my native graphics API to try and coerce wgpu into tracking the lifetimes and barriers appropriately. This is very much a band-aid patch while I wait for a proper fix in #4067.
Testing
Will be tested as part of Bevy's FSR integration bevyengine/bevy#12768.
Checklist
cargo fmt
.cargo clippy
. If applicable, add:--target wasm32-unknown-unknown
--target wasm32-unknown-emscripten
cargo xtask test
to run tests.CHANGELOG.md
. See simple instructions inside file.