Fix dx12 shader validation errors when dxil.dll isn't available in the local scope. #3434
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.
Checklist
cargo clippy
.RUSTFLAGS=--cfg=web_sys_unstable_apis cargo clippy --target wasm32-unknown-unknown
if applicable.Connections
Fixes #3433
Description
When using a custom path for dxil.dll that isn't in the local scope, dxcompiler's automatic validation will silently fail. This makes it so that if dxil.dll has a custom path, then we disable automatic validation and do manual validation post compilation instead.
Testing
Tested against
hello-triangle
with a customdxil.dll
path and nodxil.dll
in the wgpu folder.