a standard for geometry matrix output? – getting jit.gl.model matrixoutput into mesh / nurbs

Apr 1, 2007 at 3:13pm

a standard for geometry matrix output? – getting jit.gl.model matrixoutput into mesh / nurbs

hi all
I have searched previous threads but found nothing that addresses this specifically. I understand from jkc’s explanation here
[URL]http://www.cycling74.com/forums/index.php?t=msg&goto=65226&rid=0&srch=jitter+1.6.3.b3#msg_65226[/URL]
and from some simple experimentation that jit.gl.model and jit.gl.gridshape output matrices very differently.

My question- how can I process the data so that it is fit to work with jit.gl.mesh or jit.gl.nurbs via ctlmatrix- Using the jit.gl.render only is very limiting.
In addition I wish to pass the model matrixoutput through various abstractions I’ve made for working with gridshape-style matrices. These took a lot of work to make and it was quite frustrating to discover they wouldn’t work with the model output. Last but not least, I guess that having a standard way of working with geometry matrices also counts for something…

Sorry if I come off as somewhat bitter, but I really counted on using models as an integral part of a project I’m working on, and now it seems it may not be all that integrated into jitter yet.
-Nadav

#31118
Apr 1, 2007 at 4:16pm

Well, Jit.gl.model can potentially output more than one 13 plane
matrix for geometry, depending on how the model is created and what
type of geometry is in there, and whether or not there is more than
one distinct unconnected ‘model’ (for example the mushroom obj file
that C74 provides will output more than one 13 plane matrix for each
drawgroup ). Also, from my understanding the jit.gl.gridshape object
will use the 13 plane format but will output data with certain
dimensions for easy manipulation.

id read the jitter docs and check out the appendix for the OpenGL
matrix format.

On Apr 1, 2007, at 11:13 AM, Nadav Assor wrote:

>
> hi all
> I have searched previous threads but found nothing that addresses
> this specifically. I understand from jkc’s explanation here
> [URL]http://www.cycling74.com/forums/index.php?
> t=msg&goto=65226&rid=0&srch=jitter+1.6.3.b3#msg_65226[/URL]
> and from some simple experimentation that jit.gl.model and
> jit.gl.gridshape output matrices very differently.
>
> My question- how can I process the data so that it is fit to work
> with jit.gl.mesh or jit.gl.nurbs via ctlmatrix- Using the
> jit.gl.render only is very limiting.
> In addition I wish to pass the model matrixoutput through various
> abstractions I’ve made for working with gridshape-style matrices.
> These took a lot of work to make and it was quite frustrating to
> discover they wouldn’t work with the model output. Last but not
> least, I guess that having a standard way of working with geometry
> matrices also counts for something…
>
> Sorry if I come off as somewhat bitter, but I really counted on
> using models as an integral part of a project I’m working on, and
> now it seems it may not be all that integrated into jitter yet.
> -Nadav

v a d e //

http://www.vade.info
abstrakt.vade.info

#100671

You must be logged in to reply to this topic.