StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>If I understand right, you want to disable depth writes because you draw both opaque and transparent objects. Apart from the fact that it doesn't work that way from within GLSL, it would not produce what you want, if it did.</p> <p>If you just disabled depth writes <em>ad hoc</em>, the opaque objects coming after a transparent object would overwrite it, regardless of the z order.</p> <p>What you really want to do is this:</p> <ol> <li>Enable depth writes and depth test</li> <li>Draw all opaque geometry. If you can, in a roughly sorted (<em>roughly</em> is good enough!) order, closest objects first.</li> <li>Disable depth writes, keep depth test enabled</li> <li>Enable blending</li> <li>Draw transparent objects, sorted in the opposite direction, that is farthest away first. This occludes transparent objects with opaque geometry and makes blending work correctly.</li> </ol> <p>If, for some reason, you can't sort the <em>opaque</em> geometry (though there is really no reason why you can't do that?), never mind -- it will be slightly slower because it does not cull fragments, but it will produce the same image.</p> <p>If, for some reason, you can't sort the <em>transparent</em> geometry, you will have to expect incorrect results where several transparent objects overlap. This may or may not be noticeable (especially if the order is "random", i.e. changes frame by frame, it will be very noticeable -- otherwise you might in fact get away with it although it's incorrect).</p> <p>Note that as datenwolf has pointed out already, the fact that several objects are in one VBO does not mean you can't draw a subset of them, or several subsets in any order you want. After all, a VBO only holds some vertices, it is up to you which groups of them you draw in which order.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload