EmulationStation Runs too fast after update

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!

pjft

Thank you for testing and confirming - at least one cause of it.

Just for the sake of having the right settings, edit it in the menu, as 80000 is like 1min 20 seconds, and I'm not sure it's a value it recognizes :) Set it to 1 min or so.

Thanks!

S_Pie

@pjft Okay, it's done!

Thank you for the help. Let me know if i should do anything else :)

pjft

@s_pie Just have fun :)

theWinterDojer

This was nice to follow. Glad you figured it out.

muehltime

@s_pie awesome

Hex

So now that the problem has been found it will be quite easy to fix it.

Hex

Sources have been updated.

Pi3 binary : https://www.dropbox.com/s/su7cpgvomy5edpx/emulationstation_3Aug_Pi3_ps_updates?dl=0