RetroArch limited support #101
FlotterCodername
started this conversation in
Ideas
Replies: 0 comments 2 replies
-
I'd like to see where this goes, but I won't particularly have any valuable input on RA since I haven't been a user of it for many, many years. For reference, unless this has changed in the last 3yrs since I last looked at RA, RA on Linux puts the |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm glad my comment gave you an idea, but I have to say it's not clear what you are proposing? Some kind of pre-processor? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
retronas/retronas#1 (comment) from @gingerbeardman gave me an idea on how some limited RetroArch support can be achieved. That is vanilla RetroArch. Frontends over the top of RA may run completely different CFGs which they specify on a case-by-case basis via the CLI.
User uploads their own
retroarch.cfg
for modification, runs a task/service and gets a modified version back that lightly integrates RetroNAS.retroarch.cfg
basic format:#
starts line commentTo make this cleaner, the
#include cfg_name.cfg
statement could be used. So in the original retroarch.cfg, you'd only add at the bottom:Problem with that: this include statement will be flushed (along with any comments) if the user has
config_save_on_exit = "true"
🥴.So I don't know if that's what you'd want there.
On Windows, the file will be expected next to the original
retroarch.cfg
. I'm not familiar with macOS/Linux RA, sorry.The relevant config keys:
There are more directories that can be configured, but I limited it to the ones that make the most sense.
Beta Was this translation helpful? Give feedback.
All reactions