Error compiling and running example `runners/ash`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behaviour
Example runners/ash compiles and runs.
Example & Steps To Reproduce
git clone https://github.com/Rust-GPU/rust-gpucd rust-gpu/yard-rs/example-xp/rust-gpu/examples/runners/ashcargo run --release- error:
thread 'main' panicked at examples/runners/ash/src/main.rs:255:10:
called `Result::unwrap()` on an `Err` value: CratePathDoesntExist("examples/shaders/sky-shader")
Following the working example multibuilder, one can change the error line from
SpirvBuilder::new("examples/shaders/sky-shader", "spirv-unknown-vulkan1.1")
to
SpirvBuilder::new(concat!(env!("CARGO_MANIFEST_DIR"), "/../../shaders/sky-shader"), "spirv-unknown-vulkan1.1")
Now the example and the shader crate compiles, but running it gives an error
[mvk-error] VK_ERROR_EXTENSION_NOT_PRESENT: Vulkan extension VK_KHR_shader_non_semantic_info is not supported.
thread 'main' panicked at examples/runners/ash/src/main.rs:441:22:
called `Result::unwrap()` on an `Err` value: ERROR_EXTENSION_NOT_PRESENT
This might be fixable by updating ash, or might not be fixable at the moment. In the latter case, an explicit "support matrix"-ish table would be nice.
System Info
- Rust:
rustc 1.79.0-nightly (244da22fa 2024-04-23) - OS: MacBook Pro M1, 16-inch, 2021, macOS 14.4.1 (23E224)
- GPU: Integrated
- SPIR-V:
SPIRV-Tools v2024.3 unknown hash, 2024-06-20T14:29:42+00:00
Backtrace
N/A
Backtrace
<backtrace>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running cargo run --release in examples/runners/ash and inspect examples/runners/ash/src/main.rs around lines 255 and 441. Compare its shader path handling with the working multibuilder example and investigate the reported VK_KHR_shader_non_semantic_info failure on macOS. Done means the example runs, or its unsupported requirements are documented in an explicit support matrix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100