Civil 3D on ACC/Forma: Cloud Storage Does Not Fix Bad Habits Highlights Them

Moving a Civil 3D project to ACC or Forma Data Management can make collaboration easier, but it does not magically make the project healthy.

A drawing can open. The Xrefs can appear. The surface can display. Everyone can nod approvingly.

Meanwhile, half the project may still depend on a file living in somebody’s Downloads folder.

Here are the biggest things to get right before ACC/Forma quietly turns into a cloud-hosted scavenger hunt.

Make Sure Everyone Has the Right Access

Project access and software licensing are not the same thing.

A user may be able to see the ACC project and open drawings but still lack the collaboration licensing or folder permissions required to create and manage Civil 3D data shortcuts.

Before production starts, confirm that every user has:

• The correct Civil 3D version

• The company-approved Desktop Connector version

• Access to the correct ACC/Forma project

• Permission to the required folders

• The required Autodesk collaboration license

When one user can create shortcuts and another cannot, do not immediately blame Civil 3D. Check licensing, folder permissions, the active working folder, and the selected data shortcut project first.

Keep the Whole Project in One Environment

If the drawings are in ACC but the data shortcuts are on the network, the LandXML is on someone’s C drive, and another designer is working from a downloaded copy, you do not have a cloud project.

You have a distributed hostage situation.

Active production drawings and their dependencies should live in the approved ACC/Forma structure, including:

• Source drawings

• Data shortcut files

• Xrefs

• LandXML files

• Surface source files

• Images and point clouds

• Project-specific support files

Avoid mixing current files between ACC, network drives, local folders, and email attachments. That is how duplicate shortcuts, broken references, and competing “final” drawings are born.

Open Civil 3D Drawings From Inside Civil 3D

This one sounds painfully obvious, yet here we are.

Open production drawings from inside Civil 3D using File > Open and the approved ACC/Forma project location.

Do not double-click a DWG from Windows Explorer and assume you opened the correct cloud file. Desktop Connector uses a local cache, and identical file names can make it very easy to open the wrong copy without realizing it.

Before editing, confirm:

• The full drawing path

• The correct project

• The correct data shortcut working folder

• That the drawing is not unexpectedly read-only

• That Prospector and External References are not showing warnings

  
  

A Surface That Displays Is Not Necessarily Healthy

One of the more entertaining ACC/Forma problems is the surface that looks completely fine while its source file is missing.

For example, a surface drawing may be stored in ACC, but its definition still points to a LandXML file on one user’s C drive. Civil 3D may retain enough surface data to keep displaying contours, so the problem stays hidden.

Until another user opens the file.

Or the surface needs to rebuild.

Or the drawing refuses to upload.

The fix

Review the surface definition, locate the missing source file, place it in the approved ACC/Forma folder, and update the surface to use that cloud-hosted source. Then rebuild, save, synchronize, and test the drawing from another workstation.

A yellow warning symbol in Prospector is not decorative.

Audit and Purge Do Not Fix Cloud Dependencies

A drawing can pass Audit and Purge and still fail to upload.

That is because Audit checks the drawing database. It does not confirm that every Xref, XML file, image, point cloud, surface source, or data shortcut path is valid.

When a file will not upload, check:

1. Desktop Connector Pending Actions

2. The complete reference tree

3. Surface definitions and source paths

4. Xrefs and data shortcuts

5. Files pointing to a local C-drive location

6. Missing or unsupported dependencies

Use Audit, Purge, and Recover as part of the investigation, not as the entire investigation.

If Audit says the drawing is clean, that only means Audit did not find what Audit was designed to find. It does not mean your LandXML file has stopped living under or looking at C:\Users\SomebodyWhoLeftSixMonthsAgo.

Let Desktop Connector Finish

Saving a drawing does not mean the cloud upload is complete.

Before handing a file to another user:

1. Save the drawing.

2. Close it.

3. Check Desktop Connector.

4. Confirm the upload finishes.

5. Verify there are no Pending Actions errors.

6. Make sure the file lock releases.

An unexpected lock often means Desktop Connector is still uploading or encountered an error. Do not bypass the lock by downloading another copy and creating a second version of reality.

Custom Civil 3D Parts Need Central Management

Custom pipe sizes, catalogs, subassemblies, fonts, plot styles, and other Civil 3D resources are not automatically protected because the drawing lives in ACC.

A custom pipe size created only on one user’s computer can disappear when a company deployment update overwrites the local catalog. Civil 3D then opens the drawing, cannot find the required pipe part, and the pipes may vanish or become invalid...and the drawing starts showing Audit errors that won't clear out.

The correct process is to:

• Create and test the custom part in a controlled catalog

• Have it reviewed

• Add it to the approved deployment source

• Push it to all project users

• Confirm the next update will not overwrite it

• Test the drawing from another computer

Repeatedly recreating missing pipes without fixing the catalog is not troubleshooting. It is adding fresh errors to an existing problem.

Test From a Second Workstation

A project is not validated because it works on the computer where it was created.

That machine may already contain cached files, local XML files, custom catalogs, old network mappings, and support paths that nobody else has.

Have another properly licensed user open the critical drawings and confirm that:

• Xrefs resolve

• Data shortcuts synchronize

• Surfaces rebuild

• Pipe parts are available

• No dependencies point to another user’s C drive

• The drawing saves and uploads successfully

This simple test catches an impressive number of problems before they become milestone-week emergencies.

Issues and Fixes

The Takeaway

ACC/Forma provides cloud storage, version history, permissions, and collaboration tools.

It does not automatically repair Civil 3D references, eliminate local dependencies, manage custom catalogs, or stop users from opening the wrong copy of a drawing.

The healthiest Civil 3D cloud projects have:

• Correct licensing and folder access

• One controlled project structure

• Proper file-opening procedures

• Managed data shortcuts

• No user-specific dependencies

• Approved Desktop Connector versions

• Completed synchronization before handoffs

• Testing from more than one workstation

The real test is not whether the drawing opens for the person who created it.

The real test is whether someone else can open it from ACC/Forma, resolve everything, rebuild what matters, save it, and successfully send it back to the cloud without Civil 3D developing a new personality.

Thanks for stopping by the Den! It's not a bug, it’s a feature. Allegedly.

Images provided by ChatGPT 2026.