Re: GPL D3D-Patch

You have a Voodoo card. Use Glide. You will not see an improvement with the D3D patch. Cheers, ...Colin Peter Noble <[email hidden]> wrote in message news:B9p95.22056$[email hidden]... > I get the opposite ...sigh. > > Down to 15fps at the start of a race, moving up to 36 gradually - I've > usually crashed by then though :) I've tried the advice in the readmefile. > > P111 550/128Mb/Voodoo3 AGP with newest drivers. >

I have a problem with the new D3D-patch from Papyrus. I can start the race perfectly, running with 36 fps and 1024x768. But then after two minutes the framerate goes down to 15-17. When I press F3 and come back, the framerate is back at 36. What is wrong? I have a PIII 550, 128MB, ATI Rage Fury 32MB. Thanks

Almost the same set-up here: PIII667 o/c 750 128MB Rage Fury 32MB No problems at all, solid 36 FPS at 1280X1024. I'm using the latest "special purpose" beta drivers from ATi. They are quite stable and worth a try if you're not using them. One thing I found is that my frame rate is *a lot* better if I disable the z-buffer (see the D3D patch readme). Dale. -- ----------------------------------------------------------- - Return address invalid - Please share your reply with the newsgroup - if you must reply... [email hidden] (reverse the last three letters after the period) ------------------------------------------------------- "Hubsi" <[email hidden]> wrote in message news:8k4rr3$1ogto$[email hidden]... > I have a problem with the new D3D-patch from Papyrus. I can start the race > perfectly, running with 36 fps and 1024x768. But then after two minutes the > framerate goes down to 15-17. When I press F3 and come back, the framerate > is back at 36. What is wrong? I have a PIII 550, 128MB, ATI Rage Fury 32MB. > Thanks > >

I get the opposite ...sigh. Down to 15fps at the start of a race, moving up to 36 gradually - I've usually crashed by then though :) I've tried the advice in the readme file. P111 550/128Mb/Voodoo3 AGP with newest drivers. Peter "Sideshow Bob" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (28 lines)

> Almost the same set-up here: > > PIII667 o/c 750 > 128MB > Rage Fury 32MB > > No problems at all, solid 36 FPS at 1280X1024. > > I'm using the latest "special purpose" beta drivers from ATi. They are > quite stable and worth a try if you're not using them. > > One thing I found is that my frame rate is *a lot* better if I disable the > z-buffer (see the D3D patch readme). > > Dale. > > -- > > ----------------------------------------------------------- > - Return address invalid > - Please share your reply with the newsgroup > - if you must reply... [email hidden] > (reverse the last three letters after the period) > ------------------------------------------------------- > > "Hubsi" <[email hidden]> wrote in message > news:8k4rr3$1ogto$[email hidden]... > > I have a problem with the new D3D-patch from Papyrus. I can start the

race > > perfectly, running with 36 fps and 1024x768. But then after two minutes > the > > framerate goes down to 15-17. When I press F3 and come back, theframerate

Quoted text (7 lines)

> > is back at 36. What is wrong? I have a PIII 550, 128MB, ATI Rage Fury > 32MB. > > Thanks > > > > > >

It's not designed for Voodoo cards, stick with glide by selecting 3dfx in the options.

I use the d3d patch so I can get to the 2xfsaa option on my V5. With 2xfsaa in d3d, and my PIII 500, I can run a 1024x760 screen. With glide and 4xfsaa I'm limited to 800x600(which btw looks great) The only advantage one might see with the V2's and V3's would be the slightly better mirror images that are possible with the d3d rasterizer. dave henrie "Simon Brown" <[email hidden]> wrote in message news:JNu95.22986$[email hidden]... > It's not designed for Voodoo cards, stick with glide by selecting 3dfx in > the options. > >

Right. Another advantage would be z-buffering. It's a pitty it's so much slower on a V3. fps on full Monza grid goes from 29 with glide to 12 with d3d. Also the filtering is a bit over-the-top with the d3d rasterizer. I hope it works better on a GeForce 2 gts, cause I'm getting one to replace my v3 in 10 days.

Sounds like some kind of memory leak caused by the Rage drivers. Try different drivers.