@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.

The ghost controller is most likely your keyboard. I have the exact same experience here. You could try removing the USB dongle for the keyboard, reboot and see if the PS3 pads are detected as 1 and 2.

It was an issue for me because the PSX emu would not let me play, since the player1 controller was 'occupied', but i got around this by changing some config file, so controller 2 for player 1 and controller 3 is for player 2. Unfortunately i can't remember which config file it was. I am sure that someone would have this on the tip of their tongue.

That is brilliant thank you

@martincrocenzi said in Segmentation Fault Screen:

@zoop did you reboot the raspberry? when exactly do you get that screen? Can you detail the text or message you receive? Any capture or pic? Which Raspberry do you have? Which sd card? Any other specs? Whta do you mean with too aggressive?

Thanks!

I used a kit I ordered from Amazon for my PI setup. The details may be found here, including the details on the SD card: https://www.amazon.com/gp/product/B01LWURJMI/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Pi Model or other hardware: PI 3 Model B
Power Supply used: 5V/2.5A Power supply charger for Raspberry 3B
RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest): 4.1
Built From: Pre made SD Image on RetroPie website

The overclock settings I am using without issues are (credit YouTube vid where I found them):

https://www.google.com/url?sa=t&source=web&rct=j&url=%23&ved=0ahUKEwjkiPON2a3SAhWD1CYKHQKjD00QwqsBCDUwAg&usg=AFQjCNF1sHlk2z9QIx28jtvfnGP_UlkifA&sig2=JVDtgTiyUALlhDTby_3i1A

Stable settings for me:

gpu_mem=400
arm_freq=1400
over_voltage=6
sdram_freq=500
core_freq=500
gpu_freq=400

When I bumped the arm_freq up to 1450 I received the aforementioned error. Resolving the issue on my end was as simple as modifying my config.txt to scale back the arm_freq to 1400 again and powering the system off then back on again. To my great relief everything just worked once the setting had been changed back to a stable configuration.

I do not 100% remember how the screen looked with the error. It may have just been a single line reading segmentation fault. All I remember for sure is there was a 'segmentation fault error' on the screen and I figured it had to be my OC settings. I just had to hope I had not corrupted my image or something..

Apologies for the delayed response, I hope you find what you're looking for and are able to resolve the issue. Best luck!

I have converted FF7 to PBP but it just keeps sending me back to the game list every time

Using a RPi3 B
Offical RPi Power Supply 2.5Amp
RetroPie 4.1
Built from RetroPie premade image on retropie.org.uk
PS3 Six Axis controller over bluetooth
Emulator lr-pcsx-rearmed

@zkdr said in Hotkey for RetroArch Quick Menu (in game menu):

I've yet to be able to figure out how to swap A + B only for the retroarch menu.

Do you mean swap OK and Cancel buttons?

This config is "hidden" in Settings >> Input >> Menu Swap OK & Cancel Buttons.

Got it sorted ,I plugged the raspberry pi3 into my HD TV and the screen was able the handle the default 1920x1080 resolution.Then went into Kodi settings and set the resolution to the nearest to 1280x1024 which was 1280x720.
Another leason learned on the Pi.

Thanks guys for all your help and support.

@edmaul69 I changed the file permissions and it still didnt work. I read somewhere that the configs folder @ /RetroPie/configs/n64 is just a shortcut to /opt/RetroPie/configs/n64 so I changed that one too but no luck. The system changes it back to what it decides is best and none of my changes stick

So, I purchased a mini HDMI to a standard HDMI cable, and replaced the cable and adapter I had (the amazon basics mini HDMI to female full size HDMI adapter). Everything works perfect now. Thanks everyone!!