Gears 5

i'm getting weird results for both gears 4 and 5.

with MDH 100 all 3 sensitivities should be the same value, but instead i'm getting very low ads and zoom sens values.

vertical sens seems to be much lower than horizontal.

longshot zoom deadzone is also back again. that was already patched in gears 4 and gears remaster.

It sounds like a really poorly optimized game for PC.

Has there been any word on being able to tweak sensitivities a little more with the upcoming release of Gears 5?

random acceleration and smoothing in 2019 just when i thought microsoft was starting to look out for us PC gamers.

also, when i convert my sens (i play on low sens) at 800 DPI it tells me 0s for all 3 values. Should i lower DPI to 400 or even lower to get more accuracy? I hate when they dont account for low sens users 😕

thanks for your efforts as usual DPIwizard, always nice hopping into a new game with my same sens off the bat ❤️
 

Edited September 5, 20196 yr by zhaka

@DPI Wizard could you measure the vertical sens too, please?

also a small suggestion: it would be convenient if the calculator told you the discrepancy for every aim, when using the aim - all option.

no, it's like the tech test.

i actually have a mouse that allows vertical dpi to be adjusted separately. too bad that logitech doesn't have this feature as well.

the mouse support has 3-4 problems:

1. polling rate affects sensitivity

2. vertical sensitivity lower than horizontal

3. long shot zoom "deadzone", especially in the vertical direction

4. high input lag with 60 fps. the mouse input needs about 120 fps to feel reasonably snappy.

Edited September 9, 20196 yr by stereo3D

mouse smoothing is on by default. the in-game option does nothing and the input.ini is ignored, so there is no fix.

Edited October 31, 20196 yr by stereo3D

@DPI Wizard

Is FOV accurate for gears 5 3440 x 1440 ultra widescreen monitors (21:9).  Right now it's always saying actual FOV = whatever I input, which I would find surprising to be the case based on what I've read on this site.

The calculator is fixing actual FOV to exactly match the input value and changing the vertical FOV based on the width resolution.  For example: a 3440 x 1440 resolution is outputting actual FOV of 100H and 53 V, but if I input 2650x1440 it outputs 100H and 67.7V.

Also, FYI, Gears 5 FOV limit is 100.

Thanks for the update!  What are some of the other changes?  Do you know if the comment about 500hz vs 1000hz polling rate still applies?

I dont know if this has been updated on the website but I am almost positive that the controller settings affect your mouse settings. I might make a new post since this one seem kinda old but the reason theres weird mouse behavior is because aim acceleration is at 10 in controller settings. I put this to 0 along with the deadzones just to be safe. This allows you to use 1000hz polling rate with no acceleration.

I'm trying to convert from apex to gears 5 but I think there's something I'm not getting right, why the 360° distance has so much difference?I've tested in game and about 30cm/360 should be 1 sens. Fov seems too low as well compared to apex.
what can it be?

Edited December 11, 20205 yr by shura30

@DPI Wizard - any support plans for Gears of War remaster?

On 5/10/2022 at 10:14 PM, STR8_AN94BALLER said:

@DPI Wizard - any support plans for Gears of War remaster?

 

bump on this

Just wanted to add that when I have a "Mouse Zoom Sensitivity" of less than 3 in this game, the tracking is terrible. If you move the mouse slow enough, tracking in any direction cuts out completely. Also there's some serious angle snapping. Tested on 2000 and 800 DPI.