Yeah, that is the page where I read about the workarounds :) I was a bit unsure if there were other differences to think about, but it sounds like it is safe to go for a multiplayer adapter. Thanks for the info.

So as a test, I changed the runcommand.sh script to # comment out the if/then statement and make it only load the jsX device. It now read as:

function start_joy2key() { [[ "$DISABLE_JOYSTICK" -eq 1 ]] && return # get the first joystick device (if not already set) # if [[ -c "$__joy2key_dev" ]]; then # JOY2KEY_DEV="$__joy2key_dev" # else JOY2KEY_DEV="/dev/input/jsX" # fi # if joy2key.py is installed run it with cursor keys for axis, and enter + tab for buttons 0 and 1 if [[ -f "$ROOTDIR/supplementary/runcommand/joy2key.py" && -n "$JOY2KEY_DEV" ]] && ! pgrep -f joy2key.py >/dev/null; then # call joy2key.py: arguments are curses capability names or hex values starting with '0x' # see: http://pubs.opengroup.org/onlinepubs/7908799/xcurses/terminfo.html "$ROOTDIR/supplementary/runcommand/joy2key.py" "$JOY2KEY_DEV" kcub1 kcuf1 kcuu1 kcud1 0x0a 0x09 & JOY2KEY_PID=$! fi }

This test didn't work. I still have the same results of not being able to trigger RunCommand.

It's variable, and I'm still working through them one by one, but yes.

I don't really want to overclock, but Mario 64, Diddy Kong Racing, Mario Kart & Starfox work pretty well. I still have the original console, so although they're not perfect, those ones are pretty decent.

Goldeneye & Perfect Dark seem to need more power to run well. Conker's Bad Fur Day is unplayable. Working on F-Zero X & Wave Race, as I've read they should work without an overclock, but aren't brilliant on mine.

Why do you ask?

Rob

@Danorak1981 said in Converting Genesis and Super Famicom Controllers to USB:

Is there any reason that I wouldn't be able to solder a female USB to the Raphnet board in order to fit it flush inside the SNES pad?

You should absolutely be able to do that.

No, I just meant I haven't tried to tackle setting it up yet. I will definitely open a new thread if I have issues. :) Thanks again!

The rebuild of the kernel did the trick! My thanks go out to @obsidianspider for the original post on how to fix it! Marking as solved!

@Dopy25 said in How To Apply Raphnet Kernel Patch To Fix "Northwest" Drift:

I know the last comment on this was over a year ago, but I am having issues applying these patches. Has there been any update to this process?

I am having the exact same issue as @Dhrystone from above. Second patch fails at 1 out of 1 hunk, 3rd patch at 2 out of 4 hunks. I tried repeating the whole process, and even proceeding anyway, but the patch still does not apply, and without the second (and third?) the only difference is that now emulation station is constantly scrolling.

I know this is a serious Necro, but I'd rather not lose all the progress on the thread.

I'm seeing the same issue here as @Dhrystone and @Dopy25.

Is anyone with a bit more kernel compilation experience able to offer some advice here?

@edmaul69
True that, I'm glad he's really cheap with his stuff :)

I'm having exactly the same issue with a Raspberry Pi Zero and a raphnet 4nes4snes adapter (using 2 NES controllers). The controllers show up when plugged in, regardless of how they are plugged in, but only work when plugged into a hub that is plugged into the RP0. On occasion the direct-plugged controller works but I cannot repeat this.

I think there is some issue with how the raphnet adapter generates the USB signals.

add "usbhid.quirks=0x289b:0x0002:0x040" (without quotes) to the end of the line in /boot/cmdline.txt. it will split the controller into two. Check out anything about the Xin-mo arcade controller to get more info, a lot of the same stuff applies