It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I tried quite unsuccessfully to bind my SNES30 controller input to Shovel Knight. I connected via bluetooth, confirmed connection via Windows. Pairing showed successful (both on PC and steady blue light of SNES30 pad). In game, the D-pad navigated the menu but nothing more. No other buttons would work, nor would Mr. Knight move in game. In the controller settings, the controller config was grayed out.

Connected via USB, it was slightly more successful. The controller config wasn't grayed out, but controls would not bind.

I didn't have much success with joytokey, but I don't like using that anyway. It always seems a little laggy, so I'd rather use my 360 controller. But ideally, the SNES30's dpad would be much more suited to this game!

Any help would be appreciated, thank you.

Win 10 64 bit, i7, R9 290, 16 GB DDR3, SSD, Inamax B520 Bluetooth 4.0 USB Dongle Adapter (don't think any of that matters)
No posts in this topic were marked as the solution yet. If you can help, add your reply
I figured it out! Well, it's a highly functional workaround at least.

With the SNES30 controller off, hold B+Start to turn it on. This will initialize it as a bluetooth keyboard. Go to the options, bind controls, and select bind all. It will take you through the control bindings. It works great!!

Not exactly official support, but, I think it's a satisfactory solution. I was getting frustrated with the XBOX analog stick and its awful D-pad!
avatar
jazzfluteman: I figured it out! Well, it's a highly functional workaround at least.

With the SNES30 controller off, hold B+Start to turn it on. This will initialize it as a bluetooth keyboard. Go to the options, bind controls, and select bind all. It will take you through the control bindings. It works great!!

Not exactly official support, but, I think it's a satisfactory solution. I was getting frustrated with the XBOX analog stick and its awful D-pad!
It also depends on the firmware for your controller. I've got the NES30 Pro and the workaround for Xpad to work was a specific firmware update.
If all else fails, use Antimicro and map the keyboard input to your controller.

It's amusing how Microsoft are still expecting their worthless xinput standard to catch on any day now.