orthogonalize p.transform produces the same result

looks pretty solid to me fn AreaOfUVPolyFace pobj mapc face = ( mverts = polyop.getmapface pobj mapc face; uvs = for v in mverts collect polyop….

fn AreaOfUVPolyFace pobj mapc face = ( mverts = polyop.getmapface pobj mapc face; uvs = for v in mverts collect polyop.getmapvert pob…

from the sdk for hPolygon Point3 *rgb The color values at the vertices. The rendering mode must include GW_ILLUM for these values to be used. Note…

there’s no bug you need to set the correct render limits unRegisterRedrawViewsCallback li fn li = ( gw.setRndLimits #(#lighting,#backcull,#colorVer…

you could do it the other way around and add a function publishing mxs nterface to either the dlm or dlc

dlx’s are handled differently so you can’t use them the same as a dlm or dlc also MAXScript plug-ins do not generally use ClassDesc so their .cpp …

not sure what you are talking about

it works I’ve tested it the paramblock that’s changing is a reference target to the helper plugin so when the paramblock sends the message to it’s …

yeah you can do that in your NotifyRefChanged function of the helper switch(msg) { case REFMSG_CHANGE: if(htarg == pblock) { ParamID lastp…

is the parameter a reference ?

sorry yes, all param blocks, I assumed it was just all params in the block

you can enable and disable notifications with IParamBlock2::EnableNotifications(BOOL onOff) though it’s a “global” switch for params in the block, s…

you could send that message yourself in a PBAccessor for that Parameter when it’s changed

the faces are the same order (geometry face == vertex colour face) but the vert indices within each can be different. vcol.jpg1276x790 17.4 KB f…