You don’t need to use automatic 0 for the jit.gl.render object.
The fact that things stay on your screen probably has to do with
the erase_color of the jit.gl.render object. The message should be :
erase_color 0. 0. 0. 1. (with the first 3 zero’s for r, g, b, the
fourth nr. is the one which cause the screen not to clear entirely
when it is set below 1., depending on how low it is, 0 being the
lowest, things will stay on screen longer or ‘fade away’ slowly.
Furthermore, make sure you use the ‘deph_enable’ 0 or 1 depending on
what you want to accomplish
when using the automatic 0 argument, you need to individually bang
every GL object in which you use it. Say you draw a primitive using
jit.gl.gridshape and a text using jit.gl.2dtext, both with automatic
0 enabled, you will see the following :
when banging the gridshape first, the shape will be drawn on screen,
then you bang the gl.text, which will be rendered on top of your shape.
If you send them a bang in the other order, you’ll render the text
first, and then the shape on top of it, blocking out the text.
The best way to do this is to send the bangs of the qmetro to a
trigger object. Where you use the amount of bangs needed according to
the amount of jit.gl.something objects you use.
In the above example that would be : t b b b erase The most right
outlet of the object is connected to the jit.gl.render, clearing the
scene, then the following two bangs to the gridshape and text object,
depending which one you render first, you connect the third outlet to
the first one you want to render on screen, and the seconde outlet to
the one you wish to bang next.
Finally, the first bang goes into jit.gl.render again which puts the
resulting image in your window.
Hope this clears things up a bit…
