Thanks for the comments, guys. I agree that the write-up does end a bit abruptly, biostud. I'd still like to add a bit more to it with regard to the wide range of framerates that you see in this game. I just need to learn a bit more about how to make use of a spreadsheet program for this. (See
this previous thread for information on this issue.)
I'm sure, when (if) I do get another stick of 1GB memory, that I'll see how that looks running the timedemo and performance log, blurredvision. So far, this has bee a fairly expensive game to play. Besides the cost of the gamw, itself, it required me to ditch my Ti4200 and get a new video, and then it required me to buy a GB of RAM. I think that I'll just enjoy using what I've got for at least awhile.
😉
Too bad that the Nvidia Peformance Graph is no longer bundled into their drivers, like it originally was. It sure would be interesting to be able to see what is happening when the single player game drops into the very low framerates. In particular, the question in my mind is whether the video card is simply unable to keep up (e.g., too many triangles) or whether we are seeing a problem with the driver that is leaving the GPU twiddling its thumbs with nothing else it can do for the moment.
If you aren't familiar with the Nvidia Performance Graph, I took a look at it when I did
an analysis of Desert Combat's performance, using drivers that had the Performance Graph incorporated into them. These days, Performance Graph is only available as a standalone program from Nvidia that will only work with a game program that has a couple of lines of code in it calling for Peformance Graph. This bit of code would be removed before the final release of the game; so, unless you are a game developer with access to the source code, Performance Graph is of no use to most folks, now.
Space
