Civil 3D Connector - Known Limitations
- Sometimes, creating a viewable version of your Data Exchange might not be possible. In these cases, you will not see a specific error warning for the issue.
- Your changes might not be saved after you create a Data Exchange through the Connector.
- Adding the geometry to different layers in a Data Exchange for a pipe network should not trigger an update to the Data Exchange. However, this is causing the Data Exchange to be updated unnecessarily.
- Data Exchange creation fails for a few attached files due to failure of IFC export.
- Primitives such as lines, rectangles, and other similar objects cannot be selected when creating a Data Exchange using the All Objects filter.
- You might get an error message 'Error occurred when attempting to run translator exe' when creating a Data Exchanges from Civil 3D files.
- Civil 3D is unable to read parameters written from another Civil 3D file.
- Creating a Data Exchange using the By Object filter for Alignment and Profile is not working correctly.
- The current layer is turned off while creating a Data Exchange using the Layer State filter.
- The transparent Connector icon does not change with the selected theme of host application at runtime.
- Layer and Parameter mapping is not functional with Rhino and Tekla Connector Data Exchanges.
- The Filter By option in the Data exchange window does not remember your previous selection when you reopen it.
- Data Exchanges created using IFC import may not display any data when viewed in ACC.
- Creating or updating large data models through the Civil 3D connector might not generate a viewable.