Ian Romanick wrote:
> curious, what are TF_{min,mag}filter_cnst supposed to do? I modified the
the specs say.. constant bi-linear (0.25).
so i guess its 4 samples shifted right by 2 added together.
> If that's the case, then is it just a hold over from older Matrox hardware
> that couldn't do
Leif Delgass wrote:
>
> On Sat, 23 Mar 2002, Brian Paul wrote:
>
> > The Radeon driver currently advertises itself as an OpenGL 1.2
> > implementation. It would be nice to bump it up to 1.3.
>
> I'm going to do this for the mach64 driver, it should be simple since all
> these extensions will b
On Sat, 23 Mar 2002, Brian Paul wrote:
> The Radeon driver currently advertises itself as an OpenGL 1.2
> implementation. It would be nice to bump it up to 1.3.
I'm going to do this for the mach64 driver, it should be simple since all
these extensions will be fallbacks. :)
Let me just check m
On Saturday 23 March 2002 04:31, you wrote:
> Tony,
>
> I've just commited a simple change to remove the AGP requirement in the
> mach64-0-0-3-branch, as suggested by Michel. This is rather preliminary
> and I'm not sure if it's enough to get it running on a PCI Mach64.
Hi,
I've just tested the
The Radeon driver currently advertises itself as an OpenGL 1.2
implementation. It would be nice to bump it up to 1.3.
Here are the extensions that equate to OpenGL 1.3 and what
it takes to support them:
GL_ARB_multisample
We don't have to advertise any multisample visuals so
th
Those of you working on texture memory management should keep in
mind 1-D, 2-D, 3-D, cube map textures and compressed textures. I
think we're currently only implementing 2-D textures in Radeon and
using fallbacks for the rest.
Its been a long time since I looked at the Radeon specs but I seem
t
Robin Redeker wrote:
>
> Hi,
>
> i am working on a level editor and when linking
> the program with efence, i get a segmentation fault,
> here the backtrace:
> -
> #0 scale_internal_ubyte (components=3, widthin=32, heightin=48,
> datain=0x4a8b9e00 "\0
Am 23.03.2002 04:50 schrieb(en) José Fonseca:
> Unfortunately the tuxracer source code isn't of much help, since the
> tux geometry is created by an embebed tcl interpreter from a script,
> so it's not obvious the what's the state when it's being drawn.
I have seen a similar problem in quake 1
Hi,
i am working on a level editor and when linking
the program with efence, i get a segmentation fault,
here the backtrace:
-
#0 scale_internal_ubyte (components=3, widthin=32, heightin=48,
datain=0x4a8b9e00 "\026\021\f%\026", widthout=32, heightout
