![]() ![]() Then you can also remove other likely problematic things such as the mouse identifying itself as a mouse+keyboard to Windows at the same time. Unless Logitech can fix this issue (they likely have no idea where to even start), they'll likely have to go driverless too - at least for the actual performance, non-casual line - if they want to compete in the big leagues. Even if people don't know the issue exists, they just wind up with a better, more consistent experience because they're unable to gimp their mouse with non-deterministic software. Due to being driverless, they're not exposed to this issue. This is why I believe lots of pros have gravitated towards Zowie mice. I don't know if it's generating different DPIs each time, or doing something else entirely, but everything from cursor sensitivity, speed, to feeling of a dead zone or lack thereof completely changes each time. It still gives you the wildly, non-deterministic mouse settings each time you hit save to upload a new profile to the mouse. Possible solution for debian-based distributions would be: sudo apt-get upgrade Miscellaneous The program is not complete yet. However, the Linux kernel since version of 5.2 may recognize IDs properly. So there's a few changes between the two if people are trying to identify possible differences. Some logitech devices use the same id for bluetooth receiver. I now have to buy a new G302 simply because installing the software permanently destroys the mouse, never capable of getting it back to factory performance state.Ĭlick to expand.I have not studied the differences in these softwares much, but If I remember correctly, the default state of LGS was not using a "persistent profile" and G-Hub seems to do something differently, possibly having them as a default setting. You can attempt to re-upload new settings to the mouse over and over and sometimes it will get close to how it was from the factory, but generally never quite as good. It's more difficult to notice on a 3366, but the same thing still happens. This behavior is far easier to notice on AM010 sensors because the sensor really has no positive quality at all besides hair trigger sensor response being about the closest modern thing you can get to a MLT04 in that regard. You will be permanently STUCK with inferior cursor control compared to what it shipped with from the factory. Then after you unplug it, it will feel like an entirely different mouse that you will NEVER recreate the fresh out of the box factory movement. Simply take a brand new mouse like a G302 fresh out of the box that's never been exposed to any form of Logitech software (the mouse controls great fresh out of the box), run it through whatever benching/diagnostics, then do the act of just plugging the mouse in to another computer with G-hub already installed (without even changing a single setting, just plugging it in then unplugging it). ![]() The results should be easily quantifiable if anyone wants to actually test it (QVC). But this phenomenon with Logitech's new G-hub software is exponentially worse than pre-G-hub software where even a caveman should be able to tell. It's like the method of writing data to the mice these companies are using is completely incapable of any deterministic behavior WHATSOEVER. Even if you're saving a setting of 800 DPI, sometimes it will feel slower and lagging behind, other times faster. g810-led -gn modifiers C955FF g810-led -gn indicators 0FFF00 g810-led -kn numlock 0FFF00 g810-led -kn scrolllock 0FFF00 g810-led -kn capslock 0FFF00 # Set backspace, escape, and delete red.So, I have always said that anytime you install mouse software and save settings to the mouse, it always gives you a wildly different result each time whether it's Logitech or some other company's software. g810-led -gn numeric FFE600 # Set top numbers to a light green. g810-led -gn fkeys ffffff g810-led -gn arrows ffffff g810-led -gn functions ffffff g810-led -kn w ffffff g810-led -kn a ffffff g810-led -kn s ffffff g810-led -kn d ffffff # Set the num-pad to a light yellow. g810-led -an 1490E1 # Set fkeys and WASD to white. #!/bin/bash # Set all keys to a light blue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |