rec.autos.simulators

> Here is the solution to making enabling FSAA with GPL, as told to me by
> snoopy80 on rage3d.com:

> "Hey, great news. Just installed the 4.1 cats, and to my disappointment, GPL
> was still broken. So I ***** in the forum a bit, and Anemotion posts the
> solution to our problem. It's on page 5 of the 4.1 Catalyst thread. In
> short, in your Core.ini file, change
> DirectMirrorRendering from 1 to 0. It fixed the problem for me. Now we can
> enjoy GPL while being able to use new drivers. Hurra!

> Adam"

> I have one caveat to add to this:  When I tried some back-of-the-pack starts
> with Cat4.1, my car and much of the lower half of the screen was gone, and
> only reappeared after the race got under way.  I despaired, but after trying
> various things, I reduced the Graphics Detail Bias in GPL just slightly from
> max detail.  This seems to fix the problem.

> Now on my 2.4ghz AthlonXP + 9700pro I'm seeing 36fps back-of-the-pack starts
> at 1280x1024 with 6xFSAA 16xAA with all the detail sliders maxed, except as
> noted above!   Yay!!

> rms

> "Hey, great news. Just installed the 4.1 cats, and to my disappointment, GPL
> was still broken. So I ***** in the forum a bit, and Anemotion posts the
> solution to our problem. It's on page 5 of the 4.1 Catalyst thread. In
> short, in your Core.ini file, change
> DirectMirrorRendering from 1 to 0. It fixed the problem for me. Now we can
> enjoy GPL while being able to use new drivers. Hurra!

> Adam"

> I have one caveat to add to this:  When I tried some back-of-the-pack starts
> with Cat4.1, my car and much of the lower half of the screen was gone, and
> only reappeared after the race got under way.  I despaired, but after trying
> various things, I reduced the Graphics Detail Bias in GPL just slightly from
> max detail.  This seems to fix the problem.

> Now on my 2.4ghz AthlonXP + 9700pro I'm seeing 36fps back-of-the-pack starts
> at 1280x1024 with 6xFSAA 16xAA with all the detail sliders maxed, except as
> noted above!   Yay!!

> rms

> > You can solve this by sacrificing a *** at full moon, or, as
> > alternative, make sure  DisableZBuffer = 1 is in core.ini.

>     This is a non-solution, since it halves framerate.

>     IRT 3.7, there is one difference that I recall compared to 4.1.  When
> pulling out of the practice pitlane at monza, and looking to the left at the
> Guardrail, in 3.7 with fsaa+aa turned on I distinctly recall that the
> guardrail edges were nice and filtered, with no jaggies.  That's what I
> recall anyway.

> But with 4.1 and fsaa+aa, the guardrail has very noticeable jaggies, though
> once you get out on the track everything looks filtered and smooth.

> I'll have to d/l Cat3.7 again and do an A/B comparison, but in any case I'm
> pretty happy with Cat4.1 both in GPL and the modern games I'm playing now
> (DeusEx2 / Tombraider6 / Tenebrae Quake1).

> Anyone have a link to Cat3.7 for WinXP ?  thx

> rms

>>>You can solve this by sacrificing a *** at full moon, or, as
>>>alternative, make sure  DisableZBuffer = 1 is in core.ini.

>>    This is a non-solution, since it halves framerate.

> The former solution it is then - now where do I find one?

>>>>You can solve this by sacrificing a *** at full moon, or, as
>>>>alternative, make sure  DisableZBuffer = 1 is in core.ini.

>>>    This is a non-solution, since it halves framerate.

>> The former solution it is then - now where do I find one?

>You have until February 6th (next full moon) to find one. Good luck.

>Mr. S.

> >>>    This is a non-solution, since it halves framerate.

> >> The former solution it is then - now where do I find one?

> >You have until February 6th (next full moon) to find one. Good luck.

> Snopes says ***s are an internet fable. Sorry.