greater_than not working as expected

[Paul Foley]

I have the following config file for Brawlhalla. 

https://docs.google.com/spreadsheets/d/1JqXFRgkjtGnTrf7rhweE7JrjfmjwDg4iC4L6zs6WaF8/edit?usp=sharing

moving the mouth piece corresponds to pressing the d-pad directions. I want it so that if I move the mouthpiece left/right > 75% it also presses Y to dodge/dash. However, greater_than 50 is the highest value that works for me. If I set it to greater_than 75 it never triggers. Even if I push the mouthpiece all the way left/right to its physical limit the Y input still doesn't get triggered. I'm using the Quadstick FPS with Firmware 2365. Any suggestions?

Thanks, 

Paul 

[Fred Davison]

joystick_deflection_maximum		50
joystick_deflection_minimum		10

The joystick max position is so wide that the output value that is calculated never exceeds the value of the greater_than.

The "value" of the joystick position that is being compared to the greater_than value is affected by several factors but the TL;DR is to adjust the values you are using with the greater_than to something you are comfortable with.

https://quadstick.s3.amazonaws.com/documents/user_manual/um/joystick.htm  for the details.

The larger the joystick_deflection_maximum is, the less sensitive the joystick is.  The farther you need to move it to get to 100% output.  If you were to make the max 100 or 200, then the joystick would be very sluggish.  If you made the max 15, then the joystick would be too sensitive to use comfortably.  

FPS's can sometimes go down to 0 on the joystick_deflection_minimum.  I ship them out the minimum set to 2 and the maximum set to 20.   I think if the max was set to 20 instead of 50 the greater_than could be up to 99.

After all the internal Quadstick calculations for the joystick, the games themselves usually have several adjustments w.r.t sensitivity.  You just need to achieve a balance and decide where you want to adjust things.

[Paul Foley]

Thanks for the quick reply Fred. Below are the default joystick values I use in QMP. min 2 and max 30 which is similar to what you ship with. 

I added more tabs to the spreadsheet with different values for joystick_maximum_deflection and greater_than. https://docs.google.com/spreadsheets/d/1JqXFRgkjtGnTrf7rhweE7JrjfmjwDg4iC4L6zs6WaF8/edit?usp=sharing

All tabs work as desired except max_50_gt_70. In that one, if I push the mouthpiece all the way left/right to its physical limit the Y input still doesn't get triggered. This just makes me feel like I don't fully understand the relationship between  joystick_maximum_deflection  and greater_than. Based on the sliders in QMP, my understanding is that a joystick_maximum_deflection .of 50 means the output doesn't reach 100% until the mouthpiece is moved all the way to its physical limit. Is that incorrect? My understanding was that greater_than of 70 meant the mouthpiece had to be moved 70% of the way to its physical limit for the output to be triggered. But it seems like I'm missing some relationship between  joystick_maximum_deflection  and greater_than since greater_than 70 works when joystick_maximum_deflection is 30 but not when joystick_maximum_deflection is 50.

Based on what you said, I'm guessing maybe a joystick_maximum_deflection of 50 would in fact be beyond the physical limit of the mouthpiece. And that it's far enough beyond the limit that even pushing it all the way, I will not reach 70%. Is that the proper interpretation? 

[Fred Davison]

The numbers were originally scaled for the original model.  The Hall effect sensor in the FPS has a flatter curve so to reach the same value the max number has to be smaller than it was for the old joystick.

The physical position is scaled into a 0-100% output.  If the max position is too big, you won't get to 100.  The greater_than is compared to calculated output value, not the physical position.

I just checked with this test config:  any_direction test and the greater_than 25, 50 and 100 all worked at the expected points.    https://test.quadstick.com can be used to monitor the output values from the joystick. 1.00 would be 100% on the axes outputs.

[Paul Foley]

Got it, thanks for clarifying that for me. And good to know about  https://test.quadstick.com. I'll check that out.

Thanks!