Morgan

I had a few questions regarding the same patch, for the patch and other files, see this post:

https://cycling74.com/forums/get-control-rate-data-back-from-gl-land/

(4 of 4) As I understand, it's more efficient to output the gl.model matrix only once and process as needed. In the patch attached to the above linked post, clicking the green toggle sets the gl.model to automatic 0, and starts banging the jit.matrix immediately below. I must be doing something incorrectly. When I switch off the gl.model's output, I only see a few of the edge polys. Is there a simple mistake there?

(4 of 4) As I understand, it's more efficient to output the gl.model matrix only once and process as needed. In the patch attached to the above linked post, clicking the green toggle sets the gl.model to automatic 0, and starts banging the jit.matrix immediately below. I must be doing something incorrectly. When I switch off the gl.model's output, I only see a few of the edge polys.  Is there a simple mistake there?

jit-gl-model-only-passes-fragments-of-the-polygons-with-automatic-0

the patch you are referencing did not upload, so can't really say without seeing it.

Hey Rob. Here is the compressed patch. I haven't had time to work on this much, but it seems to be part of how gl.model outputs texture and verts etc together. Using models made with 123d catch, they disappear, using duck.dae, the texture is the only thing that disappears

most likely what's happening is your model-file has multiple drawgroups, and therefore will output a separate matrix for each drawgroup.

you need to look at the jit.gl.model help file, in the "drawing" tab, so see the proper way to draw a multiple drawgroup model with gl.mesh.

you must set the gl.mesh to @automatic 0, and trigger a draw with each matrix received from gl.model.

this is also the only way to get the gl.mesh to draw using the gl.model's material settings.

try your model with the gl.model help file, and see if it draws correctly.

an alternative approach is to use something like poly~ and create a separate gl.mesh for each drawobject.

load up each gl.mesh with the corresponding drawgroup matrix once at initialization, and then do whatever you want with the gl.mesh.

you will have to handle the materials yourself in this case.

most likely what's happening is your model-file has multiple drawgroups, and therefore will output a separate matrix for each drawgroup.
you need to look at the jit.gl.model help file, in the "drawing" tab, so see the proper way to draw a multiple drawgroup model with gl.mesh.

you must set the gl.mesh to @automatic 0, and trigger a draw with each matrix received from gl.model.
this is also the only way to get the gl.mesh to draw using the gl.model's material settings.
try your model with the gl.model help file, and see if it draws correctly.

an alternative approach is to use something like poly~ and create a separate gl.mesh for each drawobject.
load up each gl.mesh with the corresponding drawgroup matrix once at initialization, and then do whatever you want with the gl.mesh.
you will have to handle the materials yourself in this case.


jit.gl.model only passes fragments of the polygons with automatic 0?