antialias

Attached is anim.node.planets from examples. In the 'planets' sub patcher gridshapes are captured to a context not explicitly named. Does each subpatcher reliably create a unique gl context? Just wondering about best practise for capturing textures—in what situations it would be necessary to use named contexts.

Attached is anim.node.planets from examples. In the 'planets' sub patcher gridshapes are captured to a context not explicitly named.  Does each subpatcher reliably create a unique gl context? Just wondering about best practise for capturing textures—in what situations it would be necessary to use named contexts.

unnamed-gl-context-in-subpatchers-for-jit-gl-node-capture

the easiest way to capture a group of objects to a texture is to include them in a sub-patcher, and throw in a jit.gl.node.

the objects will all automatically bind to the gl.node sub-context, as long as you don't explicitly provide a context name as an attribute.

if the objects are in a patch with a gl.node and a normal context, they will bind to the normal context unless you explicitly bind them to the sub-context.

if a name argument is not provided for normal contexts (jit.p/window @name attribute), or for gl.node sub-contexts, then one is automatically created.

thanks Rob. Does the layering order stay local to each sub-patcher context?

unnamed gl context in subpatchers for jit.gl.node capture