Updated EmulationStation for Windows
-
Add a "Completed" metadata tag.
Why not...
Allow saving subset options for individual systems.
I don't like the idea. Subsets are global settings that can apply to everything ( colors/screen view ). This is why I designed "customViews" -> It applies only to gamelists... The only subset that has interest be saved by system is the "gamelist subset". The theme can be refactored to use customViews instead.
Collections don't show anything inside parentheses.
Never rename your roms : scrappers don't like it ! Or if you do it : don't use parenthesis.
Configure Input doesn't allow defining "pageup"/"pagedown" like old ES did.
I didn't change anything in the input configuration. What "old ES" version are you talking about ? Aloshi's 2.0.1a ?
ES launch games and wait for the launched exe to finish. If it returns immediatly to ES this is because the exe you launch runs another one and returns immediatly. You'll have to find another command line to run this game. I know that when you create links to Windows Store games, links return immediatly, but, I don't know any way for those shorcuts to wait for the process to end...
-
I try to use two cores for a system, and only use the first one in the list. In other words, I have a system that I have called capcom with games of alpha2012 and others of mame2003_plus, I have done the same thing that you have in your git but only the first one is there.
I know I'm sure I'm doing something wrong.<system> <name>fba</name> <fullname>Capcom</fullname> <path>~\..\emulationstation\roms\fba</path> <extension>.7z .zip .ZIP</extension> <command>%HOME%\systems\RetroArch\retroarch.exe -L %HOME%\systems\RetroArch\cores\%CORE%_libretro.dll %ROM%</command> <platform>fba</platform> <theme>fba</theme> <emulators> <emulator name="fbalpha"> <cores> <core>fbalpha2012</core> </cores> </emulator> <emulator name="mame"> <cores> <core>mame2003_plus</core> </cores> </emulator> </emulators> </system>
-
I don't like the idea. The theme can be refactored to use customViews instead.
I've got 16 subsets (and counting), which would take hundreds of customViews with all the possibilities! See here and here. Changing bg, colours, font, and all the other little things on a per system basis would be more ideal. (And being able to quickly change them again, meaning not editing the system xml files to do this.) I already have 2 customViews, but I guess I'll have to make some awkwardly specific ones ┐( ̄ヮ ̄)┌
Never rename your roms : scrappers don't like it !
Scrapers actually read the hash of most roms fine. For me, renaming is the way to go for pretty much anything but ES/RetroArch, so it's what I've always done to give myself information on the genre and release year. I've made some batch files with regex find-replacing to clean up my gamelist xml's, so I'm fine now.
I didn't change anything in the input configuration. What "old ES" version are you talking about ? Aloshi's 2.0.1a ?
Yep. Just adding a page up/down to grid view would be good. Add this xinput to es_input to test. (It works on basic/detailed.)
<input name="pageup" type="axis" id="4" value="-1" /> <!-- Right Analog Up --> <input name="pagedown" type="axis" id="4" value="1" /> <!-- Right Analog Down -->
-
@CarissaIsWierd Your screenshots show very interesting things. Is there any way you can share your theme with me, so I can "play" with it and analyse it ?
-
-
@jero said in Updated EmulationStation for Windows:
I try to use two cores for a system, and only use the first one in the list. In other words, I have a system that I have called capcom with games of alpha2012 and others of mame2003_plus, I have done the same thing that you have in your git but only the first one is there.
I know I'm sure I'm doing something wrong.<system> <name>fba</name> <fullname>Capcom</fullname> <path>~\..\emulationstation\roms\fba</path> <extension>.7z .zip .ZIP</extension> <command>%HOME%\systems\RetroArch\retroarch.exe -L %HOME%\systems\RetroArch\cores\%CORE%_libretro.dll %ROM%</command> <platform>fba</platform> <theme>fba</theme> <emulators> <emulator name="fbalpha"> <cores> <core>fbalpha2012</core> </cores> </emulator> <emulator name="mame"> <cores> <core>mame2003_plus</core> </cores> </emulator> </emulators> </system>
Finally I managed to run several cores, I did not know that I had to assign it in ES within the edition of metadata, now it works perfectly for me. I really didn't see anything in git about this, or possibly skip the info and I didn't realize it. I am very happy with this.
-
@CarissaIsWierd Your theme is full of very good ideas, and I totally understood the need for saving subset per system in some "conditions". So....
I took time to think & code something, but, I've just commited a new version containing something that will interest you very much : I added support for a new 'hierarchy' for subsets, and added the attribute appliesTo -> You can name the view/customView the "subset option" is for ( and name several separating them with a comma ) & then you can have per system options for your gamelists ( using a "view customisation" screen )
Here's a sample :
<subset name="tileborders" appliesTo="Tiles"> <include name="yes" /> <include name="no">./tilesquareborders.xml</include> </subset>
-
@f-caruso That's actually really nice! I think I've found a bug already though. Replace the List BG subset in my theme with this:
<subset name="> List > BG" appliesTo="detailed"> <include name="Retro">./options/list-bg-2.xml</include> <include name="Pixel">./options/list-bg-1.xml</include> <include name="Shapes">./options/list-bg-3.xml</include> </subset>
Now change it to Pixel or Shapes under Theme Configuration. Trying to select Retro under View Customisation will change it to whatever you just selected for all systems. It basically locks out selecting the first option if something different is selected under Theme Configuration. So far it's doing it for all the subsets I'm writing out like that.
Edit: Looking at es_settings.cfg, it might be because all options are no longer saved there if the first is selected.
-
@CarissaIsWierd The
>
character should be escaped when used in an XML file, your fragment above is not valid XML. Use>
instead. -
@CarissaIsWierd True... Fixed..
-
@f-caruso Almost perfect! But I can't get it to appear for two views with a comma like you mentioned. It should be like this, right?
<subset name="tileborders" appliesTo="detailed, grid"> <include name="yes" /> <include name="no">./tilesquareborders.xml</include> </subset>
I'm probably being a nuisance now, but I found another issue :x
Step 1. Set up a system with its own options via View Customisation.
Step 2. Select some of the same options for all systems via Theme Configuration.
Step 3. Edit any option for the customised system/s and it'll remove options from es_settings.cfg that now match to what is being used universally....Meaning when the Theme Config options are changed again, those system specific options from before are now lost. Making them permanent in es_settings would be a better solution, adding a "Reset Gamelist Customisations" to each system to clear them out. (Changing the theme resets everything as well, so that could be used too.)
-
- I didn't say "a comma and a space" ;-) Try without space.Custom view names can have spaces so, spaces are tested too.
- Not an issue to me. It acts just like it should : If the custom setting is the same that the global settings, it has to be set to "default" and then, removed from es_settings. If you don't remove them, changing a global setting will not change anymore views that have been customized at least one time : it's worse...
-
If you don't remove them, changing a global setting will not change anymore views that have been customized at least one time.
That's the idea, locking those settings so they don't get changed. (Unless they're reset.) I can see how that'd be an issue, if one was to change a lot until they get things right, but that goes both ways. Having a way to "lock" a system subset option (with a button?) and a lock icon with it could work, but that could be making it too complicated. Oh well! I still appreciate all the time you've put into this fork. Looking at the commits on Github is like wizardry. My brain is too squishy for it ϵ( 'Θ' )϶
-
excuse the really n00by question, but if I want to update my existing Emulation Station build, am I okay to replace all of my existing Emulation Station files with the entire contents of the latest build from github? Or if I do that, will I lose all my custom settings? Thanks in advance!
-
@f-caruso I started playing with my 3DS again and forgot all about the great background music so many themes have. So now I'm extracting a bunch of them and wondering if there's a way to make them loop in ES. I've found the code to add them, but they don't loop, and they also don't start up again when exiting a game. (I have to cycle to a different system or return to the carousel for it start playing again.)
Themes also have very short sound files for opening games. Is there ES code for similar functionality?
As for an idea, pointing <path> to a folder rather than a file could play a random file each time:
<sound name="bgsound"> <path>./assets/sound/bgm/</path> </sound>
@MiL0 Settings are stored at
C:\Users\----\.emulationstation
, so it's save to replace the files inProgram Files
. -
@CarissaIsWierd it already exists for a while. Use the name "directory".
<sound name="directory"> <path>./assets/sound/bgm/</path> </sound>
-
@f-caruso
I think "directory" doesn't work because 3DS bgm's extract as .wav files. I found this in AudioManager.cpp. Would adding .wav make them play?if (extension == ".mp3" || extension == ".ogg")
Nevermind entirely, .wav files are huge! I'll just convert them all to .mp3.
-
Is posible add to your EmulationStation for Windows the posibilitie to close the emulator window with HOTKEY+START just like RetroArch and Attrack Mode do????
-
@maxiducoli That's something you configure in RetroArch, not in EmulationStation.
Even on RetroPie, that's part of RetroArch's joystick auto-configuration file. Just find your joypad auto-configuration file - should look like one of these if you download it from RetroArch's updater - and add 2 lines to it:
input_enable_hotkey_btn = "X" input_exit_emulator_btn = "Y"
where
X
is the key for yourHotkey
button andY
is the one for theStart
button. -
@mitu
thats works fine with RetroArch, but not with others emulators.
Like PCSX2 or Cenu or Citra, etc, etc.
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.