Software: 0.93.72
Issue: The Axis2Buttons boolean function for Logical or Virtual axis 9 freezes the device if the axis is moved towards the max value. The device must be restarted to recover.
For this test I set up logical axis 9 to read from physical axis 1 on the SCE Gladiator:
Moving the roll axis to the left, towards min value, results in the correct activation of the buttons by A2.
However moving the axis to the right leads to the axis being frozen. Both buttons and axes become unresponsive. Here is the position of the axis at the moment the device froze:
A2B splits the axis in 7 zones, so button P109 should trigger when the axis moves past ~37449. The device froze when it passed 37508 (moving the axis slowly).
I aditionaly made the following observations:
The issue only affects logical/virtual axes 9. A2B on other axes seems to work fine.
Also, the issue only affects logical/virtual axis 9 IF the first external device expected in the current autoconfiguration is present.
I am able to get A2B on logical 9 to work without freezing if the SCG is moved to the 2nd position in the list of external devices:
