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 5

post #41 of 54
To summarize my input, (hopefully won't dilute the thread) considering the present state of the game and the present state of the most used mice, from what i read before, in many threads and personal settings widely used:
- use 400/450 or 800/900 dpi in CSGO. These values are enough, accurate enough, and do not impair your aim potential under normal conditions. Choose what feels best to you and stay consistent.
- raw input is preferred, by whichever method you choose, but raw input off is ok if it's more comfy to you.
- 500 Hz are enough for most hw setups, but most newer, competitive mice handle 1000 Hz well.
- choose a sens that lets you turn L/R 150-170 degrees comfortable on your used space and stick with it.

Hopefully it may help some new players or ppl that are unsure due to all these technical arguments with a good starting point smile.gif
post #42 of 54
I play on 400 DPI and 2.8 sens in CS:GO and I tried 800 DPI and 1.4 as a test. Although the movement needed to do a 360° is still the same, I have the feeling that crosshair is more nervous when trying to aim precisely at a long range. Pit => A on dust2 for example. And 400 DPI feels smoother and more controlled.

So 400 DPI is what is prefer.
post #43 of 54
Quote:
Originally Posted by broodro0ster View Post

I play on 400 DPI and 2.8 sens in CS:GO and I tried 800 DPI and 1.4 as a test. Although the movement needed to do a 360° is still the same, I have the feeling that crosshair is more nervous when trying to aim precisely at a long range. Pit => A on dust2 for example. And 400 DPI feels smoother and more controlled.

So 400 DPI is what is prefer.

400 has more degree skipping, 800 is smoother. The "nervous" is just your hand shaking or being unsteady.
my baby
(14 items)
 
   
CPUMotherboardGraphicsRAM
4690k ASUS H97M-e/CSM GTX 970 Mixed Brand 
Hard DriveOSMonitorKeyboard
Samsung 850 EVO Windows 10 ASUS VG248QE Corsair K65 
PowerCaseMouseMouse Pad
Corsair CX500 Corsair SPEC-01 Steelseries Kinzu Sudden Attack SteelSeries QcK+ 
AudioAudio
HyperX Cloud II Sennheiser Momentum IEMs 
CPUGraphicsRAMHard Drive
i7-2860QM@2.5GHz AMD Radeon 6770M 1GB Crucial 16GB DDR3L 1333MHz SODIMM For Mac  Samsung 850 EVO  
OSMonitorMouseAudio
MAC OSX El Capitan High-res Upgraded display 1680x1050 15.6" Steelseries Kinzu Sudden Attack RHA MA750 
  hide details  
Reply
my baby
(14 items)
 
   
CPUMotherboardGraphicsRAM
4690k ASUS H97M-e/CSM GTX 970 Mixed Brand 
Hard DriveOSMonitorKeyboard
Samsung 850 EVO Windows 10 ASUS VG248QE Corsair K65 
PowerCaseMouseMouse Pad
Corsair CX500 Corsair SPEC-01 Steelseries Kinzu Sudden Attack SteelSeries QcK+ 
AudioAudio
HyperX Cloud II Sennheiser Momentum IEMs 
CPUGraphicsRAMHard Drive
i7-2860QM@2.5GHz AMD Radeon 6770M 1GB Crucial 16GB DDR3L 1333MHz SODIMM For Mac  Samsung 850 EVO  
OSMonitorMouseAudio
MAC OSX El Capitan High-res Upgraded display 1680x1050 15.6" Steelseries Kinzu Sudden Attack RHA MA750 
  hide details  
Reply
post #44 of 54
Thread Starter 
Wanted to try and stay away from the pixel skipping element of this. Pretty much everyone knows if you try to play on 400dpi at 1920 and use 10 sensitivity in game, you'll probably skip pixels tongue.gif.

Anyone have any success at least trying what i've done?

It still feels great for me and I'm so glad to have just taken a stab at it. (fyi, I saw another post earlier talking about mouse feeling delayed/floaty. Make sure your within your native dpi steps for your mouse.)
post #45 of 54
Quote:
Originally Posted by hallux View Post

Wanted to try and stay away from the pixel skipping element of this. Pretty much everyone knows if you try to play on 400dpi at 1920 and use 10 sensitivity in game, you'll probably skip pixels tongue.gif.

Anyone have any success at least trying what i've done?

It still feels great for me and I'm so glad to have just taken a stab at it. (fyi, I saw another post earlier talking about mouse feeling delayed/floaty. Make sure your within your native dpi steps for your mouse.)
There is no such thing as pixel skipping in a 3D enviroment, you can however skip degrees, example

(YAW*SENS*CPI)/CPI=degrees moved per mouse count
(0.22*10*400)/400=2.2
This means for every mouse count you are moving 2.2 degrees, you want this number to be as low as possible for maximum accuracy.

Resolution has nothing to so with it either.
my baby
(14 items)
 
   
CPUMotherboardGraphicsRAM
4690k ASUS H97M-e/CSM GTX 970 Mixed Brand 
Hard DriveOSMonitorKeyboard
Samsung 850 EVO Windows 10 ASUS VG248QE Corsair K65 
PowerCaseMouseMouse Pad
Corsair CX500 Corsair SPEC-01 Steelseries Kinzu Sudden Attack SteelSeries QcK+ 
AudioAudio
HyperX Cloud II Sennheiser Momentum IEMs 
CPUGraphicsRAMHard Drive
i7-2860QM@2.5GHz AMD Radeon 6770M 1GB Crucial 16GB DDR3L 1333MHz SODIMM For Mac  Samsung 850 EVO  
OSMonitorMouseAudio
MAC OSX El Capitan High-res Upgraded display 1680x1050 15.6" Steelseries Kinzu Sudden Attack RHA MA750 
  hide details  
Reply
my baby
(14 items)
 
   
CPUMotherboardGraphicsRAM
4690k ASUS H97M-e/CSM GTX 970 Mixed Brand 
Hard DriveOSMonitorKeyboard
Samsung 850 EVO Windows 10 ASUS VG248QE Corsair K65 
PowerCaseMouseMouse Pad
Corsair CX500 Corsair SPEC-01 Steelseries Kinzu Sudden Attack SteelSeries QcK+ 
AudioAudio
HyperX Cloud II Sennheiser Momentum IEMs 
CPUGraphicsRAMHard Drive
i7-2860QM@2.5GHz AMD Radeon 6770M 1GB Crucial 16GB DDR3L 1333MHz SODIMM For Mac  Samsung 850 EVO  
OSMonitorMouseAudio
MAC OSX El Capitan High-res Upgraded display 1680x1050 15.6" Steelseries Kinzu Sudden Attack RHA MA750 
  hide details  
Reply
post #46 of 54
Ideally you simply remain below a value where 1 count results into movement that is NOT bigger then a single pixel on your monitor (near crosshair).
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
post #47 of 54
no. please stop repeating yourself
post #48 of 54
if you're playing on 16000x9000, even if you "skip" 10 pixels for every mouse count, it doesn't matter at all if the enemy's head is 100 pixels wide.
so the only thing that matters in the end is ratio between the angular granularity corresponding to your in-game sens, and the finest angle you need to aim at in-game
main
(15 items)
 
old
(14 items)
 
 
CPUMotherboardGraphicsRAM
4770k maximus vii impact nvidia gtx 970 crucial ballistix tactical 16gb 
Hard DriveCoolingOSMonitor
crucial mx100 noctua nh-c14 windows 7 ultimate sony cpd-g520 
KeyboardPowerCaseMouse
kbp v80 matias quiet silverstone sx500-lg ncase m1 v3 logitech g100s with mcu replaced by teensy2.0 
Mouse PadAudioAudio
allsop raindrop xl chord mojo hifiman re-600 
CPUMotherboardGraphicsRAM
i7 920 evga x58 sli le galaxy gtx 460 crucial something 3x1gb 
Hard DriveCoolingOSMonitor
intel 330 180gb scythe kotetsu windows 8.1 pro sony cpd-g520 
KeyboardPowerCaseMouse
logitech k120 silverstone st75f-gs nxzt h440 evga torq x5 
Mouse PadAudio
allsop raindrop mobo 
  hide details  
Reply
main
(15 items)
 
old
(14 items)
 
 
CPUMotherboardGraphicsRAM
4770k maximus vii impact nvidia gtx 970 crucial ballistix tactical 16gb 
Hard DriveCoolingOSMonitor
crucial mx100 noctua nh-c14 windows 7 ultimate sony cpd-g520 
KeyboardPowerCaseMouse
kbp v80 matias quiet silverstone sx500-lg ncase m1 v3 logitech g100s with mcu replaced by teensy2.0 
Mouse PadAudioAudio
allsop raindrop xl chord mojo hifiman re-600 
CPUMotherboardGraphicsRAM
i7 920 evga x58 sli le galaxy gtx 460 crucial something 3x1gb 
Hard DriveCoolingOSMonitor
intel 330 180gb scythe kotetsu windows 8.1 pro sony cpd-g520 
KeyboardPowerCaseMouse
logitech k120 silverstone st75f-gs nxzt h440 evga torq x5 
Mouse PadAudio
allsop raindrop mobo 
  hide details  
Reply
post #49 of 54
Quote:
Originally Posted by qsxcv View Post

if you're playing on 16000x9000, even if you "skip" 10 pixels for every mouse count, it doesn't matter at all if the enemy's head is 100 pixels wide.
so the only thing that matters in the end is ratio between the angular granularity corresponding to your in-game sens, and the finest angle you need to aim at in-game

Yeah but let's say you're skipping 20 pixels for every 100...even if the head is 100 pixels big, if you flick to it then you have 4/5 chance to get a headshot. Why not up the DPI and make it 100% chance?
post #50 of 54
not sure I follow that logic. If you flick, your error is going to be based on your real movements, not any setting.
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