GPL: FSAA working with Catalyst 4.1 drivers !!! w000t

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

muahahaha...Victory. PAPADOC

Quoted text (24 lines)

>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 >

My Blog all about politics and the terror war. www.papadoc.net/PinkFlamingoBar.html

rms wrote:

Quoted text (24 lines)

> > 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

My understanding was that AA doesnt work in GPL because its 16bit, and ATI wasn't/isn't supporting it. Mind you I wouldn't want to be ATI and pissing off a whole bunch of actuall Formula car drivers that use this game for simulation practice. Gordon

On Tue, 20 Jan 2004 05:38:07 GMT, "rms" <[email hidden]> wrote: >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. That happens when there are too many poly's in view, since the Z-buffer is only 16 bit. You can solve this by sacrificing a virgin at full moon, or, as alternative, make sure DisableZBuffer = 1 is in core.ini. Cheers! Remco

Thanks for the tip about Cat 4.1 and GPL. I tried the 4.1 driver out and found that GPL had a lot of "shimmering" in the distance along the kerbs/edge of the track. I found the same issue with the 3.9's as well. Very annoying. It also seemed that the frame rate was down by 5-10% as well from the 3.7s that I've been using. So, I went back to the 3.7's. After reverting back to 3.7, I returned here to be reminded of the point about the core.ini change, which I forgot to try. Would that change have gotten rid of the shimmering and improved the frame rate at all? If so, I'm willing to try the 4.1's again. FWIW, my system is an Athlon XP2100, 640 Megs RAM, WinXP Pro, Radeon 9700 Pro (nothing overclocked). YMMV. rms wrote:

Quoted text (23 lines)

> 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

Thanks for the tip about Cat 4.1 and GPL. I tried the 4.1 driver out and found that GPL had a lot of "shimmering" in the distance along the kerbs/edge of the track. I found the same issue with the 3.9's as well. Very annoying. It also seemed that the frame rate was down by 5-10% as well from the 3.7s that I've been using. So, I went back to the 3.7's. After reverting back to 3.7, I returned here to be reminded of the point about the core.ini change, which I forgot to try. Would that change have gotten rid of the shimmering and improved the frame rate at all? If so, I'm willing to try the 4.1's again. FWIW, my system is an Athlon XP2100, 640 Megs RAM, WinXP Pro, Radeon 9700 Pro (nothing overclocked). YMMV.

Quoted text (23 lines)

> 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

> You can solve this by sacrificing a virgin at full moon, or, as > alternative, make sure DisableZBuffer = 1 is in core.ini. This is a non-solution, since it halves framerate. rms

"rms" wrote: > > > You can solve this by sacrificing a virgin 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?

Thanks for pointing this out Roger :) It is soo nice to not have that flickering box on top of the screen. Those GPLEA cars look just marvelous at 1600x1200 with 2x aa 16 anistropic. Dave :) "rms" <[email hidden]> wrote in message news:393Pb.10437$[email hidden]... > 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

Quoted text (9 lines)

> 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 aftertrying > various things, I reduced the Graphics Detail Bias in GPL just slightlyfrom > max detail. This seems to fix the problem. > > Now on my 2.4ghz AthlonXP + 9700pro I'm seeing 36fps back-of-the-packstarts > at 1280x1024 with 6xFSAA 16xAA with all the detail sliders maxed, exceptas > noted above! Yay!! > > rms > >

> After reverting back to 3.7, I returned here to be reminded of the pointabout > the core.ini change, which I forgot to try. Would that change have gottenrid > of the shimmering and improved the frame rate at all? If so, I'm willingto try > the 4.1's again. 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

I think that you can still download older driver sets at www.ati.com rms wrote:

Quoted text (24 lines)

> > After reverting back to 3.7, I returned here to be reminded of the point > about > > the core.ini change, which I forgot to try. Would that change have gotten > rid > > of the shimmering and improved the frame rate at all? If so, I'm willing > to try > > the 4.1's again. > > 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

I think that you can still download older driver sets at www.ati.com

Quoted text (24 lines)

> > After reverting back to 3.7, I returned here to be reminded of the point > about > > the core.ini change, which I forgot to try. Would that change have gotten > rid > > of the shimmering and improved the frame rate at all? If so, I'm willing > to try > > the 4.1's again. > 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

BRH wrote: > I think that you can still download older driver sets at www.ati.com or here http://www.driverheaven.net/downloads/index2.htm

Tony Rickard wrote:

Quoted text (8 lines)

> "rms" wrote: > >>>You can solve this by sacrificing a virgin 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.

Quoted text (13 lines)

>Tony Rickard wrote: >> "rms" wrote: >> >>>>You can solve this by sacrificing a virgin 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.

Snopes says virgins are an internet fable. Sorry. PAPADOC Pierre PAPA DOC Legrand Killing Terrorists One Word at a Time! www.papadoc.net/PinkFlamingoBar.html

BTW, I tried Cat3.7, and see no difference compared to Cat4.1, with fsaa enabled. In any case computers in the 3ghz+ range with 9800pros should be able to play this game at 1600x1200 all the time, so fsaa will less and less important in gpl. rms

"PAPADOC" wrote:

Quoted text (10 lines)

> >>>>You can solve this by sacrificing a virgin 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. > > Snopes says virgins are an internet fable. Sorry.

Good news. Just done a Google search and found some islands apparently full of 'em

Quoted text (13 lines)

>> >>>>You can solve this by sacrificing a virgin 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. >> >> Snopes says virgins are an internet fable. Sorry. > >Good news. Just done a Google search and found some islands apparently full >of 'em

hehe Careful apparently some have a wicked sense of humor, I believe that the same people named both Greenland and the Virgin Islands. PAPADOC My Blog all about politics and the terror war. www.papadoc.net/PinkFlamingoBar.html

You will still get artifacts that are not seen on a properly FSAA's screen...simple fact of graphics. All the edges will crawl and jaggies will appear...its exactly why even the most outrageously expensive graphic cards all do FSAA. Look at all the Magazine Screenshots, all terribly messed up and I suspect they dont do that on purpose. Probably more they are used to the jaggies and dont notice them....but to someone who knows its painful. PAPADOC >In any case computers in the 3ghz+ range with 9800pros should be able to >play this game at 1600x1200 all the time, so fsaa will less and less >important in gpl. > >rms > My Blog all about politics and the terror war. www.papadoc.net/PinkFlamingoBar.html

On Thu, 22 Jan 2004 15:50:37 -0600, PAPADOC <[email hidden]> wrote:

Quoted text (18 lines)

> >>> >>>>You can solve this by sacrificing a virgin 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. >>> >>> Snopes says virgins are an internet fable. Sorry. >> >>Good news. Just done a Google search and found some islands apparently full >>of 'em > >hehe Careful apparently some have a wicked sense of humor, I believe that the >same people named both Greenland and the Virgin Islands. >

And of course, the Pacific Ocean, too. -- __________ ____---____ Marco Antonio Checa Funcke \_________D /-/---_----' Santiago de Surco, Lima, Peru _H__/_/ http://machf.tripod.com '-_____|( remove the "no_me_j." and "sons.of." parts before replying