Overclock.net › Forums › Components › Mice › Rival 110
New Posts  All Forums:Forum Nav:

Rival 110 - Page 32

post #311 of 387
Quote:
Originally Posted by S.M. View Post

So with what mouse tester test could one show this isn't a problem in the 110 ?

Seeing most people that actually have one are fairly positive about it, I'll probably order one and can do some tests if I know which ones.

I could only find this link about cpp and mice .That site seems really serious about peer reviewed methods though xD
Edited by Menthalion - 10/19/17 at 5:04am
post #312 of 387
Quote:
Originally Posted by Leopardi View Post

How come it isn't a problem, that anything above 500cpi is unusable?
lol, your g100s too
post #313 of 387
Quote:
Originally Posted by AloneInTheDuck View Post

lol, your g100s too
G100s is unusable because of the buttons not registering clicks tongue.gif
Leopardi
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7-4790K Gigabyte Z97X-Gaming 5  MSI GeForce GTX 980 OC 4GB 2x8GB Kingston 2133MHz DDR3 
Hard DriveOSMonitorPower
Crucial MX100 512GB Windows 8.1 Dell U2312HM Seasonic P-660 
CaseMouseMouse Pad
Fractal Design Define R4 Thermaltake Tt eSPORTS Ventus R Turtle Beach Drift 
  hide details  
Reply
Leopardi
(13 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7-4790K Gigabyte Z97X-Gaming 5  MSI GeForce GTX 980 OC 4GB 2x8GB Kingston 2133MHz DDR3 
Hard DriveOSMonitorPower
Crucial MX100 512GB Windows 8.1 Dell U2312HM Seasonic P-660 
CaseMouseMouse Pad
Fractal Design Define R4 Thermaltake Tt eSPORTS Ventus R Turtle Beach Drift 
  hide details  
Reply
post #314 of 387
Quote:
Originally Posted by Menthalion View Post

So with what mouse tester test could one show this isn't a problem in the 110 ?

Seeing most people that actually have one are fairly positive about it, I'll probably order one and can do some tests if I know which ones.

I could only find this link about cpp and mice .That site seems really serious about peer reviewed methods though xD
http://www.overclock.net/t/1535687/mousetester-software/0_100

Unusable is hyperbole. It still has a PCS over 1.5m/s (as opposed to 4.5m/s @ 500dpi.)

CPP is counts per poll. It's a measurement of reporting.
Money
(17 items)
 
Z575
(9 items)
 
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 @ 3.8Ghz MSI B350 Pro Carbon GIGABYTE R9 390 8GB 1100/1650Mhz 16GB Team DDR4-3000 
Hard DriveHard DriveHard DriveCooling
PNY CS1311 240GB - OS 2 x 2TB WD Black Raid 0 Synology DS416slim 4 x 1TB (raid 5) Corsair H100 
OSOSMonitorKeyboard
Windows 10 Pro ElementaryOS Loki BenQ XL2411 144Hz HPE 87 w/ Browns + Ducky PBT caps 
PowerCaseMouseAudio
EVGA 600W B2 Lian Li PCA05N Steelseries Rival 100 FiiO G10K + Philips SN9500HiFi 
CPUMotherboardGraphicsRAM
AMD A6-3420M @ 2.2Ghz 1.1v Lenovo Torpedo A55 6720g2 8GB Kingston 1600 CL9 
Hard DriveOSMouse
Samsung 840 250GB ElementaryOS x86_64 Abyssus 3.5G 
  hide details  
Reply
Money
(17 items)
 
Z575
(9 items)
 
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 @ 3.8Ghz MSI B350 Pro Carbon GIGABYTE R9 390 8GB 1100/1650Mhz 16GB Team DDR4-3000 
Hard DriveHard DriveHard DriveCooling
PNY CS1311 240GB - OS 2 x 2TB WD Black Raid 0 Synology DS416slim 4 x 1TB (raid 5) Corsair H100 
OSOSMonitorKeyboard
Windows 10 Pro ElementaryOS Loki BenQ XL2411 144Hz HPE 87 w/ Browns + Ducky PBT caps 
PowerCaseMouseAudio
EVGA 600W B2 Lian Li PCA05N Steelseries Rival 100 FiiO G10K + Philips SN9500HiFi 
CPUMotherboardGraphicsRAM
AMD A6-3420M @ 2.2Ghz 1.1v Lenovo Torpedo A55 6720g2 8GB Kingston 1600 CL9 
Hard DriveOSMouse
Samsung 840 250GB ElementaryOS x86_64 Abyssus 3.5G 
  hide details  
Reply
post #315 of 387
Interesting. The sensor reports the product ID to be 0x45, which is the same as in PMW3330. PMW3325 is 0x43. Pin locations are same as in PMW3325 (different vs. PMW3320 and A3050/S3059; uses 3pin SPI vs. 4pin in A3050). Also the sensor is running at 2.1 V as opposed to 3.3 V PMW3320/S3059. PMW3325 is 1.8-2.1 V VCC.

Not sure if my setup is completely correct however. I don't feel like cutting the traces and keeping the MCU in reset could still intervene somehow.
post #316 of 387
Got this mouse because it seemed like something I'd like. Sensor works great at lower dpis. The mouse build quality feels really good. My problem is sensor position. I hate when they move it off center. This would have been my primary if it wasn't for that issue. This was also my issue with the ventilator. All these really nice shapes/sizes are finally getting great sensors but they keep placing the sensor position too low!
post #317 of 387
Quote:
Originally Posted by Ramla777 View Post

This was also my issue with the ventilator.

lachen.gif
post #318 of 387
lachen.giflachen.gif
post #319 of 387
Quote:
Originally Posted by trism View Post

Interesting. The sensor reports the product ID to be 0x45, which is the same as in PMW3330. PMW3325 is 0x43. Pin locations are same as in PMW3325 (different vs. PMW3320 and A3050/S3059; uses 3pin SPI vs. 4pin in A3050). Also the sensor is running at 2.1 V as opposed to 3.3 V PMW3320/S3059. PMW3325 is 1.8-2.1 V VCC.

Not sure if my setup is completely correct however. I don't feel like cutting the traces and keeping the MCU in reset could still intervene somehow.

Could it be a 3325 with a 3330 SROM? tongue.gif
    
CPUMotherboardGraphicsRAM
Intel Core i7 4790K SABERTOOTH Z97 MARK 1 NVIDIA GeForce GTX 760 Corsair  
RAMHard DriveOptical DriveCooling
Corsair  Seagate ST31500341AS MSI DH24ABS Stock 
OSMonitorMonitorKeyboard
Windows 10 64 bit Samsung 2233RZ BenQ XL2411Z Filco Majestouch-2 (Cherry MX Black) 
MouseMouse PadAudio
Logitech G403 Razer Gigantus ROG Thunderbolt 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
Intel Core i7 4790K SABERTOOTH Z97 MARK 1 NVIDIA GeForce GTX 760 Corsair  
RAMHard DriveOptical DriveCooling
Corsair  Seagate ST31500341AS MSI DH24ABS Stock 
OSMonitorMonitorKeyboard
Windows 10 64 bit Samsung 2233RZ BenQ XL2411Z Filco Majestouch-2 (Cherry MX Black) 
MouseMouse PadAudio
Logitech G403 Razer Gigantus ROG Thunderbolt 
  hide details  
Reply
post #320 of 387
Probably indeed some sort of Frankenstein Sensor, perhaps it was cheaper to change the form factor so they could reuse shell design(s)?

Could it be this isn't the only model or refresh they're looking to use it in ? The Rival 150 / 160 question hasn't been answered yet.

But now we're already looking into what sensor it's based on and what's modified, is there any consensus how it performs and where it might lack ?
Edited by Menthalion - 10/20/17 at 5:22am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Mice
Overclock.net › Forums › Components › Mice › Rival 110