2012

■ Some data cannot be translated completely. For example, product-specific
features such as dynamic blocks, can be represented visually but not
behaviorally.
■ Nested references are not merged into the host DGN file when exporting
a DWG file with nested references as V7 DGN. The nested reference is not
displayed in the host DGN file but the reference chain still exists.
■ AEC objects are not supported and users must use EXPORTTOAUTOCAD
command to convert the objects to base ACAD objects before exporting
to DGN.
■ AutoCAD does not support exporting linetype definitions with DGN files.
If a DGN file contains linetype definitions, but .rsc files do not contain
these linetype definitions in the Symbology path in MicroStation, then
when the DGN file is exported from AutoCAD and opened in MicroStation,
the linetypes do not display correctly because of missing linetype
definitions.
See the DGNEXPORT Conversion Table specific details about the scope of
exporting DWG objects and other data to DGN files.
NOTE Do not export drawings that include V8 DGN underlays to a V7 DGN format
file. The V8 DGN references cannot display in a V7 DGN file because the V8 DGN
file format is not a valid design file for the resulting V7 DGN file.
Recommendations
To optimize the data transfer to the MicroStation DGN file format, consider
the following recommendations:
■ Minimize the use of custom objects and other data unique to
AutoCAD-based products
■ Use simple linetypes as much as possible
■ Use simple hatches and hatch styles
■ Use simple gradients and gradient styles
■ Use simple dimension styles if possible
■ Use TrueType text fonts rather than SHX text fonts
■ Work primarily in one format, DWG or DGN, rather than switching back
and forth
Export MicroStation DGN Files | 1945