Julien Bayle

I need to use rapid switching between OBJ models.

 is perfect to store OBJ as matrices... and switch BUT is there a better strategy instead of loading everything at launch time by using a uzi loading ALL files consecutively into an only 

 that output vertices matrices to each index of my 

Any experiences would be interesting for me :-)

I need to use rapid switching between OBJ models.
jit.gl.model is perfect with matrixoutput 1 as I want to draw with a jit.gl.mesh.

jit.matrixset is perfect to store OBJ as matrices... and switch BUT is there a better strategy instead of loading everything at launch time by using a uzi loading ALL files consecutively into an only jit.gl.model that output vertices matrices to each index of my  jit.matrixset ?

Any experiences would be interesting for me :-) 

Hi there,
I need to use rapid switching between OBJ models.
jit.gl.model is perfect with matrixoutput 1 as I want to draw with a jit.gl.mesh

strategies-for-pre-loading-a-lot-of-obj-models

can't you create several gl scenes (with something like jit.node) and render ony one at a time ?

could you do something where you had a bunch of poly~ instances with each voice loading a different model into a jit.gl.model object. then use the target message to send a bang to an individual voice that would output the matrix to the mesh which is outside the poly~? not sure if this would be better but it is an alternative.

i suppose you could also do something in javascript with an array of jit.gl.model objects

You can also enable @matrixoutput in gl.model and then you can collect all the data in a jit.matrixset object that goes to a jit.gl.mesh for reconstruction.

as explained, I already set up a system loading a series of model, getting the vertices as a jitter matrix from jit.gl.model and feeding a jit.matrixset

this is just this loading part and conversion from obj to matrix that I wanted to improve, eventually

OK ... It wasn't clear to me what you were looking for. I guess the obvious improvement would be to write the matrixset as a binary file and simply read that in instead of having to keep reading in the models with jit.gl.model.

OK ... It wasn't clear to me what you were looking for. I guess the obvious improvement would be to write the matrixset as a binary file and simply read that in instead of having to keep reading in the models  with  jit.gl.model. 

I used the technique of saving 3d models to be able to recall them very quickly using an index: (jit.gl.model@textureouput1> collect with jit.matrixset and save them as a binary file>jit.gl.mesh).

It worked well and was very fun with kinect's 3d scans.

Some trouble with uniform n of vertices of different models for texture mapping....

I used the technique of saving 3d models to be able to recall them very quickly using an index: (jit.gl.model@textureouput1> collect with jit.matrixset and save them as a binary file>jit.gl.mesh).
It worked well and was very fun with kinect's 3d scans.
Some trouble with uniform n of vertices of different models for texture mapping....

Hi Enrico, thanks, set of matrices as binaries seems the way to go as testcase was writing too . (matrixoutput 1 and not textureoutput but I think this is what you meant)

about number of vertices, indeed, matrixset have to be set up for the whole set. I used to use it with the maximum of vertices for each set I need.

Strategies for Pre-Loading (a lot of) OBJ models ?