I'm not sure if people have moved on to a better one but I'm still using http://www.notalent.org/sensitivity/sensitivity.htm and with 3500 DPI, default Win sensitivity and 1.6 in-game sensitivity, it tells me I'm sitting at 2.9in/360.
The problem is that it doesn't take m_rawinput into account I believe. So I feel as if that's not my correct in/360. I'm not entirely sure how this works, but can someone tell me what it would be or "feel like" with m_rawinput on 1?
I'm not sure if people have moved on to a better one but I'm still using http://www.notalent.org/sensitivity/sensitivity.htm and with 3500 DPI, default Win sensitivity and 1.6 in-game sensitivity, it tells me I'm sitting at 2.9in/360.
The problem is that it doesn't take m_rawinput into account I believe. So I feel as if that's not my correct in/360. I'm not entirely sure how this works, but can someone tell me what it would be or "feel like" with m_rawinput on 1?
Don't quote me on this but I think m_rawinput 1 just ignores the windows sensitivity. And since you said your win sensitivity is the default it wouldn't really make a difference whether it's on or off.
Don't quote me on this but I think m_rawinput 1 just ignores the windows sensitivity. And since you said your win sensitivity is the default it wouldn't really make a difference whether it's on or off.
if your windows is at default 6/11 then it'll be the same with or without raw_input.
So you'd leave the multiplier at 1 and put your DPI to 3500, which you have correct at 2.9 inch/360
If it feels off, then it maybe your mouse is not really set at 3500 DPI. I would take a ruler and just check that it's around 3 inches to do a full turn.
if your windows is at default 6/11 then it'll be the same with or without raw_input.
So you'd leave the multiplier at 1 and put your DPI to 3500, which you have correct at 2.9 inch/360
If it feels off, then it maybe your mouse is not really set at 3500 DPI. I would take a ruler and just check that it's around 3 inches to do a full turn.
I just found out I had m_mousespeed set to 1, and I have no idea why when my other mouse accel commands are off. Changing this to 0 made a noticeable difference in what my in/360 felt like. Not sure if it "fixed" anything per se.
Kuza, I checked my mouse drivers and such, it's at 3500. Always has been as well. Does polling rate affect sens, or just how quickly I'm allowing it to recognize my actions (if I remember correctly, this is what it's used for, right? If not, correct me).
I just found out I had m_mousespeed set to 1, and I have no idea why when my other mouse accel commands are off. Changing this to 0 made a noticeable difference in what my in/360 felt like. Not sure if it "fixed" anything per se.
Kuza, I checked my mouse drivers and such, it's at 3500. Always has been as well. Does polling rate affect sens, or just how quickly I'm allowing it to recognize my actions (if I remember correctly, this is what it's used for, right? If not, correct me).
Correct, polling rate only affects your device latency. If you feel like your mouse isn't reacting as quickly as you want it too no matter how fast you put the sens then your issue might be input lag from your monitor as well. Device input lag will give your mouse that sluggish feel.
Sometimes this can also be fixed a bit by lowering your flip queue in ATI video cards or likewise your per-rendered frames with NVIDIA cards.
Correct, polling rate only affects your device latency. If you feel like your mouse isn't reacting as quickly as you want it too no matter how fast you put the sens then your issue might be input lag from your monitor as well. Device input lag will give your mouse that sluggish feel.
Sometimes this can also be fixed a bit by lowering your flip queue in ATI video cards or likewise your per-rendered frames with NVIDIA cards.
It does feel a bit slow and sluggish. Maybe I should get used to playing without m_rawinput turned off? Not sure why I would need to or want to since I've been playing with it for as long as I can remember.
There's always me now maining soldier and not practicing as scout and playing it nearly as much but I don't feel like it's that really. That doesn't really make aim feel slow and sluggish. Could it be my mousepad wear and tear is finally coming into play? Well, the part I use anyway. I haven't had it a really long time or anything, though.
It's not really a reacting problem though, like you mentioned. The only reaction problem is my inability to click in time sometimes, but that's fixable via playing more. It's more me becoming to feel more uncomfortable with my sensitivity as of recently, and that it feeling kind of slow and sluggish is a problem in there somewhere. I only notice this on hitscan since projectiles require a complete different way of aiming.
It does feel a bit slow and sluggish. Maybe I should get used to playing without m_rawinput turned off? Not sure why I would need to or want to since I've been playing with it for as long as I can remember.
There's always me now maining soldier and not practicing as scout and playing it nearly as much but I don't feel like it's that really. That doesn't really make aim feel slow and sluggish. Could it be my mousepad wear and tear is finally coming into play? Well, the part I use anyway. I haven't had it a really long time or anything, though.
It's not really a reacting problem though, like you mentioned. The only reaction problem is my inability to click in time sometimes, but that's fixable via playing more. It's more me becoming to feel more uncomfortable with my sensitivity as of recently, and that it feeling kind of slow and sluggish is a problem in there somewhere. I only notice this on hitscan since projectiles require a complete different way of aiming.
raw input also disables (in-game) the tiny amount of windows mouse acceleration that you otherwise need to edit your registry to remove, iirc
raw input also disables (in-game) the tiny amount of windows mouse acceleration that you otherwise need to edit your registry to remove, iirc
m_rawinput 1 bypasses the windows mouse acceleration by using the "raw input" form the mouse drivers.
If you´ve checked all acceleration cvars in TF2 there is still the possibility of buil-in prediction/accel of your mouse.
Some mice also have weird issues when used at other than their native dpi settings (usually 400 or 450 and/or a multiple of that).
tl;dr Tell us what mouse you use, it´s probably a hardware/driver issue.
m_rawinput 1 bypasses the windows mouse acceleration by using the "raw input" form the mouse drivers.
If you´ve checked all acceleration cvars in TF2 there is still the possibility of buil-in prediction/accel of your mouse.
Some mice also have weird issues when used at other than their native dpi settings (usually 400 or 450 and/or a multiple of that).
tl;dr Tell us what mouse you use, it´s probably a hardware/driver issue.
Assuming you use a Deathadder 3.5G you could try the following:
-update the firmware (some versions have a jittering issue)
-set the sens to 10/10 in the drivers (interpolation is not set to 10/10)
-use 1800 dpi, apparently it´s the native dpi setting that works better than 3500 dpi
Assuming you use a Deathadder 3.5G you could try the following:
-update the firmware (some versions have a jittering issue)
-set the sens to 10/10 in the drivers (interpolation is not set to 10/10)
-use 1800 dpi, apparently it´s the native dpi setting that works better than 3500 dpi
Okay, I updated my firmware from 2.44 to 2.45 and managed to get blue screened by clicking "update" on my drivers lol.
I'll try the other two options as well later on and will check in with whatever results I get.
Okay, I updated my firmware from 2.44 to 2.45 and managed to get blue screened by clicking "update" on my drivers lol.
I'll try the other two options as well later on and will check in with whatever results I get.
"Set the sens to 10/10 on the drivers" you mean windows sens, right?
"Set the sens to 10/10 on the drivers" you mean windows sens, right?
I use this sensitivity calculator: http://www.funender.com/quake/mouse/index.html
It is designed for Quake, but since the engines are similar enough, the information still works.
Using a high DPI and low ingame sensitivity will give you negative acceleration which will cause your mouse to slow down when you move it fast even when raw input is on. I used to use a very low ingame sens and a DPI of 64000 but never realized how severe the negative accel was until I changed my settigns.
Plug in your refresh rate and monitor's resolution width to find at what point the negative acceleration starts to kick in. The lower the number, the more often you will be effected by negative acceleration. Then lower your DPI in the calculator and raise your ingame until the negative acceleration number is high enough that it won't effect you, but that you still have the same sensitivity.
Also, make sure your mouse's polling rate is set as high as possible. That will give you the best accuracy. However, if it starts jittering from the smallest things, then you should consider lowering it.
I use this sensitivity calculator: http://www.funender.com/quake/mouse/index.html
It is designed for Quake, but since the engines are similar enough, the information still works.
Using a high DPI and low ingame sensitivity will give you negative acceleration which will cause your mouse to slow down when you move it fast even when raw input is on. I used to use a very low ingame sens and a DPI of 64000 but never realized how severe the negative accel was until I changed my settigns.
Plug in your refresh rate and monitor's resolution width to find at what point the negative acceleration starts to kick in. The lower the number, the more often you will be effected by negative acceleration. Then lower your DPI in the calculator and raise your ingame until the negative acceleration number is high enough that it won't effect you, but that you still have the same sensitivity.
Also, make sure your mouse's polling rate is set as high as possible. That will give you the best accuracy. However, if it starts jittering from the smallest things, then you should consider lowering it.
raw input on just means your windows sens is automatically set to 6/11.
raw input on just means your windows sens is automatically set to 6/11.
Different mice react differently to different DPI settings. Very few mice actually perform better at higher DPI, that's usually where you start to see weird positive or negative accel issues. Also, monitor refresh rate and resolution have absolutely nothing to do with your mouse's imperfections, that's all determined by the sensor in the mouse.
That said, the DA still has one of the best sensors on the market and the weirdness you feel when turning on or off raw input is probably the built in accel in Windows kicking in. If you're on Windows 7 turning off "enhance pointer precision" doesn't fully disable accel and, as tranche said, if you haven't used a registry fix that's probably the difference you feel when you toggle raw input.
Also to answer the original question in short: For sensitivity calculators raw input enabled is equivalent to a Windows sensitivity of 6/11 with the MarkC mouse fix(or some other registry fix) applied to disable Windows built in mouse acceleration.
Different mice react differently to different DPI settings. Very few mice actually perform better at higher DPI, that's usually where you start to see weird positive or negative accel issues. Also, monitor refresh rate and resolution have absolutely nothing to do with your mouse's imperfections, that's all determined by the sensor in the mouse.
That said, the DA still has one of the best sensors on the market and the weirdness you feel when turning on or off raw input is probably the built in accel in Windows kicking in. If you're on Windows 7 turning off "enhance pointer precision" doesn't fully disable accel and, as tranche said, if you haven't used a registry fix that's probably the difference you feel when you toggle raw input.
Also to answer the original question in short: For sensitivity calculators raw input enabled is equivalent to a Windows sensitivity of 6/11 with the MarkC mouse fix(or some other registry fix) applied to disable Windows built in mouse acceleration.
kirby"Set the sens to 10/10 on the drivers" you mean windows sens, right?
No, i meant the razer drivers. Rawinput bypasses all windows settings anyway.
Not_MatlockUsing a high DPI and low ingame sensitivity will give you negative acceleration which will cause your mouse to slow down when you move it fast even when raw input is on.
http://www.funender.com/quake/mouse/index.html#input
m_rawinput 1 uses raw input (aka WM_INPUT) and therefore removes the issue of negative accel.
The stuff about the polling rate is true.
kirby you could try measuring your in/360. Even if it doesn´t feel like 2.9 in/360 it might be correct.
Probably the easiest way to get it pretty exact:
-place the mouse on a sheet of paper
-mark where the right side of the mouse is
-do a 360 to the left
-mark again where the right side of the mouse is
-measure the distance between the two lines
[quote=kirby]"Set the sens to 10/10 on the drivers" you mean windows sens, right?[/quote] No, i meant the razer drivers. Rawinput bypasses all windows settings anyway.
[quote=Not_Matlock]Using a high DPI and low ingame sensitivity will give you negative acceleration which will cause your mouse to slow down when you move it fast even when raw input is on.[/quote]
http://www.funender.com/quake/mouse/index.html#input
m_rawinput 1 uses raw input (aka WM_INPUT) and therefore removes the issue of negative accel.
The stuff about the polling rate is true.
kirby you could try measuring your in/360. Even if it doesn´t feel like 2.9 in/360 it might be correct.
Probably the easiest way to get it pretty exact:
-place the mouse on a sheet of paper
-mark where the right side of the mouse is
-do a 360 to the left
-mark again where the right side of the mouse is
-measure the distance between the two lines
get a ruler
go in game
measure it
get a ruler
go in game
measure it
I don't have a ruler. My life is hard.
Thanks, Setsul and Kuza for helping me out. Hopefully this "slow and sluggish" feeling goes away now.
I don't have a ruler. My life is hard.
Thanks, Setsul and Kuza for helping me out. Hopefully this "slow and sluggish" feeling goes away now.