EnablePointerLock Regression?

If you load the First Person Movement example and click the screen, the mouse disappears and you get a ‘Hit escape to show your cursor’ message from the browser. The mouse is now captured and you can use your mouse to look around. Great, works as intended.

But, if you hit escape and get the mouse cursor back and immediately start clicking the screen again it takes about 2 seconds for the pointer lock to capture the cursor again.

I’m not sure if maybe this has always been the case and I’m only just noticing it? Or if this is a new issue?


Hi @george1,

Indeed I can reproduce the issue on my side as well. I know there are some limitations on the browser Pointer Lock API with iframes, not sure if this is the same issue:

Try submitting an issue about it in the engine repo.