Help - Twitchy Mouse #4341

[Bacon55]

Everytime I've seen one of these threads it seems there's some uber gaming mouse involved. I think i need to get one of these for testing.

OR I need you guys having a problem to plug in a regular mouse and tell me what you see. It could as easily be a setting on the mouse as a setting in the game, especially that we only have one mouse settting and the code comes directly out of DrirectX.

Anyone else having this problem with a mouse that isn't super adjustable dpi?

Cheapo MS laser mouse, same problem. MUCH more noticeable for me in 1.31 vs 1.30.

Not sure why, but it's very frustrating trying to hit a long distance target if they're sitting in the "skipped" pixels.

[blackelk]

Ok, switched to the cheapest mouse microsoft makes, the basic wheel mouse, and it works flawlessly - none of the jerky insta-flip stuff the sidewinder mouse does... Unfortunately, it only has 3 buttons with the clicky scroll wheel, so 1/2 my functionality has changed with my button mapping, but at least I can aim the gawd-dang guns now...

[piercer]

Interesting, will need to pull an old cheapy out of the garage. My mouse is a Logitech G500, maybe it has something to do with the report rate or which drivers are set for use in the settings.

P-

[saxton]

all the mouses I posted yesterday are cheap as F***. The first DYNEX mouse I pointed out had the problem came with a 5 dollar keyboard at the time. So it happens with cheap mouses too, just certain type work no matter what the price is and other don't I guess

[delems]

Interesting, I have a Logitech G5 (pretty sure) and put it on the 1000 dpi setting, there is also a 2000 dpi setting, but it is too fast. I haven't looked at my mouse settings in System Preferences. I don't use third part software, just plug it in (to my Mac) and go. I have noticed that 'skip' also, but haven't paid too much attention to it until I read this post. I'll keep an eye on it.

[popeye0]

Ok guys i figured out what was wrong with my mouse play.

Logitech has some new drivers out so go and check for your mouse to see.

On the "advanced settings" page make sure that "wwii.exe" is selected.

Then highlight it.

Then set up the speed control to the lowest setting in the mouse "setpoint soft ware". Get rid of the rest of the settings and just use the one that says "400".

Save it.

Then make sure that you have selected the soft ware to detect any games that you have.

Load the game and adjust the mouse slider to the setting that works best for you.

[kaputman]

This issue has been around for a long, long time. This game has always had an extremely bizarre sensitivity scale - the default setting is already as low as it can go.

More and more people are getting higher DPI mice every day, which just makes it more noticeable. If you are running at a 1200+ DPI resolution mouse, then you are going to have some serious sensitivity problems. The only fix for this is to go into your mouse drivers and manually lower your DPI (which is absurd), or go into your Windows control panel and lower your "Pointer Speed" (also a bad idea; see this: http://www.nextlevelgamer.com/tweaks/dont-modify-your-windows-sensitivity).

This is an issue with game coding. To just quickly address it now, you could just change the scale of the sensitivity bar in the game. As of right now, people like me can only increase sensitivity from the default level, which is not desirable because it is too sensitive as is.

Even with that quick fix, though, it would not address the issue of the "pixel skipping" that occurs at every distance, but most noticeably on those 500-800m shots with rifles. This appears to just be how the game is coded; the rifle's iron sights follow the Window's cursor exactly. Most games where you would define the aiming movement as "smooth" have the weapon's sights being almost dragged around by the cursor. The weapon is not responding to your cursor's pixels, but is just being pulled by your cursor's movement.

All being said, this is not a bug but a development issue, that has been around as long as I can remember, and I've been playing since 2001.

[piercer]

Hmmmm... this is interesting.

It appears the 'sweet' spot on my mouse is around 600dpi with the in-game mouse sensitivity slider bar around 40%. That seems so far to get a smooth panning of the rifle not noticing any skipping really in preliminary tests but will need to field test it some more. This is with a G500.

I've also noticed that the game and I think remember reading this somewhere slows down the X-axis of the mouse, so no matter how high you set it you can't really spin around (which I agree is a good thing) But I've noticed this creates some discontinuity with Y-axis motion as the same curtailing doesn't appear to have happened on the Y axis. Is this true? I think it should be equally applied to both axii as my mouse jumps up and down quickly but pans smoother across X.

P-

[aurbo]

Not being able to aim at the exact pixel you want to has been around for a very long time. I've used low end mice and high end dpi switch on the fly (400dpi - 2000dpi) mice. I've even tried different surfaces.

I recall it happening to me just the other day, and as already mentioned it is most noticeable with the rifle at >300m shots. Very noticeable when you stay in a static position and EI continue to come to the same position. You already have it ranged and have confirmed hits, then the mouse doesn't line up.

Look through binos, see EI looking out one of the new bunker windows, figure range on shot and set sights to 400m, shoot, EI dead. Shortly after another EI is looking out the window, I can see the pixel I want to line up on and bring the sights into place, but they won't align on the correct pixel for the shot.

Usually I just swing the rifle off target and back onto target and am able to line up correct then. Sometimes I have to move my avatars position slightly to be able to line up. It's a minor annoyance and can be worked around.

[kaputman]

You can call it a minor annoyance, but it often means the difference for me on shots where there is a short firing opportunity at long range, like an EI moving from window to window at 600m. You can work around the pixel skipping on static targets, but I mean, how long has this problem existed? I think a fix is in order.

Something that is more than a minor annoyance is having to lower my Logitech G9x down to 400 DPI in order to play the game.

[munchkin]

I did lower the setting to 400 dpi and it's better. Problem is, I never had to do that with the previous versions of the game.

[blackelk]

I think there are 2 different problems being addressed here.

My problem was not just simply bouncing one pixel here and there, my issue was that aiming with the mouse would have random sudden outbursts where the aim would go full speed in some direction while moving to aim. It would be like having someone standing next to you, and while you were aiming, every few seconds or several times a second, they would whack your mouse hand throwing the aim way off across the screen.

It was not a minor annoyance, it made the game essentially unplayable.

This problem occurred with the high end microsoft sidewinder gaming mouse.

It was completely resolved by using the bottom end budget 3 button mouse.

[munchkin]

The problem you describe has been around for ages. For as long as I can remember my sight, especially when I do AAA, suddenly starts to rotate left or right to return back.

This is not what we're talking about here, those are two separate issues, even though I've started to experience this happening up and down as well with 1.31.

The problem this is about is the pixeljumping. It's always been difficult to aim exactly at one specific pixel but now it's much worse, it jumps so much it's sometimes impossible to aim at an ei that's only 100m away, you only end up on either side of him.

Changing the DPI to the lowest has improved this but it's still worse than it ever was before 1.31.

[saxton]

I feel like this issue is getting looked over again as it has in the past even though now since 1.31 a lot more people are having more severe of an issue. They released what they are probably going to fix for a hotfix and this isn't part of it

[synxer]

So did RATs confirm this as a bug?

[oo6oo7]

I have also noticed this. I have a mouse that lets me scale sensitivity on the fly and when I bring it all the way down to 200dpi I no longer have the same fidelity as in 1.30. I used to be able to aim a pixel or so at a time with a sniper rifle, but now it will go back and forth a couple pixels making it hard to get the rifle right on target.

[GOPHUR]

Bug? Dunno yet. Can't determine if it is the app or a conflict with something else. It is ticketed for more work (see thread title).

[valis]

Noticed similar... mouse will work fine for minutes, it will then force-ably jump to one side of the screen and slowly descend.

[lutorm]

Gophur, here's the issue:

I have my turret movement mapped to the mouse in my cfml:

x

With this mapping, I can without a problem move the turret in single pixel increments on my 1920x1200 monitor.

I also have my inf aim mapped to the mouse:

	x

but here I can not move the aim point of my scoped Kar98 in single pixel increments, but it moves in steps that are noticeably larger than a single pixel, thus making it potentially impossible to hit something small because it is "between" the aim point steps. Note that this can not have anything to do with the mouse, because the same mouse works perfectly when aiming turrets.

Moreover, I tried to see if this was a mouse issue by trying to see if I could move the aim point in smaller increments using keys. If I try to set fine adjustment using a key in the way that Spoon suggests for tanks:

	
o
u

this works as expected, I can move the turret very slowly by holding down the o/u keys, such that it takes probably 15 minutes to go a full turn. The turret aim point passes through every pixel during its motion.

If I try the same with the infantry:

	
o
u

this makes the trooper turn 360 degrees in about 5 seconds, way too fast to see if it makes the same steps as when aiming with the mouse.

Something is different for inf aiming vs turret aiming. The turret works perfectly, inf aiming does not. Inf aiming should work the same as turret aiming.

[C0b0]

Me too with rifle and never happened to me before, I'm trying changing monitor to improve the fps.

I have jumps... but from the beginning, with second movement for turret.

[GOPHUR]

Thanks Lut. Very informative. Added to ticket.

[Marcusa]

I have the ability to adjust my mouse sensitivity fairly easily because the controls for that are located on my mouse. If I did not have this capability I would be up **** creek. In 1.30 my mouse was almost always on the normal sensitivity setting and it was fairly easy to shoot with. With 1.31 I always have to turn it down. What was previously the normal sensitivity setting is very difficult in 1.31 to shoot a rifle on a fixated target not far away. I play on the lowest sensitivity setting now otherwise it's extremely difficult to hit anything.

[Marcusa]

and my mouse wheel is very sensitive in game. makes it difficult since i use it for adjustable sights.

[munchkin]

I'm getting more and more annoyed with this problem. It affects all mouse play and since I use mouse for AAA/ATG aiming as well and the behaviour is the same there.

It's starting to become a real game breaker.

[piercer]

I logged in last night for the first time in about 6 weeks. This issue is the same or worse. Not sure why it's so jumpy, can be very frustrating as inf and I don't remember it ever being this bad in pre 1.31 versions.

P-