Mouse DPI / Accuracy / Sensitivity issue

A lot of players, me included, on the Steam forum seem to have an issue with mouse accuracy / sensitivity. It's almost as if the mouse is using the wrong DPI resolution.

The most typical situation where this issue is noticeable is trying to snipe with the tank's rail-gun; the smallest movement on the mouse will cause the crosshair to "skip" over several pixels making fine-tuning your aim impossible. Lowering sensitivity would clearly solve (hide) this issue; but would make actually turning around and moving incredibly sluggish.

Not sure what is to blame - maybe something to do with mouse acceleration, or the scale at which the mouse axis are mapped, or how the game uses Windows mouse settings rather than raw input; or if it's due to frame-render-ahead (unlikely, as it isn't sluggishness on the mouse, it's quite literally imprecision); but it is a really irritating issue and judging by the accuracy of some snipers, one that is somehow solveable.

Bumping because I have the same problem. Any easy way to fix this? I "optimized" my mouse settings and the little skips are still there.

Don't use absurdly high sensitivity.

Lower sensitivity is superior when any sort of precision is required regardless of what you think it does to turning speed.

Some of us don't have the desk space for a properly low sensitivity, me included. Just because there is a workaround does not mean it's not a bug that needs addressing.

One theory is that it is an "aim-assist" style snapping grid that's been jammed into to make Xbox controllers functional;

as discussed here:
http://forums.steampowered.com/forums/s ... stcount=15

I've yet to verify.

I currently have one inch on either side of my mouse. I don't think lowering my sensitivity is an option.

Input is handled quite oddly in this game, however it never stopped me from hitting stuff.

You can't key in Sensitivity into ini files, there is no numerical representation of the value it uses - the only way to gauge your sensitivity in this game is to use the slider and then measure it yourself.

There is no acceleration enabled by default unless there is a controller plugged then ideally the controller gets acceleration.

Mouse Smoothing should default to false nowadays as well.

I haven't experienced any of your issues but granted I haven't played much after Update 5 (read: 0 hours due to uninstall).

You may want to contact Gaf about this as he seems to be the person to go to when it comes to engine issues.

You better have some nice day,

grimbar

"MouseSensitivity=74.300491" - from hostileinput.ini. It's a numerical representation of the slider's value. The Unreal engine supports a wealth of other mouse configuration options, although whether the game will respect them, allow you to keep them, etc is another matter.

You may have struck gold with this; I have a joystick plugged in, which caused me massive problems (not being able to navigate menus, character always turning left) until I set allowjoystick=false in the hostileEngine.ini; However, as it is no doubt still detecting the device as plugged in, even though it is not processing the inputs, it may well be incorrectly applying Xbox Gamepad sensitivity and scaling settings to mouse input. It would also explain why a fair few players (those without Joysticks) don't experience this issue.

You too, cheers.

Edit:
http://www.youtube.com/watch?v=Ve8-0n1Txf4 < there's an example of the issue in that video at around the 8 minute mark, and the commentator's theory on why it happens.

Unfortunately the numeric value doesn't help you whatsoever and any change to the ini will not be respected when it comes to that value.

The value is saved directly to a certain profile, best bet is finding a value by fiddling with the slider and then stick to it, as you can't compare those values to any other well known FPS and it makes it quite tough to do anything useful with input.

Anyhow I'm digressing and ranting, I have a controller as well but haven't experienced those issues.

There are ways to force a revert to default (updates, adding incompatible entries, making other changes, etc) - but play with the slider and check the ini file numerical value to see it changing to correspond to the slider's value. The two correspond.

There is no aiming grid. View rotation roughly is based on (signal from mouse * mouse sensitivity). Mouse signal is based on your mouse's DPI and ranges from 400 for a crappy mouse to 5600 for a high-end gaming mouse.

If you have a low dpi mouse then you will need a high sensitivity to perform one full rotation. With a high dpi mouse you would have a much lower sensitivity to perform that full rotation moving your mouse the same physical distance on your desk.

I personally use a Razer Deathadder at both home and work. It's set to 3600 dpi updating at 1000 hertz and is silky smooth.

so uping the hertz will affect how smooth it is in the game? mine was always on 500

400 CPI, fairly low on the end of the "slider" and boy it was silky smooth nor was it too slow.

Statements regarding smoothness based around the CPI don't make people look informed, no offense.

What this game requires, and I plead for that during early beta in conversations with Gaf as well as on this forum, is treating input like any other of the well known shooters.

A uniform way of dealing with sensitivity, including numerical values. Treat it in such a way t hat a sensitivity of 1 is the same in this game as it is in those other games, and for god's love we need raw input.

But since these changes won't happen and haven't happened I'll remain a sad person.

Yes Ace42 the numerical value relates to the slider but since you can't do anything with that value in a sense that you would be able to calculate stuff to translate your sensitivity (you know most good gamers have 1 sensitivity for every game) it remains useless.


Here is the proper way of dealing with input (assuming WM_MOUSEMOVE since we probably can't get WM_INPUT)

Code:

(360 / (m_yaw * DPI * Windows Sensitivity Multiplier * In-Game Sensitivity))

That's the formula to calculate your view rotation horizontally in cm per 360. A grid for aiming (65536 Iterations as in other games) combined with proper input and formulae would allow gamers who know what they are doing to have a nice transition into this game so they won't feel alienated by awkward input.

I never really got the impression that you want that kind of player in your game anyway, had to be said.

I've never had an issues with using mice in any other game, including any other Unreal-engine game at all, so it is safe to assume my mouse's DPI isn't useless, nor its refresh rate terrible. Some quirk of MNC means that precise aiming simply isn't possible at the sensitivities needed to have a similar amount of travel used to perform a 180 / 360 as in other shooters. However, if you want to start donating free Razer Deathadders to players, I'll find that to be an excellent solution too.

Don't buy Razers. Ain't happy with my Mamba.

Steelseries is nice, Logitech works too and Roccat also does some good work.

OT: Didn't have any troubles with my mouse. I use a Logitech G9 at the moment and it's pretty good. I turn the DPI down anyway for precise stuff so yeah...

Original Razer Deathadder (not the Respawn) is one of the best mice ever made, go read some Sujoy.

Top Tier: WMO 1.1a, IME 3.0, SSeries Xai, Razer DA, Logitech MX500

Assuming people know how to overclock the polling rate on the old school mice.

No need to spend a fortune on beast mice -> get WMO or IME

Other mice don't compare.

I use the razer diamondback 3G so long as it keeps not-dying. Thing isn't even in production anymore and still keeps on trucking like the first day I used it. Except the lights don't work so good any more. I don't mind that.

Maybe it's good from a technical standpoint but from my experience (including my mamba I own 4 Razer mice) non of them stood the test of time. That's why I don't recommend them at all.
And yes I also own the original Deathadder. It was unusable after three months.

My diamondback 3G has lasted about six years so far. I don't know what you do to your mice but it's probably somewhere along the lines of what I do to headsets.

Funny because I also broke a Razer headset once...

But I don't do anything unusual. My Logitech G9 is still truckin' and I had that pretty much since it came out.
It was also nothing mechanical. They just move around at random and don't work for the first five minutes after turning my PC on and so on.