NOTE: only talking about LOWERing (not raising) your fps through a console variable.
So what do you guys think?
Since there's no such way to pull low-fps tricks off, like the e3m5 windtunnel stop, why not use something which lets you to customize your fps and therefore help to make the trick...
Of course you can use high resolution, effected graphics or software rendering to get lower fps, but then you won't be able to optimize your run.
How 'bout resolution changing during recording, you may ask, but again, it's problematic. GLQuake doesn't even allow, WinQuake does, but it takes shitload of time, breaks the rhythm.
I'm interested in your opinions.
So what do you guys think?
Since there's no such way to pull low-fps tricks off, like the e3m5 windtunnel stop, why not use something which lets you to customize your fps and therefore help to make the trick...
Of course you can use high resolution, effected graphics or software rendering to get lower fps, but then you won't be able to optimize your run.
How 'bout resolution changing during recording, you may ask, but again, it's problematic. GLQuake doesn't even allow, WinQuake does, but it takes shitload of time, breaks the rhythm.
I'm interested in your opinions.
Thread title:
