cheater wrote: ↑24 Dec 2020, 17:07
is there a way to use the ploopy with other sensors, like eg the logitech hero?
The tracking improvements from the 3310 to the 3360 were huge, the 3360 to the Hero... not so much. The 3360 (originally the Logitich exclusive 3366 in the original G502 and G303) has the benefit of better surface tuning (to control lift off distance), Qsxcv's open source firmware and it can be bought as a break out board on Tindie (the sensor is not exclusive to one mouse maker).
The Hero sensor is just as good tracking wise, and a firmware update upped the max DPI even further (25k vs. 16k
![Confused :?](./images/smilies/icon_e_confused.gif)
). That increase is totally irrelevant when anything above 3000 DPI is literally unusable
![Laughing :lol:](./images/smilies/icon_lol.gif)
. It is also more power efficient (dynamic framrate?). That is part of what made Logi's new wireless gaming mice so competitive).
For wired DIY stuff the 3360 is ideal (Logi created the Hero sensor in house for power efficiency and to avoid licensing fees, not because of tracking issues in the 3360/3366 sensor). Hell for a trackball a "laser" sensor like the ADNS 9800 might work well. No reason to reverse engineer another sensor which is harder to source, and whose only benefits are wireless applications.
If you have an older mouse you want to make better you should do something like this
https://youtu.be/nyb6M89QrWI and stick with the 3360 module on Tindie, a teensy, and Qsxcv derived firmware.