MeshInstance with Mesh Material Billboard Mode bug on web export (GLES3)

[jayypluss]

Godot version

3.4.4

System information

ubuntu-20.04 (in which Github Actions is using to build), Firefox (to run deployed project)

Issue description

My Github Action Web Export present problems on collectables objects that I have in the game that are MeshInstances with QuadMeshes of which the material's texture is a 2D image and Billboard Mode Enabled.

• The Repo
• The Game
• The Issue

I can't reproduce this locally on localhost webserver, not with my project and not with Minimal reproduction project attached. I am only reproducing and testing it after deploying (to Game link above). Haven't tried deploying Minimal reproduction project yet.

Build actions:

• https://github.com/jayypluss/BreezyWave/blob/main/.github/workflows/push-export.yml
• https://github.com/jayypluss/BreezyWave/actions/runs/2425815227
• https://github.com/jayypluss/BreezyWave/runs/6701741938?check_suite_focus=true

Evidences:

https://user-images.githubusercontent.com/17395606/171698978-7763a589-6220-4b95-b617-c55c711306b9.mp4

https://user-images.githubusercontent.com/17395606/171698971-06218b3b-2e46-4164-8491-ce34198c0194.mp4

Steps to reproduce

• Create MeshInstance
• Add Quad Mesh as Mesh
• Add new Material
• Enable Billboard Mode for this material (under Parameters)
• Enable Use Alpha Scissor
• Add an image with transparent background as texture of the Material

Minimal reproduction project

I did this minimal project below but I can't reproduce this problem with it.

debug_project.zip

[MossFrog]

Must be something do with the hardware configuration you have, seems to work fine for me on Chromium on Manjaro Linux (Tried the game link directly). Have you tried changing the texture settings to uncompressed and force PNG? Might be a bug caused by WebP compression.

[jayypluss]

Thanks for the response, funny It's not happening to me anymore on my Arch Linux too, I will test on Windows too. I have tried changing the Render Priority to 99 for this mesh before the last build, might it be related to that? I will also do more testing setting the value back to 0 to check it out.