Overclock.net › Forums › Components › Mice › Questions about relationship between ingame res and mouse dpi CS:GO
New Posts  All Forums:Forum Nav:

Questions about relationship between ingame res and mouse dpi CS:GO - Page 3

post #21 of 54
This also might be why when I play on 1440x1080 I always feel as there is something wrong with my aim compared to 1280x720 or 1024x768. Using 400DPI on my mouse. Very interesting..
post #22 of 54
Thread Starter 
Quote:
Originally Posted by Harrywang View Post

This also might be why when I play on 1440x1080 I always feel as there is something wrong with my aim compared to 1280x720 or 1024x768. Using 400DPI on my mouse. Very interesting..

Well, I know for me at least, ever since changing to 1600dpi 1600 in game res 5 days ago i've never felt better in the game. I've never had a problem snapping onto people, it was always tracking and getting that consistent feel from my mouse. Feels great now. Hopefully it works for some other people as well. My advice is to just try it.
post #23 of 54
So what is it you are saying ? match DPI as close to your RES?
post #24 of 54
Thread Starter 
Quote:
Originally Posted by Ka0sX View Post

So what is it you are saying ? match DPI as close to your RES?

Yes, as long as you stay within native dpi steps of your mouse try to get your dpi as close to your in game res as possible and give it a shot. Has worked really well for me.

For example if you played with 800x600 at 400 dpi. Try 1920-1080 at 1600 dpi or 1280x720 at 800dpi

Or if you played 640x480 at 400dpi like myself then try 1600x900 at 1600dpi or 1920x1080 at 1800dpi

I have yet tried to test setting dpi higher than in game resolution like some people do (ie 1024x768 at 1600dpi) so I can't comment on how that is, but I assume it would be sort of the same or it might be too sensitive.
post #25 of 54
I used 3500dpi on 800x600 for months to no problems. You just need to lower the sensitivity setting to get the same inches per 360.

There's nothing magical about DPI, you just can't set your sensitivity setting itself too high or you will have a hard time hitting long range shots no matter what you're used to.
post #26 of 54
Thread Starter 
Quote:
Originally Posted by wareya View Post

I used 3500dpi on 800x600 for months to no problems. You just need to lower the sensitivity setting to get the same inches per 360.

There's nothing magical about DPI, you just can't set your sensitivity setting itself too high or you will have a hard time hitting long range shots no matter what you're used to.

Yeah, you can get the same inches 360 on any dpi level. What i'm saying is I can tell a noticeable difference on 1600 in game resolution when using 1600 dpi or 400 dpi

400 dpi with the same inches 360 as 1600 dpi feels slower to me when I go to track someone moving, like I have to put a lot more effort into it where as 1600dpi feels fine/easy/minimal effort
post #27 of 54
Lower DPI values have a larger effective small movement threshold. Computer mice have a small deadzone at smaller than a single output pixel so that the cursor doesn't move while the mouse is not moving. The cursor has to move at least a single count from the position where it last outputted movement. So at extremely slow tracking speeds, lower DPIs will be slightly behind. Same thing if you have 1600dpi internally and downscale it to 400dpi, though it won't be because of sticking to pixel centers in that case.

But this deadzoning behavior shouldn't be big enough to feel it when you're tracking people unless you have an extremely high sensitivity.

If resolution is affecting anything then you should see if raw mouse input still has the same behavior. Resolution shouldn't affect anything, FPS gameplay logic isn't aware of the pixels on your screen.
post #28 of 54
DPI definitely makes a difference....go try 20 sensitivity on 100 dpi and then try 2 sensitivity on 1000 dpi. it's so choppy on 100 dpi even though both turn the same cm/360.
post #29 of 54
Quote:
Originally Posted by bond10 View Post

DPI definitely makes a difference....go try 20 sensitivity on 100 dpi and then try 2 sensitivity on 1000 dpi. it's so choppy on 100 dpi even though both turn the same cm/360.

Well yea....cause nobody SHOULD use that, try comparing 400 dpi to 1600 dpi then come back, or even 800.


If it does feel choppy it is hardly noticeable unless you're using a sniper rifle.

I personally just decided to go with 400 dpi and stick with it, the mouse felt smoother somehow. Like small mini movements didn't cause me to go off target.
post #30 of 54
The only thing I think that holds true is that you should increase dpi and reduce ingame sens if 1 count of movement translates to a yaw or pitch movement on your screen that is larger then a pixel (near the crosshair), if it bothers you.

That and I know what Skylit meant about sens 1.0, but it has nothing to do with precision, but control over counts, etc.

Skylit (in his quote), meant that:

1 count * sens 2.0 * m_yaw/pitch value X

is not "exactly" the same as:

sens 2.0 * m_yaw/pitch value X = newValue

and then doing 1 * newValue afterwards.

(though the mathematical outcome, distance is the same, which I'm aware of)
Quote:
It's similar to interpolation on MCU/CPU level, but does not share the same general effect you would expect as game engine is calculated in angle degrees. The lower the sensitivity, the more general precision points you can aim at, albiet situational to resolution scale. Larger requiring more, or lower sensitivity; independent variable from general DPI which does not increase precision as you know. There is also no central value.

In game sensitivity in general is typically a multiplier of default yaw and pitch angles. Value of 0.022 in any engine with quake roots.

Example: Sensitivity "3" x 0.022 = recalculated to 0.066. But this isn't the true 0.066 angle you could set manually, granted valve locked off changing pitch in source.

Anyway, anything not using the median of 1.0 has recalculation effect, similar to what's experienced in mice not using their native to native circumvented resolution.

Edited by CorruptBE - 2/1/16 at 3:06pm
Desktop (Main)
(21 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5820K ASUS X99-A/USB 3.1  ASUS ROG Strix GeForce GTX 1080 Kingston HyperX 16GB 3Ghz  
Hard DriveHard DriveHard DriveHard Drive
Samsung 840 Pro Seagate Barracuda 1.5 TB Seagate Barracuda 2.0 TB Seagate Barracuda 4TB 
Hard DriveOptical DriveCoolingOS
Seagate Barracuda 4TB Le random dvd writer Corsair Hydro Series™ H100i Windows 10 Professional 64 bit 
MonitorKeyboardPowerCase
iiyama ProLite G2773HS Corsair K70 Super Flower 1200W (Platinum) Corsair 600T Black 
MouseMouse PadAudioAudio
Nixeus Revel Allsop Raindrop XL ASUS Xonar Essence STXII Sennheiser HD650 
Audio
Musical Fidelity X-Can v3 
  hide details  
Reply
Desktop (Main)
(21 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 5820K ASUS X99-A/USB 3.1  ASUS ROG Strix GeForce GTX 1080 Kingston HyperX 16GB 3Ghz  
Hard DriveHard DriveHard DriveHard Drive
Samsung 840 Pro Seagate Barracuda 1.5 TB Seagate Barracuda 2.0 TB Seagate Barracuda 4TB 
Hard DriveOptical DriveCoolingOS
Seagate Barracuda 4TB Le random dvd writer Corsair Hydro Series™ H100i Windows 10 Professional 64 bit 
MonitorKeyboardPowerCase
iiyama ProLite G2773HS Corsair K70 Super Flower 1200W (Platinum) Corsair 600T Black 
MouseMouse PadAudioAudio
Nixeus Revel Allsop Raindrop XL ASUS Xonar Essence STXII Sennheiser HD650 
Audio
Musical Fidelity X-Can v3 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Questions about relationship between ingame res and mouse dpi CS:GO