Shape is perfectly fine. I like it a lot. I would make the butt shallower but it's not particular significant.
Feet are ****. I don't worry about damaging the bottom foot opening the mouse. I just apply a pattern of tape over it afterwards because things are better like that anyways.
Sensor doesn't track immediately if you set it down while moving particularly fast. This happens to the MLT04 and 3310 too, but on the MLT04 it seems to behave less poorly and on the 3310 it happens at a higher speed and seems like it starts tracking more easily.
The sensor tracks and tracks awkwardly when near the liftoff distance. LOD is rather high, probably almost three CDs.The sensor has a minor Z-axis Y movement problem
. Lifting the mouse causes the cursor to move downwards, and placing down the mouse causes the cursor to move upwards.
At this point I move from linux to windows, plug in the mouse, install Synapse 2, log in, and Synapse 2 begins updating something; "Do not disconnect any Razer device or shut down your computer until the update is finished." The update moves at glacial speed of 1% per thirteenish seconds. Fantastic. A command prompt window flashes at 85%, then a few seconds later the update immediately jumps to 100%.
At this point the main window of the driver software opens and I can't click anything on it. I can click other windows programs and the taxk bar, but not this. This window doesn't show up in task manager. I close razer synapse through the task tray and reopen it through the start menu. A command prompt flashes when it first opens this time. The window is now interactable and has a task bar entry. I close it and reopen it to see if the command prompt flashes again. It doesn't, there's a login splash screen instead. Apparently the software update was partially incomplete.
The driver software is extremely hard to read because my windows machine is currently running a blurry CRT and a lot of the text is "dark gray on darker gray".
I set the DPI settings and polling rate with little issue.
I mess with the lighting settings and something glitches out and a certain option wouldn't take inputs until I pressed random stuff. Nice.
I go to surface calibration to reduce the LoD because of the previously-mentioned Z-axis problem, and it won't let me do anything until I select a razer mousepad. The liftoff distance setting doesn't work. Nice. I unselect surface calibration.
I unplug the mouse and put it back in my linux system. I check polling rate with evhz. It's 1000hz. "MS Paint test" confirms DPI is also still set to 1000. I press the DPI button five times and it ends up on one of the DPI steps. (I set all the DPI settings to values that aren't contained in the set of default DPI steps.) Oh well.
The mouse is held together by cleverly-shaped plastic and a single screw. I remove the weight. Reconfirmed the sensor is a 3329 and the switches are chinese omrons. I put it back together and add teflon mouse tape.
I switch back to windows and compare it to the KPM FW1.11 in mouse comparator. Top: synapse open. Bottom: synapse closed. Left: tracking test. Right: hammer test. (Note that only the first two or three tracked samples are important/valid in the hammer test, because both mice go moving at random speeds after the immediate strike. The hammer test is used to check for MCU sample buffering and obvious heavy smoothing, and delayed tracking startup behavior but that's rather rare.)
The bottom is labeled "abyssus" but is the abyssus v2. I'm lazy.
behind the kpm with the mouse connected to synapse
, and 1ms
behind the kpm when the mouse is not.
Note that the KPM has a delay (less than 1ms, but still present) relative to the WMO. Note that it's not necessary to uninstall synapse. Just prevent it from running before plugging in the mouse. This means not running synapse on startup if you don't want to replug your mouse after shutting off synapse every morning.
I check the mouse button latency tester.
It has three or five milliseconds more mouse button latency than the KPM FW1.11
; the KPM FW1.11 is approximately eight milliseconds faster than the WMO. Movement and liftoff don't seem to affect it.
I'm probably going to keep it and use it despite the minor problems because it's a bit better than my WMO in everything but sensor response, where it's less than 2ms behind.
Summary: Good shape, feels fine. Has a Z-axis bug. Button latency is acceptable but not stellar. Motion samples are delayed by like 1ms for some reason, 2ms with synapse. Prime target for modding, but it has a 3329.
Subjectively, the tracking feels pretty regular
, and I like it a lot.Edited by wareya - 7/23/16 at 12:37pm