Transformation Data and Internalize Options

I have two questions about transformation data.

When I use the NonUniformScale Component the ScaleNU data that comes out of the "X" output doesn't match the Values that I expect to see. You can see from the screenshot I get ScaleNU(0.5,0.5,0.5).

I should point out that the transformation itself is working great. I am getting the correct geometry... but I am trying to figure out a method to save a couple of transformations that I can apply to other GH files that I would open Later.

Basically I need to Scale some Geometry by a specific amount, then Move it to an specific Position. I have this working well, I just want to be able to apply the same Transformations to Geometry in other files without Cutting and Pasting the whole Definition.

It may be worth noting that I am not wishing to have Live Updating... just simply hoping to calculate my Scaling and Positioning, then use those values in 20-50 other files.

I don't think I have explained this super clearly, but maybe somebody out there gets the gist. Let me know where I need to clarify.

Thanks for any suggestions.

Replies to This Discussion

Permalink Reply by Hannes Löschke on January 1, 2013 at 3:27pm

There's two errors in the string formatting method for translating the Scale Transform for display purposes. While the text ist wrong, the transform data is correct, as you already pointed out.

public override string ToString()
[...]

if (this.m_x == this.m_z && this.m_y == 1.0)
{
return string.Format("Scale2D XZ({0:0.#})", this.m_y);

-> should be m_x or m_z. m_y is always 1.0
}

[...]
return string.Format("ScaleNU ({0:0.#},{0:0.#},{0:0.#})", this.m_x, this.m_y, this.m_z);

-> will always return the x scaling factor m_x. should read {0:0.#},{1:0.#},{2:0.#}

As to your problem: there is a Transform Param. You can internalize your transformations and copy this param across your definitions or store it in a separate file. If your geometry is stored an separate layer in several Rhino files, you should look into the GeometryPipeline component.

Permalink Reply by AB on January 1, 2013 at 8:33pm

Hannes,

Thanks for the reply.

You answered both questions and I am using the Transform Param to internalize... then copying between files. This works fine for my needs and I won't sweat the fact that the Strings that Display Transformation data are off.

Thanks again.

RSS