It looks ok, but when I watch the 2 quads from another point I have the following problem:
any idea?
0
5 replies to this topic
Sponsor:
#3 Members - Reputation: 772
Posted 12 December 2012 - 05:15 PM
That;s the good old transparency sorting issue. The solution is above, as AliesBinman explained. As well as carefully looking at your blending/transparency/depth writing options.
The reason is that you can't just draw transparent/blended pixels in random order (depending a bit on your blending and transparency testing methods enabled). In picture2, the foreground image got rendered first. Even though its transparent, also the non-filled pixels wrote a depth value to the depth buffer. After that, you rendered the second quad in the background. But before just plotting those pixels on the canvas, the graphics engine is testing if there is nothing in the foreground occluding it, by comparing depth. Monkey farts, it seems that the quad in front is blocking your way.
Sorting from back- to forward is one way to prevent this, though it still doesn't always work for quads intersecting each other. Second, check your blending / transparency testing options. Transparent pixels shouldn't write a depth value either. If you are using a shader, the fragmentshader for example could simply kill the transparent pixels to prevent this.
The reason is that you can't just draw transparent/blended pixels in random order (depending a bit on your blending and transparency testing methods enabled). In picture2, the foreground image got rendered first. Even though its transparent, also the non-filled pixels wrote a depth value to the depth buffer. After that, you rendered the second quad in the background. But before just plotting those pixels on the canvas, the graphics engine is testing if there is nothing in the foreground occluding it, by comparing depth. Monkey farts, it seems that the quad in front is blocking your way.
Sorting from back- to forward is one way to prevent this, though it still doesn't always work for quads intersecting each other. Second, check your blending / transparency testing options. Transparent pixels shouldn't write a depth value either. If you are using a shader, the fragmentshader for example could simply kill the transparent pixels to prevent this.
#5 Crossbones+ - Reputation: 5185
Posted 12 December 2012 - 06:54 PM
If you don’t have the ability to sort the objects then you need to use discard inside the shader when you detect that the alpha value is 0.
L. Spiro
L. Spiro
It is amazing how often people try to be unique, and yet they are always trying to make others be like them. - L. Spiro 2011
I spent most of my life learning the courage it takes to go out and get what I want. Now that I have it, I am not sure exactly what it is that I want. - L. Spiro 2013
L. Spiro Engine: http://lspiroengine.com
L. Spiro Engine Forums: http://lspiroengine.com/forums
I spent most of my life learning the courage it takes to go out and get what I want. Now that I have it, I am not sure exactly what it is that I want. - L. Spiro 2013
L. Spiro Engine: http://lspiroengine.com
L. Spiro Engine Forums: http://lspiroengine.com/forums
