Re: [Dri-devel] UT2k3 playability status?

2003-03-28 Thread Daniel Vogel
On Fri, 28 Mar 2003, Ian Romanick wrote: > Right now UT2k3 is toast on all open-source drivers. The only drivers > that seem to work are ATI's, Nvidia's, and (perhaps) PowerVR's > close-source drivers. I'm *trying* to get some time in on the R200 > driver, but I'm pretty swamped by my other D

Re: [Dri-devel] UT2k3 playability status?

2003-03-28 Thread Ian Romanick
Dan wrote: Hi all, I just installed UT2k3 and all patches and tried it under xfree86-4.3.0 and there are a number or rendering 'issues' apparent. I have a Radeon 64MB DDR ViVo: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 64 DDR] (prog-if 00 [VGA]) Subsy

[Dri-devel] UT2k3 playability status?

2003-03-28 Thread Dan
Hi all, I just installed UT2k3 and all patches and tried it under xfree86-4.3.0 and there are a number or rendering 'issues' apparent. I have a Radeon 64MB DDR ViVo: 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 64 DDR] (prog-if 00 [VGA]) Subsystem: ATI T

Re: [Dri-devel] thanks for the XFree-merge

2003-03-28 Thread Martin Spott
Ian Romanick <[EMAIL PROTECTED]> wrote: > Since it appears that the filp work has been merged in to the trunk, [...] Oh, I noticed too late > I'm going to freeze the texmem-0-0-1 branch and begin the arduous task of > merging the trunk. Since I'm not quite as experienced at doing merges

[Dri-devel] [Fwd: [Mesa3d-dev] [ mesa3d-Bugs-677007 ] glDrawArrays with GL_LINEStype]

2003-03-28 Thread Keith Whitwell
The use of 'minimum = 1' is definitely correct for GL_LINES. It sounds like what's actually happening is that the stride of the vertex arrays isn't being taken correctly into account when chopping the large arrays into bite-sized chunks... Keith --- Begin Message --- Bugs item #677007, was open

Re: [Dri-devel] Re: alpha planes, glxinfo, etc

2003-03-28 Thread Ian Romanick
Leif Delgass wrote: I ran into that as well, see: http://marc.theaimsgroup.com/?l=dri-devel&m=104457475806902&w=2 I think the code related to bufferSize in xc/programs/Xserver/GL/mesa/src/X/xf86glx.c is suspect regarding bufferSize. I think the X visual depth is being used instead of the sum of

Re: [Dri-devel] thanks for the XFree-merge

2003-03-28 Thread Ian Romanick
Martin Spott wrote: I'd like to express my thanks for the merge of XFree86-4.3 and the related work. The current 'trunk' is the most stable and accurate implementation of hw- accelerated OpenGL I've seen on Linux with a Radeon (in my case) for quite some time (as long as you factor out the light po

[Dri-devel] Re: alpha planes, glxinfo, etc

2003-03-28 Thread Leif Delgass
On Fri, 28 Mar 2003, Keith Whitwell wrote: > Leif Delgass wrote: > > On Thu, 27 Mar 2003, Keith Whitwell wrote: > > > > > >>Leif Delgass wrote: > >> > >>>I removed the alpha component from the visuals because the 32 bit span > >>>read function in i830_span.c doesn't read alpha from the framebuff

[Dri-devel] alpha planes, glxinfo, etc

2003-03-28 Thread Keith Whitwell
Leif Delgass wrote: On Thu, 27 Mar 2003, Keith Whitwell wrote: Leif Delgass wrote: I removed the alpha component from the visuals because the 32 bit span read function in i830_span.c doesn't read alpha from the framebuffer (it always returns 255). There's a comment there saying that it should w

[Dri-devel] thanks for the XFree-merge

2003-03-28 Thread Martin Spott
I'd like to express my thanks for the merge of XFree86-4.3 and the related work. The current 'trunk' is the most stable and accurate implementation of hw- accelerated OpenGL I've seen on Linux with a Radeon (in my case) for quite some time (as long as you factor out the light position issues with