You don't like core=auto and cycles=auto?

I do not like the core=auto and cycle=auto. I like to choose my own cycles and core.

You're the boss 😀

Dynamic cycles have their use and their disadvantages. Some games like Broken Sword won't work well with auto cycles (weird animations) but also, a large amount of games show "glitches" in the sound. This is probably caused by cycles trying to "catch up".

Cycles are not directly linked to speed - some parts of a game will stress your CPU at 20 000 cycles while others will easily allow for 100 000 or more. You can easily notice this by sound breaking up. So, say you're playing a game and are at a part in the game which requires far less power and allows for many cycles - like, say, a 2D screen. Suddenly you move to a 3D part and auto cycles quickly tries to drop the cycles to 50 000. This is when your sound will glitch. Some games have this constantly when a sound plays too (like Beneath A Steel Sky) so it's better then to stick to fixed cycles.

or use undocumented cycle limit 😉

abyss wrote:

I use the frameskips a lot.

With the graphics and sclaer optimizations, frameskip isn't that important anymore...

or use undocumented cycle limit

That's not undocumented 😉

So far the only game I've tried that doesn't seem to like the auto cycles is "F-15 Strike Eagle III". I use this auto options with the rest of my games and I like it a lot.

Good job with 0.7 ! Games like Duke3D and Quake works like ten times faster and steadier.