vue file format Fm: charles vaughn 72330,26 To: YOST Group
5 messages in this thread
76702,413
.. THE FOLLOWING SENT TO ANOTHER FORUM MEMBER IN ERROR..
We have attempted to use the DXF solution, 2 problems:
1: 2d motion generated from the polyline by 3ds, thus to get 3d motion
we must gen 2 lines xy then xz and attach to dummies to get
a 3d motion.
2: The data are REQUIRED to be frame accurate, so we must generate
a point for each frame. 3DS then places 2 keys at each frame point
causing us to have to manually remove the excess keys. THIS IS VERY
TEDIOUS when 6 or 7 hundred points are involved, and is magnified
2x by problem #1 above.
Cinetron is the manufacturer of professional motion picture animation
and optical effects computer systems, and as you might suspect, we have
massed a pile of stable motion software over the past 20 years and would
very much like to port this to 3ds both internally for use by our guys
who do legal visualization projects, and perhaps as a 3rd party supplier
to
3ds..
PS we're developers for AutoCad
Any interest?
Thanks
Charlie
Your problem #1 appears to be because you're creating a .shp 2D file from
the polyline instead of a .lft 3D path. Check out your DXF3DS documention
for info on how to make a .lft file.
I can't really help you with much else right now… I'm too busy. Sorry.
– G
Thanks, I'll try the LFT solution. As to problem #2, we can only hope(?)
that there is a solution in the wind. Thanks again
Charlie
Not sure this will solve your problem #2, but you can globally reduce the
number of keys in the Keyframer using the Time/Scale Segment command. For
example, if you've got 200 frames with a Position key at each frame, use
Time/Scale Segment to reduce the number of frames to 100, then use it again
to return the number of frames to 200. The result will be that the keys are
now on every other frame of the 200 frames.
– Jack
Jack, Many thanks, I'll try that and let you know how it works. Charlie