We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo run --color=always --package prisma --bin prisma --profile release -- scenes/damaged_helmet.glb
[1/4] 📜 Parsing and loading the scene... thread 'main' panicked at /Users/iceice666/.cargo/registry/src/index.crates.io-6f17d22bba15001f/naga-22.1.0/src/back/msl/writer.rs:286:21: internal error: entered unreachable code: metal requires all arrays be constant sized stack backtrace: 0: _rust_begin_unwind 1: core::panicking::panic_fmt 2: <naga::back::msl::writer::TypeContext as core::fmt::Display>::fmt 3: core::fmt::write 4: naga::back::msl::writer::TypedGlobalVariable::try_fmt 5: naga::back::msl::writer::Writer<W>::write_functions 6: naga::back::msl::writer::Writer<W>::write 7: naga::back::msl::write_string 8: wgpu_hal::metal::device::<impl wgpu_hal::metal::Device>::load_shader 9: objc::rc::autorelease::autoreleasepool 10: wgpu_core::device::resource::Device<A>::create_compute_pipeline 11: wgpu_core::device::global::<impl wgpu_core::global::Global>::device_create_compute_pipeline 12: <wgpu::backend::wgpu_core::ContextWgpuCore as wgpu::context::Context>::device_create_compute_pipeline 13: <T as wgpu::context::DynContext>::device_create_compute_pipeline 14: wgpu::Device::create_compute_pipeline 15: prisma::render::renderer::Renderer::new 16: prisma::main note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace. Process finished with exit code 101
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Environment
cargo run --color=always --package prisma --bin prisma --profile release -- scenes/damaged_helmet.glb
LOG
The text was updated successfully, but these errors were encountered: