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

I want to follow up on this. My posts give the impression that there is an issue with RA 1.10.0, but the truth is quite the opposite!

The change in the behavior of lightgun support appears to stem from this:

https://github.com/libretro/RetroArch/pull/13258

If I'm reading this correctly, this is the summary:

Pre-1.10.0: lightgun coordinates were scaled to the visible game area, which resulted in some lightgun-like devices being confused by various aspect ratios. I did not experience issues with this because I used a border sized to each game's aspect ratio with my Sinden Lightguns.

1.10.0+: lightgun coordinates cover the whole monitor screen and treat the visible game area as part of that entire screen. I think that this is a very positive change. The issue I experienced with the odd scaling was due to me not adjusting the Sinden border to cover the entire boundary of my 16:9 TV screen. After doing that, all manners of game aspect ratios work very well!

I hope that this clears up any confusion that I may have caused!

arpruss created this issue in libretro/RetroArch closed convert abs mouse from screen to viewport coordinates; fix relative m… #13258

How to try out on a Raspberry Pi:

Exit Emulationstation

Make a backup of your current emulationstation binary /opt/retropie/supplementary/emulationstation/emulationstation.

Make a backup of /home/pi/.emulationstation/es_input.cfg

Start jstest /dev/input/js0 # or 1, 2, depending on your setup or if USB attached controllers jstest /dev/input/by-id/<your usb controller> and press the hotkey button, or a button not yet assigned. Note down the button number when pressing that button.

Put this number into the es_input.cfg below the controller section you just used for jstest. The line to be added is:

<input name="hotkey" type="button" id="_put_here_the_noted_button_number_" value="1"/>

Change to folder RetroPie-Setup: cd ~/RetroPie-Setup

Clear out previous source tree: sudo rm -rf tmp/build/emulationstation-dev

Make a folder mkdir -p tmp/build/emulationstation-dev and change to the folder pushd tmp/build

Run git clone --recursive --depth 1 --branch fb_hotkey_gamedesc_scroll https://github.com/Gemba/EmulationStation emulationstation-dev

Return to previous folder and run sudo: popd && sudo then:

./retropie_packages.sh emulationstation-dev depends ./retropie_packages.sh emulationstation-dev build

After successful building, copy the emulationstation binary: sudo cp /home/pi/RetroPie-Setup/tmp/build/emulationstation-dev/emulationstation /opt/retropie/supplementary/emulationstation/. Exit sudo shell.

Start Emulationstation

To revert: Restore your backup of es_input.cfg and emulationstation and run cd ~/RetroPie-Setup && sudo ./retropie_packages.sh emulationstation-dev clean to clean the cloned repo.

Your feedback is appreciated.

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

You can use a similar solution to the one in this post, where the requirement was to have the Pause function being triggered without a hotkey.

Could find the solution on my own.

The correct syntax is J0B4/H0VX
where the "X" is set to be 1(up) 2(right) 4(down) or 8(left) depending on the direction.

@lolonois Good call. Now I know what the hotkeybtn is used for.

Hello and welcome to this forum.

Alas, you won't find much support for a third-party RetroPie installation here, because we can't know how much its makers changed the official installation image. On top of that, RetroPie's licence and the licences of many of its components don't allow commercial use, including selling it as part of a commercial product. The people who sold it to you broke those licences.

So, you'll have to either ask the vendor about the problems with their product, or install the official image from https://retropie.org.uk/download/. In the latter case, you should make a backup of your old system and its games as described here – or just use another SD card.

We'll be happy to help you with any problems you may have with the official image. As a side effect, you may learn a bit or two about the inner workings of the wonderful retrogaming box of bricks that RetroPie is. 👍

Be sure to read https://retropie.org.uk/forum/topic/3/read-this-first to get more useful information to start in this forum.

The hotkey enable button, being RetroArch specific, is part of the joypad auto-configuration profiles saved in /opt/retropie/configs/all/retroarch/autoconfig.

@scenariol113
OK
I figured it out with some off site help.

I was able to compile it by editing the supermodel directory /Src/Input/inputs.cpp

in the input.cpp file you edit the UI Controls line (1st line) for "uiExit"

where it says INPUT_UI, "ESCAPE" you change it to INPUT_COMMON, "NONE"

Then you run the -config-inputs command and map your keys.

The UI Exit should be in the list now to map it.

Now you can exit supermodel from somewhere besides a keyboard.

Here is a youtube link and the guy that helped me. Read the comments and you will get a better understanding

@darknesscrysis i kind of like the idea of having an on-screen cheat sheet appear when holding the hotkey, especially since i don't play all the time and tend to forget some of the custom combos i've set up. though to help with that, i've made a printout and keep it near the TV. here's what i mean:

cheatsheet.jpg

it's just a basic inkscape document with some fancy paths and a font i forget the name of :) if you're interested i can upload the .svg file somewhere for you.

@busywait Good thinking, i have aksed and will put answer here when i get one, just in case it helps anyone else out in future

@saccublenda Thanks. Don't have a keyboard plugged on my bartop so I will use the Quick menu / options solutions...I can live with that.

Thanks.

@mitu
I do have 4 usb joysticks modules attached. Maybe I have a hot key setup by mistake.

Thank you, gives me a whole bunch of new stuff to try tomorrow morning, see if I can get it working.

@dankcushions Did that, no effect. I'll google to see how else I can get a verbose log, but last time I didn't see anything.

No, it's not specific to the RetroArch version, overrides don't save the hotkey configuration, it's saved only when saving the whole configuration.
You can try to add an extra configuration line in /opt/retropie/configs/gba/retroarch.cfg with

input_toggle_fast_forward_btn=X

where X is the button input code for L2 - you can find it from your gamepad autoconfiguration file in /opt/retropie/configs/all/retroarch-joypads/<gamepad.cfg>.