@Plantor07 been literally dealing with this for days with 8bitdo and Stadia. Tried this and it worked for me.

https://github.com/atar-axis/xpadneo#installation

@jdoc said in How to get 8-Way / 4-Way joystick controls in Defender and Stargate:

Just had to nuke and pave my system, but discovered that mame2003 changed a bit. This cheat still works, but “mame2003-cheats” has changed to “mame2003-cheat_input_ports”.

So changing mame2003-cheat_input_ports = “disabled” to mame2003-cheat_input_ports = “enabled” will make this work again.

Thanks for this. This may be the reason that the MS Pacman speed button stopped working a few years ago, too. I'm gonna give this a try and see if it helps there.

EDIT: Confirmed. This fixed the issue. I posted on this forum about it ages ago and nobody had any idea what was wrong. Thanks!

And yes, in hope rather than expectation I did try changing:

config_version=3.6.0

to

config_version=5.7.1

It did not, of course, help, except that instead of dumping to a Workbench 1.3 "insert disk" screen, the game now dumped to a Workbench 1.3 "insert disk" screen in the wrong aspect ratio.

@barbudreadmon
Sorry, when I said I got both monitors working, I meant that Retropie was displaying on both. The left monitor has the game, the right monitor was displaying scripts. I just can’t get the actual game screen to display over 2 monitors. No game play on the monitor on the right even though Retropie seems to be recognizing it.

Thanks!

@mitu thank you man!
you are great! ( as always....))

Well, the OP should just move to MAME current tbh, not only it has support for TATE in both directions, but it probably also has better support for cocktail mode (i highly doubt all cocktail fixes from the past 22 years were backported to MAME2003+).

As for FBNeo, it is not suitable at all for cocktail setups : some games had their 2P mode and cocktail mode tied together, and ended up being un-cocktail-ified so that 2 players could play them without requiring a cocktail setup.

Just came across this script, very nifty, but can't log in. The login window on my browser just keeps popping up after I enter my credentials. I've verified that the service is running through Terminal. Any suggestion? Python, RetroPi, etc are all up to date. Running on Rpi4. I updated/changed the login credentials, but should still work.

@hoeveler Hi, yes, you are right. It has greater access to the GPIOs and supports additional controller types besides arcade. Also, it does not have a DAC/amp.

BTW: Is the DAC/amp an important feature in your case?

@mitu

I’ve tinkered with clrmamepro before but my results kind of sucked with it. The last time I had to do any of this was with the good tools way back in the original Xbox one days.

Any direction for a good tutorial on how to use Clrmamepro the proper way as I obviously had no idea what I was doing even tho I followed a guide lol.

Any other noob friendly sorting by .dat tool recommendations would also be appreciated, like I said it’s been a long long time since I’ve had to do this or anything like it and things appear to have come leaps and bounds since then

neither of these things (permissions or starting clean) seemed to resolve. I also @ByteThis did not seem to rectify this by only configuring player 1 (but good idea) With a clean install and remapping all the input settings I am getting to where the select and start button only work in the retropie menu (scrolling diffrent consoles exploring settings etc.... But when I launch a rom NONE of the bottons work.

I ran some more jstest output today....

davis@raspberrypi:~ $ jstest --normal /dev/input**/js0**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

davis@raspberrypi:~ $ jstest --normal /dev/input**/js1**
Driver version is 2.1.0.
Joystick (DragonRise Inc. Generic USB Joystick ) has 7 axes (X, Y, Z, Rx, Rz, Hat0X, Hat0Y)
and 12 buttons (Trigger, ThumbBtn, ThumbBtn2, TopBtn, TopBtn2, PinkieBtn, BaseBtn, BaseBtn2, BaseBtn3, BaseBtn4, BaseBtn5, BaseBtn6).
Testing ... (interrupt to exit)
Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:ofAxes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 6: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off

So it sees both controllers, but does not detect any button or axis input events. I think It is time to just replace them. Ive had them over a year and the more I think about it the more I think I possibly damaged these things. They used to be mounted in a metal cabinet and the opening I cutout for the control panel was very tight. (see attached called "old") old.jpg

New cabinet.......

new.jpg

I think its time to just replace the usb encoders.

Thank you!!!

3.17.4 is out to fix all the reported problems. 🙂

@gilllig said in Retropie doesnt boot with changed config:

Ive installed raspOS and retropie, but now they dont even run))

What exactly does this mean - they're both not running ?

I tried to choose emulationstation at the settings, I tried to add line "/usr/bin/emulationstation" in the /home/pi/.bashrc, but its not working...
I cant understand how to make autostart for raspOS or for retropie

You're running in an unsupported configuration, as I mentioned in my previous post, so you should not use the normal RetroPie auto-start options from the menu.

If you have installed the RaspiOS with Desktop, then just use the default option to boot to the Desktop. You can start EmulationStation from a terminal by typing emulationstaton. If you wish to automatically start Emulationstation after the boot to desktop is done, then

create the $HOME/.config/autostart folder add a .desktop file with the command to start the terminal and EmulationStation (lxterminal -e emulationstation).

@mitu said in FYI: Retroachievements will improve more:

I expected 0.0 to make the game viewable area to be hugging the top size. I'm expecting the X/Y positions for the Custom AR to be anchored top left, so 0 vertical bias should fuse the image to the screen top.

That's exactly the issue I reported. Switch to Vulkan and it will appear as you'd expect. The Y position is only wrong when using gl or glcore.

Play with Bias Y and watch the viewable area in the background. You should see that one single frame where it appears where you'd expect before it pops into the incorrect position.

ADDING: I searched online for others having the problem. They are. Most are using GL and are advising others to set Bias Y to 1. This "looks" correct, but is a terrible workaround for a fairly obvious bug, especially for those who mix render modes.

@Mrobot said in ControlBlock issue on Raspberry Pi 4B:

I can access the bash interface on it, but that is about it.

if you have shell access, can't you just run the setup script again and choose to remove the package ? Run

cd $HOME/RetroPie-Setup sudo ./retropie_setup.sh

to get to the setup dialog and remove the package.

Hi! Does anyone know if it's possible to set the the to look as the "multi artwork" version? Or if there is any alternate version? Thanks!

@Folly said in Streets of Rage Remake 5.2 on Retropie 4.8.8 Issue:

Which file is it ?

It's in the main RetroPie repository now, hence has been removed from the extras.