[maxmsp] [jitter] from .OBJ to matrixout
D
ceo at diurnal.net
Sat Sep 8 10:59:42 MDT 2007
- Previous message: [maxmsp] Re: Re: Latency interrupting Max/MSP performance
- Next message: [maxmsp] [jitter] from .OBJ to matrixout
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all I am still focussing on jit.mesh and discovered this: when importing an roof.obj file: # WaveFront *.obj file # safe as roof.obj g Extrude_NURBS v 100 35.755325 0 v 0 85.755325 0 v -100 35.755325 0 v 100 35.755325 -20 v 0 85.755325 -20 v -100 35.755325 -20 vt 0 1 0 vt 0.5 1 0 vt 1 1 0 vt 0 0 0 vt 0.5 0 0 vt 1 0 0 f 1/1 2/2 5/5 4/4 f 2/2 3/3 6/6 5/5 in jit.model (with matrixoutput 1 ) you'll get a matrix of 8 planes with dimensions 12 X 1 Focussing just on the vertices (first three planes) they are: 1. -0.25 0.1 0. 0.25 0.1 0. 0.25 -0.1 1. -0.25 0.1 <forward and back to the same vertex > 0. 0.25 -0.1 1. -0.25 -0.1 0. 0.25 0.1 -1. -0.25 0.1 -1. -0.25 -0.1 0. 0.25 0.1 <forward and back to the same vertex > -1. -0.25 -0.1 0. 0.25 -0.1 Why does jit.model not make it like this ?: 1. -0.25 0.1 0. 0.25 0.1 0. 0.25 -0.1 1. -0.25 -0.1 0. 0.25 0.1 -1. -0.25 0.1 -1. -0.25 -0.1 0. 0.25 -0.1 These give with drawmode quads exact the roof as declared in roof.obj Regards DO_Ray PS still wondering how a connection matrix looks like
- Previous message: [maxmsp] Re: Re: Latency interrupting Max/MSP performance
- Next message: [maxmsp] [jitter] from .OBJ to matrixout
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
