That feature is originally from gulikoza's experimental patch and already included in bulids of mine (when turning on 'show details'), gulikoza's, and UBER BUILD's.
http://www.dosbox.com/wiki/SVN_Builds

I don't think that displaying fluctuating real cycles is important for playing games.

ykhwong wrote:

That feature is originally from gulikoza's experimental patch and already included in bulids of mine (when turning on 'show details'), gulikoza's, and UBER BUILD's.
http://www.dosbox.com/wiki/SVN_Builds

I don't think that displaying fluctuating real cycles is important for playing games.

Thank you! I didn't expect it to be available already, and am glad to hear that it is. I agree that fluctuating numbers aren't useful, but it might be useful to have a general idea of whether the program is running at 10,000 or 20,000, etc., for us in making a conf for distribution. Thank you again.

for us in making a conf for distribution.

Which is pretty useless because either =max/=auto works or, if you derive a fixed
cycles count from that, your "distribution" will suck on lower powered systems
that would run fine with =max/=auto.

I guess I vaguely knew that, but was curious about what the numbers were anyway. So, yes, the information is useless, but it might be interesting (no more than that) to know...

They usually fluctuate far too much to be of interest when comparing against fixed cycles.

OK - You might want to rename this thread "Don't waste your time counting cycles."

Well you can count or watch the cycles as long as you want 😉
Just be careful when trying to derive fixed cycles from that, you're usually far
better off checking if the game works with a low fixed cycles count or auto cycles
(probably cycles=max 80% or cycles=max limit 40000 or whatever works good).

I made a patch for this some time ago; I don't know if still works with current svn, though.