@alturis said in RetroPie 4.7.1: Trouble getting custom_viewport_... settings to work:

Are you suggesting I fix that myself in the github project?

The file is from the upstream Retroarch's repository - you can submit a PR there to have it fixed.

@mitu Awesome, thank you!

Looks like a good use case for git on LAN? You can tag or branch your config sets rolled out for other machines than yours. Later merge all your latest and greatest changes from your machine into the friends' branches from time to time. If something breaks you can easily go back in time.

@rmbell34 said in Core settings per folder possible?:

@folly It worked! Thanks so much! That was the issue. I needed to change the emulators.cfg to tell it where the retroarch.cfg was in the famicom folder. Thanks again!

Great to hear it is working.

Curious,
what lines did you have in the famicom emulators.cfg ?

It should have added it when you updated your patched lr-nestopia.

@dankcushions said in Can't Find Shader Core Configs:

@alphabetapie 'quick menu' isn't enough info but i suspect you mean quick menu > options? in which case: https://retropie.org.uk/docs/RetroArch-Core-Options/

Yup, found it. Was in the retroarch-core-options.cfg. Thanks again! Always a super-helpful forum!

I would add that in the /boot/cmdline.txt parameters, I changed the resolution to 768x768 and everything is now centered and looks correct....except, the top few lines of the [TAB] menu in Mame are cut off....

This is so strange.....

@ReadyPlayaWon that’s interesting, thanks. Not too bothered about trying Moto Racer, but I think I’ve got CM2.0 lying around somewhere - I’ll give it a try.

@treki said in Are the individual configurations also backed up?:

Where are the RetroPie settings (RetroPie setup) stored?

Most of them are in the /opt/retropie/configs folder, which is shown as \\retropie\configs over file shares.

Could someone explain to me why amiberry is seen as more plug and play compared to puae, and is the recommended emulator here? Everything I've thrown at puae (lha and hdf) seems to work, I get access to the lovely CRT shaders, and I'm probably going to have to mess about with config on a per game basis for either anyway? Amiberry seems way more of a pain in the arse on several levels, to me - and that's not even considering the strange resolution switching issue I'm getting.
I'm considering just binning it off and going with puae; am I going to regret that for some reason I've yet to experience?

@fatfrog Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Welcome to this forum.

For RetroArch cores, see https://retropie.org.uk/docs/RetroArch-Configuration/#hardcoded-configurations. Besides, that applies to the official RetroPie image. Third-party images may have other config hierarchies and are not supported here for that reason (among others).

Other emulators are not standardised and may save their configurations in different places. Which emulators are you exactly interested in?

@BuZz I didn't copy anything on my 4.6 fresh install. Permission issue arose immediately. Of course I should be able to fix with chown.

@Wojima said in Override cfgs won't load:

I also have Save Configuration on Exit and Use Global Core Options File turned off.

You should save a game remap file, not a game override, I don't think input controls are saved in configuration overrides - see https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping.

You can also leave the global core options on, if you want a per-game option file, then you can save game options just as you do with overrides/remaps.

@Kookamunga said in need help saving settings in retroarch:

Check out my response here:

https://retropie.org.uk/forum/topic/12318/failed-saving-config-to-opt-retropie-configs-psx-retroarch-cfg/13?_=1588868505415

See if that works for you.

i found the close session, but when it exited to the nothing running in retroarch menu, i couldn't press anything to navigate...this is difficult for me. i've been trying to fix this for like 4 days hahaah! i suck at this, but i enjoy the challenge i guess! anyway, thanks if anyone has had this happen to them and would throw me a bone, i'd sure appreciate it!
thank you

Self-Solving Problems Department: the trick is to put "cocoe" in the EMULATORS.CFG line rather than "coco"...

@mitu said in Making Gambatte tell the difference between GB and GBColor:

core_options_path =

That was the bit I was missing. Never seen a "core_options_path =" line before. Thanks :)

Okay so I ended up reflashing the sd card and start from scratch, which helped.

@mindfieldx Yes, it's part of the 4.5 release: https://github.com/RetroPie/RetroPie-Setup/commit/47035624de6e26b52a9c0d7529926c307440a6f5

0 joolswills committed to RetroPie/RetroPie-Setup fixed: make sure autoconf.cfg is owned by $user when adding/changing values

@DetroitKp The 2nd config you posted (corresponding to the USB controller being plugged in) is a full RA config, that is produced when you save the config from the GUI (or enable saving on exit).
Are you sure it's the same file you're posting ? I don't think there's any mechanism in RetroPie to switch those files depending on the controllers used. Maybe the 1st file is the one from /opt/retropie/configs/all and the 2nd one from the /opt/retropie/configs/arcade ?

When you configure a controller, Emulationstation will create a controller configuration file in /opt/retropie/configs/all/retroarch-joypads with the button mappings, and that's all.

Your configuration steps are fine, and to choose what player the controller gets assigned, you indeed have to set input_playerX_joypad_index. So 1st controller would have the index 0, assigning it to P3 would be

input_player3_joypad_index = 0

etc.

You can leave input_autodetect_enable to true , otherwise the auto-config mapping for the controller would not be loaded.

I would check where the 2nd file is coming from and if it's from the /opt/retropie/configs/arcade folder, you should reset it to default:

# Settings made here will only override settings in the global retroarch.cfg if placed above the #include line input_remapping_directory = "/opt/retropie/configs/arcade/" #include "/opt/retropie/configs/all/retroarch.cfg"

I found the problem (or just one solution atm). There is something that libretro does not like in the driver implementation. Now I can fully play the Super Mario in the PC browser and on Android Chrome in my smartphone.

Sorry for the noise and thanks for your time, but hopefully everyone will benefit from this once I have made a demo.