Re: NASCAR 2002 OpenGL framerate fix

On Sat, 16 Feb 2002 13:53:39 -0500, "John Cauthen" <[email hidden]> wrote: >Now get this... he says that after making this change, his frame rates went >from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of >the blurriness that he was seeing before. I've heard others complain of >blurry textures in OpenGL, so this sounds like a wonder patch to me. It does indeed.. I'll try immediately and let you know if it works! Andre

On Sat, 16 Feb 2002 13:28:02 +0100, Andre Warringa <[email hidden]> wrote:

Quoted text (9 lines)

>On Sat, 16 Feb 2002 13:53:39 -0500, "John Cauthen" ><[email hidden]> wrote: > >>Now get this... he says that after making this change, his frame rates went >>from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of >>the blurriness that he was seeing before. I've heard others complain of >>blurry textures in OpenGL, so this sounds like a wonder patch to me. > >It does indeed.. I'll try immediately and let you know if it works!

Nope, doesn't work here :-/ With a-filtering on, the value was 2 in my ini file. I turned a-filtering off in the game and set the value in the ini to 0 Gfx in OpenGL still look extremely bad (washed out and VERY blocky) and I have the same fps (25fps at the back of the grid with 43 cars visible, between 25-50 during the race depending on how many cars are on the screen). This is with all details on max. Could you ask your friend which gfx card he has and what drivers? Your friends discovery certainly sounds promising, now we just have to find out why it works for him and not for me :) Andre

My rendOGL.ini doesn't have a line for that... Marc "John Cauthen" <[email hidden]> wrote in message news:a4kvc9$511r$[email hidden]... > I've just learned from a fellow league member that he has stumbled upon a > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002yet,

Quoted text (14 lines)

> but as soon as my copy arrives, I'm going to give this a try - it makes > sense based on what he sees in the default settings. > > Here's his fix: > > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering in the > options really doesn't work. His was set at "8" after it was supposedly > disabled. This manual edit of the .ini file did the trick! > > Now get this... he says that after making this change, his frame rates

went > from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of > the blurriness that he was seeing before. I've heard others complain of > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > You guys try it out and report back with your results, okay? This couldbe

Quoted text (10 lines)

> a real Godsend for this product if it's universally applicable. > > A great big thank you to Rick, of PSRL for discovering and sharing this > info! > > John Cauthen > Sport Planet > > >

Have you launched the sim in Open GL yet? Perhaps it gets put there after it sim is executed in Open GL. Don Burnette "Marc Collins" <[email hidden]> wrote in message news:3Eub8.34479$[email hidden]...

Quoted text (7 lines)

> My rendOGL.ini doesn't have a line for that... > > Marc > > "John Cauthen" <[email hidden]> wrote in message > news:a4kvc9$511r$[email hidden]... > > I've just learned from a fellow league member that he has stumbled upon

a

Quoted text (12 lines)

> > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002 > yet, > > but as soon as my copy arrives, I'm going to give this a try - it makes > > sense based on what he sees in the default settings. > > > > Here's his fix: > > > > Open the Ogl.Rend file. > > Adjust Antisitropic filterlevel to 0. > > Save changes > > > > He goes on to say that the option to shut off anisotropic filtering in

the > > options really doesn't work. His was set at "8" after it was supposedly > > disabled. This manual edit of the .ini file did the trick! > > > > Now get this... he says that after making this change, his frame rates > went > > from 25 fps, to 60-75 fps! As if that's not enough, he says it got ridof

Quoted text (17 lines)

> > the blurriness that he was seeing before. I've heard others complain of > > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > > > You guys try it out and report back with your results, okay? This could > be > > a real Godsend for this product if it's universally applicable. > > > > A great big thank you to Rick, of PSRL for discovering and sharing this > > info! > > > > John Cauthen > > Sport Planet > > > > > > > >

Just disable the darn thing, I have run several comparisons and I just can't see that much difference with it on versus off. So I just leave mine off, but running d3d. Don Burnette "Alan Bernardo" <[email hidden]> wrote in message news:vTub8.2709$[email hidden]... > This may be the case for some but not for all. My frame rates are just > fine, what I expected them to be. > > Still, the news is good for those who are having problems. In the readmeit > mentions this antistrophic number, saying that changing it to something > other than what your particular card can handle will have little effectand

Quoted text (7 lines)

> do no harm. > > Alanb > > "John Cauthen" <[email hidden]> wrote in message > news:a4kvc9$511r$[email hidden]... > > I've just learned from a fellow league member that he has stumbled upon

a

Quoted text (12 lines)

> > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002 > yet, > > but as soon as my copy arrives, I'm going to give this a try - it makes > > sense based on what he sees in the default settings. > > > > Here's his fix: > > > > Open the Ogl.Rend file. > > Adjust Antisitropic filterlevel to 0. > > Save changes > > > > He goes on to say that the option to shut off anisotropic filtering in

the > > options really doesn't work. His was set at "8" after it was supposedly > > disabled. This manual edit of the .ini file did the trick! > > > > Now get this... he says that after making this change, his frame rates > went > > from 25 fps, to 60-75 fps! As if that's not enough, he says it got ridof

Quoted text (17 lines)

> > the blurriness that he was seeing before. I've heard others complain of > > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > > > You guys try it out and report back with your results, okay? This could > be > > a real Godsend for this product if it's universally applicable. > > > > A great big thank you to Rick, of PSRL for discovering and sharing this > > info! > > > > John Cauthen > > Sport Planet > > > > > > > >

This may be the case for some but not for all. My frame rates are just fine, what I expected them to be. Still, the news is good for those who are having problems. In the readme it mentions this antistrophic number, saying that changing it to something other than what your particular card can handle will have little effect and do no harm. Alanb "John Cauthen" <[email hidden]> wrote in message news:a4kvc9$511r$[email hidden]... > I've just learned from a fellow league member that he has stumbled upon a > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002yet,

Quoted text (14 lines)

> but as soon as my copy arrives, I'm going to give this a try - it makes > sense based on what he sees in the default settings. > > Here's his fix: > > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering in the > options really doesn't work. His was set at "8" after it was supposedly > disabled. This manual edit of the .ini file did the trick! > > Now get this... he says that after making this change, his frame rates

went > from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of > the blurriness that he was seeing before. I've heard others complain of > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > You guys try it out and report back with your results, okay? This couldbe

Quoted text (10 lines)

> a real Godsend for this product if it's universally applicable. > > A great big thank you to Rick, of PSRL for discovering and sharing this > info! > > John Cauthen > Sport Planet > > >

It has been. Marc "Don Burnette" <[email hidden]> wrote in message news:iJub8.25340$[email hidden]...

Quoted text (14 lines)

> Have you launched the sim in Open GL yet? > Perhaps it gets put there after it sim is executed in Open GL. > > Don Burnette > > "Marc Collins" <[email hidden]> wrote in message > news:3Eub8.34479$[email hidden]... > > My rendOGL.ini doesn't have a line for that... > > > > Marc > > > > "John Cauthen" <[email hidden]> wrote in message > > news:a4kvc9$511r$[email hidden]... > > > I've just learned from a fellow league member that he has stumbled

upon > a > > > fix for the slow frame rates in N2002 using OpenGL. I don't haveN2002 > > yet, > > > but as soon as my copy arrives, I'm going to give this a try - itmakes

Quoted text (11 lines)

> > > sense based on what he sees in the default settings. > > > > > > Here's his fix: > > > > > > Open the Ogl.Rend file. > > > Adjust Antisitropic filterlevel to 0. > > > Save changes > > > > > > He goes on to say that the option to shut off anisotropic filtering in > the > > > options really doesn't work. His was set at "8" after it was

supposedly > > > disabled. This manual edit of the .ini file did the trick! > > > > > > Now get this... he says that after making this change, his frame rates > > went > > > from 25 fps, to 60-75 fps! As if that's not enough, he says it gotrid > of > > > the blurriness that he was seeing before. I've heard others complainof > > > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > > > > > You guys try it out and report back with your results, okay? Thiscould > > be > > > a real Godsend for this product if it's universally applicable. > > > > > > A great big thank you to Rick, of PSRL for discovering and sharingthis

Quoted text (11 lines)

> > > info! > > > > > > John Cauthen > > > Sport Planet > > > > > > > > > > > > > > >

I leave mind off and also do not see ny difference whats so ever. "Don Burnette" <[email hidden]> wrote in message news:sSub8.25383$[email hidden]... > Just disable the darn thing, I have run several comparisons and I justcan't > see that much difference with it on versus off. >

That line only gives you the max level of antisotropic your video card can achieve. It shouldn't affect the fps if you have already disabled the option in the game IMHO. I will nonetheless give it a try. John Cauthen wrote:

Quoted text (29 lines)

> > I've just learned from a fellow league member that he has stumbled upon a > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002 yet, > but as soon as my copy arrives, I'm going to give this a try - it makes > sense based on what he sees in the default settings. > > Here's his fix: > > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering in the > options really doesn't work. His was set at "8" after it was supposedly > disabled. This manual edit of the .ini file did the trick! > > Now get this... he says that after making this change, his frame rates went > from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of > the blurriness that he was seeing before. I've heard others complain of > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > You guys try it out and report back with your results, okay? This could be > a real Godsend for this product if it's universally applicable. > > A great big thank you to Rick, of PSRL for discovering and sharing this > info! > > John Cauthen > Sport Planet

-- Philippe "Philster" Sergerie

"John Cauthen" <[email hidden]> wrote in message news:a4kvc9$511r$[email hidden]... > I've just learned from a fellow league member that he has stumbled upon a > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002yet,

Quoted text (14 lines)

> but as soon as my copy arrives, I'm going to give this a try - it makes > sense based on what he sees in the default settings. > > Here's his fix: > > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering in the > options really doesn't work. His was set at "8" after it was supposedly > disabled. This manual edit of the .ini file did the trick! > > Now get this... he says that after making this change, his frame rates

went > from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of > the blurriness that he was seeing before. I've heard others complain of > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > You guys try it out and report back with your results, okay? This couldbe

Quoted text (7 lines)

> a real Godsend for this product if it's universally applicable. > > A great big thank you to Rick, of PSRL for discovering and sharing this > info! > > John Cauthen > Sport Planet

Here's my experience with this fix: first the specs: AMD 1.0 ghz 512 sdram 128 MB GF3 Ti200 at 200/450 Game: 1024x768, 16-bit, 4X FSAA, 26 in front, 9 behind. Mirror=Some, World View=Medium. Everything else maxed. I had Anistropic *enabled* (before this test), and I was getting 22-28 fps, 22 in the heaviest traffic. There was no such file as ogl.rend, so I assume you meant "rend_ogl.ini". Even after I unchecked Anistropic Filtering in the game, the ini file still showed it set to 8, just as you said. I changed that number to 0, and went back into the game with all other settings identical. New FPS: 33 min, 52 max. (and that's with 4x FSAA enabled!), this is almost a minimum 50% increase in FPS, and at max, it's nearly doubled. That's conclusive proof, in my book. Thanks for the post.

On Sat, 16 Feb 2002 10:18:43 -0600, "Jeff Jones" <[email hidden]> wrote: >There was no such file as ogl.rend, so I assume you meant "rend_ogl.ini". >Even after I unchecked Anistropic Filtering in the game, the ini file still >showed it set to 8, just as you said. I changed that number to 0, and went >back into the game with all other settings identical. This seems to be the difference.. when I uncheck A-filtering, it's set to 2 in the rend_ogl.ini file. Same happens with the d3d_ini file btw, also set to 2 when I disable A-filtering. And setting it to 0 makes no difference here.. >New FPS: 33 min, 52 max. (and that's with 4x FSAA enabled!), this is almost >a minimum 50% increase in FPS, and at max, it's nearly doubled. I want that too :-/ Andre >That's conclusive proof, in my book. Thanks for the post. > >

I've just learned from a fellow league member that he has stumbled upon a fix for the slow frame rates in N2002 using OpenGL. I don't have N2002 yet, but as soon as my copy arrives, I'm going to give this a try - it makes sense based on what he sees in the default settings. Here's his fix: Open the Ogl.Rend file. Adjust Antisitropic filterlevel to 0. Save changes He goes on to say that the option to shut off anisotropic filtering in the options really doesn't work. His was set at "8" after it was supposedly disabled. This manual edit of the .ini file did the trick! Now get this... he says that after making this change, his frame rates went from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of the blurriness that he was seeing before. I've heard others complain of blurry textures in OpenGL, so this sounds like a wonder patch to me. You guys try it out and report back with your results, okay? This could be a real Godsend for this product if it's universally applicable. A great big thank you to Rick, of PSRL for discovering and sharing this info! John Cauthen Sport Planet

Guys, as a compromise between gaining fps for sacrificing some away visual quality, try setting Aniso in rend_ogl.ini to 4. For some of you the preset may look poor because simply it's set too high. 8 will most likely look blurry on most graphics cards, except perhaps on GF4's - I don't know that yet. Setting the value to 4 (you may also want to try 2 or 3, I don't know for sure how the game translates these values but assume the valid values aRE 0, 2, 4, 8 for Aniso off, 16 tap, 32 tap and 64 tap), but if it does what I think it does, 8 will set Aniso to 64 tap, which is prone to look blurry on a GF3 or GF2. And it'll slow the fps down a lot. 32 tap (achieved probably by a value of 4) still visually improves the image considerably, but at a much lower framerate hit. Just a suggestion... Achim "John Cauthen" <[email hidden]> wrote in message news:a4kvc9$511r$[email hidden]... > I've just learned from a fellow league member that he has stumbled upon a > fix for the slow frame rates in N2002 using OpenGL. I don't have N2002yet,

Quoted text (14 lines)

> but as soon as my copy arrives, I'm going to give this a try - it makes > sense based on what he sees in the default settings. > > Here's his fix: > > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering in the > options really doesn't work. His was set at "8" after it was supposedly > disabled. This manual edit of the .ini file did the trick! > > Now get this... he says that after making this change, his frame rates

went > from 25 fps, to 60-75 fps! As if that's not enough, he says it got rid of > the blurriness that he was seeing before. I've heard others complain of > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > You guys try it out and report back with your results, okay? This couldbe

Quoted text (10 lines)

> a real Godsend for this product if it's universally applicable. > > A great big thank you to Rick, of PSRL for discovering and sharing this > info! > > John Cauthen > Sport Planet > > >

Err... that's exactly how it's supposed to work. The game detects the max level of anisotropy supported by the card and drivers and stores this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the graphics options screen simply controls whether the game uses that level of anisotropic filtering or not. - Eric "John Cauthen" <[email hidden]> wrote in message news:a4kvc9$511r$[email hidden]... > Open the Ogl.Rend file. > Adjust Antisitropic filterlevel to 0. > Save changes > > He goes on to say that the option to shut off anisotropic filtering inthe > options really doesn't work. His was set at "8" after it wassupposedly > disabled. This manual edit of the .ini file did the trick!

On Sat, 16 Feb 2002 16:06:01 -0500, "Eric Busch" <[email hidden]> wrote:

Quoted text (7 lines)

>Err... that's exactly how it's supposed to work. The game detects the >max level of anisotropy supported by the card and drivers and stores >this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the >graphics options screen simply controls whether the game uses that level >of anisotropic filtering or not. > >- Eric

So theoretically setting A-filtering to 0 should not make any difference in fps and texture quality? Andre

Make a difference compared to what? Setting the value in the INI to 0 should be the same an unchecking the checkbox on the options screen. The difference being that if you left the INI set to 0, checking the checkbox would then have no affect as you would be turning on 0 levels of anisotropy which would be the same as not using it in the first place. I guess it might be possible that there is(are) some driver(s) out there that is(are) able to override the game's checkbox setting and force anisotropic filtering to be enabled, but in that case a setting of 0 would disable it if you chose to leave it forced at the driver level. - Eric "Andre Warringa" <[email hidden]> wrote in message news:[email hidden]... > So theoretically setting A-filtering to 0 should not make any > difference in fps and texture quality?

"Eric Busch" <[email hidden]> wrote in message news:a4mhjq$ss5$[email hidden]...

Quoted text (7 lines)

> Err... that's exactly how it's supposed to work. The game detects the > max level of anisotropy supported by the card and drivers and stores > this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the > graphics options screen simply controls whether the game uses that level > of anisotropic filtering or not. > > - Eric

Except that doens't make any sense from my example. When I go edit the ini file to read '0', my framerates improve dramatically. If I set it to '8', they drop dramatically. I did this several times to verify. Besides that, I've never heard of an ini file setting that tells what a card /can/ do, unless it's something obvious like "MaxAnistropicCapable" or something like that - usually the setting is just a value for what it's currently set at.

Making sense or not, that's how it works in the game. The rend_d3d.ini and rend_ogl.ini simply store the card's capabilities as detected by the config program. If it makes you feel better you can pretend that it says "MaxAnisotropicLevel=n" instead of "AnisotropicLevel=n", but it's just a name (the line could read "Jimmie_Walker=n" and still work the same). However as I stated in a follow up post, I guess it possible for some drivers to be able to force anisotropic filtering to be enabled even if an application does not specifically ask for it to be enabled. If this is occurring, you should see no visual or performance difference when you uncheck and check the anisotropic filtering option, as the drivers are always forcing it to be enabled regardless of the checkbox state. In that case, setting the INI value to 0 would be the same as disabling anisotropic filtering in the card's display properties (assuming of course that the drivers give that option) and you should then see a resulting performance increase and loss of visual quality. - Eric "Jeff Jones" <[email hidden]> wrote in message news:a4mq61$ic4$[email hidden]... > Except that doens't make any sense from my example. When I go edit theini > file to read '0', my framerates improve dramatically. If I set it to'8', > they drop dramatically. I did this several times to verify. Besidesthat, > I've never heard of an ini file setting that tells what a card /can/do, > unless it's something obvious like "MaxAnistropicCapable" or somethinglike > that - usually the setting is just a value for what it's currently setat.

Eric, That would appear to be the case for me. If I run the N2K graphics card setup program and select OpenGL it creates the files rend_ogl.ini with Anisotropic=16. I assume this would be the max value then for my ATI8500 card. If I toggle Anisotropic filtering on or off in the game it makes no difference either in frame rate or quality. I change Anisotropic=0 in the rend_ogl.ini file my frame rates jump from 30 to 100 fps. I had originally set Anisotropic filtering to application preference in the ATI control panel settings. What I settled on as my best solution is the following. In the ATI control panel settings I set Anisotropic filtering on all the time with a value of 4 In the rend_ogl.ini file I also set the Anisotropic=4 With these settings I am getting very nice graphics quality and frame rates of 60 to 80. This is with 2xFSAA 1024x768x16. Dave B "Eric Busch" <[email hidden]> wrote in message news:a4mr2j$138$[email hidden]...

Quoted text (19 lines)

> Making sense or not, that's how it works in the game. The rend_d3d.ini > and rend_ogl.ini simply store the card's capabilities as detected by the > config program. If it makes you feel better you can pretend that it > says "MaxAnisotropicLevel=n" instead of "AnisotropicLevel=n", but it's > just a name (the line could read "Jimmie_Walker=n" and still work the > same). > > However as I stated in a follow up post, I guess it possible for some > drivers to be able to force anisotropic filtering to be enabled even if > an application does not specifically ask for it to be enabled. If this > is occurring, you should see no visual or performance difference when > you uncheck and check the anisotropic filtering option, as the drivers > are always forcing it to be enabled regardless of the checkbox state. > In that case, setting the INI value to 0 would be the same as disabling > anisotropic filtering in the card's display properties (assuming of > course that the drivers give that option) and you should then see a > resulting performance increase and loss of visual quality. > > - Eric

On Sat, 16 Feb 2002 18:47:30 -0500, "Eric Busch" <[email hidden]> wrote: >course that the drivers give that option) and you should then see a >resulting performance increase and loss of visual quality. Weird.. the original poster said his friend had an fps increase AND got rid of the blurry effect by setting a.filtering to 0.. Mysteries of the universe.. Oh well, it runs fine in D3D on my system, except for a weird shadow problem.. most of the times the shadows are ok, but now and then they become half see-through.. but I can live with that :) Andre

The line in the ini file is the amount of anisotropy that the game will use when you turn on anisotropy in the options. The value seen in the ini can be one of the following: 1 (none), 2, 4, 8, 16, etc (power of 2 sequence). By default the value the game comes up with is the max anisotropy a card supports (2 for a GF1 or GF2, 8 for a GF3, 16 for a Radeon), but then reduced a bit if you're running higher resolutions (1280 drops it to 4, 1600 drops it to 2). You can change this value as you see fit in the ini file to have whatever anisotropy level you want in the game. For what it's worth, 0 is as far as I know not a valid number to use. The power of 2 business is how DirectX and OpenGL deal with anisotropic settings. When the anisotropic check box is disabled, the game does NO anisotropic, so I this "trick" for speeding up the framerate sounds very strange to me :) But hey, if it seems to give good results, then that's cool. Jeff do you see these framerate changes when you switch the ini settings when you have the anisotropic setting unchecked? It would certainly do this if you still have the anisotropic box checked. Grant. Jeff Jones wrote:

Quoted text (17 lines)

> > "Eric Busch" <[email hidden]> wrote in message > news:a4mhjq$ss5$[email hidden]... > > Err... that's exactly how it's supposed to work. The game detects the > > max level of anisotropy supported by the card and drivers and stores > > this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the > > graphics options screen simply controls whether the game uses that level > > of anisotropic filtering or not. > > > > - Eric > > Except that doens't make any sense from my example. When I go edit the ini > file to read '0', my framerates improve dramatically. If I set it to '8', > they drop dramatically. I did this several times to verify. Besides that, > I've never heard of an ini file setting that tells what a card /can/ do, > unless it's something obvious like "MaxAnistropicCapable" or something like > that - usually the setting is just a value for what it's currently set at.

"Eric Busch" <[email hidden]> wrote in message news:a4mr2j$138$[email hidden]...

Quoted text (19 lines)

> Making sense or not, that's how it works in the game. The rend_d3d.ini > and rend_ogl.ini simply store the card's capabilities as detected by the > config program. If it makes you feel better you can pretend that it > says "MaxAnisotropicLevel=n" instead of "AnisotropicLevel=n", but it's > just a name (the line could read "Jimmie_Walker=n" and still work the > same). > > However as I stated in a follow up post, I guess it possible for some > drivers to be able to force anisotropic filtering to be enabled even if > an application does not specifically ask for it to be enabled. If this > is occurring, you should see no visual or performance difference when > you uncheck and check the anisotropic filtering option, as the drivers > are always forcing it to be enabled regardless of the checkbox state. > In that case, setting the INI value to 0 would be the same as disabling > anisotropic filtering in the card's display properties (assuming of > course that the drivers give that option) and you should then see a > resulting performance increase and loss of visual quality. > > - Eric

My drivers do not force anistropic filtering, they never have. No matter how many words you type, or how eloquently you explain it, if I set the ini file to 0, my framerates improve. If I set it to 8, they drop significantly. My Anistropic Filtering is unchecked in the game menu either way. I'm not trying to slam you, or call you a liar, I'm trying to tell you what is actually happening on my system. a 50% increase in framerate tends to have more of an impact on what I believe than a technical explanation of a guy in usenet. Again, nothing personal.

> Who makes your card Jeff? I want to compare makes and models on this. It > will be interesting to see what Paul has. > > John Cauthen Gainward GF3 Ti200, 128 MB version.

On Sat, 16 Feb 2002 23:22:19 -0600, "Jeff Jones" <[email hidden]> wrote:

Quoted text (8 lines)

> >> Who makes your card Jeff? I want to compare makes and models on this. It >> will be interesting to see what Paul has. >> >> John Cauthen > > >Gainward GF3 Ti200, 128 MB version.

GF2 GTS here on a P3 500, using the 12.90 drivers. Andre

Jeff Jones wrote:

Quoted text (32 lines)

> > "Eric Busch" <[email hidden]> wrote in message > news:a4mr2j$138$[email hidden]... > > Making sense or not, that's how it works in the game. The rend_d3d.ini > > and rend_ogl.ini simply store the card's capabilities as detected by the > > config program. If it makes you feel better you can pretend that it > > says "MaxAnisotropicLevel=n" instead of "AnisotropicLevel=n", but it's > > just a name (the line could read "Jimmie_Walker=n" and still work the > > same). > > > > However as I stated in a follow up post, I guess it possible for some > > drivers to be able to force anisotropic filtering to be enabled even if > > an application does not specifically ask for it to be enabled. If this > > is occurring, you should see no visual or performance difference when > > you uncheck and check the anisotropic filtering option, as the drivers > > are always forcing it to be enabled regardless of the checkbox state. > > In that case, setting the INI value to 0 would be the same as disabling > > anisotropic filtering in the card's display properties (assuming of > > course that the drivers give that option) and you should then see a > > resulting performance increase and loss of visual quality. > > > > - Eric > > My drivers do not force anistropic filtering, they never have. > > No matter how many words you type, or how eloquently you explain it, if I > set the ini file to 0, my framerates improve. If I set it to 8, they drop > significantly. My Anistropic Filtering is unchecked in the game menu either > way. I'm not trying to slam you, or call you a liar, I'm trying to tell you > what is actually happening on my system. a 50% increase in framerate tends > to have more of an impact on what I believe than a technical explanation of > a guy in usenet. Again, nothing personal.

Just FYI, Eric B. is not just "a guy in usenet" you know :-) Beers and cheers (uncle) Goy "The Pits" http://www.theuspits.com/ * Spam is for losers who can't get business any other way * "Spamkiller" http://www.spamkiller.com

Andre, Sorry for the delay in responding, it's been a very long day at work and I'm just now getting to see it. I'll ask what kind of graphics card he has and get back to you. From the other responses, I can see that this issue is going to be all over the ballpark. I'm working in the dark on it since I still don't have the game as yet. I'll ask though.... John Cauthen "Andre Warringa" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (7 lines)

> On Sat, 16 Feb 2002 13:28:02 +0100, Andre Warringa > <[email hidden]> wrote: > > >On Sat, 16 Feb 2002 13:53:39 -0500, "John Cauthen" > ><[email hidden]> wrote: > > > >>Now get this... he says that after making this change, his frame rates

went > >>from 25 fps, to 60-75 fps! As if that's not enough, he says it got ridof

Quoted text (22 lines)

> >>the blurriness that he was seeing before. I've heard others complain of > >>blurry textures in OpenGL, so this sounds like a wonder patch to me. > > > >It does indeed.. I'll try immediately and let you know if it works! > > Nope, doesn't work here :-/ > > > With a-filtering on, the value was 2 in my ini file. I turned > a-filtering off in the game and set the value in the ini to 0 > > Gfx in OpenGL still look extremely bad (washed out and VERY blocky) > and I have the same fps (25fps at the back of the grid with 43 cars > visible, between 25-50 during the race depending on how many cars are > on the screen). This is with all details on max. > > Could you ask your friend which gfx card he has and what drivers? > Your friends discovery certainly sounds promising, now we just have to > find out why it works for him and not for me :) > > > Andre

Hmmm.... this I can't answer. What card do you have? I'll post Paul's card make here as soon as I've heard back from him on it. John Cauthen "Marc Collins" <[email hidden]> wrote in message news:L0vb8.34501$[email hidden]...

Quoted text (36 lines)

> It has been. > > Marc > > "Don Burnette" <[email hidden]> wrote in message > news:iJub8.25340$[email hidden]... > > Have you launched the sim in Open GL yet? > > Perhaps it gets put there after it sim is executed in Open GL. > > > > Don Burnette > > > > "Marc Collins" <[email hidden]> wrote in message > > news:3Eub8.34479$[email hidden]... > > > My rendOGL.ini doesn't have a line for that... > > > > > > Marc > > > > > > "John Cauthen" <[email hidden]> wrote in message > > > news:a4kvc9$511r$[email hidden]... > > > > I've just learned from a fellow league member that he has stumbled > upon > > a > > > > fix for the slow frame rates in N2002 using OpenGL. I don't have > N2002 > > > yet, > > > > but as soon as my copy arrives, I'm going to give this a try - it > makes > > > > sense based on what he sees in the default settings. > > > > > > > > Here's his fix: > > > > > > > > Open the Ogl.Rend file. > > > > Adjust Antisitropic filterlevel to 0. > > > > Save changes > > > > > > > > He goes on to say that the option to shut off anisotropic filtering

in > > the > > > > options really doesn't work. His was set at "8" after it was > supposedly > > > > disabled. This manual edit of the .ini file did the trick! > > > > > > > > Now get this... he says that after making this change, his framerates > > > went > > > > from 25 fps, to 60-75 fps! As if that's not enough, he says it got > rid > > of > > > > the blurriness that he was seeing before. I've heard otherscomplain

Quoted text (23 lines)

> of > > > > blurry textures in OpenGL, so this sounds like a wonder patch to me. > > > > > > > > You guys try it out and report back with your results, okay? This > could > > > be > > > > a real Godsend for this product if it's universally applicable. > > > > > > > > A great big thank you to Rick, of PSRL for discovering and sharing > this > > > > info! > > > > > > > > John Cauthen > > > > Sport Planet > > > > > > > > > > > > > > > > > > > > > > > >

I had a feeling that people's experiences with this were going to be extremely varied. This is the type of thing that I'm sure gives developers absolute fits when trying to address the driver issues associate with PC games. I wish I had my own experience to relate to regarding this but I still don't have the game. Hopefully this will become a little more clear as time rolls on. John Cauthen "Trapper" <[email hidden]> wrote in message news:b8vb8.1785$[email hidden]...

Quoted text (11 lines)

> I leave mind off and also do not see ny difference whats so ever. > > > "Don Burnette" <[email hidden]> wrote in message > news:sSub8.25383$[email hidden]... > > Just disable the darn thing, I have run several comparisons and I just > can't > > see that much difference with it on versus off. > > > >

"Jeff Jones" <[email hidden]> wrote in message news:a4m0p0$d6b$[email hidden]...

Quoted text (11 lines)

> > Here's my experience with this fix: first the specs: > > AMD 1.0 ghz > 512 sdram > 128 MB GF3 Ti200 at 200/450 > > Game: 1024x768, 16-bit, 4X FSAA, 26 in front, 9 behind. Mirror=Some, World > View=Medium. Everything else maxed. > > I had Anistropic *enabled* (before this test), and I was getting 22-28

fps, > 22 in the heaviest traffic. > > There was no such file as ogl.rend, so I assume you meant "rend_ogl.ini". I just passed his message clip along here, very well could have been a typo or a misidentification of file name. I saw that he had anisotropic misspelled also, so that was probably a transfer error. > Even after I unchecked Anistropic Filtering in the game, the ini filestill > showed it set to 8, just as you said. I changed that number to 0, and went > back into the game with all other settings identical. > > New FPS: 33 min, 52 max. (and that's with 4x FSAA enabled!), this isalmost > a minimum 50% increase in FPS, and at max, it's nearly doubled. > > That's conclusive proof, in my book. Thanks for the post. So it worked as advertised once you got the right file name? Interesting... it seems to have no effect for some. Again, I'll have to find out what card he has and report back. I'm glad you had positive results from it. John Cauthen

"Andre Warringa" <[email hidden]> wrote in message news:[email hidden]... > On Sat, 16 Feb 2002 10:18:43 -0600, "Jeff Jones" <[email hidden]> > wrote: > > >There was no such file as ogl.rend, so I assume you meant "rend_ogl.ini". > >Even after I unchecked Anistropic Filtering in the game, the ini filestill > >showed it set to 8, just as you said. I changed that number to 0, andwent

Quoted text (8 lines)

> >back into the game with all other settings identical. > > This seems to be the difference.. when I uncheck A-filtering, it's set > to 2 in the rend_ogl.ini file. Same happens with the d3d_ini file btw, > also set to 2 when I disable A-filtering. > And setting it to 0 makes no difference here.. > > >New FPS: 33 min, 52 max. (and that's with 4x FSAA enabled!), this is

almost > >a minimum 50% increase in FPS, and at max, it's nearly doubled. > > I want that too :-/ Wow... this just further clouds the mystery around this! As I've told a few others, I'll find out what card Paul has and report back so we can compare notes. John Cauthen

"Eric Busch" <[email hidden]> wrote in message news:a4mhjq$ss5$[email hidden]... > Err... that's exactly how it's supposed to work. The game detects the > max level of anisotropy supported by the card and drivers and stores > this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the > graphics options screen simply controls whether the game uses that level > of anisotropic filtering or not. Apparently in Paul's case, it's still trying to use that level of filtering even though he has it unchecked. I'm just guessing, but those are the results he (and now a few others) have seen simply by changing from 8 to 0. John Cauthen

Quoted text (17 lines)

> > - Eric > > > "John Cauthen" <[email hidden]> wrote in message > news:a4kvc9$511r$[email hidden]... > > Open the Ogl.Rend file. > > Adjust Antisitropic filterlevel to 0. > > Save changes > > > > He goes on to say that the option to shut off anisotropic filtering in > the > > options really doesn't work. His was set at "8" after it was > supposedly > > disabled. This manual edit of the .ini file did the trick! > >

"Eric Busch" <[email hidden]> wrote in message news:a4mkuj$c1c$[email hidden]...

Quoted text (11 lines)

> Make a difference compared to what? Setting the value in the INI to 0 > should be the same an unchecking the checkbox on the options screen. > The difference being that if you left the INI set to 0, checking the > checkbox would then have no affect as you would be turning on 0 levels > of anisotropy which would be the same as not using it in the first > place. > > I guess it might be possible that there is(are) some driver(s) out there > that is(are) able to override the game's checkbox setting and force > anisotropic filtering to be enabled, but in that case a setting of 0 > would disable it if you chose to leave it forced at the driver level.

That might explain it Eric! It's obvious from the results thus far that this is handled differently by different cards. John Cauthen

"Jeff Jones" <[email hidden]> wrote in message news:a4mq61$ic4$[email hidden]...

Quoted text (16 lines)

> > "Eric Busch" <[email hidden]> wrote in message > news:a4mhjq$ss5$[email hidden]... > > Err... that's exactly how it's supposed to work. The game detects the > > max level of anisotropy supported by the card and drivers and stores > > this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the > > graphics options screen simply controls whether the game uses that level > > of anisotropic filtering or not. > > > > - Eric > > Except that doens't make any sense from my example. When I go edit the ini > file to read '0', my framerates improve dramatically. If I set it to '8', > they drop dramatically. I did this several times to verify. Besides that, > I've never heard of an ini file setting that tells what a card /can/ do, > unless it's something obvious like "MaxAnistropicCapable" or something

like > that - usually the setting is just a value for what it's currently set at. Who makes your card Jeff? I want to compare makes and models on this. It will be interesting to see what Paul has. John Cauthen

"Grant Reeve" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (20 lines)

> The line in the ini file is the amount of anisotropy that the game will > use when you turn on anisotropy in the options. The value seen in the > ini can be one of the following: 1 (none), 2, 4, 8, 16, etc (power of 2 > sequence). By default the value the game comes up with is the max > anisotropy a card supports (2 for a GF1 or GF2, 8 for a GF3, 16 for > a Radeon), but then reduced a bit if you're running higher resolutions > (1280 drops it to 4, 1600 drops it to 2). You can change this value > as you see fit in the ini file to have whatever anisotropy level you > want in the game. > For what it's worth, 0 is as far as I know not a valid number to use. > The power of 2 business is how DirectX and OpenGL deal with anisotropic > settings. > When the anisotropic check box is disabled, the game does NO > anisotropic, > so I this "trick" for speeding up the framerate sounds very strange to > me :) But hey, if it seems to give good results, then that's cool. > > Jeff do you see these framerate changes when you switch the ini settings > when you have the anisotropic setting unchecked? It would certainly do > this if you still have the anisotropic box checked.

Could it be that in some cases the checking of the anisotropic filtering in the options box isn't having an effect on the specific driver? I'm working in the dark on this still, but there seems to be cases where this option being unchecked has no affect on the performance. John Cauthen

Quoted text (11 lines)

> > Grant. > > Jeff Jones wrote: > > > > "Eric Busch" <[email hidden]> wrote in message > > news:a4mhjq$ss5$[email hidden]... > > > Err... that's exactly how it's supposed to work. The game detects the > > > max level of anisotropy supported by the card and drivers and stores > > > this value in the rend_d3d.ini and rend_ogl.ini. The checkbox on the > > > graphics options screen simply controls whether the game uses that

level > > > of anisotropic filtering or not. > > > > > > - Eric > > > > Except that doens't make any sense from my example. When I go edit theini > > file to read '0', my framerates improve dramatically. If I set it to'8', > > they drop dramatically. I did this several times to verify. Besidesthat, > > I've never heard of an ini file setting that tells what a card /can/ do, > > unless it's something obvious like "MaxAnistropicCapable" or somethinglike > > that - usually the setting is just a value for what it's currently setat.

The again, we all put our pants on one leg at time (OK - most of us do!). Todd "Goy Larsen" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (7 lines)

> > > Jeff Jones wrote: > > > > "Eric Busch" <[email hidden]> wrote in message > > news:a4mr2j$138$[email hidden]... > > > Making sense or not, that's how it works in the game. The

rend_d3d.ini > > > and rend_ogl.ini simply store the card's capabilities as detected bythe

Quoted text (7 lines)

> > > config program. If it makes you feel better you can pretend that it > > > says "MaxAnisotropicLevel=n" instead of "AnisotropicLevel=n", but it's > > > just a name (the line could read "Jimmie_Walker=n" and still work the > > > same). > > > > > > However as I stated in a follow up post, I guess it possible for some > > > drivers to be able to force anisotropic filtering to be enabled even

if > > > an application does not specifically ask for it to be enabled. Ifthis > > > is occurring, you should see no visual or performance difference when > > > you uncheck and check the anisotropic filtering option, as the drivers > > > are always forcing it to be enabled regardless of the checkbox state. > > > In that case, setting the INI value to 0 would be the same asdisabling

Quoted text (9 lines)

> > > anisotropic filtering in the card's display properties (assuming of > > > course that the drivers give that option) and you should then see a > > > resulting performance increase and loss of visual quality. > > > > > > - Eric > > > > My drivers do not force anistropic filtering, they never have. > > > > No matter how many words you type, or how eloquently you explain it, if

I > > set the ini file to 0, my framerates improve. If I set it to 8, theydrop > > significantly. My Anistropic Filtering is unchecked in the game menueither > > way. I'm not trying to slam you, or call you a liar, I'm trying to tellyou > > what is actually happening on my system. a 50% increase in frameratetends > > to have more of an impact on what I believe than a technical explanation of

Quoted text (12 lines)

> > a guy in usenet. Again, nothing personal. > > Just FYI, Eric B. is not just "a guy in usenet" you know :-) > > > Beers and cheers > (uncle) Goy > > "The Pits" http://www.theuspits.com/ > > * Spam is for losers who can't get business any other way * > "Spamkiller" http://www.spamkiller.com

The Geforce cards do have an anisotropic filtering option in the display properties, but the game shouldn't rely on it. When you have the INI set to 8, do you see a visual difference between checking and unchecking the option? If you restart and set the INI to 0, do you see a visual difference (comparing screenshots from the same place on the track would probably be the easiest way to check)? - Eric "Jeff Jones" <[email hidden]> wrote in message news:a4nec6$4jf$[email hidden]... > My drivers do not force anistropic filtering, they never have. > > No matter how many words you type, or how eloquently you explain it,if I > set the ini file to 0, my framerates improve. If I set it to 8, theydrop > significantly. My Anistropic Filtering is unchecked in the game menueither > way. I'm not trying to slam you, or call you a liar, I'm trying totell you > what is actually happening on my system. a 50% increase in frameratetends > to have more of an impact on what I believe than a technicalexplanation of > a guy in usenet. Again, nothing personal.

Todd Sorensen wrote: > > The again, we all put our pants on one leg at time (OK - most of us do!). So true, I have no idea just how good Eric is at this stuff, although I do seem to remember him having a bit of knowledge about the subject when I first stumbled upon this NG, which btw happened more years ago than I care to remember :-), but I would think that since he's working for Papyrus, he wouldn't be here just trying to impress us with his supposed knowledge ? :-) Beers and cheers (uncle) Goy http://www.theuspits.com http://www.teammirage.com "A woman is an occasional pleasure but a cigar is always a smoke" --Groucho Marx--

Yes I agree. I read every post I see from Eric because of his "inside" knowledge. The guy is a great asset to this newsgroup. Todd "Goy Larsen" <[email hidden]> wrote in message news:[email hidden]... > Todd Sorensen wrote: > > > > The again, we all put our pants on one leg at time (OK - most of usdo!).

Quoted text (17 lines)

> > So true, I have no idea just how good Eric is at this stuff, although I > do seem to remember him having a bit of knowledge about the subject when > I first stumbled upon this NG, which btw happened more years ago than I > care to remember :-), but I would think that since he's working for > Papyrus, he wouldn't be here just trying to impress us with his supposed > knowledge ? :-) > > > Beers and cheers > (uncle) Goy > > http://www.theuspits.com > http://www.teammirage.com > > "A woman is an occasional pleasure but a cigar is always a smoke" > --Groucho Marx--

"Todd Sorensen" <[email hidden]> wrote in message news:cLZb8.178355$[email hidden]... > Yes I agree. I read every post I see from Eric because of his "inside" > knowledge. The guy is a great asset to this newsgroup. > > Todd > The trouble is...you can't get any real DIRT outta him. Sure he is a wealth of technical knowledge, debugging our papyrus problems, but ask him what is next or why the price is higher and you won't even know he's around. :) I too remember him from the pre Papyrus days. I'm pretty sure he was a leader in getting the Rendition cards working and overclocking the systems, back before the web had any overclocking sites for reference. It's always a pleasure to have folks like Eric to turn to...Thanks for looking in on us now and then. dave henrie

I found out now that Rick's card is a Visiontek GeForce 3 Ti-200, fwiw. John Cauthen "Jeff Jones" <[email hidden]> wrote in message news:a4nem7$ogo$[email hidden]... > > > Who makes your card Jeff? I want to compare makes and models on this.It

Quoted text (10 lines)

> > will be interesting to see what Paul has. > > > > John Cauthen > > > Gainward GF3 Ti200, 128 MB version. > > > >

Thats because he's on the tech side, not the stupid marketing/sales side... -- Biz "Don't touch that please, your primitive intellect wouldn't understand alloys and compositions and,......things with molecular structures,....and the....." - Ash Dave Henrie <[email hidden]> wrote in message news:qF_b8.81482$Pz4.359058@rwcrnsc53... > > "Todd Sorensen" <[email hidden]> wrote in message > news:cLZb8.178355$[email hidden]... > > Yes I agree. I read every post I see from Eric because of his "inside" > > knowledge. The guy is a great asset to this newsgroup. > > > > Todd > > > The trouble is...you can't get any real DIRT outta him. Sure he is a > wealth of technical knowledge, debugging our papyrus problems, but ask him > what is next or why the price is higher and you won't even know he's around. > :) > I too remember him from the pre Papyrus days. I'm pretty sure he was a > leader in getting the Rendition cards working and overclocking the systems, > back before the web had any overclocking sites for reference. > It's always a pleasure to have folks like Eric to turn to...Thanks for > looking in on us now and then. > dave henrie > >

How do you know what frame rate youre getting? I have a 32meg Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

When you start driving or sitting in the pits push the F key, display will be in upper right corner. "twenty-four" <[email hidden]> wrote in message news:[email hidden]... > > How do you know what frame rate youre getting? I have a 32meg > Nvidia TNT2 M64 and things still seem pretty choppy. (thanx) >

Great!! Thats got it, thanks for the quick reply. Btw, Im only(?) getting a number from 9.-- to 10.-- . Is that normal or acceptable for my system? 333mhz celeron 512 megs 32 meg nvidia tnt2 papyrus 2002 season Thanks again .. On Sun, 03 Mar 2002 00:21:09 GMT, "Harry Mailahn" <[email hidden]> wrote:

Quoted text (7 lines)

>When you start driving or sitting in the pits push the F key, display will >be in upper right corner. >"twenty-four" <[email hidden]> wrote in message >news:[email hidden]... >> >> How do you know what frame rate youre getting? I have a 32meg >> Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

Dude get a Dell

"twenty-four" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (10 lines)

> > Great!! Thats got it, thanks for the quick reply. > > Btw, Im only(?) getting a number from 9.-- to 10.-- . Is that > normal or acceptable for my system? > > 333mhz celeron > 512 megs > 32 meg nvidia tnt2 > papyrus 2002 season

Well looking at your system, you have enough memory....Everything else is not good. You'll be needing a much faster cpu, a much faster vid card with a preferred 64 to 128 megs of onboard memory. You just don't have the horsepower to do more than private solo training laps... dave henrie

Quoted text (7 lines)

> > Thanks again .. > > On Sun, 03 Mar 2002 00:21:09 GMT, "Harry Mailahn" > <[email hidden]> wrote: > > >When you start driving or sitting in the pits push the F key, display

will > >be in upper right corner. > >"twenty-four" <[email hidden]> wrote in message > >news:[email hidden]... > >> > >> How do you know what frame rate youre getting? I have a 32meg > >> Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

twenty-four wrote:

Quoted text (9 lines)

> Great!! Thats got it, thanks for the quick reply. > > Btw, Im only(?) getting a number from 9.-- to 10.-- . Is that > normal or acceptable for my system? > > 333mhz celeron > 512 megs > 32 meg nvidia tnt2 > papyrus 2002 season

Unfortunately, with those specs you won't get much better. Good thing Tax Refund time is about here. :-) -- Fester "Is it that we need a nobrainer Linux desktop OS for people with no brains or should people do a little more reading and smarten up?" from alt.linux.mandrake NG

Well, I guess that explains it. I havent had a good reason to upgrade (other than the memory) before so this looks like my excuse. :) On Sun, 03 Mar 2002 06:09:51 GMT, "Dave Henrie" <[email hidden]> wrote: > Well looking at your system, you have enough memory....Everything else is >not good. You'll be needing a much faster cpu, a much faster vid card with >a preferred 64 to 128 megs of onboard memory. You just don't have the >horsepower to do more than private solo training laps... >dave henrie

Yup. Its the justification I needed to upgrade. Before it seemed like overkill. On Sun, 03 Mar 2002 13:29:05 GMT, Uncle Fester <[email hidden]> wrote: >Unfortunately, with those specs you won't get much better. Good thing >Tax Refund time is about here. :-)

"twenty-four" <[email hidden]> wrote in message news:[email hidden]... > > Yup. Its the justification I needed to upgrade. Before it > seemed like overkill. unfortunately, there is NO SUCH THING as overkill when you are talking about new sims....they EAT old equipment. dave henrie

Yup. I primarily use my computer for work (web development) and, other than needing more memory and win xp pro, it has been plenty of power. For both me and my computer, this game is by far the most demanding program Ive ever run. On Sun, 03 Mar 2002 17:19:39 GMT, "Dave Henrie" <[email hidden]> wrote: > unfortunately, there is NO SUCH THING as overkill when you are talking >about new sims....they EAT old equipment. >dave henrie

My game box is over twice the computer my work box is and I run CAD and 3d solid modeling software! MadDAWG

You're in serious trouble with that card... -Larry "twenty-four" <[email hidden]> wrote in message news:[email hidden]... > > How do you know what frame rate youre getting? I have a 32meg > Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

Oh, hit the "F" key while on the track to see your frame rates. -Larry "twenty-four" <[email hidden]> wrote in message news:[email hidden]... > > How do you know what frame rate youre getting? I have a 32meg > Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

I havent had any problems, its been a good card but then I dont push my system very hard and I do regret not going for the 64meg version. :( On Thu, 07 Mar 2002 21:29:15 GMT, "Larry \(The Other Larry\)" <[email hidden]> wrote:

Quoted text (9 lines)

>You're in serious trouble with that card... > >-Larry > >"twenty-four" <[email hidden]> wrote in message >news:[email hidden]... >> >> How do you know what frame rate youre getting? I have a 32meg >> Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)

After a lot of experimentation, my frugal butt has gotten the frame rate to peak at about 18. And thats running in an openGL 800x600 window on a 1024x768 desktop!! Ive tweaked out the detonator 27.70 driver using NVmax and reduced the field cars down to four. I tell ya, the performance and playability aint that bad and, as often as I play, it seems to be acceptable for now. On Thu, 07 Mar 2002 21:29:51 GMT, "Larry \(The Other Larry\)" <[email hidden]> wrote:

Quoted text (9 lines)

>Oh, hit the "F" key while on the track to see your frame rates. > >-Larry > >"twenty-four" <[email hidden]> wrote in message >news:[email hidden]... >> >> How do you know what frame rate youre getting? I have a 32meg >> Nvidia TNT2 M64 and things still seem pretty choppy. (thanx)