Webgpu, depth sample count mismatch warning with antialias on

[yankun_yang]

Hi all!

Several questions arise when playing with WebGPU. I’m not sure if these are related to my implementations. Highly appreciate if someone could explain.

1. 
   Getting this warning with antialias on, it’s not blocking me from running the code per say, but does it mean antialias won’t be functional with webgpu, at least for now?
   2. Getting this error when injecting inspector to webgpu renderer. I’m getting this error only with R3F - is someone else encountering this issue and is this specific to R3F only? If so, why? (I also asked in r3f channel but haven’t got any answer yet).
   

[Mugen87]

@yankun_yang

Getting this error when injecting inspector to webgpu renderer. I’m getting this error only with R3F - is someone else encountering this issue and is this specific to R3F only? If so, why? (I also asked in r3f channel but haven’t got any answer yet).

This probably happens because the animation loop is not defined with renderer.setAnimationLoop() which is a prerequisite for Inspector usage. With the next release, the Inspector is going to log a proper warning instead of throwing a runtime error.

Do you mind demonstrating the sample count warning with a live example? Use below fiddle as a starter template: three.js dev template - module - JSFiddle - Code Playground