[Crostini Bug Fix] Mouse controls restricted on Chromebook

[Andrew-J-Larson]

Using the Linux (Beta), installing the mcpe launcher was no problem at all. However while playing the game, it seemingly likes to restrict mouse movement at certain points while turning around and such. With unmodified sensitivity settings, it's almost like it restricts mouse movement at about 360° in left and right directions. Putting the sensitivity higher allows for about 1-2 revolutions before it starts restricting again.

For the Chromebook specs, it's using an Intel Celeron x86_64 (not arm) so I've been using the Debian amd64 builds.

If you need more information or some sort of logs, feel free to comment.

[ChristopherHX]

restrict mouse movement at certain points while turning around and such

Awful Chrome OS Linux Beta bug? No I won't plan buy one. Or it is a feature to keep you away from the following x11 feature or bug.

Also x11 is so buggy e.g. Debug the launcher while mouse is locked (ingame) break on a breakpoint ( gdb debugger) ide is showing over the Minecraft window (hides it completely) Then the bug, where is my mouse??? ...x11 is so buggy... imaging debugging without a cursor

This may happen randomly thanks to x11.

[Andrew-J-Larson]

So you're saying that maybe the mouse is hitting the edges of the window when trying to look around, even though it appears to hide the mouse as normal?

[ChristopherHX]

I mean on x11 with plain ubuntu 20.04 not ChromeOS (linux beta), I cannot confirm your weird ChromeOS behaviour. I can rotate my view endless (very fast) without hitting the window borders ca. 10 * 360° + without problems on real x11 linux. Even made the window very small, still not getting your problem.

I can't and don't want to change the behaviour of your window system, Chrome OS has it's own or just another one.

[Andrew-J-Larson]

I guess it's nothing wrong with the Linux app at all.

I did some more research and it turns out to be an issue with how permissive Crostini is when it comes to pointer-locks in Linux apps.

It suggests turning on a flag (chrome://flags/#exo-pointer-lock), which I'll have to try out later to see if it fixes the issue I'm having.

[sal-melliculus]

Enabling mouse capture flags worked for me, but I have both #enable-pointer-lock-options & #exo-pointer-lock enabled. Though #exo-pointer-lock should be the only one affecting a linux program.

[Andrew-J-Larson]

@ChristopherHX maybe since now we know how to fix the issue with the mouse, this thing should be closed, but with information about the bug added in the wiki/how to?