I wanted to sort the objects delivered to the renderer to avoid these awful alpha-clippings on objects farther away.
i thought this could be achieved by reordering the objects with the getSlice (Node) Node - but it doesnt have any effect on layer connections (altough vvvv allows you to connect to layer pins).
yes, it still behaves like in the old system, when rendering was done over renderpass and priority. priority wasn’t spreadable. and now the layer output is not spreadable. this is by design. so i wouldn’t speak of a bug but of a missing feature.
however implementing this feature wouldn’t be a feature all the time. for most cases it would just result in a performance penalty, because of the overhead of resorting draw calls within group or renderer nodes. also the graphic card wouldn’t like it too much. a consequence of this late sorting would be that resources like effects, texture and renderstates would have be switched all the time.
so this single output of a layer is more a logical connection.
if you want to sort subsets of xfiles, this can be done with getslice (node). also transformations can be sorted this way. so maybe this could work around?
yes. layers are no spreads. cant’t the AlphaTest, ZWriteEnable or Group with prority nodes help you?
Yes. I got it sorted out even before I wrote this post by sorting the transformations and the filetexture inputs.
I just wanted to point to this “bug” or inconsitnency of v4 behaviour or whatever you want to call it.
zwriteenbale didnt work for me, though.
greets.
eno.