RetroArch Config Confusion and Issues
-
@meleu OK cool....that's clear enough..think I manage that :)
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
@dankcushions that would maybe make sense.
This is kind of exact example though of conflicting information regarding this,one school of thought says to just use the config editor and enable save on exit and another completly conflicting one is to edit the files manually...
It probably is multiple schools of thought. I wouldn't call it conflicting information it just different points of view and different ways of doing the same thing! Given the same challenge people will present multiple solutions. Perception is everything. It just depends on your level of experience and knowledge. It's like command line vs. GUI. One way is probably more comfortable and suits your needs better than the other but that's neither right nor wrong. It wouldn't be very flexible if everything was completely linear! ;) Options are good!
It's a hierarchy which makes perfect sense really. Global changes at the top and more granular at the bottom. I agree with Dank you would being doing a lot more work if it was only one config file per emulator! :/
-
@Riverstorm Don't get me wrong,I totally think that options and flexibility are indeed benificial and essentially the very ethos behind open source software.I do believe however that flexibility need not be compromised by useability.I think a system where you have one file for 'global' configs and then one file for each emulator(that overrides any global settings changed for that emulator) which is accessed through ONE universal global interface makes sense doesn't it?And this would also leave far less room for error and conflicts.
-
This post is deleted! -
@dankcushions Yes I know that's the case currently....what I was saying is wouldn't it make more sense if individual config files would simply override global settings for that particular emulator and all this was done from one unified interface?
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
@Riverstorm Don't get me wrong,I totally think that options and flexibility are indeed benificial and essentially the very ethos behind open source software.I do believe however that flexibility need not be compromised by useability.I think a system where you have one file for 'global' configs and then one file for each emulator(that overrides any global settings changed for that emulator) which is accessed through ONE universal global interface makes sense doesn't it?And this would also leave far less room for error and conflicts.
I agree some processes could be simplified but also you have to remember it's not one piece of software. Not quite sure how to word that. It's several really. You have RetroPie, Libretro cores, Retroarch, Emulationstation basically several pieces working together.
If it was one group or one company I could see the merits of a unified uniform software solution to our retro gaming needs. As I get older I don't want to say cynical but the world just isn't black and white made up of good people and bad. You make one group happy and the opposition is upset. It's a lot of compromises and gray area and honestly I can only thank my lucky stars for RetroPie. It works great really once you get it down and is only getting better! :)
-
@Riverstorm I must also paradoxically say 'hear hear' to that statement too! :)
-
Ok...so now I've messed something up,I think I turned on the HW Bilinear Filtering (mistakingly thinking that was the smoothing setting!) in RetroArch PSX and now the games won't boot...can I just delete the config files so that it goes back to using the default global settings and then make a new config from there?
-
These are the files I have in my PSX configs folder:
content_history.lpl emulators.cfg libretro.cfg libretro.so.cfg retroarch.cfg
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
Ok...so now I've messed something up,I think I turned on the HW Bilinear Filtering (mistakingly thinking that was the smoothing setting!)
it is
-
@dankcushions ahhhh,thats what I thought.....very wierd in that case then as the games wont boot,just returns back to emulation station.I haven't had any issues with turning on smoothing in PSX emulator before
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
@dankcushions ahhhh,thats what I thought.....very wierd in that case then as the games wont boot,just returns back to emulation station.I haven't had any issues with turning on smoothing in PSX emulator before
but of course HW Bilinear Filtering is what it's called in the retroarch GUI, not the configuration editor, so if you've been messing about in RGUI who knows what you've changed :) you could start with /tmp/runcommand.log to see the crash.
also, weren't you asking about shaders? the config editor tells you not to use video_smooth if you're using shaders.
-
@dankcushions yes I'm aware about not using shaders with smoothing.Something has changed in the Retroarch config that it doesn't like,but I can't access the retroarch editor now because the game quits before it has a chance to load....I think I need to do it in the main retroarch and load the psx core
-
@Wolfman100 what does games not loading have to do with the configuration editor? It's a script. hadn't we covered this? :)
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
the game quits before it has a chance to load....
Backup early and often...restore when needed...sometimes it's just easier and quicker! :)
-
ha..also a 'hear hear' for that!as I mentioned though,shouldn't I be able to simply delete the config files for PSX I changed and it'll revert to default 'global ' settings?
-
well I've managed to ascertain that its something in my
/opt/retropie/configs/psx/retroarch.cfg
that it doesn't like,as when I remove the file the game boots fine,but without BIOS
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
Unless I'm going blind I definetly can't see that in there...
How did you edit this file ? via saving in retroarch RGUI or manually ? Because the include needs to be at the end, or the settings in the file wont take effect. When using
#includeRetroArch will use the first config it sees, so any of the configuration options in this file that are also in theconfigs/all/retroarch.cfgwill be ignoredthe default per system configs have a comment that mentioned this and the configuration editor will make sure the include is last.
-
I edited in RetroArch....
Crisis now averted though as I pulled in the Config files for a setup I had on another card.This made the Retro-Pie emulation station menu change,as that build was still on 3.7..but it's working all good besides that.Not sure why it went so crazy though.
I did also manually edit the include to be at the end incidently,as I read that somewhere else,and strangely it didn't make any difference at all....
-
@Wolfman100 said in RetroArch Config Confusion and Issues:
ha..also a 'hear hear' for that!as I mentioned though,shouldn't I be able to simply delete the config files for PSX I changed and it'll revert to default 'global ' settings?
I noticed when I (re)install a core using retropie_setup, it creates a retroarch.cfg.rp-dist in the respective config directory. You can use it to "restore factory settings".
;-)
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.