Recalbox Forum

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • recalbox.com
    • Gitlab repository
    • Documentation
    • Discord
    1. Home
    2. betlog-betlog
    3. Topics
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 25
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by betlog-betlog

    • betlog-betlog

      Input_axis_threshold - deadzone - analog stick range - etc
      GamePad/GPIO/USB encoder • dualshock 4 inputaxisthresh deadzone analog range • • betlog-betlog

      8
      0
      Votes
      8
      Posts
      5249
      Views

      betlog-betlog

      To be clear: The stick IS operating as analog. But the zone of movement where it is analog is very small, kicks in at a relatively high value (presumably at least 4096,4096), and reached 100% input almost immediately with only a very small movement. There is a large area towards the outside of the movement circle, seems like more than half of it, where all movement is at 100% despite not being anywhere near the physical limit of the stick movement. black=no effect grey= effect, engages suddenly at high value, and quickly reaches 100% with very little movement. white=100% effect, reaches 100% well before stick physically reaches edge of range. ^^^ bad ^^^ Modern controller sticks self-centre, so a huge analog deadzone is redundant, and suddenly outputting 100% effect when it's nowhere near 100% of it's physical movement range.. is very tedious.

    • betlog-betlog

      Mupen64plus problem
      Recalbox General • mupen64plus • • betlog-betlog

      5
      0
      Votes
      5
      Posts
      2041
      Views

      betlog-betlog

      I got the impression that mupen64 was for N64 games only....yes? In any case, the variables that I want to alter never actually stays changed after I set it, so I'm finding it difficult to even learn by trial and error. ie: input_axis_threshold in retroarch and AnalogDeadzone in mupen64 But I only made the original post in case it was a bug.