Yes, I understand it.
The whole point is to bypass this behaviour somehow and get pos A into
the deformer even if it is above envelope operator.

W dniu 2013-04-12 22:39, Alok pisze:
The whole idea of the operator stack to have progressive changes. If you have envelope operator below your custom operator then the point positions array will return current state after the update from the envelope operator.

For example, let's say an arbitrary point "x" in the mesh is at pos A. There is an envelope operator in the stack which moves "x" from pos A to pos B. Then in the your operator the pos of "x" will be pos B. However if your operator is below the envelope operator in the stack then the position of "x" will be pos A.

ALOK

GANDHI

/ chef directeur technique - lead technical director


[email protected] <mailto:[email protected]>

T:

*450 430-0010 x225

F:

*450 430-0009
www.modusfx.com <http://www.modusfx.com>

---------------------------------------------------------------------------------------------


MODUS

FX


120 Rue Turgeon,


Sainte-Therese (Quebec) CANADA J7E 3J1


Follow us on

Facebook <http://www.facebook.com/ModusFX>

&

Twitter <https://twitter.com/Modusfx>
**
On 12/04/2013 4:26 PM, Bartosz Opatowiecki wrote:
Hey,

Lets forget about node transformations, only vertices are being deformed.
If, within an update function I get a geometry like this:

Primitive prim = (CRef)ctx.GetInputValue(0,0);
PolygonMesh mesh(prim.GetGeometry(0,siConstructionModeModeling));
CVertexRefArray outPoints = outMesh.GetVertices();
CVector3Array pos = outPoints.GetPositionArray();

and put its data back:

Primitive outPrim(ctx.GetOutputTarget());
PolygonMesh outMesh(outPrim.GetGeometry(0,siConstructionModeModeling));
CVertexRefArray outPoints = outMesh.GetVertices();
outPoints.PutPositionArray(pos);

my output mesh should stay still even if envelope operator is below it.
Am I right ?

W dniu 2013-04-12 20:10, Alan Fregtman pisze:
From what you said you're already setting the pointpositions (aka deforming), so you have *already* /taken over/. You can set the deformation to be absolute if your data is absolute and taking the object's transform into consideration.

If you mean if you can disable operators downwards... no, you can't.



On Fri, Apr 12, 2013 at 12:18 PM, Bartek Opatowiecki <[email protected] <mailto:[email protected]>> wrote:

    Hi,

    I'm working on a customOperator which is deforimg a mesh.
    It is sitting at the top of an animation construction mode .
    I would like it to take over the deformation at some point
    and ignore entire construction stack below it.

    thanks,
    Bartek



No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 2012.0.2240 / Virus Database: 2641/5740 - Release Date: 04/12/13



Reply via email to