Confirming that this issue appears to be affecting the latest version. Running Minecraft v1.17.41 on a laptop with Windows 11 operating system:
Steps to Reproduce:
Connect a Nintendo Switch Pro controller to Windows as a Bluetooth device, and calibrate if necessary
Launch Minecraft and verify/adjust the "Controls: Controller" settings in the menu
Enter a world and attempt to sprint while walking forward by simultaneously pressing the associated controller button (clicking the left stick "L3" by default)
Observed Results:
The player only continues to walk forward and does not begin sprinting.
Expected Results:
The player should begin sprinting after pressing the mapped "sprint" button.
I've tried several different tests/variables, all with the same results. The game/computer recognize the L3 entry, as I'm able to manually change the mapping of "Sprint" to a different button, then map it back to L3. No matter which button is mapped, it doesn't properly sprint. Also getting the same result by using the default calibration after pairing, or after running the Windows Game Device Calibration Wizard.
PeteFred05
Confirming that this issue appears to be affecting the latest version. Running Minecraft v1.17.41 on a laptop with Windows 11 operating system:
Steps to Reproduce:
Connect a Nintendo Switch Pro controller to Windows as a Bluetooth device, and calibrate if necessary
Launch Minecraft and verify/adjust the "Controls: Controller" settings in the menu
Enter a world and attempt to sprint while walking forward by simultaneously pressing the associated controller button (clicking the left stick "L3" by default)
Observed Results:
The player only continues to walk forward and does not begin sprinting.
Expected Results:
The player should begin sprinting after pressing the mapped "sprint" button.
I've tried several different tests/variables, all with the same results. The game/computer recognize the L3 entry, as I'm able to manually change the mapping of "Sprint" to a different button, then map it back to L3. No matter which button is mapped, it doesn't properly sprint. Also getting the same result by using the default calibration after pairing, or after running the Windows Game Device Calibration Wizard.