hey you need to render directly into a matrix, so you won't have your floating window display... or after the matrix. For that, give a name to your jit.gl.render, and the same name to a matrix which will be receiving everything.

BUT (that "but" is important) that's probably not the way to go : if you do that, exit jit.gl.picker, or jit.gl.handle or any facility with the window, because the jit.window won't be the primary context render target. Moreover you have some constraints with your matrix that are not necessarly easy to figure out. You had better stay in the opengl world once the render is done. That's all because jit.gl.rendre can only render into one context, so you generally want to do any other operation before. using jit.gl.videoplane or jit.gl.node.

Thank you vichug, i tried out the first part and yeah it rendered really slow and bad lol. In the patch below that is basically what I was trying to do with scissors. (the interlacing part)

But! yeah if I want this interlaced effect how do i do it with the phys patch i posted in the first message? I am having a hard time understanding how to do so with either jit.node or jit.video plane. Sorry if your just repeating yourself, having a tough time understanding.

well what you want to do is not easy ! least obvious part is what it how it will behave with picker. Also the problem is that i don't have a kinect to test it myself. but idea is like this:

you'll notice 10 instances of jit.gl.camera, each has a viewport defining an area of the jit.gl.render destination where it is rendered. Those zones are strips which are 1/10th of the rendering zone in width. You need then to replace the position of the cameras manually. I created a jit.gl.gridshape for testing. If you have two different "things" to render : make each of those "things" inside a jit.gl.node, both jit.gl.node will render in the same jit.gl.render, and each camera will target a different jit.gl.node.

Awesome, i was playing with it and this seems to be a step in the right direction. But I am having a bit of a problem. With so many gl cameras it is eating up way too much fps getting like 15 when i have the ten up and the "particles" going. I think i can simplify the patch a bit, and in doing so do you think there is another way to achieve this interlacing thing I want?

What I mean is instead of the picker being controled by kinect position I just change the central_force based on kinect data. It will do the same thing I want it to do, so therefore I can just skip using the phys.picker and moveable object entirely, only using the static points.

I tried this with the gl.camera method, and it was smother but the fps only went up by a little bit. I was researching this a bit more and some people suggested using the jit.gl.texture and jit.gl.slab, but I couldnt get that to work, any ideas?

Here is the updated patch with the picker gone and everything controlled by a slider on the right. This will work perfectly, now if i could only get the interlacing look.

i don't know how jit.gl.slab work, nor jit.gl.texture, so i can't really help you on that, sorry... jit.gl.slab is for writing shaders and it's another programming language entirely. If you want better performances though, it's probably the way to go.