Mednafen Lynx runs too fast!

I have tried Roadblaster on the Handy core but has a lot of graphical glitches and so am force to use Mednafen lynx core which seems to have no graphically glitches but the games run way too fast. Is there a way to get them to run at their correct speed?

That usually indicates a vsync problem. If it’s only in that core, though, it may be something up with it, specifically. Either way, if you go to settings > frame throttle > Maximum Run Speed 1.0x, it should bring it back down to normal.

Looked in the frame throttle options and its already on 1.0x even tired turning on limit max run speed but that didnt help either

any ideas?

I have the same problem with mednafen-wonderswan. It runs at 75FPS for some reason, i never did work out why. Vsync is enabled, and frame throttle is set to 1.0. When i hit F1 and go into the menu the framerate goes back down to 60FPS, but then when i exit the menu and go back into the game it jumps back up to 75FPS.

For wonderswan, I believe it actually ran at 75 fps. Lynx could go up to that, but it apparently had a variable framerate. Perhaps it’s try to always run at that max 75 fps? Is it going faster than that for you, BlockABoots?

Its reporting 60fps, the audio isnt speeded up however its just the video/game. If you load up handy and run roadblaster that runs at the correct speed but has graphically glitches

So there is no fix for this then and is just a bug in the Mednafen lynx core, im guessing this core doesnt get much attention so probably wont be fixed??

Dunno. You could try using mednafen standalone and see if it exhibits the same behavior. If so, you could bring it up with them. If not, we could try to figure out what’s going on on our end.

Ok have tried Mednafen standalone and it has the same issue, ill try and reach out to them and see if they can look at it, odd thing is that the music is at the correct speed and handy which Mednafen is based runs at the correct speed but handy has gfx glitches on roadblasters

ah, good to know. Good luck on getting it resolved :slight_smile:

If/when they get it fixed up, you’ll have to wait for us to update our sources, which may take awhile, depending on how invasive the changes are.

Ok thanks. In the meantime is there anyway that I can limit the fps to a certain value so I can get this to run slightly slower in retroarch??

I guess you could try messing with the slow motion options but that’s probably not going to be adequate to do what you want.

I guess that would slow the audio down also?? So there not an option in Retroarch where you can set specific fps or refresh rate?

No, it’s not something you should ever do, really.

Ok bit of an update on this, i finally got a reply on a thread i created on the Mednafen forums (about 2 months later). I asked the following question…

"[b]I have been using Mednafen Lynx in retroarch and noticed that Roadblaster seemed to be running too fast (just video not audio) from what i remembered it play like on my lynx console, i tried the Handy emulator and sure enough that ran at the correct speed but handy has gfx glitches on Roadblasters where Mednafen Lynx does not. I have tried just yout standalone Mednafen emulator and Roadblasters still runs too fast so its not an issue with just the RetroArch build

Can you team look into this and possibly fix it please.[/b]"

and the replay i got back…

"[b]As retroarch and mednafen derive from the original handy source code base, this seems to be a bit unlikely. Nevertheless, there have been some small changes on the code. But I would suspect that the reason is a different one. Handy is not cycle accurate in several places, but especially at the sprite engine. Handy has a possibility to limit the execution speed. Seems this has been removed for retroarch/mednafen (well its in the GUI/ windows-dependent GUI code).

The cycle accurate thing will most likely never be fixed, it is just too much work to reverse engineer the asic in detail.

The speed limitation has to be outside of the handy code part. But it should be possible to add that.[/b]"