Rendering Scene Design Database Design Import

Database Design Import (DBDI) enables the migration of CATIA V5 data stored in a legacy database into 3DEXPERIENCE.

This topic specifies the import correspondences between V5 data types and 3DEXPERIENCE content types, and the import result. The statuses for import results are fully imported, partially imported, and not imported (-).

This page discusses:

See Also
In Other Guides
Database Design Import (Dbdi)

Common Import Behavior

This section describes the behavior of CATIA V5 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.

V5 Data Type 3DEXPERIENCE Content Type Import Result
Applications (a command to import lights, environments and cameras). Imported as Technological Package or by creating a rendering scene:
  • If a Technological Package already exists, the new entities created in the 3DEXPERIENCE platform are stored in this existing Technological Package.
  • If there is no existing Technological Package, a new one is automatically created as soon as you create a light, a camera, an environment or a sticker.
 Fully imported
Lights Lights Fully imported
Environments Environments Fully imported
CamerasCamerasFully imported
StickersStickersFully imported
Shooting- -
Turntable Not persistent -
Shadow Stickers - -

ENOVIA VPM V5 Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

ENOVIAvpm Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

X-CAD Design Management Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

SmarTeam Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.

Adapter for X-PDM Database to 3DEXPERIENCE

There are no differences with respect to the common import behavior.