start button exits emulators in lr-picodrive and lr-genesisplus

dox1842

So I went in and modified the config file for my controller and got it working. I just unassigned the hotkeys.

The problem here though is that the hotkeys work without me pressing the "activate hotkeys" button. In other emulators this feature is kind of nice - ill admit I never used it before until just now to test it out but being able to hold down the hotkey button and exit an emulator or reset the console instead of going into the menu to do it is nice. Here is the question - Why is the "hotkey always on" behavior only prevalent in the megadrive/genesis emulators and not the other LR emulators??

mitu

@dox1842 said in start button exits emulators in lr-picodrive and lr-genesisplus:

Why is the "hotkey always on" behavior only prevalent in the megadrive/genesis emulators and not the other LR emulators?

It's not, it's something you probably (mis) configured just for those systems.

dox1842

@mitu How can I reconfigure it for the systems?? I looked on google and there is supposedly a "hotkeys always on" feature but I cannot find it in retroarch nor find it in the setup script.

mitu

@dox1842 Can't say I heard about this 'hotkeys always on' feature - do you have any references ?

dox1842

lHere is someone with the exact same issue as me. Here is a post with the exact same problem and the solution of "hotkeys always on" is on the bottom.

mitu

@dox1842 1st post seems like a hw problem and the 2nd one looks like an wrong hotkey configuration, but nothing about a particular setting in RA. Sorry, I though you were searching for a setting to have 'hotkey always on' in RetroArch and I thought your found a reference to such setting existed, because I haven't heard about it.

mediamogul

@mitu said in start button exits emulators in lr-picodrive and lr-genesisplus:

Can't say I heard about this 'hotkeys always on' feature - do you have any references ?

This particular issue is confusing, as it actually seems somewhat backwards in concept. By not having any hotkey button defined, all the assigned emulator functions will activate without a modifier. Since, again in concept, most people see a button-activated function as a being a hotkey, rather than there being a lack of one, everything gets lost in translation.

Somehow or another through the activation of 'save on exit' there's a config file overriding the assigned hotkey of the automatic joystick config and the start button is being allowed to exit RetroArch without having a modifier. Straightening the whole thing out is another matter, as I'm not sure how extensively everything is messed up now. I would recommend that @dox1842 first disable 'save on exit' and then go back setting each of the retroarch.cfg files to their default state.

dox1842

@mediamogul how do I set each of the retroarch.cfg files to their default state? I deleted my retroarch.cfg file for the genesis/megadrive and had it recreated and still had the same issue.

mediamogul

@dox1842

There should be a default config backup in each of the respective folders that you can copy and past from. The main config can be found at /opt/retropie/configs/all/ and the individual system configs at /opt/retropie/configs/system-name/.

dox1842

@mediamogul What gets me is I have the hotkey defined as button 10> that's the left analog stick on the Logitech controller. The CFG for genesis has this in it so im assuming the button is defined. I am at work now but ill check out the "backups" when I get home

dox1842

@mediamogul I just reset the all config along with the snes and genesis config to default settings. The problem still exists with sega but also now with snes. I am pulling my hair out now!! Any ideas?

dox1842

@mediamogul @mitu Ok I found the solution. If you read the second link I posted , what the guy was saying is that even though the auto assign hotkey was 10 I had to reconfigure it to 10 again under the retroarch settings.

I am baffled by how this works but it does work so im happy now!! Thanks for your help.

mediamogul

@dox1842

I'm glad it's working and the resolution is expected behavior, but keep in mind that this only fixes the singular hotkey issue. While that's a positive for now, as long as you have 'save on exit' enabled and you continue to change your settings further, each system will have different configuration settings and problems like the one you just solved will begin to surface in other areas.