yes, I will submit a mozilla bug.
Meanwhile I noticed that if I do not use my shader to remove the greenscreen, I do not see flickering so far…
Here is a link to playground where I am using the same shader as in the original post
(I convert the input rgb to hsv and check if I am within tolerance from the chroma)
I am wondering if I am doing something “illegal” in the fragment shader.
I remember long time ago, I ran into a problems in Maya’s custom shader when I introduced too many variables in it. Maybe there are similar limitations in shaders here too?
I am getting more inclined to say that it is a mozilla bug. First of all, so far I have seen this only in Firefox. Besides that, I can “fix” by closing / opening developers’ console panel (pressing F12)
Similar thing happening to me only on Firefox. If you have a canvas open, go to a different tab for a while, when you come back the canvas will flicker until a resize happens (dev tool opening/ closing triggers the resize). This is not only happening with Babylon but with other apps that render to the canvas as well.