Alan Hourihane wrote:
On Tue, Mar 26, 2002 at 10:36:41PM -0700, Jens Owen wrote:
I've made some headway on this today, and could use some feedback based
on your BSD experience. I've attempted to move the packing of
drmRadeonInitCP into the 2D ddx driver, and the main concern I'm seeing
In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
4 bytes/texel is assumed when calculating for the max texture size. If we
always convert to 2 bytes/texel for a 16bpp screen when choosing texture
formats, shouldn't that be factored into the calculation? So we'd use
On Wed, Mar 27, 2002 at 03:17:56PM -0500, Leif Delgass wrote:
In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
4 bytes/texel is assumed when calculating for the max texture size. If we
always convert to 2 bytes/texel for a 16bpp screen when choosing texture
formats,
On Wed, 27 Mar 2002, Daryll Strauss wrote:
On Wed, Mar 27, 2002 at 04:00:55PM -0500, Leif Delgass wrote:
On Wed, 27 Mar 2002, Alexander Stohr wrote:
So we'd use
mach64Screen-cpp for the calculation instead of a fixed 4
bytes/texel?
Then the comparison would be:
if
I've commited code to enable notex and tiny vertex formats for mach64.
Cool! I've got the first playable version of Counter-strike(WINE, GL
mode, 640x480, screen res 800x600). Great cudos!
Though I have to admit there are some problems.
1. After closing glxgears, there were some pieces of the
Oops, i should better care for sending
things to the mailing list address.
-Original Message-
From: Alexander Stohr
Sent: Wednesday, March 27, 2002 22:14
To: 'Leif Delgass'
Subject: RE: [Dri-devel] Max texture size
No, i dont see problems with that.
When the resoultion changes and
Ian Romanick wrote:
On Wed, Mar 27, 2002 at 03:17:56PM -0500, Leif Delgass wrote:
In the code to set MaxTextureLevels in the Rage128 and Radeon drivers,
4 bytes/texel is assumed when calculating for the max texture size. If we
always convert to 2 bytes/texel for a 16bpp screen when
On Wed, Mar 27, 2002 at 10:53:48PM +, Keith Whitwell wrote:
Actually I think the test is correct, and that I was thinking of 16 bit
textures plus a full set of mipmaps at the time. Thus the numbers should be
doubled in the 32 bit case, rather than halved for 16 as Leif was suggesting.
On Wednesday 27 Mar 2002 10:13 pm, Leif Delgass wrote:
The gears problem seems to happen if you close the window with the X or
whatever in the window title bar. Using ESC doesn't have this problem. I
guess there's a problem in the context teardown somewhere.
This problem also happens with
Alexander Stohr wrote:
(This is based on the idea that a full set of mipmaps packs
perfectly to take
up two times the size of the base texture). That's also
not true for all
architectures...
Ok, that explains a bit. However, in some circumstances we
may loose a
level.
I found that calls to TexParameter were not setting the texture wrapping
and texture filter in some cases (where the driver private texture object
struct had not already been allocated). This is now fixed and solves the
following bugs:
- artifacts with plasma gun in q3
- blocky wall textures
11 matches
Mail list logo
