Example 1:
In ZDoom, when mouselook is used, the slightest cursor move results in a cascade of seemingly random camera jerks which makes targeting impossible.
Example 2:
In OpenRA, when it's running in a window, the cursor highlight appears way below the actual mouse cursor. In fullscreen mode the highlighting is positioned correctly.
Those suggest that the mouse position rapidly switches between (for lack of a better description) its Wayland coords and its X11 coords, resetting to the X11 coords when the mouse is not moving. This also suggests that Orbment itself and the Xwayland client running under it have different ideas on what the screen size is.
Linux 4.1.4-1-Arch
orbment-git r414
wlc-git r668
Example 1:
In ZDoom, when mouselook is used, the slightest cursor move results in a cascade of seemingly random camera jerks which makes targeting impossible.
Example 2:
In OpenRA, when it's running in a window, the cursor highlight appears way below the actual mouse cursor. In fullscreen mode the highlighting is positioned correctly.
Those suggest that the mouse position rapidly switches between (for lack of a better description) its Wayland coords and its X11 coords, resetting to the X11 coords when the mouse is not moving. This also suggests that Orbment itself and the Xwayland client running under it have different ideas on what the screen size is.
Linux 4.1.4-1-Arch
orbment-git r414
wlc-git r668