EmulationStation Runs too fast after update

S_Pie

So i should do a basic install from the retropie setup. Would that do the trick and write over the currently installed ES?
And will it remove all my roms?

Aryetis

@s_pie said in EmulationStation Runs too fast after update:

write over the currently installed ES?
And will it remove all my roms?

Yes you can try to uninstall then reinstall EmulationStation from the retropie_setup script. It should not affect your roms, savestates, and scrapped description/picture, etc.

BuZz

https://github.com/RetroPie/EmulationStation/issues/200

Need as much information as your set-up as possible please so we can reproduce it (including es configs as detailed in my reply on the issue tracker)

pjft

Just to confirm, if you go to "Other Settings", disable "Power Savings" and restart ES, does it change anything?

S_Pie

@aryetis Thanks for your reply :)

All right. I'll start by removing ES from the core-packages, and then install it from binary afterwards. Am i correct ?

pjft

@s_pie You don't need to remove it. Just reinstall it. I can't promise you won't lose any configurations from ES.

But if you can go to the bug @BuZz just posted, maybe you can help us track this down - and in the meantime we can provide a working build for the time being.

S_Pie

@buzz My setup is as follow:

RP 3
Retropie 4.2
EmulationStation v.2.5.1RP
USB wireless Keyboard (with dongle)
PS3 Controller

Do you need anything else? :)

BuZz

@s_pie /opt/retropie/configs/all/emulationstation/es_settings.cfg

also the output of uname -a

S_Pie

@pjft I'll do my best. But please bear in my mind that this is completely new to me :)

The power saving was enabled, and i could by pure luck get it disabled. It is very difficult for me to hit the buttons because of the speed of the scrolling.

BuZz

I am currently rebuilding the premade binaries to v2.4.1 again - source install will still install the latest.

S_Pie

@buzz All right.. This is a shot in the dark, but is this the info you need?

<?xml version="1.0"?>
<bool name="BackgroundJoystickInput" value="false" />
<bool name="CaptionsCompatibility" value="true" />
<bool name="DrawFramerate" value="false" />
<bool name="EnableSounds" value="true" />
<bool name="MoveCarousel" value="true" />
<bool name="ParseGamelistOnly" value="false" />
<bool name="QuickSystemSelect" value="true" />
<bool name="SaveGamelistsOnExit" value="true" />
<bool name="ScrapeRatings" value="true" />
<bool name="ScreenSaverControls" value="true" />
<bool name="ScreenSaverOmxPlayer" value="true" />
<bool name="ShowHelpPrompts" value="true" />
<bool name="ShowHiddenFiles" value="false" />
<bool name="StretchVideoOnScreenSaver" value="false" />
<bool name="VideoAudio" value="true" />
<bool name="VideoOmxPlayer" value="false" />
<int name="MaxVRAM" value="100" />
<int name="ScraperResizeHeight" value="0" />
<int name="ScraperResizeWidth" value="400" />
<int name="ScreenSaverTime" value="0" />
<string name="AudioDevice" value="PCM" />
<string name="CollectionSystemsAuto" value="" />
<string name="GamelistViewStyle" value="automatic" />
<string name="OMXAudioDev" value="both" />
<string name="PowerSaverMode" value="default" />
<string name="Scraper" value="TheGamesDB" />
<string name="ScreenSaverBehavior" value="dim" />
<string name="ScreenSaverGameInfo" value="never" />
<string name="ThemeSet" value="zoid" />
<string name="TransitionStyle" value="fade" />

Does that mean i should do a new full update from the retropie setup?

pjft

@s_pie That sounds about right. If you can edit that file and mark "PowerSaverMode" to "disabled" (if you can't edit it in the menu), and then start ES, see if that helps.

S_Pie

@pjft All right. By accident, the VRAM limit got set to 0Mb. Would that have a consequence for restarting?

pjft

@s_pie Yes :) Make it 100 or 80. You can likely exit ES and edit the file before restarting.

pjft

@s_pie Actually, if you have the chance, can you edit

to not be zero, but be, say, 60000 ?

S_Pie

@pjft So, i disabled the powersaving, and set the VRAM Limit to 100. Rebooted the Pie, and the problem still stands.
If by anything, the menu seems to go a bit faster now - did not think it could be possible :)

I will try set the ScreenSaverTime now and reboot.

pjft

@s_pie We have people who complain things are too slow, others that things are too fast...

We can't please everyone :P

Just joking, of course.

We'll get to the bottom of this.

Thanks for your patience.

@BuZz - let me know if you want me to put up a build for 2.4.1 on GitHub or something in the interim.

S_Pie

@pjft I'm the one thanking for the help, i'm just sitting in little Denmark and try to figure this out :)

It's not easy to please everyone, but you are doing af damn fine job !

okay, i rebooted again and ........... it works ?! The menu seems to be back to normal - no idea why ?

So what now ?

pjft

@s_pie Ok.

So that's important.

The "ScreenSaverTime" set to zero was suspicious, especially as in the new code for Power Savings we are doing something with that value.

Thank you.

If you want to be a bit more of a tester, try going to the menu, and change screensaver time to 0 seconds, exit the menu, and see if it fails again. Then set it back to 60000 - or anything more to the right. See if it works.

Thanks!

S_Pie

@pjft When set back to 0, it acts up really fast again. When changed to 80000, it becomes normal.

So it's definitely something with that setting!