Thanks. This bug should have happened in production studio on OpenGL as well (on your hardware; the issue is hardware-specific - it’s a small precision bug in our new shader pipeline that we enabled yesterday). We’ve disabled this on production for now.