Robbie

If I want to fade between 2 jit.gl.nurbs using jit.xfade (having

matrixoutput to 1 on both) should I use 2 jit.gl.gridshapes? I have been

trying to modify the tutorial no 37 but arent having any luck.... Robert

If I want to fade between 2 jit.gl.nurbs using jit.xfade (having
matrixoutput to 1 on both) should I use 2 jit.gl.gridshapes? I have been
trying to modify the tutorial no 37 but arent having any luck.... Robert

newbi-question-xfading-between-nurbs

It's pretty straight forward. If you got that tutorial, this is easy.

I thought it may have problems with different dims and orders, but

that's fine. If you attach a patch, we can see where you may have

> If I want to fade between 2 jit.gl.nurbs using jit.xfade (having

> matrixoutput to 1 on both) should I use 2 jit.gl.gridshapes? I have been

> trying to modify the tutorial no 37 but arent having any luck.... Robert

It's pretty straight forward.  If you got that tutorial, this is easy.
 I thought it may have problems with different dims and orders, but
that's fine.  If you attach a patch, we can see where you may have
went wrong.

On 8/15/07, robbie b  wrote:
> If I want to fade between 2 jit.gl.nurbs using jit.xfade (having
> matrixoutput to 1 on both) should I use 2 jit.gl.gridshapes? I have been
> trying to modify the tutorial no 37 but arent having any luck.... Robert
>
>
>


I did have a quick question: how come the pak object for the left xfade

nurb, through [s nurby], controls both nurb positions? Shouldnt the [pak

position] object attached to the right nurb be in control of that nurb when

xfade receives a [xfade 1] message? EG below:

> It's pretty straight forward. If you got that tutorial, this is easy.

> I thought it may have problems with different dims and orders, but

> that's fine. If you attach a patch, we can see where you may have

> #P newex 273 348 101 196617 jit.op @op + @val 0.;

> #P flonum 308 262 35 9 0. 1. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 787 34 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 726 78 108 196617 jit.noise 3 float32 4 4;

> #P newex 726 107 89 196617 prepend ctlmatrix;

> #P newex 458 259 156 196617 jit.gl.nurbs foo @matrixoutput 1;

> #P message 536 608 55 196617 floating $1;

> #P flonum 302 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 264 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 224 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 193 558 103 196617 pak color 0.5 0.5 0.5;

> #P flonum 857 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 819 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 779 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 754 510 85 196617 pak scale 1. 1. 1.;

> #P flonum 876 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 838 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P flonum 798 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;

> #P message 496 557 94 196617 smooth_shading $1;

> #P message 595 557 90 196617 lighting_enable $1;

> #P newex 307 558 92 196617 pak poly_mode 0 0;

> #P hidden newex 536 491 50 196617 loadbang;

> #P message 408 557 81 196617 depth_enable $1;

I did have a quick question: how come the pak object for the left xfade
nurb, through [s nurby], controls both nurb positions? Shouldnt the [pak
position] object attached to the right nurb be in control of that nurb when
xfade receives a [xfade 1] message? EG below:

On 8/15/07, keith manlove  wrote:
>
> It's pretty straight forward.  If you got that tutorial, this is easy.
> I thought it may have problems with different dims and orders, but
> that's fine.  If you attach a patch, we can see where you may have
> went wrong.
>
> Email with questions,
> Keith
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #P newex 273 348 101 196617 jit.op @op + @val 0.;
> #P flonum 308 262 35 9 0. 1. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 308 283 48 196617 xfade $1;
> #P number 787 34 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 787 55 54 196617 dim $1 $1;
> #P button 726 51 15 0;
> #P newex 726 78 108 196617 jit.noise 3 float32 4 4;
> #P newex 726 107 89 196617 prepend ctlmatrix;
> #P newex 273 320 49 196617 jit.xfade;
> #P newex 458 259 156 196617 jit.gl.nurbs foo @matrixoutput 1;
> #B color 5;
> #P toggle 536 590 15 0;
> #P message 536 608 55 196617 floating $1;
> #P toggle 368 498 15 0;
> #P flonum 302 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 264 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 224 532 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 193 558 103 196617 pak color 0.5 0.5 0.5;
> #P flonum 857 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 819 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 779 483 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 754 510 85 196617 pak scale 1. 1. 1.;
> #P newex 307 581 42 196617 s nurby;
> #P flonum 876 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 838 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 798 531 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 496 534 15 0;
> #P message 496 557 94 196617 smooth_shading $1;
> #P toggle 595 534 15 0;
> #P message 595 557 90 196617 lighting_enable $1;
> #P toggle 141 538 15 0;
> #P message 141 559 44 196617 axes $1;
> #P toggle 389 534 15 0;
> #P toggle 348 534 15 0;
> #P newex 307 558 92 196617 pak poly_mode 0 0;
> #P hidden newex 536 491 50 196617 loadbang;
> #P toggle 408 534 15 0;
> #P message 408 557 81 196617 depth_enable $1;
> #P hidden message 536 513 14 196617 1;
> #P newex 770 555 95 196617 pak position 0. 0. 0.;
> #P toggle 454 589 15 0;
> #P newex 415 588 35 196617 sel 27;
> #P message 454 607 68 196617 fullscreen $1;
> #P newex 372 631 145 196617 jit.window foo @depthbuffer 1;
> #P newex 370 588 40 196617 key;
> #P number 178 87 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 178 115 63 196617 order $1 $1;
> #P number 119 87 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P message 119 115 54 196617 dim $1 $1;
> #P newex 288 171 42 196617 r nurby;
> #P user jit.fpsgui 73 193 60 196617 0;
> #P window linecount 3;
> #P comment 507 35 131 196617 1st and second ctlmatrices bang here;
> #P number 662 38 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P window linecount 1;
> #P message 662 59 54 196617 dim $1 $1;
> #P button 601 55 15 0;
> #P newex 601 82 108 196617 jit.noise 3 float32 4 4;
> #P newex 29 136 43 196617 jit.qball;
> #P number 74 87 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P toggle 29 87 15 0;
> #P newex 29 113 55 196617 metro 20;
> #P newex 29 167 55 196617 t b erase b;
> #P newex 210 228 156 196617 jit.gl.nurbs foo @matrixoutput 1;
> #B color 5;
> #P newex 29 388 80 196617 jit.gl.render foo;
> #P newex 601 111 89 196617 prepend ctlmatrix;
> #P comment 389 498 100 196617 draw as mesh;
> #P connect 6 0 5 0;
> #P connect 5 0 8 0;
> #P connect 8 0 4 0;
> #P connect 4 0 2 0;
> #P fasten 4 1 2 0 56 195 34 195;
> #P fasten 63 0 2 0 278 370 34 370;
> #P connect 4 2 14 0;
> #P connect 7 0 5 1;
> #P connect 17 0 16 0;
> #P connect 34 0 33 0;
> #P connect 19 0 18 0;
> #P hidden fasten 1 0 3 0 606 140 215 140;
> #P fasten 15 0 3 0 293 208 215 208;
> #P fasten 16 0 3 0 124 179 215 179;
> #P fasten 18 0 3 0 183 179 215 179;
> #P connect 48 0 47 1;
> #P fasten 49 0 47 2 269 552 260 552;
> #P connect 3 0 55 0;
> #P connect 61 0 55 0;
> #P connect 55 0 63 0;
> #P fasten 50 0 47 3 307 552 291 552;
> #P fasten 47 0 42 0 198 578 312 578;
> #P fasten 27 0 42 0 413 576 312 576;
> #P fasten 30 0 42 0 312 578 312 578;
> #P fasten 37 0 42 0 501 576 312 576;
> #P fasten 35 0 42 0 600 576 312 576;
> #P fasten 33 0 42 0 146 578 312 578;
> #P fasten 25 0 42 0 775 576 312 576;
> #P fasten 43 0 42 0 759 576 312 576;
> #P connect 62 0 61 0;
> #P connect 54 0 55 1;
> #P fasten 51 0 31 0 373 523 353 523;
> #P connect 31 0 30 1;
> #P fasten 52 0 21 0 541 626 377 626;
> #P fasten 22 0 21 0 459 626 377 626;
> #P fasten 51 0 32 0 373 523 394 523;
> #P connect 32 0 30 2;
> #P hidden fasten 26 0 28 0 541 531 413 531;
> #P connect 28 0 27 0;
> #P fasten 20 0 23 0 375 607 412 607 412 586 420 586;
> #P fasten 23 0 24 0 420 606 451 606 451 586 459 586;
> #P connect 24 0 22 0;
> #P connect 56 0 54 0;
> #P hidden fasten 26 0 38 0 541 531 501 531;
> #P connect 38 0 37 0;
> #P hidden connect 29 0 26 0;
> #P connect 53 0 52 0;
> #P hidden fasten 26 0 36 0 541 531 600 531;
> #P connect 36 0 35 0;
> #P fasten 11 0 9 0 667 78 606 78;
> #P connect 10 0 9 0;
> #P connect 9 0 1 0;
> #P connect 12 0 11 0;
> #P connect 58 0 57 0;
> #P fasten 59 0 57 0 792 74 731 74;
> #P connect 57 0 56 0;
> #P connect 44 0 43 1;
> #P connect 60 0 59 0;
> #P connect 39 0 25 1;
> #P fasten 45 0 43 2 824 504 809 504;
> #P fasten 40 0 25 2 843 550 831 550;
> #P fasten 46 0 43 3 862 504 834 504;
> #P fasten 41 0 25 3 881 550 859 550;
>
> On 8/15/07, robbie b  wrote:
> > If I want to fade between 2 jit.gl.nurbs using jit.xfade (having
> > matrixoutput to 1 on both) should I use 2 jit.gl.gridshapes? I have been
> > trying to modify the tutorial no 37 but arent having any luck.... Robert
> >
> >
> >
>

newbi question - xfading between nurbs