Fix Vulkan surface capabilities being advertised when its query failed. #6510
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
I'm sure there's related tickets, but it's hard to dig up :/
Description
Observed in the wild Vulkan adapter gets chosen despite the surface being not compatible (e.g. causing a Vulkan adapter to be chosen over a working GL adapter). This happend because Vulkan backend violated the contract of returning usable surface configs.
Extending
GetSurfaceSupportError
is somewhat unrelated. More of a desperate attempt to output more information.Testing
I unfortunately don't have a repro case for any of these failures.
Checklist
cargo fmt
.taplo format
.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.