10 replies to this topic

[TELEFORCE]

I've been practicing head shots lately, and I've been trying to figure out the best way to get them. I've been practicing with an Adder with 2 ER PPCs, a TC3, and advanced zoom.

What I noticed with advanced zoom, is that despite having my mouse set to 200 DPI, my crosshairs still jump to some kind of invisible snap point on the viewing screen. I can try to aim for a 'mech's head, but the crosshairs will snap to a spot which is usually not the head but a torso location instead.

I found that by slightly changing my 'mech's position, I am able to aim for what I want, but the crosshairs still snap to some spot on the screen.

Is there a workaround for this?

[Lily from animove]

care to describe this a bit with pictures? pictures help devs a lot mroe than just a text.

[TELEFORCE]

I'll try to whip up a video later.

The behavior I'm describing is similar to how the grid snap feature in programs like AutoCAD works. It forces the mouse to snap onto intersections of a grid instead instead of being free-roaming.

I'm experiencing that same behavior with MWO using advanced zoom, but the "grid" invisible, yet my mouse snaps to it and keeps me from aiming precisely at 'mech locations.

[John1352]

Are you saying it feels like the resolution of your aim is low? In an extreme sense, similar to being able to shoot in 4 directions in a simple game, except here you get 1000 "steps" through 360 degrees.

[TELEFORCE]

John1352, on 19 September 2015 - 01:36 AM, said:

Are you saying it feels like the resolution of your aim is low? In an extreme sense, similar to being able to shoot in 4 directions in a simple game, except here you get 1000 "steps" through 360 degrees.

That looks like a better way of describing it. I'm not sure if I hit the bottom limit of the game's aiming resolution, or if it's a limitation of my mouse (Logitech G700s). I thought 200 DPI was plenty low, but maybe MWO can't handle that precisely?

[l33tworks]

Lol @despite having my mouse set to 200 dpi. Set your dpi to 1500 and lower the in game sensitivity. 200dpi is wayyyyy to low. Thats your problem.

[Squirg]

Usually DPI doesn't matter, but 200 is hilariously low.

You can try:
Lowering your resolution
Lowering your sensitivity in game
Increasing your DPI

[John1352]

I think you'd need to test it with the mouse and MWO's sensitivity settings right down to be sure. It does seem that the crosshair moves in noticeable steps though.

edit: as the guys above said, it would probably be better to set mouse to 1000 and use the ingame slider.

Edited by John1352, 19 September 2015 - 01:45 AM.

[zaku potion]

yeah I think your DPI is whats causing the stepladdering, even at 400dpi its pushing it for longer distances in MWO. You might have the same distance sensitivity but you need to up the resolution so your smaller movements register. You will need to compensate by lowering your sens too. Go to training grounds with a mech that has fast torso twist+2 arm actuators, and use a bearing marker at 0/90/180 or whatever. aslong as youre on some marker to measure another 90 degrees with.

1.mark your mouses position on your mousepad and slowly move your mouse from your initial bearing to one 90 degrees away.
2. measure how many inches/centimeters it took you to get the 90 degrees
3. change your dpi and tune your sens so you have the same measurement for 90 degrees as the original dpi.
4. no more mouse chunks blocking your peeps from getting up in that head

[Mawai]

I have a Logitech G500 mouse. It has a button to set DPI sensitivity. The DPI values are customizable.

I have mine currently set for 400, 1200, 1900 and 4000dpi. I usually use 1200 or 1900 in MWO with a bit of a tweak to in game sensitivity. I have never seen a snap to grid effect. My guess would be that your 200 dpi is far too low or you also have the MWO in game sensitivity set incorrectly. Between the two of them I suspect it would be quite possible to get a noticeable minimum step size when you move the mouse.

P.S. 4000dpi requires about 1/2" of movement to go from one side of the screen to the other but I find it way to high to hold aim effectively for me in MWO.

P.P.S. One other item that can cause a step is the polling rate. If you don't transfer data from the mouse sufficiently often it will tend to jump around. My mouse is set to 1000 (or 1ms polling rate) which seems to work fine for me.

Finally, if you have a logitech mouse, their website probably has some software you can download to set these values ... especially if it is a gaming mouse.

Edited by Mawai, 19 September 2015 - 07:12 AM.

[TELEFORCE]

Thanks for the advice everyone! I set the in-game mouse sensitivity to its lowest setting and played around with my mouse's DPI settings and now I no longer have the problem.