Troubleshooting ProjectWise & AutoCAD Civil 3d Performance

There is no “Silver Bullet” when it comes to improving performance with integrated Civil 3d. Every error cleaned up makes a difference.

PLEASE TEST in your environment before applying this to Production data.

• NO WORKING ON PROJECT FILES OUTSIDE OF PROJECTWISE EXPLORER – EVER
  Do NOT export them and then import them after editing. Do NOT edit them directly in your working directory. This is the number 1 cause for slow performance.
• ProjectWise version needs to be current – each version has performance improvements and additional features. 
  Project Participants (that work in Civil 3d) should be using ProjectWise version 10.00.03.271 as of 01/01/2020
  
  
• Installation of ProjectWise Data Shortcut editor – Only for the users that create, edit and control the data shortcuts. The data shortcut file should be maintained so that it is as error free as possible. Remember that when you have the DSProj file open it is checked out to you and nobody else can change it.
  
  
• Add DMSSET commands to the Civil3d startup LISP or to the profile
  • If using Sheet Set Manager set SharedSheetSets = 1 & SheetSetUnlockTime = 10 (sec) to 3 or 5.
  • Use #HOOKLESSREPATH = 1 to automatically repair broken data shortcuts
  • Set SHEETCHECKUPDATETIME = 120 (Sec) to 4 (240) or 5 min (300) to lengthen the time between checking for reference file changes.
  • INDEXCTL = 3 To organize files by layer and spatial data for faster file open and recalculation. (See the Autodesk help and website for more info on this.)
    
    
• The workstation should have as much memory as possible. Set virtual memory to 2x physical memory. (From the Autodesk discussion group)
  
  
• Each user’s ProjectWise network settings need to be adjusted so that only the needed datasources display. – Improves the connection and reconnection time.
  
  
• In ProjectWise Explorer create specific program names and Open actions in for every version. i.e. Civil3D 2016, Civil 3d 2017, … Using less specific program groups (such as ACLauncher) can cause integration to fail or open more slowly. Program groups should be like “AutoCAD.acadCivil3d.Drawing.PW.22.0.”
  By default the current template includes these program groups.

This article is on revision 2 and will be incorporated into the Green Book during 2020.

Please feel free to add comments and additional information.