con_maxfps or something. I set mine to 200, basically with it set to 100 and 200, 50 on the 100 set is the same as 100 on the 200 set. Really you'll notice no difference between say 60-70 fps and 100, since your monitor can really only do 75fps, which is usually the max so anything higher than that makes no difference. THat's why sometimes you can stop fps at say 75, even if it can do 200! A waste of computer to try to go 200, when 75 is enough.
I do have a fast computer and video card.
check ironchef Maximum PC rig of the month JUNE 2003.
set com_maxfps xx - Medal of Honor defaults to a maximum frame rate of 100 fps. If your video card is capable of higher frame rates, you can change this "cap" by changing the "xx" value to a higher setting. Some people use a maximum rate of 999. However, the actual fps (frames per second) varies depending on several factors in the individual maps. To If you don't want to use r_swapinterval, try capping your frame rate to smooth things out. Monitor the frame rate to find your maximum fps, then cap just below. For example, if you get 80 fps max, but most frequently 65 fps, then cap at 60-65. The objective is to maintain a relatively consistent fps to achieve smooth performance.
bobz
Last edited by bobzilla on Sun Jul 18, 2004 12:08 am, edited 1 time in total.
Hey that's a good tip, you should post that in the Tip of the Day thread (Mapping forum)
I've got it set to 200, I like that higher, it's more sensitive to small changes in the fps, like with a 100 you might not notice a 5-10fps increase/decrease but here its like 20 fps, I know that's not good for general play but for testing and tweaking peformance it's good for finding those small jumps that might really affect a lower end machine, but enough of my blabbering...