Updated EmulationStation for Windows
-
@LiveFreeDead According to the build log, freetype repo was not available yesterday night ( http://download.savannah.gnu.org/releases/freetype/freetype-2.7.tar.gz - Unable to connect to the remote server )... But you always can access build history on appveyor and download the latest successful builds.
-
@f-caruso
Redraw exiting game BUG:This shows the re-draw bug when I exit any game, using any theme. The only reason it comes back at 21 seconds is due to me manually moving the window using the mouse, once I do this it fades the collection wallpaper and icon back in.
BTW I can actually exit from one Collection and enter another and the wallpaper/icon is still missing until the 3rd or 3th time I enter a collection then it also redraws properly after fading back in.
I have always had this bug since your first 2.10 release, it has changed a bit (improved) as it used to lose some collection icons and the main wallpapers on the carousel .
Doesn't matter if I use windowed mode or full screen.
I just noticed if I run a 2nd rom once it's messed up, once it returns from that it is fine again. and the next exit is broken - so I am thinking a flag/toggle is set wrong or checked to be a value >1 instead of =1 or something.
I have tried transitions set to fade, slide and none, always does this glitch.
jdrassa's version does not do this.
I have NVidia GTX 550Ti, but this bug also affected my nVidia 610m on my laptop. I have tried this with 1 rom on a clean release and it still happens.
-
@LiveFreeDead Hi Glenn, from Austalia ;-) (dawn it is far from France...), I don't reproduce the problem, but you don't provide a lot of informations.
To be in 1.9 release condition, you should try setting the option "HIDE WHEN LAUNCH..." to ON ? This option is not available in 1.9 releases, and loading/unloading is a bit different when disabled. Does the problem still occur ?
Image loosing/reloading is caused by not enough VRAM. Your theme is HD and needs a lot of VRAM. Maybe your scapped images are very big too. Using your theme & preloading, it would require > 3Gb VRAM (yes 3Gb !!!) you can see it enabling the option "show framerate"- to keep everything in memory. There is a mecanism to unload/reload resources (which, honestly, should be rewritten too, but I didn't touch it yet). I have flickerings issues too when I set VRAM too low and it occurs in the 1.9 release too -> Try increase VRAM limit - On Windows with an NVIDIA card, you can set it to 500 without any problem.
Are you using a powersave mode ? When using powersave, Mouse/Keyb events are the only way to redraw the screen... Maybe it is related too -> Try disable powersave modes.
-
Yeah, I have lived in Tasmania all my life, most I done was make LastOS (Windows mods) since early 2000's until today, it's a lot slower since Windows 10 came and killed off modding. I guess that is why I switched to Emulation, it's always gonna be appreciated.
Increasing VRAM fixed it, Do you have the ability to detect how much vRam is available, because my system has 1023 MB Physical Memory and seeing as the default ram size is 100mb it might be worth checking this in a Windows OS quickly each boot so it can change the default 100mb (if detected as 100mb to be more by default (not Pi's default)).
If I enable "Hide when Running Game" it will crash ES entirely when I exit back to ES, I have to close with TaskMGR, I use a dual screen setup, this might cause a issue).
I use Power saving mode disabled since mentioning the issues with scraping with it set to anything else making it abort scraping. Since you made it drop usage I had no need to enable it, like you said then, you can disable it for Windows machines ;)
I thought the 200MB Vram would have been fine, thanks again for simple fix, but maybe we can force a dual reload when returning from a ROM, like i said every 2nd time you returned from a game it would work perfect again, so it is possible to get it to draw correct every time even with low vram? not important now it's fixed tho. Good run on bug fixes, that's 3 for 3 now.
-
@LiveFreeDead Tasmania... 17.125,97 kilometers from Paris... 20 hours by plane... Never went so far ;-) Don't know if I ever will... But it must be beautiful compared to where I live...
"Detect how much vRam is available" -> Can't find a portable way to determine that. Furthermore, Windows has no unique way to do that. Different methods are needed according to the kind of video card. Better not change anything, and let the user do.
The VRAM manager doesn't care about what's on the current screen. It flickers because it loads the image, it needs room, it unload the image. Then, it needs to display the image and reload it, it needs room, it unload the image again, and so on... It would need a complete rewrite, but it is a very big work... For now : Either use a low VRAM theme, either increase VRAM preference. I usually use around 250 Mb and it work pretty fine with all themes.
"Hide when Running Game" : Thanks, I do crash too, it is a bug, due to the CPU use hack I added for WIN32 . It is now solved, I'll commit it next hour.
I really hope this is the last bug !!!
EDIT : Commited
-
@f-caruso Bad news, after loading about 20 or so games in a row, the graphics glitch comes back - regardless of what I set the vRam too, it must not be clearing the pre-allocated memory and creating a new one every time until it runs out, then my guess is it does some garbage collection and it works again until the very next game where it will glitch/flicker. As you never wrote those routines, I don't expect a fix, just be aware it will happen eventually when loading and exiting a set number of games.
BTW Hide when running will show it on the default display and not the display it was currently on (when using dual monitors like I do), I'll just work around this little things as they are not too bad compared to the load/crash bug you fixed.
-
@LiveFreeDead Hi. For the flickering, it was my mistake, I just committed a fix.
I don't understand the dual screen problem -> be more specific. -
@f-caruso
Dual Screen Test:
1.I run ES in a window (defaults to screen 1)
2.I drag it to the 2nd screen (Screen 2),so I can manage my rom folders on my main screen.
3.I run a game with the Hide when running enabled, which it hides fine. (Hidden on both screens)
4.When I exit my game and ES is shown again it is on (Screen 1) again (over the folders).The new Raspberry Pi 4b has dual screen, so I am sure there will be fixes in the pi code sooner or later, doubt it will be compatible with windows tho. I don't mind if this bug is fixed, I just don't hide it currently and the loading screen is under the retroarch etc (so no desktop shown anyway).
-
@LiveFreeDead said in Updated EmulationStation for Windows:
The new Raspberry Pi 4b has dual screen, so I am sure there will be fixes in the pi code sooner or later, doubt it will be compatible with windows tho. I don't mind if this bug is fixed, I just don't hide it currently and the loading screen is under the retroarch etc (so no desktop shown anyway).
Not a bug at all... But very easy thing to do... done in 3mn... I'll commit it later.
-
@f-caruso Hi,
Small question, does the padtokey config work with your non portable version ? I tried yesterday unsuccessfully.
-
@alberion said in Updated EmulationStation for Windows:
Is there a way to start ES on a second monitor and keep it open while working on the other monitor?
im trying to make ES to always open in my tv, while y work on my pc monitor, is that possible?
Might be worth adding this before you commit the re-open on last screen, easy to check a -screen0 or -screen1 etc in the switches?
-
@LiveFreeDead said in Updated EmulationStation for Windows:
Might be worth adding this before you commit the re-open on last screen, easy to check a -screen0 or -screen1 etc in the switches?
It's not the same thing - what u want is to remember/restore window location. What @alberion wants is to play on his TV which is his second monitor... If there was a way to open ES on a given monitor, there's no way to run games & emulators on the same screen -> they will always open on the main monitor ! There's no solution to his problem.
@dukeblooders padtokey is included in emulationportable.exe. It was written in a different language (c#) before I started to work on ES.
-
@f-caruso I have a weird new bug since fixing the flickering graphics bug (previous versions never had bug) . Now when I exit a game (For certain Emulators), the gamepad I used to launch the game with no longer functions in ES, I have to use a different controller or quit and run ES again. It doesn't do this every time, in fact it only happens every 5th time or so, on average. I have tried things to make it work again, but nothing works, it is like it ignores all input from said controller. I never had this bug before, so a fresh one ;)
-EDIT-
Weirdly enough it only seems to be non RetroArch Core Emulators, mostly using Cemu (WiiU) and PCSX2, maybe it's just a conflict with the external emulators grabbing control of the USB controllers or something, so I'll try and figure out whats going on more with this glitch.
-
So many Updates and its still not working for me. I start ES and its crashing after load. :(
-
@f-caruso Thanks for your reply
Could be a nice feature on the non-portable version (if it's possible). Unless I'm mistaken, you're doing a graceful stop now, you could add a "force" parameter which kills the process instead. Just an idea for what I read about Redream case.
-
@PittStone Are you using https://github.com/fabricecaruso/EmulationStation/releases/tag/continuous-master
He hasn't updated the release one for a week and that did have a show stopping bug still, so you have to use the auto compiled version instead until he releases it as a version update.
-EDIT-
If you are using the latest, move your .emulationstation\ES_* settings to a folder and only copy back the es_system.cfg back, then run it, making new controller and hopefully this will fix your issues with it, else manually set a different theme within the es_settings.cfg and copy that back, maybe it's got something incompatible in it.
-
@dukeblooders Not sure this is really ES role to handle a global Joy2Key feature... ES has to continue to be compiled & run under linux and a Pi. It is true for my version, too - I don't wanna make a Windows only version. So, I'm not gonna port this functionnality into ES code, and I'll let it where it is : in the other exe - it exists... it's cool, isn't it ?
@LiveFreeDead : I really can't reproduce ur controller problem. Plus, I did't even touch one line of code in the Input manager...
@alberion The latest version supports the command line "--monitor N" ( where N is the monitor index starting at 0 ). As I suspected some emulators open on the main screen even if I tell them to run on the second one. I have a workaround for retroarch, but you'll have to configure the other emulators manually to use the second monitor...
@PittStone Can't help without informations.. -
@LiveFreeDead Hello, yes, this works. I deleted the settings, systems and controller files and now "es" is loading. Thanks.
-
@PittStone Changed theme ?
-
@f-caruso Theme was changed automaticly. I changed back to "Magazine Madness" and this theme works too.
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.