[zbh23]

I’m not sure if you guys have seen this:

Updated Python Scraper

But a co-worker and I got this working brilliantly on a rpi B+

[zbh23]

from home have you tried:

~/.emulationstation/gamelists/

Within that directory there should be a directory for each system that you have scraped with a gamelist.xml

That xml file will reference the directory where the box art is stored also.

[zbh23]

So I tested using alt as my hotkey assignment and it worked, then I tested a few other keys that are mapped in my controller setup and all of the keys I tested were successful.

So it seems that assigning “n” as the hotkey causes an issue due to the default “n” as the input_shader_prev key.

[zbh23]

Yes I have tried setting the value to a different key, placing the value to nul, and commenting out the line to no avail.

[zbh23]

That is the thing, the “n” key binding is my entry for input_enable_hotkey (so that I can press “n” and another key to escape the emulator).

This functionality works, but if I simply press “n” it also conducts the input_shader_prev action.

[zbh23]

At the start of a game there is no yellow text. The only yellow text I see is after hitting the “n” key and the shader selection dialog is displayed.

If it helps the controllers I have are actually configured as keyboards (hence why I need the use of the “n” key). I have their configuration setup in the main retroarch.cfg here:

/opt/retropie/configs/all/

so there shouldn’t be anything overriding the primary retroarch config via the autodetect controller process.

As for the emulator specific config (I am using snes when the issue occurs); the files doesn’t contain any key bindings, the only lines in that file are related to a shader I explicitly selected and video smoothing properties.

[zbh23]

I just checked and there was a retroarch.cfg in

/opt/retropie/emulators/RetroArch/configs

I commented out the lines regarding input shader next and previous; however the issue still exists.

[Author]

Posts