Hey, all.
Thanks for the replies to my wheel questions. I ended up getting a Logitech
Formula Force GP (the *only* FFB wheel that works with XP, apparently). I
love it. Now that I have the weekend off, I can forget about sleep and
worry about getting my line at Atlanta perfect! ;-)
I'm running (as stated in my last posts about D3D vs. OpenGL) N4 in OpenGL,
at 800x600x32, on a 1GHz Athlon with a GeForce2 MX. The mipmapping seems to
be a little blurry, as are some of the textures. It was *really* bad until
I adjusted the "texture quality" line in one of the N4 INI files to 100%
instead of auto. It's *okay* now, but I want to see what I can do about
increasing the LOD (level of detail), mip distance, and polygon drop-down
distance.
Non-graphics-card geeks need not proceed... :-)
I've downloaded the NVIDIA 22.80 drivers and NVmax for Windows XP. I'm a
little confused as to what, and where, to set these properties I'd like to
change. I've enabled 4X AGP and all the hardware goodies that need to be
enabled anyway. I've run the N4 3D setup program fresh after rebooting, to
give the maximum results. But I am a total OpenGL n00b. I need someone to
hold my hand and take me through any graphic options, either in N4's INIs or
in NVmax, that could result in higher image quality. My framerates are
great right now, especially with 42 cars, so a performace hit is not that
big a deal.
Thanks!
- John P. Wilson
- [email hidden]
Hi, I was a D3D only guy in N4 because whenever I switched to OGL mode it
looked like crap. I got rivatuner which is a util that allows the graphics
settings to be tweaked in D3D and OGL modes. Enable anisotropy, Level 2 is
a good setting, and turn off v-sync. That'll help a lot. You should have
the same options in NVMax
"John P. Wilson" <[email hidden]> wrote in message
news:bQBJ7.46019$[email hidden]...
> Hey, all.
>
> Thanks for the replies to my wheel questions. I ended up getting aLogitech
> Formula Force GP (the *only* FFB wheel that works with XP, apparently). I
> love it. Now that I have the weekend off, I can forget about sleep and
> worry about getting my line at Atlanta perfect! ;-)
>
> I'm running (as stated in my last posts about D3D vs. OpenGL) N4 inOpenGL,
> at 800x600x32, on a 1GHz Athlon with a GeForce2 MX. The mipmapping seemsto
> be a little blurry, as are some of the textures. It was *really* baduntil
to
> give the maximum results. But I am a total OpenGL n00b. I need someoneto
> hold my hand and take me through any graphic options, either in N4's INIsor
Quoted text (11 lines)
> I adjusted the "texture quality" line in one of the N4 INI files to 100% > instead of auto. It's *okay* now, but I want to see what I can do about > increasing the LOD (level of detail), mip distance, and polygon drop-down > distance. > > Non-graphics-card geeks need not proceed... :-) > > I've downloaded the NVIDIA 22.80 drivers and NVmax for Windows XP. I'm a > little confused as to what, and where, to set these properties I'd like to > change. I've enabled 4X AGP and all the hardware goodies that need to be > enabled anyway. I've run the N4 3D setup program fresh after rebooting,Quoted text (10 lines)
> in NVmax, that could result in higher image quality. My framerates are > great right now, especially with 42 cars, so a performace hit is not that > big a deal. > > Thanks! > > - John P. Wilson > - [email hidden] > >The best thing you can do to your current setup is to come back down to
earth and run 16 bit color. The difference onscreen is hardly noticable but
the performance it frees up is amazing. I have a GF3 (and have used a
GF2MX400 prior) and I have to say that even with my GF3 I continue to run
16bit color. That freed up enough horsepower to tweak everything else upward
and also run FSAA 4x.
John P. Wilson <[email hidden]> wrote in message
news:bQBJ7.46019$[email hidden]...
> Hey, all.
>
> Thanks for the replies to my wheel questions. I ended up getting aLogitech
> Formula Force GP (the *only* FFB wheel that works with XP, apparently). I
> love it. Now that I have the weekend off, I can forget about sleep and
> worry about getting my line at Atlanta perfect! ;-)
>
> I'm running (as stated in my last posts about D3D vs. OpenGL) N4 inOpenGL,
> at 800x600x32, on a 1GHz Athlon with a GeForce2 MX. The mipmapping seemsto
> be a little blurry, as are some of the textures. It was *really* baduntil
to
> give the maximum results. But I am a total OpenGL n00b. I need someoneto
> hold my hand and take me through any graphic options, either in N4's INIsor
Quoted text (11 lines)
> I adjusted the "texture quality" line in one of the N4 INI files to 100% > instead of auto. It's *okay* now, but I want to see what I can do about > increasing the LOD (level of detail), mip distance, and polygon drop-down > distance. > > Non-graphics-card geeks need not proceed... :-) > > I've downloaded the NVIDIA 22.80 drivers and NVmax for Windows XP. I'm a > little confused as to what, and where, to set these properties I'd like to > change. I've enabled 4X AGP and all the hardware goodies that need to be > enabled anyway. I've run the N4 3D setup program fresh after rebooting,Quoted text (10 lines)
> in NVmax, that could result in higher image quality. My framerates are > great right now, especially with 42 cars, so a performace hit is not that > big a deal. > > Thanks! > > - John P. Wilson > - [email hidden] > >Hi Simracer,
has anyone checked whether the N4 graphics (the mips) are 32bit at all, or
whether they are 16bit?
Achim
"SimRacer" <[email hidden]> wrote in message
news:n2cK7.16825$[email hidden]...
> The best thing you can do to your current setup is to come back down to
> earth and run 16 bit color.
"Back down to earth?" LOL. It's a proven fact that most NVIDIA cards are
now optimized for 32-bit color - that's why there is little or no
performance loss. And it looks a hell of a lot better. Why would I
*decrease* my color depth if I wanted *more* image quality?!
> The difference onscreen is hardly noticable but the performance it frees
> up is amazing.
I'm sorry, but did you *read* my post? I'm not looking for performance; I'm
looking for image quality. And the difference is *very noticeable*,
especially in the cockpit.
> That freed up enough horsepower to tweak everything else upward
> and also run FSAA 4x.
Ha. Why not go back to 32-bit color and increase your resolution? FSAA was
developed exclusively for low-resolution use. That's why it's so
performace-hogging; it uses the "extra" horsepower your card has (since
you're running in a lower res) for its smoothing effects. And 4X FSAA?!
*I'm* the one who should be telling *you* to come back down to earth....
- John P. Wilson
- [email hidden]
If the textures aren't 32 bit than you do need to come back down to earth.
The best way to increase picture quality is to increase resolution, and
since thats what you wanted, its the best way to go, nVidia's implementation
of FSAA is really poor compared to what the voodoo's used to offer from what
I understand as well.
--
Biz
"Don't touch that please, your primitive intellect wouldn't understand
alloys and compositions and,......things with molecular structures,....and
the....." - Ash
John P. Wilson <[email hidden]> wrote in message
news:nljK7.22598$[email hidden]...
> "SimRacer" <[email hidden]> wrote in message
> news:n2cK7.16825$[email hidden]...
> > The best thing you can do to your current setup is to come back down to
> > earth and run 16 bit color.
>
> "Back down to earth?" LOL. It's a proven fact that most NVIDIA cards are
> now optimized for 32-bit color - that's why there is little or no
> performance loss. And it looks a hell of a lot better. Why would I
> *decrease* my color depth if I wanted *more* image quality?!
>
> > The difference onscreen is hardly noticable but the performance it frees
> > up is amazing.
>
> I'm sorry, but did you *read* my post? I'm not looking for performance;
I'm
> looking for image quality. And the difference is *very noticeable*,
> especially in the cockpit.
>
> > That freed up enough horsepower to tweak everything else upward
> > and also run FSAA 4x.
>
> Ha. Why not go back to 32-bit color and increase your resolution? FSAA
was
> developed exclusively for low-resolution use. That's why it's so
> performace-hogging; it uses the "extra" horsepower your card has (since
> you're running in a lower res) for its smoothing effects. And 4X FSAA?!
> *I'm* the one who should be telling *you* to come back down to earth....
>
> - John P. Wilson
> - [email hidden]
>
>
