Leaderboard

Well, I couldn't get it to work (Firmware v1.20). I first tried putting the SF30pro in windows mode (x-input), which is usually the first requirement to get rumble support in emulators. It paired fine, I setup a Udev rule so it would automatically reconnect, but it wouldn't register the L2/R2 or Star/Home buttons. The rest worked so I tried firing up FF8 and seeing if I could at least get rumble to work. No luck - I rummaged through Retroarch settings and made sure all settings related to analog and rumble were enabled. Still Nothing. Maybe it's the emulator I'm using? IDK. So I put the SF30pro in Android mode (D-input) and that fixed the button issue. All the buttons register, but still no rumble. I'm not sure what else to try. There is nothing wrong with the controller otherwise. Pros: Everything except Rumble work on Raspberry pi and NES/SNES classic. I'm sure with time someone will bring full support to the Pi. It's such a cool controller! Turbo/Autofire feature is nice! It's easy to enable and disable, so that is really cool. Bigger and well made thumb sticks. They feel great, super locked in on your thumb. The NES30pro had smaller ones that were stiffer and less stable. They took some getting used to, these are immediately familiar. They feel the same, but slightly better than, the PS4's thimbsticks, since they have a little extra texture around the raised rim of the circular depression. If your thumb slips out, that texture catches your thumb and allows you to easily regain control. Nice improvement over the NES30 pro. LEDs are subdued. You can see them, but they don't blind you. The patterns they display are easy to understand and provide useful information about what mode the controller is in, the current player assignment, and syncing. The Retro Recievers for NES/SNES/SFC Classic Edition, NES, and SNES each work with this controller after you update the firmware on them. The Indifferent: The frequency of the auto-fire feature is so fast that it skips while firing. I think the auto-fire is optimized for the Switch and that doesn't necessarily work best for the Pi. It works, but I found it barely effective for Megaman X. It probably can't work perfect for every game, so I don't hold it against the controller. It's probably just the game I tried. Okay, It wouldn't be fair if I didn't say it. It is not an ergonomic controller. This is a pro because it looks and feels nostalgic. This is a con because it's not comfortable to play with for long periods of time. However, you don't buy this controller for comfort. You buy the Wii U controller for comfort. You buy this because it looks cool and gives you blisters while you babality your little brother on mortal Kombat! Remember, pain is weakness leaving the body! By the way, If you really want ergonomics and authentic retro gaming, the 8BitDo Retro Recievers also pair to the Wii U pro, PS4, and all 8BitDo controllers. So play your original NES, SNES, and classic edition with a modern controller. I imagine this would be useful for speed running. Cons: The rumble not working off the bat on Raspberry Pi. This is not a deal breaker. The controller rattles a bit when you shake it. That's just the nature of the thing, but it may feel a bit cheap because if it. It doesn't feel to light or otherwise flimsy. It just has a little clearance around the buttons. That is a very picky con however. EDIT: How the Different modes behave in Retropi Switch Mode - Controller pairs easily and repeatedly. It's recognized a "Pro Controller" and all buttons map when configured. NES and SNES emulators accept the input fine. However, PS1 doesn't. While I can access the Retroarch menu and control it, I can't actually play in game. For some reason the controls are not recognized by the emulator itself. Also, the Turbo feature is disabled in Switch mode. Dinput - This works fine. Recognized as "SF30 pro". I have had some issues with the controller not wanting to repair after the Pi has been off. I'm not sure what's going on. I did set up a Udev rule, as required for 8BitDo controllers. I do have the 8bitdo hack off, since this uses the new firmware. I'll have to test some more to see if it was just a one off thing, or a recurring problem. I will say, I've had similar trouble with the NES30 pro. Regardless, Dinput is the way this controller needs to be paired to the Pi. Xinput - Pairs fine and is recognized as "SF30 pro". The L2/R2 and Star/home buttons aren't recognized at all. macOS - Pairs fine and is recognized as "Wireless controller". Is not recognized during the configure input stage.

I'm playing on a 2P cabinet as well. Since we're not using the 2-player ROM, I've come up with a pretty convenient workaround to use for this competition: - go to configure inputs (this game) and map all (4) of the turtles' up/down/left/right/jump/attack inputs to the same joystick and 2 buttons on the control panel - go to configure inputs (this game) and map (4) otherwise unused buttons on your panel to the (4) coin-in buttons for the various characters When you set it up like this, you "select" your character based on which coin-up button you use. Regardless of which one you select, the controls will work the same because they're all mapped to the same controls. I actually set up my player-2 joystick to handle the credit buttons. Up = Leo, Right = Mike, Down = Don, Left = Raph Of course, this set up won't work if you want to play 2P simultaneous, but you can't do that for the competition anyway, and if you wanted to do it you could just load up the other ROM.