New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto Frameskip options are not working well #1482
Comments
I'm wondering if the device you're using is so low that auto options are just skipping non-stop, skipping every frame or enough to appear frozen? |
It looks like its working on audio buffers if the driver isint spot on there will be issues with games such as rygar. These issues went away with using the alsa driver only causes me issues when its set to pulse. The game timming does need updated to be fair but its more likely a driver issue. The same game casues issues on fbneo with with the pulse driver as well but is fine on alsa |
@schmurtzm did using the alsa driver solve your issue ? |
It also happens on Wii builds. |
Auto frameskip just automatically skips frames when there's slow downs, to help keep performance up. If the performance is so low (skipping many frames), then you'll still notice slowdowns. In other words skipping a frame here or there isn't noticable, but if you're skipping a lot of frames, you'll still notice. In fact, if you skip too many, you'll likely freeze the screen, with the last frame drawn. |
Hi, The Frameskip feature is great, it seems to work fine with fixed values and really improve the playability of demanding game on low CPU (I mainly use Mame 2003 Plus on Miyoo Mini, a little Linux handheld).
On last dev versions (b2b642c) the auto frameskip options are able to freeze the screen.
It happens on the Miyoo Mini as soon as I use one of three "auto" frameskip options.
I can also reproduce on PC (Windows) when I use
auto agressive
orauto max
(on PC it works with "auto" but slower than without frameskip).The auto frameskip options was already malfunctioning on old release (8f1498f) but it wasn't freezing.
Environnement :
Windows or Linux
core build : last current (b2b642c)
Retroarch 1.10.3 or later
Steps to reproduce :
Any plan to improve the auto frameskip options ? May be the "auto" options should be disabled for now ?
The text was updated successfully, but these errors were encountered: