EasyRPG is in Zerojay's RetroPie-Extra repo. I had it working but something went wrong with my SD card and I started a new SD card and it does not want to work now.

https://github.com/zerojay/RetroPie-Extra

When it worked, I just copied the directory of the game files into the RetroPie/ports/easyrpgplayer/games folder.

I didn't have the RTP files when it was working, but the installation file says to copy the RTP into the RetroPie/ports/easyrpg/data folder. I would guess that it would have to be the files and directories as I don't think .exe files work on the Pi.

https://github.com/zerojay/RetroPie-Extra/blob/master/scriptmodules/ports/easyrpgplayer.sh

Trying to troubleshoot it. Seeing if I can install the dependencies and then reinstall it.

I have now noticed that when the ds4 is conenected via bluetooth the thermometer appears in the corner even when the system is idle..

great :(

@tribunal88 The turnaround on this is fantastic, and you are finding things that might have otherwise persisted for a long time.

I have not updated mine since 3.2, as the install was incomplete on my system for some reason. I ended up building my own references to the .rc file using the version number in emulators.cfg. I will have to reverse this and go with a generic configuration to accommodate the rapid updates.

Only available if you installed to x86 (ubuntu).

It's working now for some reason. I'm not really sure why it didn't work the first time I tried it.

I installed Xfce. Scaled fonts, icons and cursor. Looks a bit odd, but it works. Emulationstation, kodi and the desktop are all accesible from the couch :)

In my personal experience, ive had several cdi's work where gdi's dont and vice versa, also ive noticed that changing the emulator selection makes powerstone run. on the pi its hit and miss. if you have .bin files there should be a cue... but i thought reicast was strictly cdi or gdi.

@Spiky said in DOSBox - Won't return to RetroPie menu when game ends:

I was sure there must be way how to do it without losing one key to it.

I have all of my 38 emulated systems and various ports mapped to exit out with 'select+x' so that I don't lose an individual key that could otherwise be used for game play. It's also just easier to remember. There's a bit of setup involved, but when using a controller, the final result gives everything in RetroPie that cohesive console feeling.

i figured as much
as far as i understand he installed retropie 4.1 and attract 2.0 the only thing it has is some themes and art files added for attract mode and a few sections pre set up in attract mode ...no roms or bios files included ...i guess it was worth a shot of seeing if it mattered or not ...

i would still like to know with just a normal install of retropie 4.1 and attract mode 2.0 when you add the emulator in attract mode, which is working and playing roms in emulation station,
could it be that a .cfg file in attract mode just is not listing the start command properly ?

from what i understand attract is just an overlay and alternative that still references retroarch to run the emulators ?...or is this just a problem with supported emulators in attract mode thing?

thanks for the answer though as i may try just that with full clean installs

Looks like i forgot to note it above but i made sure the hack was off. Just to be sure i removed the Bluetooth connection, then re-added it, then reconfigured the input. No luck. The fight continues.

As much as I wish that I had an answer for this, I do not. However, I do have resolution. I started over from the bare image again, and rewrote my scripts from scratch to favor ALSA over PulseAudio - and did not install PulseAudio this time around. Considering the other issues that PulseAudio was giving me, in terms of system stability (or the lack of system stability), I can only imagine that my original issues were also related to that.

On the plus side, I've managed to knock together a decent script that gives me what I was after - volume up/down followed by an indicator tone, volume up/down to exit mute state, and a functional mute toggle through tracking the volume and mute states. More complex than what I was trying originally, which was using pactl to control it all, considering that I am on of the "lucky" ones who cannot get ALSA to unmute.

there were a few issues with the "migration" code for the renames - nothing should be too problematic, but you may need to redo any "per rom" settings (we still don't migrate those), and re-install any if they were incorrectly renamed. Hopefully this is all resolved now.

@Ghost-Note I ran into this audio issue too for Reicast emulator. I dug into this issue this weekend and changed the following Reicast configuration files to resolve my Alysa driver related issue. Hope this helps!~

Located in: /opt/retropie/configs/dreamcast There's 2 config files i.e. (emulators.cfg, emu.cfg) I recommend making backups those before proceeding.

In "emu.cfg" verify the following is set to [audio] disable = 0

In "emulators.cfg" Append the following statement to configuration file and save:

reicast-audio-alsa = "CON:/opt/retropie/emulators/reicast/bin/reicast.sh alsa %ROM%"

Now you need to choose "reicast-audio-alsa" as default option in Runcommand Launch Menu. https://github.com/retropie/retropie-setup/wiki/runcommand

Pretty sure I needed up fixing all my issues.

@edmaul69 seems logic :) so yeah I'll start by the standard installation of everything, then try to run every games I wish to play on, and then see if I need any other manipulation ! (I'll buy and install the raspberry pi in the fan equiped case in case of I need to try it out.)

thanks for your guidance edmaul69 !

@AlexMurphy I have pressed TAB, I am in the menu, I have selected Input This Game
It does not recognize my arcade joystick d-pad which has been configured through Emulation Station prior to all of this.