Ah... Thanks DD_Indeed.

I'll give it a shot tomorrow and see how it goes.

@richiep I have the deadzone issue as well. I'm using the Ram controls USB adapter, and I think the deadzone is programmed in the controller. When I run a jstest on it, I can see the deadzone in the numbers, so I haven't gotten into the mame settings. I use advmame, so I'm not sure about the parameters in Mame4all, but there must be some.

Can you try advmame?

What is the USB adapter you're using? I was going to try to configure a Teensy.

ws

@ortsac
Damn, I don't want to strip the wires to my SNES controllers or take apart my console to make a panel.

I'll be using an HD CRT TV. It'd be if a more straightforward adapter was invented. But oh well.

Thanks for the help.

@Caligula88 first thing to note:
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Now, 2 questions:

Did you configure your joysticks on emulationstation? Paste here the output of this command: ls /opt/retropie/configs/all/retroarch-joypads/

Update: Fixed the input lag issue I was experiencing.

Issue: Having two PS4 USB wireless adaptors plugged into the retropie at the same time was causing interference in the Bluetooth signals causing variable input lag when playing multiplayer games like street fighter iii: third strike.

Fix: I got a USB extension cable, plugged one end into the retropie and connected one of the dongles into the other end. This allowed me to create a bit of separation between the two USB adapters which was enough to remove the interference they were running on each other.

Hope that helps anyone else running into this issue while using multiple PS4 controllers connected to multiple USB dongles on the retropie. Btw, the dongles have worked out really well in my experience, much better (in terms of input responsiveness) than connecting the PS4 controllers directly to the Bluetooth from retropie.

@peg Many thanks for all this work too. Just to let you know I had to tweak this guide slightly as when running 'make modules_prepare' I got errors on Retropie 4.8 running on a pi zero 2W. It seems that I had to install 'libssl-dev' first before this command. Can confirm that after this all other steps worked, rebooted and rumble working on both pads as expected on the Trixes adaptor.

For those getting the same errors, here's a full update to @peg guide (I take no credit and thank @peg for this easy tutorial and just helping anyone with the same issue)

# Install required tools (bc is required for modules_prepare, see Compile) sudo apt-get update sudo apt-get install build-essential bc # Setup required variables FIRMWARE_HASH=$(zgrep "* firmware as of" /usr/share/doc/raspberrypi-bootloader/changelog.Debian.gz | head -1 | awk '{ print $5 }') KERNEL_HASH=$(wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/git_hash -O -) KERNEL_VERSION=$(uname -a | awk '{ print $3 }') HID_DRIVERS_DIR=/lib/modules/${KERNEL_VERSION}/kernel/drivers/hid BUILD_DIR=~/psff_build # Setup build dir mkdir $BUILD_DIR cd $BUILD_DIR # Get kernel source wget https://github.com/raspberrypi/linux/archive/${KERNEL_HASH}.tar.gz -O ${KERNEL_HASH}.tar.gz tar xfz ${KERNEL_HASH}.tar.gz cd linux-${KERNEL_HASH} # Get Module.symvers and Module7.symvers (not sure Module.symvers is really needed) wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/Module.symvers wget https://raw.github.com/raspberrypi/firmware/${FIRMWARE_HASH}/extra/Module7.symvers # Get current kernel config sudo modprobe configs gunzip -c /proc/config.gz > .config # Enable force feedback / rumble support sed -i 's/# CONFIG_PANTHERLORD_FF is not set/CONFIG_PANTHERLORD_FF=y/' .config sed -i 's/# CONFIG_GREENASIA_FF is not set/CONFIG_GREENASIA_FF=y/' .config # install libssl-dev otherwise following driver compile will fail on 4.8 / pi zero 2w sudo apt-get install libssl-dev # Compile driver make modules_prepare make drivers/hid/hid-pl.ko # Update existing hid-pl.ko with FF support (w/ backup of old version) sudo cp -b drivers/hid/hid-pl.ko ${HID_DRIVERS_DIR} # Enable ff-memless module (not sure why "sudo echo ..." isn't enough) sudo su echo ff-memless >> /etc/modules exit # Reboot sudo reboot

@Graboid

Thanks anyways :) I have opened a new post.

@sfc_k i can comfirm that all of raphnets adapters work. I have used all of his usb boards and adapters and his wii adapters too.

@hansolo77 said in Problem with Genesis/MegaDrive USB adapters (RetroUSB and Mayflash brand):

Would you be against buying a 3rd party controller?

I'm a stickler for the originals I must say. I've had bad luck with pretty much every single after market controller I've ever tried going back even to the 80's. Even had bad luck with 2x 8BitDo's everybody seems to love. Only lately, ~20 years later, am I having problems with the real console controller brands for the first time (and even that's not their fault as they're now antiques, and I'm using them on a computer and not a console).

@edmaul69 said in Problem with Genesis/MegaDrive USB adapters (RetroUSB and Mayflash brand):

the biggest issue is the cables are crap.

I'll deal with re-wiring them if I have to, in like another 20-30 years when the controllers are going for $100+ each because they're so rare ;)

Right now I have working properly: 4x+ NES controllers, 2x SNES, 3x Genesis, 2x PS1, 2x PS2, and a bunch of Xbox 360 wireless controllers....so even though it took me a ton of trial and error I have at least a set for each proper console I emulate so I'm just leaving it at that. It was just a shame that it took so much trial and error to get to this point. I want to have a 2-player set of controllers for each console, and a backup or two so I'll probably pickup another SNES and Genesis controller, but that's about it.