by Andypandy » Wed May 21, 2003 8:25 am
Hmmm, FMS run's real nice on my computer, which uses a PII 450 MHZ processor and a Geforce 2MX 32MB card (running Win 2K OS).
Very recently upgraded to a freebee Geforce 2 Ti 64MB card- slightly better quality textures and frame rate, but now my processor is bottle necking the performance, methinks.
With the MX card I was running 1024x760 resolution with 16 bit colour, and getting between 25-70 FPS with FSAA and Anisotropic filtering switched off (they don't make that much difference to picture quality at hi-res), also depending on the model, scenery and whether the model was near the ground or up in the sky- you get better FPS in the sky, less number crunching I guess.
Running 32 bit graphics was out of the question frame rate wise, and to be honest, I can't see any difference in quality that warrants the performance hit.
With the Geforce 2 Ti card I can run at 1280x1024 with 2 x FSAA swithced in without any problems, I would hazard a guess that this is more owing to the Ti card having an extra 32MB of memory and also much faster memory clock rate and processor core clock.
Basing performance on my system, your machine should be more than upto the job.
Make sure you have any other applications closed down before loading FMS, also check your start up menu to see if anything is hogging system resources (CD players etc.)
I find FMS is very forgiving in the latter regard, but some programs may interfere with the software.
Also make sure you have the latest detonator driver for your Geforce card (available from the Nvidia website, free download), as these can make a big difference.
Switch off the FSAA and Anisotropic filtering in the driver software control panel, also switch off texture sharpening, and sett intellisample to 'performance'disable V-sync in direct 3D
If none of the above works, try turning off the sound in FMS, as this may have an impact on performance (I find it makes no difference on my machine, however) and make sure you set the program to full screen, as opposed to running in a window, as that can eat quite a few FPS.
Andy