amiberry listing game and .uae configuration ( double game list)
-
Its the first time I used amiberry today because someone asked a question about it and it works as it should.
Is there any reason .uae extension lists as a game. Because if you want a custom config you need to name it the same as the game .uae and you end up with 2 listings.
If there is a reason for it it might be best to change the extension for custom game configs . For not i removed the .uae out of the /ect config file. Just posting here incase it was an oversight as its experimental
-
@grant2258 As far as I remember uae was added as launchable file because it saves the troubles to use the gui to start a preconfigured game.
Since the default configuration part is not the Rom folder, you won't end up with two entries anyway. If you set your config path to the Rom folder manually I advise to move the actual Roms from theroms/Amigafolder to a separateroms/amiga-datafolder.I suggest the second method, because starting games by using uae files allows you to configure each option separately for each game.
-
@ectoone well i know where your coming from there is just one problem the script checks the amiga games directory. not the configs dir for the for the game configs.
if no config or auto provided, then look for rom config or choose automatically
if [[ -z "$config" || "$config" == "auto" ]]; then
# check for .uae file with the same base name as the adf/zip
if [[ -f "$rom_bn.uae" ]]; then
config="$rom_bn.uae"if it was in a zip it would be fine but if you add it to the config directory its not searching there for it.
I think the bash script does have the right behavior if a script is there with the same name as the game use it and it would work perfectly if it was zipped. If you add a config for a game it should use it.
Again its all personal choice the script could be changed to search the config directory as well it just means you would need to find the configs if there not all in a zip. If there is a use for this .uae maybe game configs should be called .cfg. I dont know the ideal solution for it though. I don't know the behavior of this emulator and the config file priority but usually command line always over rides a config so there will be a little needing added to the bash script to run uae files because it will always calling
amiberry configname.uae romname(configname.uae )
if the romname is .uae it shouldnt be calling the second parameter is attempting to insert configname.uae as a floppy and it could possibly mess the floppy image being inserted id need to test the theory out though
amiberry configname.uae
-
@grant2258 it was already suggested to relocate the config folder into the rom folder on github yet there then still would be the issue with having two entries in your gamelist when you have adf/ipf and uae files in that folder. The script is not responsible to hide an adf/ipf file if an uae files with the same name exists it's purpose is only to load the files into the emulator.
The only options to hide files are to use your method by excluding an extension from es_system.cfg, create a gamelist.xml with only the entries you want and set emulationstation to parse gamelist only or use the hidden feature and kiosk mode (although I'm not sure how that works, because I've not tried it myself).The script is setup to allow adf files to be started from emulationstation. Just dump your files into the amiga rom folder and you're good to go. And for some games that's just enough.
But by using uae files you can not only point to the discs you're using but you also can tweak your screensettings, custom controls and everything else just to fit a particular game. The initial setup can be a little bit tedious because you have to create a uae file first but in the end it is way better.
There was a script flying around once that was able to create uae files for disk games from a template which made that process a lot easier. I'll see if I can find it later. -
@ectoone
I know what you mean and that the reason I ended up here someone wanted to use a custom config for a game to change the joystick. I just noticed when doing it there was two entries when doing it. I do knwo how to fix it up for myself it was more of a to let you guys know its not a big deal in the big picture -
@grant2258 Well, I guess the main reason to keep uae in the /etc/emulationstation/es_system.cfg is that then people don't have to worry about adding it themselves and to either add it again after an update (which will override the default es_system.cfg) or to have a separate /opt/retropie/configs/all/emulationstation/es_system.cfg which will not be updated when you add a new system.
I prefer to use the default es_config.cfg and use the uae files to point to a separate folder where I keep my games. And I use that method also for scummvm, residualvm and dos games. It keeps the gamelist clear and I have all the benefits from using uae files.
Here is the script I mentioned (but I changed some things in my version a long time ago but I don't have that anymore. Maybe I can take a look at it on the weekend to replicate the changes I made. From a quick look that script also doesn't support ipf files)
https://github.com/Douggernaut/RetroPieAssistant/tree/master/Amiga
You only need to use the generate_uae.sh part (not change_configs.sh nor run_all.sh because they are obsolete with having uae in es_config.cfg and some other stuff). -
i can understand it from a perspective of that might confuse new users is all. I know the ole amiga games love certain combos to work properly. If everyone just puts everything in a zip it will work. I think a comprise could be the script searches the config dir as well and if its there itll use it and not list it
-
@grant2258 But as far as I know that is not possible because that's how EmulationStation works. It just tries to find everything in a single system folder with specific extensions. There is no way to filter it beforehand with a script. So the only way is to separate the files on your own or hide double entries with the methods I've already mentioned.
-
I requested the Config files path be pointed to the roms folder, but retract that request now due to the new features I’ve added to Amiberry directly:)
I still feel it should remain a supported file type for ES launching though as it is very useful that way
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.