Hi
Does anybody know why there are those display-artifacts on Firefox?
Chrome, Edge and Safari
Engine 2.9.2
Kind regards
Alain
Hi
Does anybody know why there are those display-artifacts on Firefox?
Chrome, Edge and Safari
Engine 2.9.2
Kind regards
Alain
That’s certainly unexpected. Are you able to share a repro? I just tried few engine examples: PlayCanvas Examples
and they work on my end - Firefox 141 on MacOS.
How do I share a project?
There are some errors in the console:
ASSERT FAILED: RenderPass cannot be started while inside another render pass. launch.js:980:2372
Vertex buffer element location 0 used by [POSITION] is already used by element [POSITION], while rendering [Pass:RenderPassForward RT:WebgpuFramebuffer | Camera: Camera, Layer: World(OPAQUE) | Node: Plane, Material: label-musterwohnung] launch.js:980:2372
Vertex buffer element location 1 used by [NORMAL] is already used by element [NORMAL], while rendering [Pass:RenderPassForward RT:WebgpuFramebuffer | Camera: Camera, Layer: World(OPAQUE) | Node: Plane, Material: label-musterwohnung] launch.js:980:2372
WebGPU RenderPipeline creation validation error: Two or more vertex attributes were assigned to the same location in the shader: 0 <empty string> while rendering Pass:RenderPassForward RT:WebgpuFramebuffer | Camera: Camera, Layer: World(OPAQUE) | Node: Plane, Material: label-musterwohnung
Object { renderPipeline: {…}, desc: {…}, shader: {…} }
launch.js:980:2372
WebGPU RenderPass validation error: In a set_pipeline command, caused by: RenderPipeline with 'RenderPipelineDescr-12' label is invalid <empty string> while rendering <empty string>
Object { renderPass: {…} }
Edit:
Your example looks fine on my machine.
Maybe you can open this?
https://launch.playcanvas.com/2262097?debug=true
Works great on Mac
I see some issues with rendering of ‘label-musterwohnung’ based on that log. Try and disable that to test.
I also see you use WebGPU … this is very new in Firefox, try WebGL?
In Firefox 140.0.4 those artifacts didn’t occur. They are only in Firefox 141.0.
When I disable “WebGPU” in PlayCanvas, then everything looks fine
Firefox released WebGPU support in 141. In 140, WebGL would be used at all times.
Well then they have to put more love into WebGPU
yes, they have about 8 issues in their tracker with our example being a repro. It will get better.