I have some 2d faces with elevation data per face (i.e. elevation is dep
faces).
When I try to Rubbersheet this, DX complains:
ERROR: RubberSheet: Invalid data: invalid data dependency: faces
If I Post(positions) before Rubbersheet, I get the same error (that is, Post
does nothing but
Ribbon creates triangles in 3d even if the input data are 2d (a feature).
Its z-component is telling AutoAxes to do what you don't want.
Try the following to remedy the situation:
Ribbon
|
Remove(, normals)
|
Mark (,positions)
|
Compute ([a.x, a.y])
|
Lloyd A Treinish:
If I remember right, to use RS, you'll need to decompose to triangles --
try Refine.
Otherwise, try the following to not use RS, which you would probably
prefer...
Mark (,positions) |
Compute ([a.x, a.y, b])
Thanks Lloyd. Refine(triangles) works well.
The
Thanks anyway, but my plot is the same regardless of this trick (and the ribbon
is still a surface). But in fooling with it, I discovered that my use of
Translate may have been the thing messing the axes up. I cut out any
translation in the z dimension, i.e. [.0001 .0001 0], and everything plots
The issue is AutoAxes getting something with 3d positions. I figured it
was Ribbon, not knowing about Translate in your network. If you had taken
the Translate out and left Ribbon the way it was, the problem would have
still been there.
Why do you need Translate? Is it because you have
I believe you want to use the fuzz attribute on the the ribbon
to get it to be on top of the rest of the plot without actually
making the thing 3D.
On Wed, 2001-10-24 at 12:03, Sharon Gibson wrote:
Thanks anyway, but my plot is the same regardless of this trick (and the
ribbon
is still a
The issue is AutoAxes getting something with 3d positions. I figured it
was Ribbon, not knowing about Translate in your network.
If you had taken the Translate out and left Ribbon the way it was, the
problem would have still been there.
I suppose the 3d positions could wreak havok somewhere
I'll see if I can beat him this time. ;-)
Try page 114 of the User's Reference. It's the Object Fuzz
entry under the Display Module documentation. Or if you
don't want to download the manual, you could do context
sensitive help on the Display Module in a net and keep
clicking next until you
