Hi Steffen,
I'm not sure I understand the meaning of "origin" here.
If I understand the problem, some parts have their origins at places that make their relative location to other parts arbitrary, and some parts have their origin such that rotations about the origin do not provide the natural rotation for the part.
- Is the purpose of this META to allow editors to place the part at an initial location in the model model that is "logical" relative to the rest of the user's parts?
If so, what is the rotation matrix for? Specifying an initial rotation?
If so, is it enough to provide a -single- origin statement?
BrickSmith 3.x has a "relative parts" file that gives a series of matrices for inserting new parts based on a -specific- parent. For example, 4624.dat (Wheel Rim 6.4 x 8) can be placed relative to 13 different parent parts, but the transform varies based on the location of the wheel pin for each one.
- Is the purpose of the META to allow editors to rotate parts logically regardless of the original origin (e.g. 3938.dat hinge 1x2 top)?
If so, isn't there an existing unofficial META !ROTATE that specifies a rotation axis from MLCad? (I think I have this totally munged in my brain, I just have a vague memory that there's already an unofficial META I could pick up in Bricksmith some day).
I _do_ think being able to "fix" the origin after the fact is potentially valuable, and I don't want this post to turn into too much of "the great is the enemy of the good". But I'd like to understand under what use case we'd use this new META in Bricksmith...
Thank!
Ben
I'm not sure I understand the meaning of "origin" here.
If I understand the problem, some parts have their origins at places that make their relative location to other parts arbitrary, and some parts have their origin such that rotations about the origin do not provide the natural rotation for the part.
- Is the purpose of this META to allow editors to place the part at an initial location in the model model that is "logical" relative to the rest of the user's parts?
If so, what is the rotation matrix for? Specifying an initial rotation?
If so, is it enough to provide a -single- origin statement?
BrickSmith 3.x has a "relative parts" file that gives a series of matrices for inserting new parts based on a -specific- parent. For example, 4624.dat (Wheel Rim 6.4 x 8) can be placed relative to 13 different parent parts, but the transform varies based on the location of the wheel pin for each one.
- Is the purpose of the META to allow editors to rotate parts logically regardless of the original origin (e.g. 3938.dat hinge 1x2 top)?
If so, isn't there an existing unofficial META !ROTATE that specifies a rotation axis from MLCad? (I think I have this totally munged in my brain, I just have a vague memory that there's already an unofficial META I could pick up in Bricksmith some day).
I _do_ think being able to "fix" the origin after the fact is potentially valuable, and I don't want this post to turn into too much of "the great is the enemy of the good". But I'd like to understand under what use case we'd use this new META in Bricksmith...
Thank!
Ben