mesa3d-dev

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[<ant...@wm...>]

> Mesa 3.3 was changed to allow arbitrary Z buffer depths at runtime,
> instead of being a compile-time option.  Looks like I missed
> something in the tdfx driver code.  Could you try this patch
> to Mesa-3.3/src/FX/fxapi.c?
> 
> diff -r1.21 fxapi.c
> 946c946
> <    fxMesa->haveZBuffer=depthSize ? 1 : 0;
> ---
> >    fxMesa->haveZBuffer=depthSize ? 16 : 0;
> 
> 
> -Brian
> 


Ok, letme know if there is something that you want me to try....
because the reason i was confused is that the Voodoo2 cards don't support
more than 16bit deep zbuffers/depthbuffers, at least from what i know ...

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[<ant...@wm...>]

> I took at look at this but didn't make any progress.  I'm not sure
> how Q3 is choosing its visual and determining the bits per buffer.

you can force it to use a 24bit depth with:
./quake3 +set r_depthbits 24 

> The game is working OK, right?

yes, it works fine, but what I wonder is: how does fxMesa respond when
asked to set a 24bit zbuffer on a card that doesn't support it!? (Voodoo2)
It should not run, therefore somewhere in there something needs fixing..

> I won't be able to look into this anymore until next week.

no, worries, i just hope it's not a bug in 3.3 

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[Brian P. <br...@va...>]

ant...@wm... wrote:
> 
> > I took at look at this but didn't make any progress.  I'm not sure
> > how Q3 is choosing its visual and determining the bits per buffer.
> 
> you can force it to use a 24bit depth with:
> ./quake3 +set r_depthbits 24
> 
> > The game is working OK, right?
> 
> yes, it works fine, but what I wonder is: how does fxMesa respond when
> asked to set a 24bit zbuffer on a card that doesn't support it!?

I think it's only reporting 24bits/z but really using 16.


> (Voodoo2)
> It should not run, therefore somewhere in there something needs fixing..
> 
> > I won't be able to look into this anymore until next week.
> 
> no, worries, i just hope it's not a bug in 3.3

-Brian

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[Daniel V. <vo...@lo...>]

On Mon, Aug 28, 2000 at 02:35:49PM -0600, Brian Paul wrote:
>
> > yes, it works fine, but what I wonder is: how does fxMesa respond when
> > asked to set a 24bit zbuffer on a card that doesn't support it!?
> 
> I think it's only reporting 24bits/z but really using 16.

Why that?

-- 
Daniel Vogel
Programmer
Loki Entertainment Software

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[<ant...@wm...>]

On Tue, 29 Aug 2000, Daniel Vogel wrote:

> On Mon, Aug 28, 2000 at 02:35:49PM -0600, Brian Paul wrote:
> >
> > > yes, it works fine, but what I wonder is: how does fxMesa respond when
> > > asked to set a 24bit zbuffer on a card that doesn't support it!?
> > 
> > I think it's only reporting 24bits/z but really using 16.
> 
> Why that?

I would assume that either the fxMesa ignores the 24 and uses 16, or
fails at 24, goes down to 16, and doesn't report 16?
But I think Brian should answer that, not me :)


BTW, good job on all your guys' conversions/ports over there are Loki! (at
least the ones' i have tried out)

> -- 
> Daniel Vogel
> Programmer
> Loki Entertainment Software
> 

Re: [Mesa3d-dev] Anyone know why: Mesa 3.3 defaults to 24bit Zbuffer?

[Brian P. <br...@va...>]

ant...@wm... wrote:
> 
> > Mesa 3.3 was changed to allow arbitrary Z buffer depths at runtime,
> > instead of being a compile-time option.  Looks like I missed
> > something in the tdfx driver code.  Could you try this patch
> > to Mesa-3.3/src/FX/fxapi.c?
> >
> > diff -r1.21 fxapi.c
> > 946c946
> > <    fxMesa->haveZBuffer=depthSize ? 1 : 0;
> > ---
> > >    fxMesa->haveZBuffer=depthSize ? 16 : 0;
> >
> >
> > -Brian
> >
> 
> Ok, letme know if there is something that you want me to try....
> because the reason i was confused is that the Voodoo2 cards don't support
> more than 16bit deep zbuffers/depthbuffers, at least from what i know ...

I took at look at this but didn't make any progress.  I'm not sure
how Q3 is choosing its visual and determining the bits per buffer.

The game is working OK, right?

I won't be able to look into this anymore until next week.

-Brian