WebGPU: VideoTexture Firefox Issue

Hi

I’m getting an error in Firefox (Latest Version - on Windows) in combination with a video texture.

WebGPU compilation info for shader module "BabylonWebGPUDevice0_CopyVideoToTexture_FragmentShader_InvertY" (1 error(s), 0 warning(s), 0 info)
 Shader 'BabylonWebGPUDevice0_CopyVideoToTexture_FragmentShader_InvertY' parsing error: unknown type: `texture_external` ┌─ wgsl:3:45 │ 3 │ @group(0) @binding(1) var videoTexture: texture_external; │ ^^^^^^^^^^^^^^^^ unknown type

It’s working fine with chrome.

Here is a playground link:

Thx for having a look.

Cc @Evgeni_Popov

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.

2 Likes

But is there really a ratified WebGPU v1? I only saw drafts on w3c.

Yes, for the time being, it seems Chrome didn’t officially announce v1 (Chrome ships WebGPU  |  Blog  |  Chrome for Developers). Here are the milestones that are defined for the WebGPU spec:

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? :laughing: IE, Netscape all the way to now…never an era of conformity.

Ah ok. Can we somehow detect which features are not usable? I mean without video textures WebGPU seems to be working fine already in Firefox

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.

Ok. All right. Thank you :slight_smile: