PDA

View Full Version : GLIntercept 0.3 = GLSL + Display Lists and more



sqrt[-1]
07-02-2004, 08:09 AM
GLIntercept version 0.3 is now released.
You can get it here: http://home.swiftdsl.com.au/~radlegend/GLIntercept/
(The Nutty mirror at http://glintercept.nutty.org will probably be updated soon)

New features include:

- GLSL shader logging and checking. This includes the ability to append any logs that were generated on the shader compile/link. Also the ability to validate and save the uniforms currently in use at each render call.
Example log: http://home.swiftdsl.com.au/~radlegend/GLIntercept/Demo03/gliInterceptLog.xml
Example shader output at render call: http://home.swiftdsl.com.au/~radlegend/GLIntercept/Demo03/Shaders/ShaderGLSL_PROG_0001_0002.txt

Some issues with uniform saving:
-ATI cards retrieving values for samplers generates a GL error and no value is returned (hence a bad value is logged) (I hope ATI fix this)
- Nvidia users need 61.xx drivers or the driver will crash with this feature (crashes on the 56.xx)

- Display list logging and checking.
Example: http://home.swiftdsl.com.au/~radlegend/GLIntercept/Demo02/gliInterceptLog.xml

- Stencil frame buffer saving at each render.(Can even color code the stencil values)

- Function Timer Log -ability to log how long the driver spends inside each OpenGL function. This can be mis-used so is only intended for advanced OpenGL users.

- Extended error logger/reporter - you can now resolve error codes and report full parameters strings to the debugger window on a GL error.

- Thread Checking While GLIntercept only supports one active render context at a time (may be fixed in future versions -you will currently get a warning), you can perform checking to see if any OpenGL calls are being made on a thread other than the main render thread. This is especially useful for applications that background load resources to ensure they do not accidently make OpenGL calls on the loading thread.

Suggested features and bug reports welcome.

(BTW: There are no prizes for guessing what demos the above log examples came from)

Tom Nuydens
07-02-2004, 08:51 AM
Originally posted by sqrt[-1]:
(BTW: There are no prizes for guessing what demos the above log examples came from)Shame, because I'm pretty sure I recognize the last one ;)

-- Tom

zeckensack
07-02-2004, 11:22 AM
I can see that you actually have some Opera-specific code in your stylesheet, but the logs are just plain unusable on Opera (v7.51, Win2k). I get all the function call names in effectively one line of plain black on white text (which wraps around to fit the window), no title, no fancy colors, no argument lists, no inline texture images, no nothing.

It'd be super cool if you could look into what's causing this.

sqrt[-1]
07-02-2004, 05:26 PM
zen:
It seems that Opera does not support XML/XSL.
http://www.opera.com/docs/specs/

If you don't want to use a Mozilla or IE based browser (I think konqueror supports it but I have not tested it), GLIntercept has a text only output option.

(or you could manually convert the XML to a HTML doc with a XML/XSL-> HTML converter , MS has one called msxsl)

knackered
07-03-2004, 07:20 AM
Or just don't use a crap browser that doesn't support XML/XSL.

Humus
07-03-2004, 08:02 AM
Originally posted by Tom Nuydens:
Shame, because I'm pretty sure I recognize the last one ;) And I recognize the first one. :)

Whoohoo! (http://esprit.campus.luth.se/~humus/temp/youwintheprize.jpg)