chronozphere

You are completely right! Thanks alot.

 

Now I know that I should not take such shortcuts in order to "optimize". 

Thanks for the reply.

 

I made a very stupid mistake by writing aPosition instead of vPosition in the second code snippet.

 

So the following gives artifacts:

aPosition = uView * uModel * vPosition;
gl_Position = uProjection * aPosition;

The following works:

aPosition = uView * uModel * vPosition;
gl_Position = uProjection * uView * uModel * vPosition;   //vPosition instead of aPosition

 

It seems strange to me why these different lines of code return different results. 

 

About the depth testing: Yes, I could have set it to GL_LEQUAL and leave it there. Good point!

 

Thanks

Can somebody explain me how I can use the gl_nv_draw_buffer extension, either in JAVA or using native code?

Thanks!

If you feel like optimizing, you could also store the normal using spherical coordinates (in R and G) and still have B left for other purposes. That would allow you to squeeze your image into an RGB format, saving 16bits per pixel.

Thanks for your helpfull reply.

I was only aware of GL_NV_draw_buffers, which didn't mention GL_MAX_COLOR_ATTACHMENTS in it's spec.

I've tested on my TF101 tablet, which has a tegra 2 soc. It reports that it has 8 color attachments. This is probably the same for tegra 3.