Overclock.net › Forums › Components › Mice › An Overview of Mouse Technology
New Posts  All Forums:Forum Nav:

An Overview of Mouse Technology - Page 3

post #21 of 110
Why is this still not a sticky?
Fast enough
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 6600k ASUS Z170 Pro Palit GeForce GTX 980 Ti 16 GB 
Hard DriveHard DriveHard DriveCooling
Samsung Spinpoint F1 Samsung Spinpoint F1 Samsung SSD 750 EVO Alpenföhn Groß Clock'ner 
OSMonitorKeyboardCase
Windows 7 x64 BenQ XL2411 Lioncast LK20 Sharkoon Rebel9 
MouseMouse PadAudio
Logitech G Pro Zowie G-SR Creative Sound Blaster X-Fi Titanium PCI-Express 
  hide details  
Reply
Fast enough
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 6600k ASUS Z170 Pro Palit GeForce GTX 980 Ti 16 GB 
Hard DriveHard DriveHard DriveCooling
Samsung Spinpoint F1 Samsung Spinpoint F1 Samsung SSD 750 EVO Alpenföhn Groß Clock'ner 
OSMonitorKeyboardCase
Windows 7 x64 BenQ XL2411 Lioncast LK20 Sharkoon Rebel9 
MouseMouse PadAudio
Logitech G Pro Zowie G-SR Creative Sound Blaster X-Fi Titanium PCI-Express 
  hide details  
Reply
post #22 of 110
Quote:
Originally Posted by Arizonian View Post

Great write up. thumb.gif

Looking into sticky. smile.gif

Update: 1/9/2013 - Under Editor review.

Shameless bump hypocritesmiley.png , make this thread a sticky thumb.gif
Edited by CtrlAltel1te - 2/27/13 at 10:10am
post #23 of 110
Thread Starter 
Ok, so I recently realized I'm quite silly... With all my work on BBCode in the last two years I had forgotten basic html anchoring techniques rolleyes.gif, so I finally decided to remedy that. This version of the article now has full anchor navigation to each section and top of the document. Additionally I want to slightly re-work the 2-D section in optimal sensitivity as its not the most clear or precise in some ways.
post #24 of 110
Hi,

Great article, some comments:

xiii) microswitches
I feel this chapter could add some more information.
As for example common differntiators of popular microswitches etc.
Also the so frequent happening double click issue could be added.

xvii) SROM
It should maybe be added that SROM is provided (and developed) by the sensor manufacturer and not from the mouse manufacturer/brand.
Also the srom of the sensor ic is not necessarily a part of the firmware update.To upgrade the srom later the firmware/hw needs to support that feature (not all mice do, even though they support updating of the firmware).
There is no risk in updating the firmware if the implementation is solid. Even power outtage or similar should not brick the mouse. However you would need another mouse to start the firmware update of the "temporarily" bricked mouse again smile.gif.
Unfortunately not all firmware update routines are as solid as they should be so in some cases of poor implementation you actually will brick your mouse - blame the manufacturer.

Other topics that could be added would be wheel/mousefeet/cable and maybe even wireless wink.gif.
post #25 of 110
Quote:
Originally Posted by Ino. View Post

Why is this still not a sticky?

same question i'm asking.

sticky pls
post #26 of 110
Time to bump again:

Sticky pls? Too many people still relate to other guides with wrong or outdated infos...
Fast enough
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 6600k ASUS Z170 Pro Palit GeForce GTX 980 Ti 16 GB 
Hard DriveHard DriveHard DriveCooling
Samsung Spinpoint F1 Samsung Spinpoint F1 Samsung SSD 750 EVO Alpenföhn Groß Clock'ner 
OSMonitorKeyboardCase
Windows 7 x64 BenQ XL2411 Lioncast LK20 Sharkoon Rebel9 
MouseMouse PadAudio
Logitech G Pro Zowie G-SR Creative Sound Blaster X-Fi Titanium PCI-Express 
  hide details  
Reply
Fast enough
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 6600k ASUS Z170 Pro Palit GeForce GTX 980 Ti 16 GB 
Hard DriveHard DriveHard DriveCooling
Samsung Spinpoint F1 Samsung Spinpoint F1 Samsung SSD 750 EVO Alpenföhn Groß Clock'ner 
OSMonitorKeyboardCase
Windows 7 x64 BenQ XL2411 Lioncast LK20 Sharkoon Rebel9 
MouseMouse PadAudio
Logitech G Pro Zowie G-SR Creative Sound Blaster X-Fi Titanium PCI-Express 
  hide details  
Reply
post #27 of 110
This need a sticky
Gaming Setup
(15 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7 2700K Z77 Extreme6 Intel HD Graphics 3000 (GT2+) NVIDIA GeForce GTX 780 3GB 
RAMHard DriveCoolingOS
CORSAIR Vengeance 16 GB  OCZ 120GB Vertex 3 SATA COOLER MASTER Hyper 212 EVO  Windows 8.1 64 Bit 
MonitorKeyboardPowerCase
Benq XL2420TE Razer Blackwidow 2014 Thermaltake Smart M 850W Power Supply COOLER MASTER HAF XM RC-922XM-KKN1 Latch Side P... 
MouseMouse PadAudio
Deathadder 2013 SteelSeries QCK + Astro A40 2013 
  hide details  
Reply
Gaming Setup
(15 items)
 
  
CPUMotherboardGraphicsGraphics
Intel Core i7 2700K Z77 Extreme6 Intel HD Graphics 3000 (GT2+) NVIDIA GeForce GTX 780 3GB 
RAMHard DriveCoolingOS
CORSAIR Vengeance 16 GB  OCZ 120GB Vertex 3 SATA COOLER MASTER Hyper 212 EVO  Windows 8.1 64 Bit 
MonitorKeyboardPowerCase
Benq XL2420TE Razer Blackwidow 2014 Thermaltake Smart M 850W Power Supply COOLER MASTER HAF XM RC-922XM-KKN1 Latch Side P... 
MouseMouse PadAudio
Deathadder 2013 SteelSeries QCK + Astro A40 2013 
  hide details  
Reply
post #28 of 110
Hm, i somehow don't get it. Read the article or parts of it few time but when it comes to the calculations starting at "Pixel Considerations" it get's complex. It sure doesn't help that english isn't my native language. While i get that funender is manly just good for fast calculating i can't manage to calculate min/max usefull cpi.

So as example: CS:GO (which i played fine on till recent changes - either just 4 fun) i had 1600cpi 2.4sens on 1920x1080 with 150fps. fov we just can assume at 106? m_yaw, windows sens is default, no accel (btw: so if i get it right: settings sens. to 1 there should be no difference to raw input in my case? But that would require an nearly impossible to match high dpi.) Now either i should have read before i just calculated using above link and set CPI to next matching 1075 and found out it allows much more precise or easier tracking than before (even if i had to lift off the mouse sometimes). But not that you say: sure with lower sens/ratio - at 1000dpi i tried too i had (still have) problems. Sure i could try out more settings but wanted to start from some calculated point. Back to that - i am not sure how to take the control area in account?
post #29 of 110
With your mouse, you should set raw input, sensitivity 1.0 and adjust DPI to your liking. When you lowered DPI from 1600 to 1075 you changed your cm/360 too. It allowed for more precise aiming because cm/360 distance increased.
post #30 of 110
Quote:
Originally Posted by diNovoM View Post

Hm, i somehow don't get it. Read the article or parts of it few time but when it comes to the calculations starting at "Pixel Considerations" it get's complex. It sure doesn't help that english isn't my native language. While i get that funender is manly just good for fast calculating i can't manage to calculate min/max usefull cpi.

So as example: CS:GO (which i played fine on till recent changes - either just 4 fun) i had 1600cpi 2.4sens on 1920x1080 with 150fps. fov we just can assume at 106? m_yaw, windows sens is default, no accel (btw: so if i get it right: settings sens. to 1 there should be no difference to raw input in my case? But that would require an nearly impossible to match high dpi.) Now either i should have read before i just calculated using above link and set CPI to next matching 1075 and found out it allows much more precise or easier tracking than before (even if i had to lift off the mouse sometimes). But not that you say: sure with lower sens/ratio - at 1000dpi i tried too i had (still have) problems. Sure i could try out more settings but wanted to start from some calculated point. Back to that - i am not sure how to take the control area in account?


There is no need to set sens to 1 and use alot of dpi, the difference will be placebo and you are hurting your aim by enabling raw input, as it always increases input latency(huge in source engine games), WM_MOUSEMOVE is totaly fine unless you want to use some stupid 5700 dpi and 0.01 sens, cuz you will get massive negative acceleration.

Just use enought dpi for your cm/360, fov and screen rez. You can test for pixel skipping by moving the mouse in-game for very slowly diagonally or in very small circles - if you dont see pixel skip then you are totally fine.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › An Overview of Mouse Technology