@mitu

Thanks!
Unfortunately,

jstest /dev/input/js0

does not trigger the turbo button, so I think it is an internal controller button. All other buttons trigger.

@el_pablo said in How to exit my own Godot ports?:

@mitu ok, so if I understand correctly even SNES games had their START + SELECT to exit? Or it's implemented into the emulator?

It's the emulator.

Are you talking about the vice libretro core or the standalone emulator ? RetroArch input combos do not apply to the standalone emulator.

@Robinson You don't need a bios for 2600, see : https://retropie.org.uk/docs/Atari-2600/

Yep that was it! Was getting my Select and Start buttons confused.

Setting the Hotkey to the same key that I had assigned to Select (and not Start) fixed it.

Cheers

thx @mitu , I think that explains it.

Retropie-Setup must have updated my retroarch.cfg when I update-all-packages, but I likely copied an "old reliable" one over from somewhere else and erased the new changes.

However I'd imagine that's still an unintended consequence when menu_disable_search_buttonis set to false?

You can try reconfiguring your controller in EmulationStation; this should rewrite the RetroArch autoconfig including the hotkey-enable function. If that doesn't work, however...

@retroprestoz said in Start button exits games without pressing select as well.:

A buddy of mine just put it together for me to use some I'm not exactly sure what he did or all of the config files and stuff.

Unfortunately, neither are we.

It is not practical to troubleshoot a system that neither you nor we have any idea how is configured. For that reason, third-party builds are not supported in any capacity.

Start here: https://retropie.org.uk/docs/First-Installation/#installation

I suggest you to backup your roms and configs, and then install the current latest official image for your hardware from https://retropie.org.uk/download.

Restore your backed-up roms but not the configs yet -- you can cherry-pick them later but if you blindly copy them all, the one that's causing your issue will come along with the rest of them.

@mitu Actually it still wasn’t working properly turns out that was only part of the problem. Apparently my retroarch hotkey configs weren’t saving when I quit retroarch so Start+Select wasn’t even set to be the exit emulator buttons. However after enabling “Save configuration on quit”. My settings saved and now it is working fine and dandy!

@MyFartSoTart

"Also in the /opt/retropie/configs/all, there is already a file named retroarch.cfg." -> obviously. Windg told you that file is corrupted. He explained you should replace it with a non-corrupted copy.

"mu: target" -> the command is "mv" (with a v, like in "velocity", not with a "u" like "unknown").

"‘retroarch.cfg.rp-dist' is not a directory" -> that's because you forgot to type the space between the two names.

Here is in 3 steps something that could help you to make less typing errors (press return after each end of line):

cd /opt/retropie/configs/all rm retroarch.cfg cp retroarch.cfg.rp-dist retroarch.cfg

The commands are :
cd, like Change Directory
rm; like ReMove
cp, like CoPy

Mind the fact there is, in the last line, a space between "retroarch.cfg.rp-dist" and "retroarch.cfg". Don't type "retroarch.cfg.rp-distretroarch.cfg" as if it was only one long word.

(as sleve_mcdichael said, it's not required to remove the file in step 2, because the cp command in step 3 will delete the original-corrupted file anyway. But I think it could help you to best understand what you are doing).

@daubsi said in Retroarch Menu is not shown anymore:

@windg Ok, understood! So you’re saying that retroarch itself sometimes corrupts the config when using its own function to save?

It is not corrupted, but changed from the default settings that selected for the proper RetroPie operation and it happens everytime you save the settings from RA menu.

@iLouzze I don't know if there's any way to turn it on automatically without an external timer. You could probably set up a "cron job" to shut it down (I don't know how to do that, though, I have only heard of it as a way you can set up scheduled events.)

@sleve_mcdichael

Hey. Figured it out. The answer was more or less staring me in the face.
In the "es_temporaryinput.cfg" there was a line for the hotkey, which I more or less copied.

<input name="hotkeyenable" type="button" id="8" value="1" /> <input name="x" type="button" id="0" value="1"/>

This is my solution. From what I've tested this hasn't messed up anything else even though it does share the
id="0" with one of the axis entries.

Thanks for the input. You can consider this topic "solved".

@ChaosEffect said in Tips for RetroArch 1.10.0:

@mitu I am not sure how often RetroPie's RetroArch will sync with upstream RetroArch. This is more of a typo correction than a new feature, but it makes the lightgun input operate as intended.

Thanks for the heads up. We don't update too often and we base the update on RetroArch's point releases, I guess it's one more reason to consider the next release for inclusion :).

Updated sample video links showing the proposed functionality as Anonfiles was shutdown.

Got four likes in the meantime. But the functionality in general does not seem to be widely anticipated?

@x_wav This means the button is not registering, so it can't be used.

What's the point of enabling it if there's no corresponding functionality in EmulationStation ?

This would be a pre-requisite to allow extra functions as currently 12 buttons are used to control ES and there are no "spare" buttons.

provided [hotkey] doesn't trump an existing input

Yes, hotkey can have three states: Absent, present or mapped to Select.

Case hotkey is mapped to Select button:
The Select is used for Start Screensaver, choose next item in screensaver media or bringing up the Options dialog in a gamelist to my knowledge. These events are consumed before the systemcarousel and gamelist logic and do not reach the later components in the GUI stack where hotkey would be processed (e.g. scroll a game's description with hotkey held and joy up/down pressed as one possible ES enhancement).

Case dedicated hotkey button:
Each GuiComponent would decide if it would act on hotkey input. In turn this also means a hotkey-button-combo can only be processed by one gui component when there are multiple gui components displayed.

@folly Sounds like great progress! Ingenious work with the PSP battery.

I bet PS2 is decent for emulation, they are powerful enough in retro terms. PSP seems more fun - I like the handheld retro aspect.

I've got an XBox One and a decent laptop as well, I like modern and retro. There is some messing around to get games to work sometimes on Windows - I had trouble with Jurrasic World Evolution this week, took me a day to get it working (it didn't like booting up in anything other than 60hz 1080p). I'm playing Halo Infinite now as well - it is so good for a free game (only the multiplayer is free though).

Thank you. Now it's working!!!

I add this rule to

/etc/udev/rules.d/99-input.rules

SUBSYSTEM=="input", ATTRS{name}=="button*", MODE="0660", ENV{ID_INPUT_KEY}="1", ENV{ID_INPUT_KEYBOARD}="1"

And now have GPIO key ID_INPUT_KEYBOARD parameter too.

pi@retropie:~ $ udevadm info --query all /dev/input/event1 P: /devices/platform/button@1a/input/input1/event1 N: input/event1 L: 0 S: input/by-path/platform-button@1a-event E: DEVPATH=/devices/platform/button@1a/input/input1/event1 E: DEVNAME=/dev/input/event1 E: MAJOR=13 E: MINOR=65 E: SUBSYSTEM=input E: USEC_INITIALIZED=28281822 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=platform-button@1a E: ID_PATH_TAG=platform-button_1a E: LIBINPUT_DEVICE_GROUP=19/1/1:gpio-keys E: ID_INPUT_KEYBOARD=1 E: DEVLINKS=/dev/input/by-path/platform-button@1a-event E: TAGS=:power-switch:

Bidding hotkey to GPIO key is now working.