Updated EmulationStation for Windows
-
@f.caruso You are amazing - thank you so much for your work on this! I am having a couple of issues with the latest build, one is minor - the log file is showing the errors below, but they don't seem to affect anything? Perhaps you will know from looking at them what could be causing this. Next, I'm experiencing unusual behavior - the app seems to work every other time I load it (I am running the portable exe as admin) -- but after working successfully, the next time I load it, it just quits at the loading screen, and the log shows the same errors below. Perhaps related? let me know what you think.
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "color" (for element of type video).
lvl1: Unknown property type "color" (for element of type video).
lvl1: Unknown property type "color" (for element of type video).
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "color" (for element of type video).
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "color" (for element of type video).
lvl1: Unknown property type "iconKodi" (for element of type menuIcons).
lvl1: Unknown property type "iconRestart" (for element of type menuIcons).
lvl1: Unknown property type "iconShutdown" (for element of type menuIcons).
lvl1: Unknown property type "iconFastShutdown" (for element of type menuIcons).
lvl1: Unknown property type "color" (for element of type video).UPDATE I was able to eliminate the errors by just commenting out these items in the theme.xml file, so the above is more of just an FYI as to the issue. Still having the intermittent starting errors; seems that no matter what I try, the program only starts every Xth time I run it - sometimes every other time but more often every 3rd or 4th time I try to run. Any ideas what could be causing this? I am running Windows 10 (latest build), and also note I was using the pre-compiled pack that you posted in your last message; not sure if the update you posted for @dukeblooders was fixed in this as well?
-
I have this Problem too. Emulation Sation quits at the loading screen. Many of Issues in the log file. I have tested the preconfigurated .zip file and it crashes too.
-
@PittStone I had the same problem, instead of only having it boot sometimes and/or return from games without crashing, I ended up reverting to 2.9 by jdrassa because for me stability is more important than new features, When it doesn't crash it still takes longer to load in the 10s of thousands of zipped roms due to me scanning each time instead of using only XML's, but the 2.9 only takes 30 to 40 seconds to do this, so tolerable, 2.10 mod actually took 2+ minutes and would hang after loading the systems.
I will keep testing his future releases, but hopefully he gets a chance to test for this loading bug with his work.
-
If @f-caruso 's fork does build and work fine on RPI devices, perhaps a good idea to integrate it (for now) could be to create a scriptmodule for it alongside the stock EmulationStation shipped with RetroPie. Similar to
mehstation
andpegasus-fe
for example. So users can have an option to install let's sayemulationstation-fcamod
similarly to what they can do with the existingemulationstation-dev
. In other words, just another flavour of EmulationStation.And because @f-caruso 's fork is still ES, it shouldn't be that difficult to do. What do you think?
-
Hi all,
@drcnyc Don't worry about the logs : you are using a theme which menu was copied from a recalbox theme. My version just does not supports useless icons like Kodi or restart. Lvl1 items are just informations.
@LiveFreeDead, @PittStone, @drcnyc
I really don't understand your starting errors (or the 2mn loading time). Jero & dukeblooders didn't report it, and I never had a single problem on any of my 3 machines. So I'm wondering is there's something about your configurations. What has changed is that I use a multi-threaded loading : I count processors and create as many threads as available cores.In order to help me, can you tell me more about your configurations -> CPU frequency & how many cores. What theme do you use ? What kind of storage do you have ( usb key, hdd, ssd ?)Forget it, I found why... I'll post a patch very soon.
But i'm still interessted in knowing your configs ( cores/theme ) -
@f-caruso I can send you my core and theme configs. Can i send you a pm anywhere for that?
-
@PittStone PMs are deactivated on this forum...
-
@f-caruso I'm too dumb to get the padtokey function to work, I've tried with project64 and redream so far and nothing works, Am I missing something? Both emulators use a combination of ALT+F4 to close. Attached is an example:
<app name="redream">
<input name="hotkeyenable start" key="(%{F4})"/>
</app>As you can see, I tried to use select+start to trigger ALT+F4 with no success.
Also as you recommended is ran ES as administrator, but nothing. Any suggestions?
-
@f-caruso https://mega.nz/#!Dkg1BYKY!_WoDJNz1lLa0W_LLVeAF1M1ihMumPQiwgy9e_cGtgVA
Here is my settings, looking forward to any fixes you share :)
-
@f-caruso O.k. is send it.
-
@LiveFreeDead LLOOLL I wasn't talkin about emulator cores... But CPU Cores !!!!
-
@sikboy You have tried, go to properties of the exe and say in properties that always start as administrator. That solved the problem for me.
-
@sikboy @jero the padtokey xml looks good. As I already said, I is generally because processes don't run with the same privileges. Run task manager, go to detail, and add column "elevated" (right click on columns). You emulators (like redream) and emulationstationportable need to have the same elevation level. It's a limitation in Windows since W8. If not, adjust in the exe properties. I personnaly don't like the "run as admin" trick. An emulator or a launcher should never run elevated - only system programs should. Plus you have UAC dialog, so you deactivate UAC which is discutable. Maybe you should juste ensure redream IS NOT elevated ! ( It works perfectly on my machine without elevation )
-
-
@f-caruso
That's easier:
Intel Core i5 2500K
Cores 4
Threads 4
Name Intel Core i5 2500K
Code Name Sandy Bridge
Package Socket 1155 LGA
Technology 32nm
Specification Intel Core i5-2500K CPU @ 3.30GHz
Family 6
Extended Family 6
Model A
Extended Model 2A
Stepping 7
Revision D2
Instructions MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, Intel 64, NX, VMX, AES, AVX
Virtualization Supported, Enabled
Hyperthreading Not supported
Fan Speed 667 RPM
Stock Core Speed 3300 MHz
Stock Bus Speed 100 MHz -
@f-caruso I just noticed something interesting. I was having the startup issues on my laptop which is running an Intel Xeon E-2176M (https://ark.intel.com/content/www/us/en/ark/products/134867/intel-xeon-e-2176m-processor-12m-cache-up-to-4-40-ghz.html) but when I ran it on my media server, which has an Intel Xeon E3-1275L v3 (https://ark.intel.com/content/www/us/en/ark/products/76300/intel-xeon-processor-e3-1275l-v3-8m-cache-2-70-ghz.html) the startup issues seem to have disappeared. Might be nothing but thought I would mention just in case this helps.
-
@f-caruso also, kind of unrelated to the startup issues above but it seems to work fine when I just run emulationstation.exe without using the portable executable. I don’t have the %home% variable set or anything like that - so curious why the portable executable is needed?
-
@drcnyc The startup random crash is related to a change I did in custom/auto collection management. The new PC may have no custom/auto collections. It's solved. I'll try to release it today.
@LiveFreeDead I really don't understand why it takes two minutes to load on your machine, I've tested my threaded loading on several machines (one has 2 threads, the others have 8 - yours has 4) and loading is generaly about 2x faster, even with an usb key. I'll add an hidden option to deactivate threaded loading, just in case... -
@sikboy Did further testing with redream. redream does not respond to SendInput. The only thing that work is SendMessage(WM_CLOSE)... I'll have to think about what do to...
-
@f-caruso Also Project64 acts the same way, I appreciate all your work so far. I'm not complaining at all, the padtokey feature is a big seller since it gives a universal way to handle your games with a controller, the same as Retropie.
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.