Hi guys,
I've been noticing some odd mouse issues when I'm in TF2. If I move my mouse too fast or just sometimes when I move it normally it will turn a lot more than I wanted it to, almost as if mouse accel was on but a lot more extreme. An example of a situation where it happens is during rollouts I'll turn to heal the demo and I'll end up facing somewhere random. Or when walking down a hall if I move my mouse a bit I'll end up getting turned around completely. This used to only happen when I had OBS open and I thought it might be an issue with my cursor going outside of the game, but even when I run the game in fullscreen it happens. I just got a new monitor today and it's been happening all day without me having OBS open. I don't think it's a mouse issue since it's worked fine in every other game. I've tried switching mousepads, unplugging and plugging my mouse back in, changing dpi and polling rate, but nothing has seemed to work. If anyone has had a similar issue or if anyone thinks they might be able to come up with a solution that would be great. Thanks!
Hi guys,
I've been noticing some odd mouse issues when I'm in TF2. If I move my mouse too fast or just sometimes when I move it normally it will turn a lot more than I wanted it to, almost as if mouse accel was on but a lot more extreme. An example of a situation where it happens is during rollouts I'll turn to heal the demo and I'll end up facing somewhere random. Or when walking down a hall if I move my mouse a bit I'll end up getting turned around completely. This used to only happen when I had OBS open and I thought it might be an issue with my cursor going outside of the game, but even when I run the game in fullscreen it happens. I just got a new monitor today and it's been happening all day without me having OBS open. I don't think it's a mouse issue since it's worked fine in every other game. I've tried switching mousepads, unplugging and plugging my mouse back in, changing dpi and polling rate, but nothing has seemed to work. If anyone has had a similar issue or if anyone thinks they might be able to come up with a solution that would be great. Thanks!
Well I assume you've ensured mouse accel is OFF but are you 10000% sure?
Check:
-control panel - hardware - mouse - pointer options - enhance pointer precision is OFF
-your mouse driver software has no accel/prediction settings enabled
-and of course your in game settings, to be extra certain, see the following commands
m_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1
Sorry if those things are obvious but ya never know.
I assume you're using the mouse that you state in your profile - the deathadder. This mouse has no built in accel that I know of. Check to ensure that you sensor/eye has no dust or other objects inside, use a bright light to really check inside there.
Another thing you can check for, are phantom devices. Sometimes when you unplug and plug in usb devices, windows creates a duplicate driver setting for that device. After a while, you can have dozens of these "phantom" devices that could interfere with usb input. Below is a link to a webpage that has an easy guide to fixing this.
http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-drivers-and-services/
That's all I can think of off the top of my head.
Well I assume you've ensured mouse accel is OFF but are you 10000% sure?
Check:
-control panel - hardware - mouse - pointer options - enhance pointer precision is OFF
-your mouse driver software has no accel/prediction settings enabled
-and of course your in game settings, to be extra certain, see the following commands
[quote]m_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1[/quote]
Sorry if those things are obvious but ya never know.
I assume you're using the mouse that you state in your profile - the deathadder. This mouse has no built in accel that I know of. Check to ensure that you sensor/eye has no dust or other objects inside, use a bright light to really check inside there.
Another thing you can check for, are phantom devices. Sometimes when you unplug and plug in usb devices, windows creates a duplicate driver setting for that device. After a while, you can have dozens of these "phantom" devices that could interfere with usb input. Below is a link to a webpage that has an easy guide to fixing this.
http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-drivers-and-services/
That's all I can think of off the top of my head.
I've got a left handed deathadder (not one of the 2013 ones)
crespiWell I assume you've ensured mouse accel is OFF but are you 10000% sure?
Check:
-control panel - hardware - mouse - pointer options - enhance pointer precision is OFF
-your mouse driver software has no accel/prediction settings enabled
-and of course your in game settings, to be extra certain, see the following commandsm_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1
Sorry if those things are obvious but ya never know.
Also, would help if you specified what mouse you have.
-Accel is off
-Ehanced pointer precision is off
-All of the settings you listed match cept for rawimput, I've always had it on 0
I'll try installing a different mouse driver and seeing what happens. The thing that I find really odd is that it only happens when I'm in TF2.
I've got a left handed deathadder (not one of the 2013 ones)[quote=crespi]Well I assume you've ensured mouse accel is OFF but are you 10000% sure?
Check:
-control panel - hardware - mouse - pointer options - enhance pointer precision is OFF
-your mouse driver software has no accel/prediction settings enabled
-and of course your in game settings, to be extra certain, see the following commands
[quote]m_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1[/quote]
Sorry if those things are obvious but ya never know.
Also, would help if you specified what mouse you have.[/quote]
-Accel is off
-Ehanced pointer precision is off
-All of the settings you listed match cept for rawimput, I've always had it on 0
I'll try installing a different mouse driver and seeing what happens. The thing that I find really odd is that it only happens when I'm in TF2.
DeerI'll try installing a different mouse driver and seeing what happens. The thing that I find really odd is that it only happens when I'm in TF2.
I edited my post a bit. Sorry. but check out the last paragraph. Also, you should definitely use raw input; not having that on could explain why this issue is unique to tf2. Raw input increases the chance that nothing undesired is interfering with your mouse input.
[quote=Deer]
I'll try installing a different mouse driver and seeing what happens. The thing that I find really odd is that it only happens when I'm in TF2.[/quote]
I edited my post a bit. Sorry. but check out the last paragraph. Also, you should definitely use raw input; not having that on [i]could[/i] explain why this issue is unique to tf2. Raw input increases the chance that nothing undesired is interfering with your mouse input.
not sure man the only thing i can think of is the driver since we tried the launch options and stuff
not sure man the only thing i can think of is the driver since we tried the launch options and stuff
So I think raw input fixed it. I can't say for sure now but I think I got it all worked out.
So I think raw input fixed it. I can't say for sure now but I think I got it all worked out.
If raw input fixed it, you probably had windows accel on.
If raw input fixed it, you probably had windows accel on.
WaldoIf raw input fixed it, you probably had windows accel on.
I'd always used 8 for my windows sens. I found out how to get back to the same inches per 360 with raw input though so it's all good.
[quote=Waldo]If raw input fixed it, you probably had windows accel on.[/quote]
I'd always used 8 for my windows sens. I found out how to get back to the same inches per 360 with raw input though so it's all good.
DeerWaldoIf raw input fixed it, you probably had windows accel on.
I'd always used 8 for my windows sens. I found out how to get back to the same inches per 360 with raw input though so it's all good.
If your windows multiplier is anything other than 1 (6/11) then you are forcing acceleration into your pointed speed.
[quote=Deer][quote=Waldo]If raw input fixed it, you probably had windows accel on.[/quote]
I'd always used 8 for my windows sens. I found out how to get back to the same inches per 360 with raw input though so it's all good.[/quote]
If your windows multiplier is anything other than 1 (6/11) then you are forcing acceleration into your pointed speed.
m_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1
can i put this on cfg folder?
m_customaccel 0
m_customaccel_max 0
m_customaccel_scale 0
m_customaccel_exponent 1
m_forward 1
m_filter 0
m_yaw .022
m_pitch .022
m_side .8
m_mouseaccel1 0
m_mouseaccel2 0
m_mousespeed 0
m_rawinput 1
can i put this on cfg folder?
sounds like high dpi + low resolution
sounds like high dpi + low resolution
I got that problem too, please help me :(
I got that problem too, please help me :(
just use 6/11 windows pointer speed. 7/11 or above will make you skip pixels. skipping pixels is bad.
you will get used to the new sensitivity quickly enough.
also, do not use synapse to change the sensitivity of your 3.5g deathadder.
use the legacy drivers (made for 3g and 3.5g).
1800 and 3500 are native steps, so you'd be best off using one of those.
1000hz is not consistent on the 3.5g, so i recommend the default 500hz.
you can uninstall the legacy drivers after you've configured everything, they're useless after configuring your settings.
if you used synapse to set a cpi of less than 3500, then it will be interpolated.
so even if you set cpi to 1800, it would not use the native step of the sensor.
synapse works fine with the newer deathadders (2013 and up), but it does not work properly with the older models (3g and 3.5g).
TLDR: 6/11. no synapse. use legacy drivers to change settings. use 500hz.
just use 6/11 windows pointer speed. 7/11 or above will make you skip pixels. skipping pixels is bad.
you will get used to the new sensitivity quickly enough.
also, do not use synapse to change the sensitivity of your 3.5g deathadder.
use the legacy drivers (made for 3g and 3.5g).
1800 and 3500 are native steps, so you'd be best off using one of those.
1000hz is not consistent on the 3.5g, so i recommend the default 500hz.
you can uninstall the legacy drivers after you've configured everything, they're useless after configuring your settings.
if you used synapse to set a cpi of less than 3500, then it will be interpolated.
so even if you set cpi to 1800, it would not use the native step of the sensor.
synapse works fine with the newer deathadders (2013 and up), but it does not work properly with the older models (3g and 3.5g).
[b]TLDR[/b]: 6/11. no synapse. use legacy drivers to change settings. use 500hz.