Nintendo switch pro controller analog stick problems in Windows 10

Can confirm this. It happens to me too. It's not the controller as I can't run even when pushing the left stick button. And it doesn't happen with mouse and keyboard under the same circumstances. Would love to be able to play this from my couch with my controller on my TV.

The issue is that the controller, by default, isn't calibrated, and Minecraft ignores any recalibration you apply. If you go into the devices and printers section of control panel, then go into the pro controller's game controller settings, you get a view of every output from the controller, including analog sticks. The sticks' default behavior is shown in the files named "both sticks [direction]". You can see how the uncalibrated sticks don't reach all the way up, preventing sprinting, and don't reach the sides either. You might think that calibrating the sticks in the settings tab of the menu helps, but it doesn't. For some reason, Windows 10 Bedrock ignores any calibration you do in this menu and always uses the default, uncalibrated settings. I can use the calibrated sticks in other, non-UWP games such as super smash flash and mari0, and the Java libraries I use when making games use the calibration as well. So, to solve the issue, the devs either need to find a way for the game to use these calibration settings or they need to allow recalibration within the game itself.

Yes, forgot to mention I had already calibrated it. I can confirm that, after calibration, the sticks have what seems to be the correct range (tested before and after calibration to notice the difference, in an non-UWP app). This kinda bums me out, I hope the developers can fix it.

@unknown and @unknown does this calibartion issue you've detailed apply to any controller used on Windows 10, or just the Nintendo Switch pro controller mentioned in this ticket's summary?

@ [[Helper] GoldenHelmet |https://bugs.mojang.com/secure/ViewProfile.jspa?name=GoldenHelmet]this only applies to calibration with the pro controller as far as I know.

Can confirm this for Minecraft 1.16.220, unfortunately. I could only recreate the issue with not being able to sprint. For the first issue about the half inputs, I recommend you set your in-game sensitivity to 100.

Thank you for your report!
However, this issue has been temporarily closed as Awaiting Response

Is this still an issue in the latest version? If so, please add a comment or update the affected version field.

To make your bug report as effective as possible, please try and include the following steps to reproduce the problem:

Steps to Reproduce:
1.
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

If your ticket does not look like the example given here, then it's likely to be closed as incomplete.

This ticket will automatically reopen when you reply.

Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki

This is still an issue

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:

1. Connect a Nintendo Switch Pro controller to Windows as a Bluetooth device, and calibrate if necessary

2. Launch Minecraft and verify/adjust the "Controls: Controller" settings in the menu

3. 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.

the switch controller on windows in general has a much more limited range compared to an xbox or even playstation controller. if you test them against each other in windows' built in game controller tester, you can see that. all switch controllers have this issue, even third party ones, as the analog sticks on switch have a larger range than what is actually used from the looks of it. i'm pretty sure if you took the case off of a switch controller and then moved the stick around, you would hit the edge of the axis. the only solution i can think of is adding a toggle for a "less range" analog stick, making it so that instead of 95% makes you go full speed, it would be 50% or something.