Search results
Results from the WOW.Com Content Network
The term 'count' is used because it's an undefined unit of measurement which could be anything and is therefore more flexible than if it were a unit of 'pixels'. Alright guys so currently i have a Razer Abyssus mouse that im using at 1800 dpi. I might be getting a SS Sensei RAW soon and obviously SS mice use cpi instead of dpi.
When you move the mouse, the mouse counts. Hence: Counts Per Inch (dpi is a pleb marketing term) Counts get logged to your OS: you move 1/400th of an inch on your pad at 400cpi, computer receives the value 1. That gets multiplied by the pointer speed setting (e.g. notch 8 will multiply by 2, therefore that 1 becomes a 2)
Unless you have played with high dpi for at least 6-8 months, all of sudden going from 400 dpi to 2400 or whatever will just make your mouse feel really wierd, even if you lower your sensitivity to compensate. finally, in windows, high dpi just sucks, unless you have very low windows sensitivity because it becomes so sensitive.
High or low DPI and the in-game sensitivity to match depends more on the mouse, I think. Some sensors behave more favorably one way or the other. Things like negative acceleration and skipping. Threadripper 3960X + EKWB / TRX40 Aorus Master / 128GB DDR4-3600 / ASRock RX 6900 XT Phantom.
I will repeat this again: sensitivity (including m_yaw, m_pitch) and screen resolution are the only settings responsible for so called "pixel skipping". DPI doesn't have connection with this issue. It's simply "speed" of your pointer on desktop or rotation in FPS game. That means you could use 5000 DPI mouse and still "skip" pixels.
Your 1800 DPI at 1 in-game sens is 2.9 cm per 360 degrees, which is ridiculously high sensitivity. At 16000 DPI with 0.1 in-game sens, you move to 3.3 cm per 360 which is still extremely high sens, but at least slightly more controllable. Windows has a sensitivity setting, type main.cpl in a command prompt.
I didn't know that there would actually be a calculation to avoid pixel skipping. To be sure that your mouse doesn't "pixel skip", just max the DPI of the mouse. Most mice today have like 5600 or 6400 DPI, which is more than enough. I just max the DPI on my Corsair M90, and adjust the sensitivity in-game accordingly.
[(Current dpi) x (In-game sensitivity)] / (Maximum dpi) = (New Sensitivity for max dpi) Using this formula you wont change the overall sensitivity in CS:S. For example if I'm using a 400dpi mouse at in-game sensitivity 0.750, and then I buy a Razer DeathAdder, I will use it at 1800dpi but reduce my in-game sensitivity to 0.167 and my overall ...
Habit of "feel" imo. Jitter reduction reasons are more apparent at DPI levels higher then 800. Been using anything in between 800 to 1800 dpi for years now (at 1080p I experience pixel skipping near the crosshair with 400 dpi, I need a minimum of about 600 dpi to avoid this).
If you check the PDF in the link I gave (page 21) the default values are: 800. 2400. 5700. Using the sniper button further lowers it to 400 DPI. Here's the review that mentions the DPI when using the sniper button. It's the first paragraph under functions.