@Folly Heh. Yes. I'm guilty of being old. I was way better with all this just 7 years ago. Anyway thank you so much once more for your help!!! I'll be using this right away!

@mtm81 Thanks for the replies up to this point - I'm pleased to say that I've got it fixed (well kind of).

With my previous setup I've confirmed that the ALL of the default settings I was putting into the pi (alsamixer, retropi config, config.txt, autorun, even going so far in the config.txt to turn off the HDMI audio all together etc) to force it to use headphones - all were working but ONLY after a certain point in the boot sequence. Up to that point, because I had the HDMI plugged in (for video only) the system was detecting that HDMI connection and setting the ouput audio to be HDMI. Once one the files config files was THEN loaded, the Headphone output would then take over.
The issue was always that, my file which was being used to control the audio volume output of the device - was being loaded BEFORE those other files took over, meaning my file was effectively turning the volume up and down on an output I wasn't using.

I've therefore changed my output to HMDI for audio output as well, and changed my cabling from using the headphone jack on the PI, to the output jack on the HDMI controller.
This works absolutely fine and works first time.

So although this issue is solved, the underlying reason still remains - if you want to use the headphone output for audio - that only is 'forced' so far into the boot sequence.

@mitu thank you, excellent advice

After running the above I noticed that indeed those axis don't work. So I tried changing the position of the connector (this one towards the joystick knob didn't have wiring guidance) and tadaa, they work now. Also this fixed somehow the skipping part, now with a long press of a button I can properly skip it.

Now I'm just trying to figure what is the minimum amount of buttons that I need (directions, start, select, hotkey and ...?) , I don't want the arcade machine to have too much buttons lying around plus I don't have the space, I want to build a double control one this time. Just hope there won't be no more trouble ahead.

Anyway, to get back to the subject, for other folks, if the joystick misbehaves, don't forget to check the wiring also. In my case this inverse polarity allowed it to work partially.

Dragonise is a generic USB controller name used in a great deal of encoders, so there's no single mapping that will work with them. If you configure your controller in EmulationStation, then the mapping you chose there should be saved in dapinput.ini automatically.

Please add some more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first and post your dapinput.ini file.

@mitu Thanks. After I built RetroArch with your commit, works well now.
스크린샷 2023-05-23 21-53-39.png

@sleve_mcdichael @mitu

I see, thank you guys for the quick response! I'll try it just as explained.

@faided said in Baldur's Gate 1 & 2, Icewind 1 & 2, Planescape Port Walkthrough:

... Baldur (yes, both) ...

You'll get much farther ahead in life if you turn off "hide extensions for known file types" now, rather than later.

@antsgamingau If one game works, but other are not, chances are the game files are not correct.
Post the file names for the games that are not working, along with the other info,.

it's a problem from current retroarch version

No, since the problem doesn't show up on other platform.

it's a problem from the core when it's build for arm (probably this one)

Unlikely, since the core on RetroPie works with Netplay using the latest RetroArch version.

The issue in this post is related to missing .info files, which were not part of Retropie's RetroArch installation until 1 year ago. Users which upgraded their RetroArch package without updating the RetroPie-Setup script had this kind of errors, which are solved with an update of RetroPie-Setup and then re-installing RetroArch.

I don't think your issue is related to the current topic.

@mitu

Thanks a lot for the guidance, that does it.
The line for the added pseudo emulator is mame %BASENAME% -ror

I just have to do the setting for all of the vertical games.
Thanks again for the help provided in this forum.

Herve

@barbudreadmon
The fact that I have isolated just philmurr's cheat to fixes separated from other cheats

@sleve_mcdichael Yes.

For example ./retropie_packages.sh image all buster would build rpi1, rpi2/3 and rpi4 images based on buster.

@chicoputo cool to see this helped someone else, somthing additional that might be be helpful.

if you re-map the controls you need to reapply the fix.

not sure what but somthing happens that causes it to default back to error state

@mitu

flashed retropie image from official site, configured keyboard and wifi, installed reicast and put bios on dc/bios (home folder) and...worked!!

Update image doesn´t works a good choice.
Now i ll do it in my main SD card.

Thanks anyway!

Thanks mitu - I didn't know about the es_input.cfg file. That's what I was looking for. My inputs don't overlap between the two boards, so I thought I'd be able to edit that file manually and create something that allowed for more than one player to control ES UI, but I couldn't get it to work. Not a big deal - player one controls the ES UI. As far as I can tell, using four players across all the boards works in the retroarch.cfg files for each platform and that's what really matters. Thanks for your help.

Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

@RetroMalina said in Pi 3B+ Peak Performance.:

My question is, Can a Retropie 3B+ run N64 games stably

Not really. Some N64 titles don't run well (or at all), even on a Pi4.

@Craine N64 games do not always run very well even on an RPi4. It's really asking a lot for an RPi3. Try one of the stand-alone (non-libretro) Mupen64plus emulators -- gliden64 or gles2rice are the ones I use (on RPi4 though).

There's also a PSX version of the game, you could maybe try that if the N64 won't run well on any emulator. PSX tends to run better than N64 in general, even on RPi3.

Should be fixed now.
We don't support Dolphin on RPI (the system is not powerful enough to run it) and also RasPi OS bullseye support is still in beta.