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

WebGL: format Depth24PlusStencil8 can't be multisampled #2726

Closed
maxammann opened this issue Jun 3, 2022 · 1 comment · Fixed by #2854
Closed

WebGL: format Depth24PlusStencil8 can't be multisampled #2726

maxammann opened this issue Jun 3, 2022 · 1 comment · Fixed by #2854
Labels
api: gles Issues with GLES or WebGL type: enhancement New feature or request

Comments

@maxammann
Copy link
Contributor

Description
I recently updated from the wgpu-hal 0.12.5 to the latest master (as of yesterday). As a result my demo failed for WebGL: https://maplibre-rs-demos.pages.dev/webgl/

panicked at 'wgpu error: Validation Error

Caused by:
    In Device::create_render_pipeline
    depth/stencil state is invalid
    format Depth24PlusStencil8 can't be multisampled

', /home/runner/.cargo/git/checkouts/wgpu-53e70f8674b08dd4/9e3cd08/wgpu/src/backend/direct.rs:2286:5

Repro steps
Run the demo of: https://github.com/maplibre/maplibre-rs

Expected vs observed behavior
I think this multisampling should be allowed.

Extra materials

Platform
Firefox

@maxammann
Copy link
Contributor Author

Got he same error when running headlessly on egl:

error: XDG_RUNTIME_DIR not set in the environment.
thread 'main' panicked at 'wgpu error: Validation Error
Caused by:
    In Device::create_render_pipeline
    depth/stencil state is invalid
    format Depth24PlusStencil8 can't be multisampled
', /home/runner/.cargo/git/checkouts/wgpu-53e70f8674b08dd4/9e3cd08/wgpu/src/backend/direct.rs:2286:5
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: wgpu::backend::direct::default_error_handler
   3: core::ops::function::Fn::call
   4: wgpu::backend::direct::ErrorSinkRaw::handle_error
   5: <wgpu::backend::direct::Context as wgpu::Context>::device_create_render_pipeline
   6: maplibre::render::resource::pipeline::RenderPipelineDescriptor::initialize
   7: <maplibre::render::stages::PrepareStage as maplibre::schedule::Stage>::run
   8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
   9: criterion::bencher::AsyncBencher<A,M>::iter
  10: criterion::benchmark_group::BenchmarkGroup<M>::bench_function::{{closure}}
  11: <criterion::routine::Function<M,F,T> as criterion::routine::Routine<M,T>>::warm_up
  12: criterion::analysis::common
  13: render::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

@cwfitzgerald cwfitzgerald added api: gles Issues with GLES or WebGL type: enhancement New feature or request labels Jun 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: gles Issues with GLES or WebGL type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants