If I may ask, what are you all using this feature for? Perhaps
there's a better way or at least a workaround.
On Thu, Apr 24, 2008 at 10:19 AM, Joshua Kit Clayton wrote:
> On Apr 24, 2008, at 3:34 AM, pascal wrote:
> > I'm not able to render on jit.window when its @visible attribute is set to
> 0 . >> " couldn't make OpenGl on window xxx"
> > Was working in Max 4.x
> Thanks for the report. Known issue. We're looking into it.
Well ...I had a patch with multiple rendering context ( one of them used as the main rendering context ..so with a jit.window visible ) .I used invisible contexts ( with usetexture , to_texture messages ) to capture the content of those invisble contexts ..Another way to achieve that ?
You can render to texture. jit.gl.texture @capture. Most likely this
will be more efficient as you won't have the overhead of multiple
windows/contexts and it will draw directly to the texture instead of
having to copy the framebuffer of the window to the texture. Search
the forums for render to texture. There are tons of threads on this
On Fri, Apr 25, 2008 at 2:31 AM, pascal wrote:
> Well ...I had a patch with multiple rendering context ( one of them used as the main rendering context ..so with a jit.window visible ) .I used invisible contexts ( with usetexture , to_texture messages ) to capture the content of those invisble contexts ..Another way to achieve that ?
I've been using oscillators in jit.gl.gridshape to modify the shape,
color and position of a sequence of shaped spheres. The patch below
leaves a 2D trail of the instancing history. I want to be able to
leave a 3D trail of shapes so I can move the camera and be able to
view the 3D trail/cluster while it is forming.
I noticed that the jit.gl.multiple help patch creates a 3D cluster of
elements which can be viewed from many directions.
In the patch below, you can see that inputs to the xyz of the camera
control its position with respect to the sphere that is being made but
the trail seems to be locked to the camera (in 2D) and is not locked
to the world space.
How can I build the instancing history in 3D so I can view it from the
camera that moves around in the world space?
Should I use jit.gl.multiple to build the instancing history? If so,
How can I do it? I couldn't find any examples that show how to
instance single elements with jit.gl.multiple.
Any help will be greatly appreciated ... I've been on this for quite a
while with limited success.
Cheers, Chuck Henry
this is a n answer to the instancing gridshapes question above.
please check that you respond to the correct thread or start a new thread if your topic is new.
Chuck, you're doing a number of things inappropriately in your patch. FIrst, I'd change the method you use with the oscillators. If you want to use audio signals check out jit.poke~ and how to write to msp buffers~. For example, you can write your x,y,and z position values to a buffer called 'scale' and then access these values from a matrix with the same name by banging the matrix and using jit.iter. I think Andrew Benson gave a good example of doing this in one of his jitter recipes (which are available on the cycling site).
A number of your messages are incorrectly formatted. erase_color is followed by 4 values; lighting_enable takes one value (0 or 1). if you want to alter the values you could use the $1 argument (and $2 $3 $4 etc) in your messages.
One of the reasons you can't move about in the space is because you are only ever drawing one gridshape and not erasing the buffer before rendering the next frame. To get the trace you are after you will need to draw more than one object each frame, and jit.gl.multiple may help you here - have a look at it's help file and you'll see that you can view the objects from different angles which you are not able to do with your example.
I'd also suggest looking into the doublebuffer setting for your window.
> The patch below
> leaves a 2D trail of the instancing history. I want to be able to
> leave a 3D trail of shapes so I can move the camera and be able to
> view the 3D trail/cluster while it is forming.
well, not quite. it's not leaving an "instancing history" if i understand your term correctly. it's just leaving trails of what was previously drawn to the buffer, because your erase_color alpha is 0. your correct that this is just in 2d. it's just pixels, not 3d geometry.
you will have to come up with something of your own in order to do what you want. gl.multiple might be a good place to start, but it's not necessary. a gl.gridshape object encapsulated in a poly~ might also be a good place to start.
I'm still working on this ... but the first step is to make an
oscillator that has a sine wave that does not go negative on the
Y-Axis of the scope.
The patcher below needs some help to achieve this property. I tried to
do it with abs with no success ... I hope someone can direct me to the
This output will go into poke scale then into the gridshape sphere. I
need the oscillator positive so the sphere doesn't go to 0 dim and
then turn inside out. There must be a way to reverse the polarity
and/or bias the Y-Axis to keep it above 0 by a certain amount.
Since the oscillator frequency and amplitude will be changing, the
biasing has to be a function of the input.