Rid of Jittery Mouse
Posted: Sun Sep 01, 2019 12:01 am
I have a 3200dpi surface mouse, I am using this configuration http://gimx.fr/forum/viewtopic.php?f=9& ... 3&start=10. Before editing the configuration, on fpsconfig gimx app I set my mouse dpi to 3200. Then manually changed it on the code, <controller id="1" dpi="3200" type="XOnePad"> . I load the game up, my settings are all aims on max speed, DZ for RS is at 5 and LS is at 10. After calibrating mouse using ctrl+F1, my new DZ is 12, new acceleration is .58 for both profile 1 and 2. Mouse is still jittery at this point, but more precisely: The crosshairs on screen moves in segments noticeably instead of smooth regardless of the speed at which I move the mouse on the mouse pad. If I move the physical device slowly, the crosshairs move slow but at random, it speeds up and slows down. If I move the mouse fast, for quick aim changes, the crosshairs do not respond and instead move even slower than me physically moving the mouse slowly on the pad.
The issue here is the emulator doesnt know of the maximum threshold of the right stick, and once it passes the threshold signal is lost and crosshair moves at a constant slow speed in the direction that corresponds to the emulation of the right stick through the use of the mouse. The solution is to put a deadzone not only for the resting spot of the mouse but also a deadzone at the threshold of the right stick of the controller.
So I started changing the "x/y circle test, radius=512" and I set the radius to 1. To my astonishment, this fixed 2 things, 1) I lost the jittery mouse motion 2) fixed how fast the crosshairs moved depending on the speed I move the mouse, fast motion corresponds with fast crosshair movement and slow with slow; I dont even need to change the buffer size or the filter to fix anything!
So I press Ctrl+F1 to save settings, and my crosshair movement is back to garbage. I click Ctrl+F1 and click F10, the radius is at a number so small that there is no movement on my crosshairs--but here is the thing, I have perfect aim movement on the crosshairs for as long as I stay on F10 with a value of 80 or less.
Can someone explain what is going on??
THIS IS WHAT I NEED HELP WITH how to set it so that when I load the configuration up, the radius loads up at 77 because it doesnt save when I click ctrl+F1.
Another issue, mouse capture is lost when I click the mouse buttons; on my laptop, the mouse cursor re-appears on the screen when I use RMB and LMB to aim and shoot while a configuration is being run. This was a problem that appeared after I download the newest gimx update.
The issue here is the emulator doesnt know of the maximum threshold of the right stick, and once it passes the threshold signal is lost and crosshair moves at a constant slow speed in the direction that corresponds to the emulation of the right stick through the use of the mouse. The solution is to put a deadzone not only for the resting spot of the mouse but also a deadzone at the threshold of the right stick of the controller.
So I started changing the "x/y circle test, radius=512" and I set the radius to 1. To my astonishment, this fixed 2 things, 1) I lost the jittery mouse motion 2) fixed how fast the crosshairs moved depending on the speed I move the mouse, fast motion corresponds with fast crosshair movement and slow with slow; I dont even need to change the buffer size or the filter to fix anything!
So I press Ctrl+F1 to save settings, and my crosshair movement is back to garbage. I click Ctrl+F1 and click F10, the radius is at a number so small that there is no movement on my crosshairs--but here is the thing, I have perfect aim movement on the crosshairs for as long as I stay on F10 with a value of 80 or less.
Can someone explain what is going on??
THIS IS WHAT I NEED HELP WITH how to set it so that when I load the configuration up, the radius loads up at 77 because it doesnt save when I click ctrl+F1.
Another issue, mouse capture is lost when I click the mouse buttons; on my laptop, the mouse cursor re-appears on the screen when I use RMB and LMB to aim and shoot while a configuration is being run. This was a problem that appeared after I download the newest gimx update.