Bug 1384897 - Mouse movement in Counter Strike: GO is bogus
Summary: Mouse movement in Counter Strike: GO is bogus
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-14 10:49 UTC by fred
Modified: 2017-05-16 09:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-16 09:09:32 UTC
Type: Bug


Attachments (Terms of Use)

Description fred 2016-10-14 10:49:54 UTC
Description of problem:
When playing the linux version of counter strike: GO (a very popular FPS from valve), mouse movement in-game is problematic: Player is always looking up, unable to look down, left, or right. Any mouse movement results in extreme camera jitter. The game is unplayable.

Game works fine using X.org.

Version-Release number of selected component (if applicable):
fedora 25 beta, upgraded from fedora 24

How reproducible:
Always


Steps to Reproduce:
1. Start a game of CS: GO
2. Select a team.
3. Try and fail to look at the ground.

Actual results:
always looking at the sky.


Expected results:
one should be able to actually move the camera.


Additional info:
Player movement is ok, meaning that if one wants to use the keyboard keys, one could move while still looking upwards.
Game works fine using X.org.

Comment 1 fred 2016-10-14 11:40:18 UTC
allright I've tried with ioquake3 and openarena as well as a few other steam games. They all have the same issue.
I think it has to do with pointer confinement:
As long as the "invisible cursor" is inside of the game window, movement is fine and game behaves correctly.
However as soon as the "insivible cursor" gets out of the game window, any additional movement results in erratic camera movement in game.

Comment 2 fred 2016-12-05 12:37:09 UTC
seems fixed since then. thanks


Note You need to log in before you can comment on or make changes to this bug.