Thanks for the info.....and how are you? Still letting all these r.a.s.
rookie drivers beat you in RASCAR? LOL....just teasing you, I am well aware
of your high-level racing skills!
Actually, the LOD changes you indicate were one of the first things I
changed. I learned that "trick" early on with F1-2001 (where the wheels of
the car in front of you would disappear about 100 feet in front of you, very
disconcerting to a real-world driver running the sim). I was actually quite
surprised to see that F1-2002 still had the same problems. But then, I
realized EA wants to sell games like everyone else in the "*** industry"
and those low LOD settings allows them to decrease their "minimum specs"
data which allows them to sell more copies of the game. Its an old ***
industry trick......they probably invented it!
And besides that, parts of cars disappearing is not what I refer to as
"flashing."
Flashing is what looks like "flash bulbs" going off on things like
buildings, crowd textures, trees....white lines on the track....and so
forth. I'm not sure why this happens in today's world of high-on-board ram
video cards (where the need for mipping textures is considerably less), but
in the older days it was because the D3D mipping algorhythms swapped the
texture from mip to mip level by page flipping them.....not blending them as
does OGL. That is why the flashing was always worse with D3D sims than Open
GL sims. Even Papyrus sims...when they went to the D3D graphics engine had
it pretty bad.....but for some reason its really bad in EA's stuff, and not
so bad in Papyrus's sims - these days at least.
I still think the overall best quality graphics (track presentation to the
driver from the***pit) is either GPL (with the later updated track
textures) or NASCAR 4.....both with the OGL renderer. N4 with OGL....was
the best of all NASCAR titles (graphics wise) from Papy! It's been downhill
ever since they switched to D3D.
What I have done to minimize the flashing in F1-2002 is the following (so
far):
a. Use 16-bit textures (its worse with 32-bit textures and the 32-bit adds
nothing IMHO, to the graphic quality otherwise - and the FPS suffers in
32-bit as well).
b. Use as high of a screen resolution as I can (based on my systems specs)
that allows 30 FPS + in race mode (usually I use the back of the pack in
race starts as a standard). For F1-2002....that would be 1280x1024x16.
c. Use Quin-FSAA.....adjusting the screen res down (per above) as needed
(actually with no FSAA, my system runs F1-2002 at 30+FPS at race starts very
well at 1600x1200x16). By the way, the FPS hit for Quin-FSAA is far less
than with 2x-FSAA.....like half as much. And, the picture quality with Quin
vs. 2x is three or four times better! At least, on my system it is.
d. Set the "mipmapLODBias" setting to "-0.5" from the default setting of
"-1.5"......and that has reduced the flashing about 20% - IMHO.
[\F1-2002\Save folder, look for the default.cfg file and the line under:
"LocalCam=Cockpit" for "MipMapLodBias=(-1.5) and change it to read (-0.5)]
That's all I've been able to find in F1-2002 to minimize the
flashing.....and all of this was learned in F1-2001 long ago! I was hoping
there were some better techniques found by all you guys.....for F1-2002!
That was the reason I asked the question above about "flashing."
Hope that makes sense?
Regards,
Tom