@mitu sorry I made another edit. I want to pass that as the %ROM% parameter so we can make another menu entry for the level editor.

@MrPacMan17 As I wrote above, thank you so much for taking the time to read and respond. I figured it out!

@mitu said in Problem with Batoh PS3 controller:

@pscotto1234 said in Problem with Batoh PS3 controller:

The customhisony driver is already installed or I have to install it?

You can also install it manually from the drivers section in RetroPie-Setup.

Ok, so I need customhisony and sixaxis (with third party support enabled) both active and installed, right?

@dankcushions You summed it all up in that last sentence perfectly!

@sigma47 Just modify the title and add [solved] to it.

@SteavinRice use the samba share method. So much easier :)

The Audio settings in the RetroPie system (or audiosettings in RetroPie-Setup's configuration/tools) is doing the same thing as the raspi-config options.

@Simrose At the time of the writing of the guide the 5.10.x was hit and miss. Maybe it is more on the "hit" side in the meantime. I guess 5.15.x is the new "hit and miss". In any case: Good luck.

Success! Ok i figured it out. This is going to be a long one so sit back, but anyone with a similar problem, i hope this will work for you. Again I am running RetroPie on a raspberry Pi 3 with a Pi2Jamma adaptor and i ran the retropiergb mod to output to a 15khz monitor. so i figured that this was an issue with the run command, so i found a file in the /opt.retropie/configs/all, named runcommand-onend.sh . In it there is a line for HDMI timings that was different then the one in the global config.txt in the boot folder. so i added the correct timings and # out the originals and it worked! but then for some reason mame was outputting a very stretched image at 1920x240, so i went into the configuration options in the run command menu and changed the settings in the edit custom retroarch config option. In it you will see that the custom viewport is set to 1920x240, so i just added a pond symbol before the commands. Since the layout seems to be UK it is a £ instead of # for us Americans but it works just the same. and now mame defaults to the listed game resolution. I have no Idea why these options did this but I wasn't going to let this beat me. I hope this helps.

fix_0.jpg fix_2.jpg
fix_3.jpg
fix_1.jpg
fix_5.jpg
fix_6.jpg
fix_7.jpg
fix_4.jpg

I got it to work placing cue and bin files into the sega32x roms folder and using lr-picodrive. After launching game, hit selct-x to bring up Retroarch menu. Scroll down to "Options" and set Input device 1 to 3 button pad. and Input device 2 to "None".

@WeirdGamerAidan Like @sleve_mcdichael stated you need an OS.

My advice is here however, not to install Ubuntu since its footprint on the hardware is rather big compared to other Linux distro's.

My personal favorite is Xubuntu x64. Works perfectly with RetroPie but has a smaller footprint, thus leaving more for RetroPie to use, thus giving a better performance for emulation. N64 games run better on the same hardware with Xubuntu, compared to Ubuntu.

Nice thing about Xubuntu is that it's very flexible and performs great on older hardware, whereas Ubuntu requires more power. The biggest difference between Ubuntu and Xubuntu is the desktop interface, but that one can really consume your hardware.

I reinstalled RetroPie all over again and the joystick setup works fine now. Couldn't figure out what was causing this issue.

Answering myself, because I'm an idiot. Sorry.

In the emulator's settings (on the GUI) I had to (re-)assign a correct mapping for pause.
It had kbd.esc and two other weird keys from the controller assigned to pause.
I assigned the button behind/below the right shoulder key to pause, no idea what those are called.
Which in my case resulted to the following in controls.ini:

[ControlMapping] ... snip ... Pause = 1-111,10-197 Rewind = 1-67

So, 10-197 is the key that was missing.

@mitu thanks

@Folly Thank you friend.

@mitu
It worked! thanks a lot.
I'm using "Version: 1.4.1" for retroarch.
I just wrote a script in python to send UDP packets with this command
"READ_CORE_RAM <address> <len>"
Then I received related bytes.

@Folly I'll give that a shot.