RE: first time with ATI

That hardware cannot handle the full flexibility of the clip planes as
defined in GLSL. The clip vertex is what is killing you. By not writing
the clip vertex, you should get what you want on that hardware. Failing
to write the clip vertex technically leaves the results undefined, but
in your case, the results provided are the ones you want.

  -Evan

-----Original Message-----
Brubaker, Pete
Sent: Wednesday, May 24, 2006 12:59 AM
To: Multiple recipients of list OPENGL-GAMEDEV-L

You might try a simpler shader as he suggests.  Like only use a
texture2D lookup, or none at all and make sure that runs fast before
using texture1D and texture3D.

Try just outputting a constant color and start adding things back in
from there to see what instruction is giving you the problem. 

-----Original Message-----
Sent: Tuesday, May 23, 2006 8:14 PM
To: Multiple recipients of list OPENGL-GAMEDEV-L

No way my friend... My shaders are really basic...

//vertex
void main()
{
  float s;
  gl_TexCoord[0] = gl_TextureMatrix[0] * gl_MultiTexCoord0;
  gl_Position = ftransform();
  gl_ClipVertex = gl_ModelViewMatrix * gl_Vertex; }

// fragment
uniform sampler3D my3dTex;
uniform sampler1D my1DTex;
void main (void)
{
  gl_FragColor = texture1D(my1DTex, texture3D(my3dTex,
gl_TexCoord[0].xyz).r); }

I comment "gl_ClipVertex = gl_ModelViewMatrix * gl_Vertex;", which it is
the only "rare" thing, but still, 1 frame per MINUTE.

I am using glew 1.3.3.0

----- Original Message -----
To: <[email protected]>
Sent: Monday, May 22, 2006 11:09 PM


> Hi Guys
>
> I am using Mobility Radeon x1600... I tested a GLSL program, which
uses
>
>    1. 3D texture
>    2. Simple Shaders (2.0)
>    3. Clipping planes
>    4. Multitexturing
>
> and, it is really slow (1 frame "PER MINUTE").
>
> I am wondering, how could it be possible?... I tested the same code
over 
> fx5200, and at least it gives 1 frame PER SECOND. I tried it over
fx6800, 
> and it gives about 25 fps. I installed latest catalyst (SP32497.exe),
and 
> even I tried with catalyst 6.4... but still, the same amazing speed.
>
> I do not undestand the reason... it is supposed x1600 is good...
> Any clue?
>
> Thanks again guys
> RIX
> 

----- 
FAQ and OpenGL Resources at:
  http://www.geocities.com/SiliconValley/Hills/9956/OpenGL

-- 
Author: =?iso-8859-1?Q?Rhadam=E9s_Carmona?=
  INET: [email protected]

Fat City Hosting, San Diego, California -- http://www.fatcity.com
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [email protected] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB OPENGL-GAMEDEV-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

----- 
FAQ and OpenGL Resources at:
  http://www.geocities.com/SiliconValley/Hills/9956/OpenGL

-- 
Author: Brubaker, Pete
  INET: [email protected]

Fat City Hosting, San Diego, California -- http://www.fatcity.com
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [email protected] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB OPENGL-GAMEDEV-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).



----- 
FAQ and OpenGL Resources at:
  http://www.geocities.com/SiliconValley/Hills/9956/OpenGL

-- 
Author: Evan Hart
  INET: [email protected]

Fat City Hosting, San Diego, California -- http://www.fatcity.com
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [email protected] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB OPENGL-GAMEDEV-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).