Re: [Dri-devel] UT2003 crash with current trunk

2003-02-21 Thread Philip Armstrong
On Thu, Feb 20, 2003 at 09:05:27PM -0500, Daniel Vogel wrote:
  There is no way in hell UT2k3 will run on MGA.  It *REQUIRES*
  ARB_texture_env_combine, which is not supported by that hardware.  Even
  if it didn't require that extension, good grief man, why torture
  yourself like that?!? :)
 
 FWIW, the Windows version of UT2003 even runs (badly) on Intel 810 and
 Voodoo Banshee cards :) A G400 actually performs better than a TNT2 due to
 the increased fillrate. (all D3D)

I've got a G400 MAX as well -- it does pretty well all things
considered when paired with a beefy enough processor to compensate for
the lack of TL. Twas briefly the fastest GPU around ISTR, til Nvidia
stole the crown with the GeForce...

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Brown
On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
 Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
 Debian unstable and the latest demo release of UT2003 (v2206 -- which
 is purported to not need S3TC extensions), I get the following
 traceback reported by UT2003:
 
 phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
 Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.

???

This looks like you are using Xig libGL.so library. Deinstall Xig libs
before doing tests like this.




---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Leif Delgass
On Thu, 20 Feb 2003, Leif Delgass wrote:

 On Thu, 20 Feb 2003, Philip Brown wrote:
 
  On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
   Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
   Debian unstable and the latest demo release of UT2003 (v2206 -- which
   is purported to not need S3TC extensions), I get the following
   traceback reported by UT2003:
   
   phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
   Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
  
  ???
  
  This looks like you are using Xig libGL.so library. Deinstall Xig libs
  before doing tests like this.
 
 No, that's ut2k3 looking for S3TC support.

Actually, I'm not sure it's S3TC.  There may be some other functionality
in that X extension that it looks for. In any case, that message just
means it couldn't find that X server extension.  I see that and I've never
had XiG drivers installed.

-- 
Leif Delgass 
http://www.retinalburn.net



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel
 On Thu, 20 Feb 2003, Philip Brown wrote:
 
  On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
   Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
   Debian unstable and the latest demo release of UT2003 (v2206 -- which
   is purported to not need S3TC extensions), I get the following
   traceback reported by UT2003:
   
   phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
   Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
  
  ???
  
  This looks like you are using Xig libGL.so library. Deinstall Xig libs
  before doing tests like this.
 
 No, that's ut2k3 looking for S3TC support.

No.

BTW, the above warning message is harmless IIRC.

   [ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
   [ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
   22FOpenGLRenderInterface14EPrimitiveType+0x373)

Might be interesting to know why it crashes inside the driver :)

-- Daniel, Epic Games Inc.


---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong
On Thu, Feb 20, 2003 at 02:25:16PM -0800, Philip Brown wrote:
 On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
  Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
  Debian unstable and the latest demo release of UT2003 (v2206 -- which
  is purported to not need S3TC extensions), I get the following
  traceback reported by UT2003:
  
  phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
  Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
 
 ???
 
 This looks like you are using Xig libGL.so library. Deinstall Xig libs
 before doing tests like this.

No, it's just UT2003 looking for that X server extension and not
finding it. I don't have any Xig libraries whatsoever.

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong
On Thu, Feb 20, 2003 at 05:53:25PM -0500, Leif Delgass wrote:
 On Thu, 20 Feb 2003, Leif Delgass wrote:
  On Thu, 20 Feb 2003, Philip Brown wrote:
   On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
Debian unstable and the latest demo release of UT2003 (v2206 -- which
is purported to not need S3TC extensions), I get the following
traceback reported by UT2003:
phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
   This looks like you are using Xig libGL.so library. Deinstall Xig libs
   before doing tests like this.
  
  No, that's ut2k3 looking for S3TC support.
 
 Actually, I'm not sure it's S3TC.  There may be some other functionality
 in that X extension that it looks for. In any case, that message just
 means it couldn't find that X server extension.  I see that and I've never
 had XiG drivers installed.

No, it's not the S3TC stuff -- note the warnings in the logfile in my
original email warning that a lack of S3TC support will lead to
reduced performance.

Googling around reveals that UT2003 complains about missing
XiG-SUNDRY-NONSTANDARD extensions for other people and it appears
entirely benign.

Phil

-- 
http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Philip Armstrong
On Thu, Feb 20, 2003 at 06:13:01PM -0500, Daniel Vogel wrote:
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
[ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
22FOpenGLRenderInterface14EPrimitiveType+0x373)
 
 Might be interesting to know why it crashes inside the driver :)

fwiw, here's the output from ut2003 if I set MESA_DEBUG and
LIBGL_DEBUG:

cpu vendor: AuthenticAMD
cpu name: AMD Duron(tm) Processor
MMX cpu detected.
3DNow! cpu detected.
Testing OS support for SSE... yes.
Testing OS support for SSE unmasked exceptions... SIGFPE, yes.
Tests of OS support for SSE passed.
SSE cpu detected.
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(param=GL_COMBINE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(param=GL_COMBINE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_ALPHA_SCALE)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_ALPHA_SCALE)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND0_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_OPERAND2_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_COMBINE_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_RGB_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_SOURCE1_ALPHA_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glTexEnv(pname=GL_RGB_SCALE_EXT)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: GL_INVALID_ENUM in glDisable(0x8513)
Mesa: Mesa user error: 

RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Leif Delgass
On Thu, 20 Feb 2003, Daniel Vogel wrote:

  On Thu, 20 Feb 2003, Philip Brown wrote:
  
   On Thu, Feb 20, 2003 at 09:12:04PM +, Philip Armstrong wrote:
Using the debs at http://people.debian.org/~daenzer/dri-trunk-sid/ on
Debian unstable and the latest demo release of UT2003 (v2206 -- which
is purported to not need S3TC extensions), I get the following
traceback reported by UT2003:

phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.
   
   ???
   
   This looks like you are using Xig libGL.so library. Deinstall Xig libs
   before doing tests like this.
  
  No, that's ut2k3 looking for S3TC support.
 
 No.
 
 BTW, the above warning message is harmless IIRC.

Yeah, I realized my error just after posting it (see my reply to myself).  
;)
 
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]
[ 7]  /scratch/phil/ut2k3/demo/System/OpenGLDrv.so(DrawPrimitive__
22FOpenGLRenderInterface14EPrimitiveType+0x373)
 
 Might be interesting to know why it crashes inside the driver :)

I agree. 

Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
supported in the MGA driver.  I see defines for what look like combiner
registers, but it's not implemented in the driver yet (I don't have
hardware docs myself so I don't know the specifics of what the cards can
do).  The INVALID_ENUMS here appear to be the result of that and a lack of
ARB_texture_cube_map (neither of which are in core OpenGL 1.2).  However,
the driver shouldn't cause a segfault even with a bad enum.  A trace from
gdb would be helpful, I think.

On the plus side, the R100 and R200 drivers now support
ATI_texture_env_combine3 and one bug that was causing vertex corruption in
the intro cinematic in the R100 driver was fixed.  However, there are
still vertex problems that appear to be in the R100 driver to track down.

I can't test R200, so I'm not sure what the status is there.

-- 
Leif Delgass 
http://www.retinalburn.net







---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel
 Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
 supported in the MGA driver.  I see defines for what look like combiner

That's a no go as we rely on this extension. The game should probably assert
in this case.

-- Daniel, Epic Games Inc.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Ian Romanick
Philip Armstrong wrote:

phil@trigger /scratch/phil/ut2k3/demo ./ut2003_demo  
Xlib:  extension XiG-SUNDRY-NONSTANDARD missing on display :0.0.

Ignore this.  This is UT2k3 trying to determine which way to do 
fullscreen.  Either the XFree86 way or the XiG way.

[ 4]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f55bb9]
[ 5]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f3e4f1]
[ 6]  /usr/X11R6/lib/modules-dri-trunk/dri/mga_dri.so [0x43f31fb7]


There is no way in hell UT2k3 will run on MGA.  It *REQUIRES* 
ARB_texture_env_combine, which is not supported by that hardware.  Even 
if it didn't require that extension, good grief man, why torture 
yourself like that?!? :)



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


Re: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Ian Romanick
Leif Delgass wrote:


Based on the MESA_DEBUG log, It looks like ARB_texture_env_combine isn't
supported in the MGA driver.  I see defines for what look like combiner
registers, but it's not implemented in the driver yet (I don't have
hardware docs myself so I don't know the specifics of what the cards can
do).  The INVALID_ENUMS here appear to be the result of that and a lack of
ARB_texture_cube_map (neither of which are in core OpenGL 1.2).  However,
the driver shouldn't cause a segfault even with a bad enum.  A trace from
gdb would be helpful, I think.


Correct.  The combiner in the G400 family is strange.  I spent some time 
looking at the docs a few weeks ago.  It should be possible to implement 
most of ARB_texture_env_combine, but not everything.  Basically, there 
is a single multiplier and a single adder.  That means that 
GL_INTERPOLATE is right out.  Also, the first operand MUST come from the 
source texture.

It's pretty kooky, but I think we could get about 60% of 
ARB_texture_env_combine and about 40% of ATI_texture_env_combine3 (no 
joke!) hardware accelerated.  If anyone (esp. anyone that has that 
hardware) would be interested in working on implementing it, I'd love to 
discuss it.  I just don't think I'll have the spare time to put too much 
effort into it.

What would be REALLY nice is to have as much of these extensions as 
possible hardware accelerated on MGA, Rage 128, and i810, AND have the 
software fallbacks MMX optimized...I can dream. :)

On the plus side, the R100 and R200 drivers now support
ATI_texture_env_combine3 and one bug that was causing vertex corruption in
the intro cinematic in the R100 driver was fixed.  However, there are
still vertex problems that appear to be in the R100 driver to track down.

I can't test R200, so I'm not sure what the status is there.


Unfortunately, it's WORSE on R200.  Not only does it not render 
correctly, it hard locks the system.  I have to hit the reset button on 
the case. :(  I'm trying to get through some of my other duties so that 
I can spend a few cycles on this.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel


RE: [Dri-devel] UT2003 crash with current trunk

2003-02-20 Thread Daniel Vogel
 There is no way in hell UT2k3 will run on MGA.  It *REQUIRES*
 ARB_texture_env_combine, which is not supported by that hardware.  Even
 if it didn't require that extension, good grief man, why torture
 yourself like that?!? :)

FWIW, the Windows version of UT2003 even runs (badly) on Intel 810 and
Voodoo Banshee cards :) A G400 actually performs better than a TNT2 due to
the increased fillrate. (all D3D)

We scale back pretty well, though the OpenGL renderer never was written with
the intention to work on G400 cards. The D3D renderer jumps through quite
some hoops to deal with very old HW, disables certain features and
simplifies certain materials/ shaders to avoid driver/ HW bugs/ limitations.
I didn't bother doing that for the OpenGL renderer, which, FWIW, runs quite
well on Voodoo 4/5 cards on Windows.

As I've been seeing posts on /. about the topic: on Windows the OpenGL
renderer performs within 5-10% of the D3D renderer on ATI and NVIDIA cards
on the machines I tested. Sometimes it's faster, but most of the times its
slightly slower than the D3D renderer, which doesn't come as a big surprise
given the amount of tweaking the D3D codepath underwent on both our end and
the driver side.

-- Daniel, Epic Games Inc.



---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel