I'm using GInput with IV-style controls, and the latest compiled version of Classic Axis. When lightly holding the trigger to enable free-aim, Tommy enters auto-aim first; fully pressing the trigger also enables auto-aim. This puts free-aim between two instances of auto-aim.
Could the mod be recognizing the lowest trigger values as higher values somehow? It appears that line 1235 of ClassicAxis.cpp is written properly, since it's correctly asking for auto-aim to be disabled when the trigger is less than 50% pressed... Could this be a result of the changes to that file in commit f2f804e (lines 1196 through 1201)?
Perhaps this is a limitation of some kind? For further reference, I'm using an Xbox Series X controller.
I'm using GInput with IV-style controls, and the latest compiled version of Classic Axis. When lightly holding the trigger to enable free-aim, Tommy enters auto-aim first; fully pressing the trigger also enables auto-aim. This puts free-aim between two instances of auto-aim.
Could the mod be recognizing the lowest trigger values as higher values somehow? It appears that line 1235 of ClassicAxis.cpp is written properly, since it's correctly asking for auto-aim to be disabled when the trigger is less than 50% pressed... Could this be a result of the changes to that file in commit f2f804e (lines 1196 through 1201)?
Perhaps this is a limitation of some kind? For further reference, I'm using an Xbox Series X controller.