... although now it's giving an error when trying to compile a dependent library:

   Compiling js-sys v0.3.49
error: expected `,`
   --> /Users/blakej/.cargo/registry/src/github.com-1ecc6299db9ec823/js-sys-0.3.49/src/lib.rs:639:39
    |
639 |         #[wasm_bindgen(js_namespace = Atomics, catch)]
    |                                       ^^^^^^^

In reply to @kvark:matrix.org
are you planning on using WGSL?

In reply to @blakej11:matrix.org
is there a way to get the wasm display region to scale along with the size of the browser window? at least for me it's appearing as a fixed 1024x768 box that doesn't change when I resize the window

If you’re using winit then I think it’s blocked by https://github.com/rust-windowing/winit/issues/1661 currently.

If you’re not using winit, you can resize it as you would normally in JS/CSS (there are a few ways to do it)

I am writing a little path tracer with wgpu-rs and have encountered a weird behavior.
About my setup:

I have two Textures A and B (both used as StorageTexture).

Render loop:

• Copy texture content B to A
• Execute compute shader:
  • Read from Buffer A
  • Write to Buffer B
• Execute render pass:
  • Present buffer B to screen

This works fine when I use 8bit color depth (rgba8 / Rgba8Unorm).
As soon as I switch to 16bit color depth (rgba16 / Rgba16Float) I get
weird purple artifacts in the rendered image.
When I resize the window (recreate the textures A and B) the artifacts change
and are sometimes even completely gone.

I encountered this issue on Linux (with Vulkan backend and X window manager).
I also tested it on MacOs (with Metal backend) but could not observe the issue there.

Has anybody encountered sometimes similar or has an idea what causes this?
Also: is this the right chat for this question or should I post it in the dev room?