First post, by Setsunaaa
For the fun of it I did video recordings with "slightly" different settings:
cycles=500000
cycleup=250000
cycledown=250000
Right before I start the video recording I boost the cpucycles to two million or three million (or more, but more was yet useless) and then do the thing I want to record.
What it gives??
During the recording the game or demo (like the gcube 64K demo in 800x600 32Bit) runs unbelievable slow, for games this gives you godlike reaction times during recording.
But the video you play back then is smooooooth, and if you know how the original program runs on a 2 GHz machine under real DOS you can fake it here pretending a 10 GHz machine *g* that way.
Some recordings should be done over night : ).
The bad side: You could record (as example) a doom demo with your godlike reaction time, and no one could prove it you cheated. But many will believe that it is too good to be true : ).
Set