Mouse Lag, Mouse Acceleration on/off option
|Affected ArmA II version:||1.04.59026||First affected build:|
|Reproduced by another DH user:||Yes||First affected ArmA II version:|
|I am using some Mods:||Single / Multi Player?:|
|I am using:||BIForumURL:|
|Reproducible for you:||NGUrl:|
|Related to content of DLC:||WIKIurl:|
In comparison to mouse movement in Arma1 the mouse movement/acceleration seems to have changed.
The faster the mouse is moved the more it accelerates the view.
Many games have an option for turning acceleration on/off, much like reverse mouse.
For a percentage of players, this is an essential preference to their play style.
Unsure as to whether this is a bug or a missing feature.
Issue is discussed in depth in the following thread, and although there are some work arounds,
they are fiddly and not fool-proof.
Updated by LMLM over 7 years ago
With regards to mouse lag, I think that is a performance issue. Try turning off anti-aliasing and post processing. That should help. Also try lowering your 3d resolution (as a test).
Updated by Whisper over 7 years ago
How can we measure this? I know I have mouse lag, more or less depending on config, but how to asses it correctly?
E6400 @ 2.3GHz, 2G RAM, 8800GT 512M, Win XP SP2, mouse MX1000 (cordless)
Settings 1280*1024, 100% fillrate, FSAA medium, terrain detail low, object detail high, VRAM High, Texture normal, PP low, shadow off
FPS in MP game 15, mouselag is very noticeable
Settings 1280*1024, 100% fillrate, FSAA disabled, terrain detail very low, object detail very low, VRAM high, Texture low, PP off, shadow off
FPS in MP game 40, mouselag far less noticeable but still present.
Not too precise for a report, isn't it?
Updated by zGuba over 7 years ago
- Category set to Controls
- Maxmem parameter deleted (
I guess it's related to CPU/VRAM performance. I had mouse lag in A1 when I set everything to medium on XP/8600GT+ despite of reasonable frame rate.
Updated by Fireball about 7 years ago
- Due date changed from 09/30/2009 to 10/30/2009
- Status changed from Assigned to Resolved
- Target version set to 1.05 BETA
- Affected ArmA II version changed from 1.02.58134 to 1.04.59026
- Reproduced by another DH user set to No
I think this is due for 1.05 BETA.
Giving an extra month for 1.05 to develop and to verify. Also I think the current BETA drivers from Nvidia help it a lot!
Updated by Fireball almost 7 years ago
- Due date changed from 10/30/2009 to 12/30/2009
- Status changed from Resolved to Duplicate
- Target version deleted (
- Reproduced by another DH user changed from No to Yes
This request bundles issues I'll rather re-open #4491 again instead - not only a performance issue.