The Idea of Modo

#1

Hello everybody!
I post my first layout. So here is what i think of modo program: It has good ideas, but unless the functionality is exposed and quickly accessable, much time is wasted. So you see that i have exposed action center; action axis; and falloff.
Falloff has also addidional ‘falloff’ in the end of command line to turn them all on (lets say).
But probably there is a way to invert them also individually? I dont know. Its sort of combining (constructing) your action volume. Probably we want a cubic or conic falloffs also.
And a graph to adjust with bezier spline in the bottom. However we have some presets already like easein and easeout and such.

Problem is that in this mess the idea gets lost. Thats why the accessibility is so important.
Maybe to reflect current tool pipe with cursor some way, by having little f or c by.
Also id like to point out that selection current mode could be reflected in cursor like with Lightwave.

I have indicated also that however tool pipe shows center as ‘selection’, it does not show off in the custom layout. It has ‘tool.set center.select on’ command. So i also want this to show off according to tool pipe.

In this picture i illustrate that multiple falloffs show up in tool properties.

#2

I post 2 scripts that i have created for Lightwave and want to see in action with modo. I cannot perl.

@version 2.2
@warnings
@script modeler

/* Used to select row of 2-point polygons and construct a wall of 4-polygons of them

*/

main
{
selmode( USER );

if( !editbegin() ) error(“no points selected” );
size = polygons.size();
polys = polygons;
for(i=1;i<size;i++) {
pntID1 = polyinfo( polys[i] );
pntID2 = polyinfo( polys[i+1] );

pnts[1]= pntID1[2]; pnts[2]= pntID1[3];
pnts[3]= pntID2[2]; pnts[4]= pntID2[3];
v2 = <pnts[2].x,pnts[2].y,pnts[2].z>;
v3 = <pnts[3].x,pnts[3].y,pnts[3].z>;
v4 = <pnts[4].x,pnts[4].y,pnts[4].z>;

if(vmag(v2-v3)>vmag(v4-v2)){
buffer = pnts[4];
pnts[4] = pnts[3];
pnts[3] = buffer;}

polygon += addpolygon(pnts);
}
editend();
selpolygon(CLEAR); 
selpolygon(SET, POLYID, polygon);

}-------------

@version 2.2
@warnings
@script modeler

/* Used to select row of 2-point polygons and construct a wall of 4-polygons of them with jump pair

*/

main
{
selmode( USER );

if( !editbegin() ) error(“no points selected” );
size = polygons.size();
polys = polygons;
for(i=1;i<size;i+=2) {
pntID1 = polyinfo( polys[i] );
pntID2 = polyinfo( polys[i+1] );

pnts[1]= pntID1[2]; pnts[2]= pntID1[3];
pnts[3]= pntID2[2]; pnts[4]= pntID2[3];
v2 = <pnts[2].x,pnts[2].y,pnts[2].z>;
v3 = <pnts[3].x,pnts[3].y,pnts[3].z>;
v4 = <pnts[4].x,pnts[4].y,pnts[4].z>;

if(vmag(v2-v3)>vmag(v4-v2)){
buffer = pnts[4];
pnts[4] = pnts[3];
pnts[3] = buffer;}

polygon += addpolygon(pnts);
}
editend();
selpolygon(CLEAR); 
selpolygon(SET, POLYID, polygon);

}

#3

Thanks for the work you have put into this, illustrating some good and bad points.
This is one area I still can’t get my head around yet.
Wishing that LUX., would be more giving in areas like this.
I feel they need to become more involved every week on their own web site with demos PDF’s and tips of how to do.

I think it would be important for the support of its customer base.

Thanks Again.

#4

Thank you Nigel!

#5

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.