[ioquake3] changed com_maxfps behaviour
kamikaze at bsdforen.de
Fri Feb 18 16:07:39 PST 2011
After updating from r1803 to r1897 I recognize some changes.
The framerate doesn't go up to com_maxfps, e.g. if I set
com_maxfps 75 it normally stays at 60, only occasionally spiking.
If I set com_maxfps 125 it stays at 100 with occasional spikes.
The result is that a couple of jumps are no longer possible for
me when com_maxfps is set to 75. E.g. q3dm13 jump from yellow
armor to mega health.
With com_maxfps 125 I was able to make the jump, though I have
the impression that it got "trickier", i.e. more difficult to do it.
I suppose this isn't really a bug, but to me it means people running
older clients have an advantage. Does anyone else witness this?
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
More information about the ioquake3