I've been trying to get my Switch Pro Controller to work with a few games using WiinUPro (64 bit). The problem lies in the analog sticks. For instance, every time I start up 'Minecraft: Windows 10 Edition' (which does have controller support) and load a world, my character moves very slowly and my camera also pans slowly (I'm assuming that Minecraft still detects the standard DInput). Similar problems occurred in 'Spec Ops: The Line' in the past.
I've tried going into WiinUPro's calibration and adjusting the limits to match the red dot, which didn't seem to work. I've installed the SCP drivers, mapped button layouts to 360 controller, and also told WiinUPro to add an XInput device all seeming to do nothing. I am connected through Windows 10 Bluetooth using a USB Bluetooth dongle and using the latest WiinUPro (0.9). I also have Steam closed completely so as to not interfere with WiinUPro's controller input.
I've combed through the internet and this forum to see if anyone else has a similar problem so I can resolve the issue myself, but to no avail. Any help would be appreciated.
Hey there, have you tried playing Minecraft without WiinUPro? I'm wondering if the game is picking up the normal DInput signals that Windows gets from the controller and if that's what it is using instead of the emulated XInput ones.
I have tried playing Minecraft without WiinUPro. It operates the same way as if I were running it with WiinUPro. It should be noted that pretty much every button works just fine save for the movement and another button that I mapped in-game.
To test out WiinUPro and the Switch Pro Controller on another game, I started up Far Cry 3: Blood Dragon and Crysis 3 and the controls worked just fine. I think Minecraft doesn't want to recognize the XInput.
Okay, since it is behaving the same way without using WiinUPro, then I would suggest to not use WiinUPro and then try calibrating the gamepad inside Window's configurer for Direct Input devices. Which is accessible by searching in the start menu for "joy" and clicking on "joy.cpl" or "Setup USB game controllers" then selecting Properties and performing the calibration steps.
I'm thinking that should solve the slow camera, which I'm thinking is being caused by Windows not detecting pressing in a full direction as a full direction.
Post by copperhead212 on Jul 11, 2018 18:01:08 GMT
Unfortunately, joy.cpl didn't solve the issue. The whole calibration setup was rather strange.
When the first step asking me to move my left analog stick to each corner popped up, the crosshair was jumping around the box. Regardless, I still tried to move my analog stick and most of the time the crosshair wouldn't even touch the corner completely. Next, it asked me to move my X and Y axes. When I moved it to the lowest percentage, it would be around 17-19% on both X and Y axes and never reached 0%. When I moved the percentage to the highest point, it registered at 117-119% on both axes. I also didn't even have to move my right analog stick all the way to reach the max percentage.
I also tried calibrating my pro controller using the Switch's calibration utility. That didn't seem to affect anything either. At this point, I wonder if it's my specific pro controller that is messed up, if Windows doesn't feel like doing its thing, or both.
Note: I've tested to see if Minecraft works with my DualShock 4 controller using 'DS4 Windows' and it works just fine.