AA is a requirement for shipping titles, yet most samples don’t implement it (at least last I checked a few months back). Only a couple had FSAA going, but how to mix that with float buffers, etc, was not explained.
I did it eventually, but it was definitely not straightforward.

I choose interfaces that let me see and control what I am doing =)

So I do still have problems, but they are of a different nature. =)

Writing code is not math, although having the math behind is important. Being a programmer myself, I know that I’m not going to stopped, however I’m frustrated by the lack of actual specific documentation. And in some cases one is supposed to read tons of bullshit (for example the OpenGL extension documentation, which includes some sort of log of decisions along with the specification).

Currently I’m dealing with the GL_COMPARE_R_TO_TEXTURE_ARB texture parameter. This should magically enable tex2dproj() to do a Z compare between the current position’s Z and the depth texture’s Z.
To debug, it would be a great start to have the plain formula used by tex2dproj(), but that isn’t available in the standard CG documentation..

I shouldn’t be telling you about implementation issues. If you have no problems then you are not earning your pay ;)

What is your actual problem? Is opengl interface too convoluted for you to figure out how to implement what you want?

I agree, maybe OpenGL sucks.. but your answer doesn’t make sense.
My complaint is about how things are not explained anywhere in detail, and you just explained the theory again 8)

With OpenGL was also pretty difficult to get the Z buffer allocated right with the Framebuffer Objects thing. Bind this, attach that.. bha !

Seems to me like I would render the scene from the lights perspective into z only texture (shadow map). Set that texture on one of the texture stages. Then render the scene from cameras perspective and also for each vertex calculate their shadow map u,v and z in light space. This could be done by transforming the vertex by the light space draw matrix and then normalizing the x,y to 0..1 range to get the uvs Then I would pass the calculated shadow map uv’s and light space z to the pixel shader. In the pixel shader I would use the shadow map uv’s to look up the z value from the shadow map and compare it to the light space z value that i am passing down to determine if the pixel is in shadow or not?

I promised a shady story, but first I need to focus on my shadow story (ah ah).

BTW, things good a good turn as I figured my shadow map projection matrix was being loaded improperly.

I was using:

cgGLSetMatrixParameterfr( mat_param, mat._m[0] );

..in place of..

cgGLSetMatrixParameterfc( mat_param, mat._m[0] );

Because I use the OpenGL format of matrices, I was mistakenly loading the matrix as a row-matrix, but it should have been as a column-matrix.

And here comes facking OpenGL too !! I can’t believe the standard tells people to think column matrices but to store row matrices ! ..in a one dimensional array, nonetheless.
This has had so much negative repercussion, especially when one considers that there is then Direct3D that tells you to think row matrices and store them that way.

That’s only an example.. I’m using a mathematical function and I don’t have the facking formula for it !!
How hard is it to put the formula in the documentation ?? It should be all over the places, but instead it’s a mission do find that simple vital information.

I don’t want to do trial and error forever, I want to know what I’m doing !!!

Fuck ATI and nVidia !!!