Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mouse sensitivity is too high when in game mode #44

Closed
frankcarey opened this issue Feb 9, 2017 · 6 comments
Closed

Mouse sensitivity is too high when in game mode #44

frankcarey opened this issue Feb 9, 2017 · 6 comments
Assignees

Comments

@frankcarey
Copy link

frankcarey commented Feb 9, 2017

When running this within VNC in #24 with:

bazel run :random_agent --define headless=false -- \ --length=10000 --width=640 --height=480

Things work fine, but when I use game mode the mouse seems to be much too sensitive and ends up flipping back and forth between gimbal lock, looking straight up or down. Is anyone else experiencing that when using the following?

bazel run :game -- --level_script tests/demo_map

Normal:
screen shot 2017-02-09 at 4 59 25 am

When using mouse, it's either this or looking straight up:
screen shot 2017-02-09 at 5 00 10 am

@anshulkatta
Copy link

@frankcarey did you fix this , looks like we need to check in the code and lower the sensitivity

@PetterBomban
Copy link

I am having the same problem running on a VM.

OS: Ubuntu Desktop 16.04.2 LTS

Hypervisor: VMware ESXi 6.0 Update 3

bazel run :random_agent --define headless=false -- --width=640 --height=480 --level_script=lt_space_bounce_hard --length 10000

@magical-inference
Copy link

I'm experiencing the same issue, any input by mouse and its looking straight down or up, but also, the mouse is caught but not displayed in the window:

https://youtu.be/5LRRjQNbwGw

Like PetterBomban i'm using a UbuntuVM, too (don't mind the gtk-theme, its Ubuntu).

Any ideas?

@xueeinstein
Copy link

This issue still exists now, especially in Psychlab which requires extensive mouse interaction. @tkoeppe @charlesbeattie Any plan to fix this? Thanks.

@charlesbeattie
Copy link
Collaborator

We are not planning on addressing this issue directly.
Results may be improved by modifying the frame rate by passing command-line arg --fps 60

One can also use the key bindings for looking around:
(Edit assets/q3config.cfg to choose different key bindings.)

bind DEL "+lookdown"
bind PGDN "+lookup"
bind LEFTARROW "+left"
bind RIGHTARROW "+right"

@tkoeppe
Copy link
Collaborator

tkoeppe commented May 18, 2018

Please reopen if there are further issues here.

@tkoeppe tkoeppe closed this as completed May 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants