Share

Known Issues in Autodesk Civil 3D 2025

This document lists known issues in Autodesk Civil 3D 2025.

Alignments
In AutoCad + Civil 3D OE, the operation of offseting a Civil 3D alignment will randomly fail. This is caused by the accuracy difference between AutoCAD Architecture and AutoCAD. Different Civil 3D Alignment components or Zooming in and out can lead to such random failures.
AutoCAD Graphic System
When multiple points are selected for deletion, the first selected point does not highlight when viewed in the wireframe visual style.
Surface hole/highlighting does not display when viewed in the wireframe visual style.
Highlighted lines in fast shaded visual mode have different line weights and colors.
Line styles in fast shaded visual mode display differently.
Cloud Collaboration (BIM 360)
If you write-lock cloud drawings, you can open the same drawing from different machines in edit mode which may result into conflict.
ESRI GIS Data Integration
In some cases it may take a long time to load layers in an ArcGIS connector web page due to a Microsoft and Qt collaboration issue.

Adjust the ArcGIS Connector windows size, drag the scrollbar, or click the item thumbnail to hide and show the details plane.
There is an error code issued when importing a layer with a property containing wchar. This also occurs with the import and save back workflow.
There is a stability issue when running the ArcGIS command after opening and closing a drawing with a Map AGOL layer.

It is important to run the ARCGISCONNECTOR command before opening drawings with Map AGOL layers.
Pressure Pipes
Pressure fittings do not display in the expected color when viewed in the wireframe visual style.
Subassembly Composer and .NET 8 Porting
The largest impact from the .NET migration is that Windows Workflow Foundation assemblies, the core engine of the Subassembly Composer (SAC), are no longer supported. We've adopted the following hybrid solution to maintain SAC assemblies in Civil 3D:

CoreWF: The open source porting of the Workflow Foundation runtime is used when PKT files build corridors.

PKT Design: PKT file creation continues using the .NET Framework. There is no .NET package or porting for the UI components of the Workflow Foundation.

What further complicates matters are the changes brought from the .NET porting: the visual basic scripting support is limited in Roslyn. Compiling the VB script in the .NET Framework is very fast, while it takes much more time to build an executable expression in .NET from the scripts.

As a reference, we are summarizing the known issues here in Civil 3D 2025:
  • Workflow running time is slower than before. This should only impact the first execution of a workflow such as creating a subassembly for the first time, or building the first applied station of a corridor. For a moderate corridor, the whole rebuilding time of a moderate corridor is improved. Please note that, open drawing time is not impacted. Specifically, the porting will not impact the loading time of the tool space.
  • Roslyn has stricter rules for VB script compiling. There may be cases where the designer does not show warnings and displays the subassembly preview, but it still may not run in Civil 3D. For example, if your workflow contains a Condition expression such as:

    AP1.X >= 1.0 _

    and AP1.Y >= 2.0 _

    Roslyn will expect more text after the ending ' _' and find it invalid. While we have fixed this issue, there could be more undiscovered inconsistency cases. If you discover failures, be sure to review your workflow and identify any possible invalid scripts, or pass the PKT file to us for closer diagnosis.

Was this information helpful?