when using --refresh 1 to raise the refresh rate to 1000 Hz it works as long as my input devices don't push events at 1000 Hz too, else it crashes gimx. Then I have to replug the teensy (pushing the button apparently doesn't work) let it be recognized again.
The error messages are always something like:
Code: Select all
../common/posix/async.c:330 write: only 58 written (requested 66)
0 1486306202.854325
../common/posix/async.c:327 async_write: write failed with error: Resource temporarily unavailable
While I'm using the keyboard or a DS4 it can be seen through --status that their input events get pushed without problems. I guess they don't update at 1000 Hz. If my mouse is set to poll at 125 Hz or 250 Hz it also works (but of course the in-game movement is very clunky at 125 Hz), but having it poll at 500 Hz or 1000 Hz breaks gimx, interestingly, since using 1000 Hz or 500 Hz mouse poll in --refresh 2 which is a refresh rate of max 500 Hz mode works.
Setup:
My mouse is a Lioncast LM30 which has a max 16400 DPI and can be set to poll 125Hz, 250Hz, 500Hz or 1000 Hz. Also I'm using a Teensy++ 2.0 and a standard USB UART Interface. Ubuntu 16.04 and the usbhid kernel module has it's refresh rate set to 1 (=1000 Hz) through the command
Code: Select all
sudo rmmod usbhid && sudo modprobe usbhid mousepoll=1
Motivations:
By adding --refresh [Integer] to the command line you're able to raise the GIMX refresh rate to a higher value than the standard 100 Hz which the GUI application provides. Given your mouse has a high refresh rate this can significantly improve the fluidity of your aiming in an FPS like e.g. Fallout 4. (A feature I'd wish for to be added back to the GUI again). --refresh 2 gives a max refresh rate of 500 Hz but it's still not enough in some games (e.g. Fallout 4)