Firefox still lacks support for a number of features, like video texture. WebGPU v1 has not yet been shipped in Firefox. I think they aim for end of this year for the official launch.
The Milestone 0 looks like a v1, but there is no official announcement, nor a ratified release on w3c.
With the spec work goes on without a ratified release and browsers implementing their own subset of diff versions of webgpu draft, I’m wondering if we are reaching the chaos era like before es6, and making it much harder for libs to detect which subset of features to use.
Just to chime in that frame graph (from the docs) vs firefox also throws error:
Encountered one or more errors while creating shader module "BabylonWebGPUDevice0_CopyVideoToTexture_FragmentShader_DontInvertY"
Since firefox shipped webgpu recently, I’ve seen loads of errors against my test bed (Seedborn). Obviously, firefox are not ready for prod yet. Its not a bjs issue.
erm, since when was the browser era not chaotic? IE, Netscape all the way to now…never an era of conformity.
Not really. Support for WebGPU is constantly evolving in Firefox, so we would have to check every day what is now supported and what is not. Also, something could be half supported and work in some cases and not some others. I think we have just to wait that they officially announce that v1 has been released before checking that everything is working correctly with Babylon. Also, there’s Safari support which is not yet finalized.