Significant changes for WebGL?

Hi!

We notice a fair amount of our users (around 5-10%) experience a bug in the WebGL build of our FPS. (using the OLD input system). The bug can be described as unexpected mouse glitches, where the view often snaps to a random position. After that you can look around again but every few seconds (users seem to report intervals of 2-40 seconds) the view snaps again to a new position. The vast majority is using Chrome so my guess is that it’s only on Chrome but could be other browsers too. We aren’t able to reproduce it ourselves unfortunately, but it appears to happen on Unity WebGL alone, and not other WebGL frameworks like three.js .

I wondered if there’s a possibility that this bug would be gone if we would change to the new input system. I mean: is the update mostly esthetic/UI improvement, or is there a difference in how it works under the hood as well?

Thanks in advance!

The underlying platform backend is separate from the old one and newly implemented. In that sense, yes, there is a difference in how it works under the hood.

That said, while it definitely could be that this is resolved by switching to the new input system, personally I’m not super optimistic here. There is still a lot of similarity between the two paths when it comes to mouse input. So could well be the problem is still there :confused: