Frame skip interface issue.

[Nightquaker]

(05-10-2014 08:26 PM)[Unknown] Wrote:  If you have frameskip set to auto, the frameskip value is the maximal number of frames to skip.

If you set this to 0, it would mean "skip at most 0 frames." That is the same as frameskip off, so it makes no sense. That's why you're not allowed to configure it that way.

If you want a fixed frameskip at 1 frame, turn off auto. If you want to skip at most 1 frame, but never 2 frames and sometimes 0, turn on auto and set it to 1.

-[Unknown]

---

By the way, you are not the first person to ask this. What do you expect auto frameskip set to 0 to actually do? I don't even understand that concept. What do you think the 0 means?

I can understand you might not realize it's the maximum allowed frameskip, but what do you think it would indicate otherwise?

-[Unknown]

I probably haven't formatted my question properly, sorry about that.
What I meant is that there was an option to set frameskip to auto and set no fixed value at all, so the maximum frameskip was unlimited. It worked very well that way and I don't really understand why interface was changed to the way it is in newest versions.

Also: either Wipeout Pulse runs alot worse on 0.9.8 than on 0.9.6, or frameskip on 0.9.8 is broken. There is a severe framerate inconsistense while using various max frameskip values with auto frameskip enabled on 0.9.8 and no problems on version 0.9.6 with exactly same settings and frameskip set to auto.
I also want to mention that if I set frameskip to auto and set a max frames skipped to 1, emulator always skips 1 frame, even where it's not needed.
Maybe there's something wrong with automatic frameskip algorithm?

P.S. Please, don't move the thread to Wipeout Pulse section as it might actually be related to a frameskip and so, the issue with emulator itself.