Skip to content
New issue

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

Bevy and winit examples won't run on macOS Monterey 12.6.2 on a MacBook Pro (Retina, 15-inch, Mid 2015) #253

Closed
bitec0de opened this issue Jan 16, 2023 · 2 comments

Comments

@bitec0de
Copy link

This was the output on running cargo run -p with_winit

warning: `vello` (lib) generated 10 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.26s
     Running `target/debug/with_winit`
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_compute_pipeline
    Internal error: new_compute_pipeline_state: "Compiler encountered an internal error"

', /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
stack backtrace:
   0: rust_begin_unwind
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/panicking.rs:65:14
   2: wgpu::backend::direct::default_error_handler
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
   3: core::ops::function::Fn::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:78:5
   4: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/alloc/src/boxed.rs:2001:9
   5: wgpu::backend::direct::ErrorSinkRaw::handle_error
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2389:17
   6: wgpu::backend::direct::Context::handle_error
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:254:9
   7: <wgpu::backend::direct::Context as wgpu::Context>::device_create_compute_pipeline
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:1462:13
   8: wgpu::Device::create_compute_pipeline
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/lib.rs:2202:17
   9: vello::engine::Engine::add_shader
             at ./src/engine.rs:215:24
  10: vello::shaders::full_shaders
             at ./src/shaders.rs:138:26
  11: vello::Renderer::new
             at ./src/lib.rs:57:23
  12: with_winit::run::{{closure}}
             at ./examples/with_winit/src/main.rs:57:24
  13: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/future/mod.rs:91:19
  14: pollster::block_on
             at /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/pollster-0.2.5/src/lib.rs:125:15
  15: with_winit::main
             at ./examples/with_winit/src/main.rs:213:9
  16: core::ops::function::FnOnce::call_once
             at /rustc/69f9c33d71c871fc16ac445211281c6e7a340943/library/core/src/ops/function.rs:251:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

with -p with_bevy it was

warning: `vello` (lib) generated 10 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.62s
     Running `target/debug/with_bevy`
2023-01-16T10:37:25.132773Z  INFO bevy_render::renderer: AdapterInfo { name: "Intel Iris Pro Graphics", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
2023-01-16T10:37:25.477810Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default    
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_compute_pipeline
    Internal error: new_compute_pipeline_state: "Compiler encountered an internal error"

', /Users/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5

..and then continued the same

@DJMcNab
Copy link
Member

DJMcNab commented Jan 16, 2023

Do the wgpu examples run?
Specifically, the boids example uses compute shaders.

Additionally, does the bevy compute_shader_game_of_life example run?

It is probably also worth asking on the wgpu matrix about this.

Unfortunately, the panic line corresponds to the very first shader; that suggests that your metal compiler does not support compute shaders at all.

@bitec0de
Copy link
Author

bitec0de commented Jan 16, 2023

wgpu boids doesn't run, no: zsh: segmentation fault cargo run --example boids

EDIT: nor compute_shader_game_of_life, it just outputs:

2023-01-16T11:04:28.532547Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default    
thread 'main' panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_bind_group
    the adapter does not support read access for storages texture of format Rgba8Unorm

sorry, this wasn't your fault; i'd assumed after having just upgraded the OS the graphics drivers would all work

shame wgpu won't work with 2015 hardware, i hope Piet remains a rendering option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants