| General Track Data
|
|
Name, Time, Speed, Mode (Time/Speed)
| Name, Time, Speed, Mode (Time/Speed)
|
Fully imported.
|
|
Tracks
|
| Location of the path relative to world and parent of the moving
object.
| Location of the path relative to world and parent of the moving
object on 3DEXPERIENCE track. | Fully imported.
|
| Non-mapping track path data
| - | - When moving some types of objects, V5 tracks use a shot data format
that is not supported in 3DEXPERIENCE. If these types of tracks are
encountered during migration, a warning will be displayed and the
track will not be migrated. |
| Multiple instance tracks such as tracks that move cameras | Two 3DEXPERIENCE track references; camera as a moving object is not applicable in 3DEXPERIENCE. | - All imported tracks will be single, separate
entities. The name for imported tracks is always the instance name.
|
| Visualization properties of a track's path (Line color, type, and
thickness. Hide/show status.)
| Line color, type, and
thickness are set according to 3DEXPERIENCE CATSettings. | - |
| Shots |
| Position, compass offsets, durations
| Shots are referred to as T-Points in 3DEXPERIENCE. | Fully imported.
|
| Shot Flags
| - | - Shots generated by the pathfinder command when
collisions are disabled are marked with a flag and are rendered in
red. This flag (and the red coloring) will not be imported into 3DEXPERIENCE. |
| Moving Objects |
| The Products or Shuttles moved by the track.
The offset of the objects from the track.
| | Fully imported
|
| Shuttles as objects
| - | -
There is no object in 3DEXPERIENCE that is the equivalent to a Shuttle. If
a track moves a shuttle, the track will directly move the product
children of the shuttle. The offsets between the shuttle and its
children will be respected.
If the V5 track moves a shuttle and that shuttle has a
referencing shuttle, the referencing shuttle (and its children)
will not be migrated. This is because referencing shuttles provide
relative motion, which is not supported by the 3DEXPERIENCE tracks. |
| Motion interpolation |
| Linear interpolation
| Linear interpolation | Fully imported. Only linear interpolation is supported in . All migrated tracks
will use this mode.
|
| Non-linear interpolations
| - | -
If a V5 track using a different interpolation is migrated, a
warning will be displayed and the interpolation type will be set to
linear.
|
| Relations to non-product objects |
| Relations to the following types of objects will not be imported. A
warning will be displayed when this happens.
Section planes: both moved and associated
Bound analysis (clash/distance) Lights
| - | -
|
| Log Data |
| Log data and attributes
| - | - |
| Operations such as Split and Join generate a new track while
keeping the original track as a Log that is the child of the new
track. Any track that is only displayed as the log of another track
is not imported into 3DEXPERIENCE. A warning is displayed in the log whenever
this happens.
The Mirror operation is the exception to this rule as Tracks
that are the source for a Mirror operation are still displayed as
children of the Tracks node in the tree. | Track as log is not imported. | Partially imported.
|
| Special Cases
|
| V5 CATPart documents
| | Partially imported.
V5 CATPart documents are migrated as a pair of objects: a 3DEXPERIENCE
product object and a 3D Rep object. If a V5 track moves a CATPart,
the migrated 3DEXPERIENCE track will point to the generated product
object.
|
| Lights | | Partially imported.
V5 tracks can move lights. Although the same double transform shot
is used in this case, the shots are interpreted differently when
interpolating the light along the track. When a V5 track with a
light is migrated, the relation to the light is not migrated and
the shot data is copied directly. Because the 3DEXPERIENCE track does not
consider the data a special case, the 3DEXPERIENCE track path may not look
like the V5 track.
|