How To Get Data Out Of A Section Drawing On Civil 3D 2014

Transcription

1 WisDOT Civil 3D Help Contents IMPORTANT: STWARE PROBLEM REPORT... 5 Corridor Data Not Dynamic in Section Views (updated 04/17/2015)... 5 Explanation of the Issue... 5 Fix... 5 Remaining Issues and Workarounds... 5 Civil 3D 2014 Sites and Feature Lines Disappear (updated 04/21/2015)... 5 Explanation of the Issue... 5 Fix... 6 Remaining Issues and Workarounds... 6 Project Drawing Migration Civil 3D 2012 to Project version migration... 6 Important potential changes between Civil 3D versions (updated 04/21/2015)... 6 New drawing format... 7 No backward compatibility... 7 Data Shortcut functionality changes... 7 Data Shortcut project migration Best Practices... 7 Factors to consider in project migration... 8 Before beginning the migration conversion to Clean and fix 2012 Project drawings and shortcuts first... 8 Make a copy of the project before migrating... 9 Project drawing migration... 9 Order of migration operations... 9 To save drawings with Civil 3D objects that are referenced to in other drawings To save drawings that are being used only as Xrefs Updating a C3D 2012 Corridor DWG into a C3D 2014 DWG How to Re-path all subassemblies within project corridor drawings WisDOT Civil 3D 2014 User Readme Civil 3D Standards Updates Before using the New WisDOT Parts Catalog Raster Design Page 1 of 107 Last updated: 6/18/2015

2 WisDOT Templates for Different dwg File Types Wis-Manager Palette Group Performance Problem (updated 04/21/2015) Custom Palettes from Civil 3D When Civil 3D Locks Up or crashes (updated 06/03/2015) Using the ClearAutodeskCache Tool What does this tool do? What folders does it clear? How to use this tool and when Temporary Fix for Missing Point Code Labels Explanation of the Defect with Point Code Labels Temporary Labeling Fix What to know about the WisDOT2014 Settings Profile To import or re-import the profile: Creating your own User Profile & Creating your own user Palettes (changed 04/17/2015) Project Data Translate DGN to DWG Workflow Using Civil 3D AutoCAD Civil 3D Import to AutoCAD Translate DWG to DGN Workflow using Civil 3D AutoCAD Civil 3D Project data workflow map (added 04/17/2015) Moving Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015) Transfer Files and Directories Use the Data Shortcuts Editor Reset Shortcut History and Folders Merging Civil 3D Project Files, Directories, and Data Shortcuts (added 04/17/2015) Rename Existing Directory and Transfer Files Use the Data Shortcuts Editor Merge Project Files WisDOT Subassemblies WisDOT Subassemblies and Superelevation (Civil 3D 2012 and beyond) WisDOT Subassembly Inputs Case 1 Single lane ramp, crown at lane edge, planar subgrade Case 2: Undivided Roadway with crown Page 2 of 107 Last updated: 6/18/2015

3 Case 3: Divided Roadway with median, baseline at median edge or center of median, crown between lanes Frequently Asked Questions Modeling Roadway Modeling Workflow Tips and Best Practices (added 04/17/2015) Roadway Modeling Tip Videos (added 06/18/2015) Modeling Crossovers Crossover Geometry Crossover Setup Surfaces Crossover Top Surface Crossover Datum Surface Pipe Networks Culvert pipes summary (updated 6/12/15) Storm Sewer Summary (updated 6/12/15) Storm and Sanitary Analysis (SSA) Project Options Settings for Storm Sewer Analysis Options Settings for Storm Sewer Other Storm Sewer Tips/Hints Sheet Layouts and Sheet Sets (added 06/03/2015) Subset Sheet Layouts Using Subset Sheet Layouts with Sheet Sets Layouts Best Practice Changing existing custom layout fields to Subset fields Exporting GIS Data (added 06/03/2015) Converting Civil 3D Parcels to GIS Shapefiles Verify the Coordinate System Export Civil 3D Objects to SDF Import SDF File into New Drawing Export Polylines with Attributes to a Shapefile WisDOT Civil 3D Linetypes (Updates added 10/05/2014) Linetype scale reference Linetype Scale MSLTSCALE Page 3 of 107 Last updated: 6/18/2015

4 PSLTSCALE CELTSCALE Working with Existing Files Settings for previous Templates Importing Older Linetypes into Older Drawings Workflow for Updating New Linetypes into Older Drawings Updating Layers with New ByLayer Symbology (added ) Workflow to update Xref files with old linetypes Working with the New Template Settings for New Templates Workflows for True size Linetypes Annotative Linetypes Linetypes Best Practices Migrating blocks between Civil 3D versions (added 04/17/2015) WORKFLOW 1 Migrating a small number of blocks Start a new block library drawing with 2014 template Insert older blocks using Design Center WORKFLOW 2 Migrating many blocks Start a new block library drawing with 2014 template Insert and explode existing block library drawing Clean up the new block library drawing Data Shortcut Best Practices (added 04/17/2015) Migrating a Project From Civil 3D 2012 to Civil 3D Moving a Project Location Renaming or Moving Individual Project Files Renaming Individual Drawing Objects Incorporating External Drawings into a Project Notable difference between Data Shortcuts in Civil 3D 2012 and in Civil 3D Updating settings and styles in production DWG files Civil 3D Styles and Drawing Settings Update AutoCAD Standards Update Using Design Center to transfer layouts from one dwg file to another (changed 04/17/2015) Appendix A Layers that changed linetypes Page 4 of 107 Last updated: 6/18/2015

5 Summary There are many good things to know about using Civil 3D that don t fit well into training material. This may include tips and tricks, troubleshooting, system settings, or processes that happen very frequently, such as importing and exporting files. This is the type of material found in this document. As new versions of Civil 3D are adopted, information about new features, best practices and adoption guidelines, as well as topics described above will be added to the specific Civil 3D Version User Readme section. IMPORTANT: STWARE PROBLEM REPORT Corridor Data Not Dynamic in Section Views (updated 04/17/2015) Explanation of the Issue Civil 3D 2014 has a defect which affects corridor XREFs in section views. The corridor objects do not update dynamically in the section views after changes are made in the corridor drawing and the XREF is reloaded in the section drawing. In the WisDOT workflow, corridors are xrefed into plan sheet section view dwgs to provide automated offset/elevation labels, and slope labels. If you have a section view dwg that was developed in C3D2014, the O/E and Slope labels in the section views may not be dynamically linked to the corridor, meaning these labels may be displaying incorrect values. Any pdf plots of plan sheet section view drawings done in C3D2014 might have incorrect labels also. Fix Autodesk has issued a software fix, and this has resolved the first issue above. Corridor edits are now reflected in the section views after the XREF is reloaded. This update has been applied to internal computers. The fix for external customers is found in wisdot-c3d14win7-64-importfiles.exe Remaining Issues and Workarounds Corridor objects still linger in section views when the XREF is detached. In order to get this data out of the section views follow this procedure: Detach the XREF Save and close the section drawing Reopen the section drawing Open the SAMPLE MORE SOURCES dialog box for the sample line group, and click Apply and OK Section styles still cannot be changed in the SAMPLE MORE SOURCES dialog box. Instead, change these in the VIEW GROUP PROPERTIES which is the most likely place this would be done anyway. Also, the corridor objects remain in the section views even if the XREF is completely detached. One last issue is that section styles cannot be changed in the SAMPLE MORE SOURCES dialog box after they have been added to the section views Civil 3D 2014 Sites and Feature Lines Disappear (updated 04/21/2015) Explanation of the Issue There is a known issue with the wisdot14.dwt that was developed using the Autodesk ACAD.dwt as its starting point. Using the ACAD.dwt template causes issues with sites becoming corrupt and disappearing. Once an audit is ran, the corresponding feature lines may get removed. Page 5 of 107 Last updated: 6/18/2015

6 Fix There is a fix for this. The hotfix for this has been updated on WisDOT devices as of For external use download and extract the following package: ftp://ftp.dot.wi.gov/dtsd/bpd/methods/civil3d-2014-win7-64/wisdot-c3d14win7-64-importfiles.exe. 2. Close Civil 3D 3. On the device to be updated, browse to C:\Program Files\Autodesk\Autodesk AutoCAD Civil 3D Change the extension of the existing AeccLand.dbx and AeccvBase.dbx files to.old, or move them to an archive location. 5. Browse to the extracted folder; \wisdot-c3d14win7-64-importfiles\autodesk-software-fixes\site- Feature-line-Fix folder 6. Copy the new AeccLand.dbx and AeccvBase.dbx files to C:\Program Files\Autodesk\Autodesk AutoCAD Civil 3D The date stamp for these file should be 3/27/2015 Please refer to the following link for further information: Disappearing-but-not-Feature-Lines-until-AUDIT.html Remaining Issues and Workarounds This fixes disappearing feature lines and sites after the fix is applied, and cannot bring back feature lines that have already disappeared. Those will need to be rebuilt. Project Drawing Migration Civil 3D 2012 to 2014 Project version migration Project migration is a choice that requires certain steps and processes be followed to ensure that all files are functioning correctly after migration. The process of changing a project between Civil 3D versions with different drawing formats needs to be thought of in terms of a complete project-based activity. This means: Additional bugs and hot fixes may need to be addressed through changes in workflows. Review the section; Important: Software Problem Report in the help document. Backward compatibility between 2012 and 2014 does not readily exist. Everyone working on a migrated project needs to be using the new version files for that project. This means not only Project Development staff, but also Technical Services, Planning, Consultants, etc. Once the decision to migrate the project is made, All DWGs, Data Shortcuts, and referenced DWGs that will still need to be edited or accessed in a project must be converted. This may require updates to base drawings created by others. The time and effort to plan and execute the project migration may require more than a few hours. Scheduling one day for project migration activities would be appropriate for most projects. Migrating project drawings involves a few more considerations besides the save-as steps and order of operations to perform the processes. Migrating all the necessary drawings can be a significant effort, and the variables described in the next sections should be recognized and understood before moving forward with the migration. Important potential changes between Civil 3D versions (updated 04/21/2015) This Civil 3D version change is referred to as a migration because of these six primary factors: Page 6 of 107 Last updated: 6/18/2015

7 1. Each version may use a different drawing format. 2. There may be no backward compatibility between Civil objects and dynamic capabilities 3. The dynamic relationships between civil objects may not function correctly when project data was saved from more than 1 software version. 4. Subassemblies use different source code files and are recompiled with a new path. 5. Data Shortcut functionality may have changed. 6. Project drawing files cannot be worked on while Edits to the Data Shortcuts files and accompanying drawings are being made. 7. Changes to WisDOT standards files and locations may be appreciably different in the latest version. New drawing format Civil 3D 2012 uses a 2010 DWG file format, and Civil 3D 2014 uses a 2013 DWG file format. In simple terms Civil 3D uses the DWG file not only as a place to store graphical information it also treats the DWG as something like a database file. To accomplish new functionality the files are written differently and new elements are added to the 2014 DWG files that does exist in the 2012 DWG files. The migration process relies on creating a copy of all Civil 3D files and Data Shortcut files and saving them into the new 2014 format, while keeping intact the original 2012 file. The original Civil 3D files are to be used for troubleshooting needs that may arise, and to ensure functionality was intact prior to the project migration into the 2014 format. No backward compatibility Since there is no backward compatibility of Civil 3D objects between the two DWG formats, there is no ability to turn a 2014 drawing back into a fully functioning 2012 drawing without a lengthy rebuild process. Success with a rebuild is not guaranteed to fully succeed. Data Shortcut functionality changes Migrating from Civil 3D 2012 to 2014 may require using the Data Shortcut Editor. 1. Data References are now cached within the host drawing and therefore no longer signal a broken reference. If the location of the Data Shortcut drawing or object within the drawing cannot be found, a cached version is used in the drawing. 2. You can remove a data shortcut from the Data Shortcuts collection in Toolspace, on the Prospector tab. This does not remove any data references to the source object that exist in a drawings, but it does prevent anyone from creating more references to the object. Data Shortcut project migration Best Practices 1. When migrating a project from Civil 3D version 2012 to version 2014 it is very important that you DO NOT do anything else with the project files other than migration. DO NOT move individual files within the migrated project folders. DO NOT copy individual files within the migrated project folders. DO NOT rename files or objects within these files. Following these instructions will prevent adding variables that will complicate troubleshooting. 2. Follow the How to Re-path all subassemblies within project corridor drawings and Project Drawing Migration sections below for the proper process to migrate your project drawings. If this process is followed, the data shortcuts will be migrated properly as well. 3. DO NOT perform a SAVE AS command within the data shortcut editor in an attempt to migrate the data shortcuts to the new version. This will create a copy of all of the XML files for the data shortcuts which can create a problem. This will happen automatically when the above steps are followed. Page 7 of 107 Last updated: 6/18/2015

8 Factors to consider in project migration WisDOT does not require project version migration as a rule. However, there are many reasons to keep up-todate on the current software version. Projects shared between in-house staff and consultant staff may require project migration to keep all staff on the same version of Civil 3D. Below are some factors to consider for the timing of a project migration. 1. The decision whether or not to migrate a project is not a black and white issue. The benefits of new software functionality and WisDOT standards may or may not outweigh the costs of migration. The completion level of design and the timeline to PS&E submittal are critical to this decision. 2. Project size and complexity will increase the level of effort necessary to migrate the project. 3. All people working on the project in Civil 3D must have the version of software being migrated to and are aware of the migration. 4. If project deadlines (30% submittal, 60% submittal, PS&E, etc.) could be jeopardized by the migration taking longer than expected, the project should not be migrated. 5. The expected time commitment to migrate the project can be absorbed by the design team. Before beginning the migration conversion to 2014 The time it will take to transfer a project will vary depending on: Amount of drawings How many drawings are consuming xrefs How many drawings are being xref d The amount of data shortcuts and drawings hosting data shortcuts The condition and version format of the original drawings The Data Shortcut project needs to be reviewed and corrected in 2012 prior to the project migration. Additional time should be expected to ensure the 2012 project is fully cleaned. All drawings and data shortcuts need to be working properly prior to going through the various migration steps outlined in the following section. Only those working directly on the migration of the project data to 2014 should be opening any of the drawings during the migration process. It is recommended that there should be a minimum amount of persons involved in doing the migrating tasks, preferably one person. The transfer is complete when all useable DWG files are saved in the 2013 format and a project integrity check has been accomplished. Clean and fix 2012 Project drawings and shortcuts first Verify that all Data Shortcuts within the 2012 project are working properly. Use the following steps as a guide to ensure that they are clean and working correctly. These steps require a working knowledge of file management and Project Data shortcut tools. These steps are required to be done in Civil 3D It is not recommended to migrate or use any of the project drawings and reference files that are not fully functional in the version they were initially created in. 1. All Data Shortcuts must be Synchronized and working properly. 2. Open the Data Shortcut project in the Civil 3D Prospector without project drawings open. a. This may require communication with the entire project team. 3. Expand the entire Data Shortcut tree for each object, and search for any Exclamation symbols. 4. Use the Right-click menu to remove or Repair Broken Shortcuts. Page 8 of 107 Last updated: 6/18/2015

9 a. An additional dialog may prompt to Repair All Broken Shortcuts. b. Respond yes. c. This may repair the rest of the broken Shortcuts in the project. d. Search for any more Exclamation symbols in the Data Shortcut tree in the Prospector. e. Close and reopen Civil 3D to save Data shortcut edits. 5. Review the file path for each data shortcut to be sure it is pointing to the correct file and location. Any data shortcut that is not pointing to the correct file or location needs to be corrected. Any drawing that used the incorrect data shortcut must be repaired. 6. Open each drawing that has a Data Shortcut, Data Reference or an Xreference one at a time and perform a registry application purge and a drawing audit. Registry Applications or regapps, are extended data attached to drawing objects created by civil 3D and ad-on applications. These regapps can severely bloat a drawing and make processing times very long. a. Type PURGE at the command line and press enter. b. Look at the command line and notice that there are many options under this command to choose from. Type the letter R or simply click on the word Regapps. c. When prompted to Enter name(s) to purge <*> press enter to accept the default of all. d. When prompted to Verify each name to be purged type N for no and press enter e. This will remove Regapps from the drawing f. To run the AUDIT command, type AUDIT at the command prompt and press enter g. You will then be prompted to fix any errors detected. Type Y for yes, and press enter. This will fix repairable errors found in your drawing. 7. Save each drawing. Make a copy of the project before migrating Save a copy of the entire project. The minimum for this is to create a copy of all the Civil 3D DWG files and Data Shortcut files. This project copy should be outside of the original project location, and outside of the project folder used to define the Data Shortcut project. Leave this version of the project in Use the original location to migrate to These will be the same folder structure for most projects. ( i.e. N:\PDS\C3D\ ) Project drawing migration When migrating a project to a version that has a newer drawing format like Civil 3D 2012 to 2014, it is important that ALL drawing files that are being used as external references (xrefs), Data References, and Sheet production drawings be saved as a Civil 3D 2014 drawing which utilizes the 2013 DWG format. Also any drawings that is being referenced into a drawing that you will be editing with Civil 3D 2014 needs to be saved as a Civil 3D 2014 drawing. It may not be necessary to transfer drawings or files to the new version if they are not going to be used in further project development and can be archived and PDF deliverables created from them. Order of migration operations The order in which DWGs are migrated to 2014 is important because Data Shortcut objects are more likely to break if they are not migrated first. Page 9 of 107 Last updated: 6/18/2015

10 Save DWGs in 2014 format. The order of file migration needs to be as follows: 1. Drawings that are only being used as External References. These drawings do not have any data shortcuts or data references in them. Typical Example: mapping file 2. Drawings with only Data Shortcut source objects that do not reference other files. Typical Example: Existing Surface file 3. Drawings with Data Shortcut References and External References where the source drawings have already been migrated. Typical Example: Corridor drawing, Plan sheet drawings 4. All other drawings. These drawings do not participate in any Data Shortcut References or External References. Typical Example: Title sheet, Construction Detail sheet The steps to properly migrate files with Civil 3D objects that use Data Shortcuts is different than DWGs that don't have Data Shortcut objects. These steps are defined below. There are special instructions for Corridor files below as well. The process of saving files that are used by other files first needs to be followed throughout the flow of data for a project. In practice, this means the order of file migrations will likely occur in the WisDOT project folder structure in the following order for commonly used folders: 1. BaseData 2. Design\AliProfs 3. Design\Corridors 4. RW 5. SheetsPlan This is a simple example to give the idea of the order of folder migration. Actual order for a project may differ. The important idea is to migrate DWGs that are used by other files first, and then migrate the DWGs that are using earlier DWGs. NOTE: Visual verification of data reference objects integrity after the conversion is crucial in this process. Do not assume object have made the conversion correctly without at least a visual inspection. To save drawings with Civil 3D objects that are referenced to in other drawings 1. Start Civil 3D Open the drawing that needs to be converted to a 2014 drawing. a. Verify that any data references or xref being consumed have been saved first (See Xrefs section below) 3. Save the drawing. 4. Navigate to the Data Shortcut tree in the Prospector a. In the right-click-menu select "Associate Project to Current Drawing" This step will associate the drawing to the Data Shortcut project. This process may be skipped if the Associate Project to Multiple Drawings tool is used on all the Data Shortcut drawings at once, after step 6. Page 10 of 107 Last updated: 6/18/2015

11 b. Verify the Working folder and the Select Project are correct in the dialog and press OK. 5. Save and close the drawing. 6. Repeat steps 2-5 above for all drawings where Data Shortcut objects are defined. 7. Verify no other users have any project drawing open. 8. With no project drawings open, synchronize and validate all Data Shortcuts in the Prospector. o Data shortcuts can become invalid if changes occur to the names or locations of drawings or reference objects. o When a data shortcut reference is broken, the icon is displayed next to the invalid data reference in Toolspace, on the Prospector tab. Validation reloads the data references if the drawing paths have not changed. Otherwise, you must repair broken references. 9. Hover over Data Shortcut in prospector, access Right-Click- menu, select Validate Data Shortcuts. Page 11 of 107 Last updated: 6/18/2015

12 10. If there are Broken Shortcut flags, access right-click-menu for an object that is flagged and select Repair Broken Shortcuts. You will need to browse and find the correct path and drawing where the object for the shortcut resides. If prompted to Repair All Broken Shortcuts select Yes/OK. 11. Close Civil 3D. To save drawings that are being used only as Xrefs 1. Start Civil 3D Open the 2012 drawing that needs to be converted. 3. Type XR at the command line to expose the External Reference palette. 4. If any of the files that are used as an xref have not be migrated, perform the following: a. Holding down the shift key select all the xref drawings in the File Reference List. Note: you do not need to select all the drawings at once if the list is long. It may process better if you divide you selection into multiple groups and then repeat steps 4-6. b. Right-click and select Open in the menu. c. Once the drawings are opened, there will be a tab for each drawing below the ribbon. d. Right-click on a tab to select a drawing. Note: select only the drawings that were opened from the xref list. e. Once the drawing is opened press the X on the tab. f. Select YES when prompted to Save changes to drawing. g. Repeat until all the drawing tabs have been closed and saved. 5. Save the original drawing that was opened. 6. You can now reopen the drawing to be edited. Updating a C3D 2012 Corridor DWG into a C3D 2014 DWG How to Re-path all subassemblies within project corridor drawings The following sequence should be applied to each project corridor drawing saved to Civil 3D These steps should not be taken until all other steps in the sections above have been completed. 2. Open the corridor drawing in Civil3D Synchronize all Data Shortcuts. 3. If the Event Viewer has been populated through any of these first steps, all the events should be cleared before proceeding. 4. Rebuild the corridor. If the Event Viewer shows events, clear the Event Viewer and then: o Open the Corridor Properties dialog and go to the Parameters tab Uncheck all the regions. Page 12 of 107 Last updated: 6/18/2015

13 Press Apply to rebuild the corridor with no regions constructed. Recheck all the regions. Press OK to rebuild the corridor with all regions constructed. Check the construction of the corridor in plan and corridor section editor. 5. In the rare case where the Event Viewer still shows events, review the Warning Descriptions, looking for:.net subassembly project, module, or class not found. If this error is found, please Methods Development at o The warning will also show the generic subassembly name. 6. If the drawing has more than one corridor, follow steps 3-5 corridor one at a time, for each corridor. 7. Repeat steps 2-6 for each drawing that has a corridor. 8. Remember to save the drawing after each corridor rebuilds correctly and before closing drawing. 9. Once corridors are built, verify all Data references are rebuilt in the drawing. 10. Close the drawing. WisDOT Civil 3D 2014 User Readme Civil 3D Standards Updates Internal staff should not use the ftp standards content for Civil 3D Customizations files can break. Updating Civil 3D 2012 from the ftp site still works. Before using the New WisDOT Parts Catalog It is strongly recommended to watch the parts catalog training material found in Raster Design Included with your Civil 3D 2014 install is AutoCAD Raster Design Methods does not have training or workflow documentation for Raster Design. More information concerning Raster Design functionality can be found at To run AutoCAD Raster Design 2014 click on the icon on the desktop, Raster Design 2014 on AutoCAD 2014 English, or go to Start>All Programs>Autodesk>AutoCAD Raster Design 2014 and select Raster Design 2014 on AutoCAD 2014 English. WisDOT Templates for Different dwg File Types WisDOT file templates are stored in C:\WisDOT\Stnd\C3D2014\DrawingTemplates If you are creating a Plat DWG, Use WisDOT14-plat.dwt to create the new file If you are creating a Pipe Network DWG, Use WisDOT14-pipe.dwt to create the new file If you are creating a Survey Point DWG and/or Survey Figures DWG, Use WisDOT14-etopog.dwt to create the new file For all other DWG file types, Use WisDOT14.dwt If you need Civil 3D Styles from another DWT, use the Import Style command which is found on the Manage ribbon. DO NOT IMPORT STYLES WITH THE IMPORT SETTGS OPT TURNED ON! Page 13 of 107 Last updated: 6/18/2015

14 Wis-Manager Palette Group Performance Problem (updated 04/21/2015) The Wis-Manager palette group, which includes blocks from the WisDOT block library, has been expanded in Civil 3D The slow performance issues have been resolved, and the palettes should open and perform as expected. Custom Palettes from Civil 3D 2012 There is no simple way to import Civil 3D 2012 custom palettes into Civil 3D Palette migration requires a multi-step process. Training material for creating, archiving, and recovering palettes is in development. Methods Development recommends waiting for this training, or contacting CAE Support for help before creating your custom palettes in Civil 3D This method will include exporting each palette object and then importing each palette object into a new palette defined and located in a specific user location. When Civil 3D Locks Up or crashes (updated 06/03/2015) Follow these steps to restart your session: 1. You may first need to use the Task Manager to end the current session of Civil 3D. 2. Make sure all sessions of Civil 3D are closed. 3. Restart Civil 3D using the Civil_3D_2014_WisDOT icon on the desktop. 4. Once Civil 3D has completed the initialization startup process the Drawing Recovery Manager should be open. Page 14 of 107 Last updated: 6/18/2015

15 a. If the Drawing Recovery Manager does not open go to the Drawing Utilities in the File pull-down menu and select Open the Drawing Recovery Manager. 5. Select every file or file grouping in the recovery pane, use the right-mouse-click menu, and delete. a. There should be no need to keep this list populated. Ignoring this step because you do not know where the other drawings in the list came from is meaningless. If you do not know, who does? These are specific to your computer user profile. 6. After you have deleted all the files and groupings listed, or if there were no files listed, close the Drawing Recovery Manager by pressing the X. 7. Close Civil 3D. Make sure all sessions of Civil 3D are closed. 8. Open the Windows Browser and type %temp% in the path field. Page 15 of 107 Last updated: 6/18/2015

16 a. This will set the path to your local user folder. 9. Select all the files in this folder and delete them. If you get a message that a file cannot be deleted, select the option to skip the file. a. Browse to C:\WisDOT\Stnd\Temp, then select all the files in this folder and delete them b. Optionally for the two previous steps, if you have the ClearAutodeskCache tool on your desktop or in C:\WisDOT\Stnd\C3D2014\Appdata\Profiles\Shortcut use this tool. It will do the previous step automatically. 10. Empty the Recycle Bin, after verifying any other files already in the trash are not needed. 11. Open Civil 3D. 12. At the Command Line key-in RECOVER. In the dialog that appears, select the last current drawing you were in when Civil 3D locked or crashed, and choose open. 13. Save the drawing once recovery is finished. 14. Repeat the last two steps one at a time for each drawing that may have been opened when the lock or crash occurred. 15. If the original drawing had xrefs attached to it, review the source drawing of each xref to ensure they can be opened by repeating the steps 12 and 13 on these drawings. If you experience a crash again at any point through these steps, start from the beginning of these steps. If you are still experiencing frequent crashes, contact DOT CAE Support at DOTCAESupport@dot.wi.gov You should now be able to work on your drawing again. Choosing to not work through these steps lessens your ability to be productive. Using the ClearAutodeskCache Tool The ClearAutodeskCache tool is an icon located on your desktop. If you do not have or see this icon on your desktop, please contact DOT CAE Support for help. What does this tool do? Running this tool will delete files and folders created in the temporary folder locations used by Civil3D to store temporary files use by the program while it is running. These files under normal circumstances will be removed by Civil3D once the program is closed. If an error or crash occurs, or memory resources reach a maximum level, these files that are created will not get removed, and when the size of these files gets large enough it will begin degrade the programs ability to properly use the resources that are available. The old AutoCAD phrase for this is clear the cache. What folders does it clear? For Civil3D 2012 it clears the files in: C:\Users\~username~\AppData\Local\Temp In Civil3D 2014 it clears the files in: C:\WisDOT\Stnd\Temp How to use this tool and when To use this tool, make sure all instances of Civil3D are closed, then double click the icon on the desktop and press the Start button on the Small dialog that appears. Once all the files have been deleted the dialog will show Cached Page 16 of 107 Last updated: 6/18/2015

17 Cleared. Press the Exit button to close the dialog. The ClearAutodeskCache can be used at any time that Civil3D is not running, and must be run if a crash of Civil3D occurs. This tool should also be used as maintenance and run on a regular basis during heavy Civil3D use at about once per week. This tool should also be used as the first way to troubleshoot sudden problems that seem to appear out of nowhere. The it was just working and now it is not type of problems. Temporary Fix for Missing Point Code Labels Explanation of the Defect with Point Code Labels A defect within AutoCAD Civil 3D 2014 has been found in which point code labels are not applied to certain subassembly points in cross section views when the corridor file is an external reference. However, these same point code labels, using the same code set style for the assembly, will show up in the source corridor drawing. Point labels are only missing where sample lines are not precisely located on a corridor frequency within each region and baseline. This is an issue which Autodesk is working to correct, but in the meantime the following fix is suggested. Temporary Labeling Fix The simplest workaround for getting the point code labels to display in cross section views is to set the <no codes> point code to use the desired label style within the code set style in the cross section drawing. The workflow is as follows: 1. Open the drawing in which the point code labels are not showing, and click on the Settings tab of Toolspace. 2. Expand the General menu. Within the General menu expand the Multipurpose Styles menu, and within that expand the Code Set Styles menu. 3. Right click on the Code Set Style you are using in your section views and select Edit. Page 17 of 107 Last updated: 6/18/2015

18 4. When the Code Set Style dialog box appears, locate the <no codes> point code, and set the label style for that code to the desired label style for the missing point labels. 5. Click Apply and OK to save the changes to the code set style. The point codes should now be labeled. NOTE: This will result in the labeling of any points without point codes associated with them. What to know about the WisDOT2014 Settings Profile MDU will need to update the Settings Profile on occasions to maintain standards tools. There are no plans or need to make any edits or updates to the CUI files or any of the workspaces associated with them. This means the user can create their own or edit workspaces without these being automatically updated or overwritten. The WisDOT2014 settings profile will always needs to be imported manually by the user. This is to ensure that any edits made by the user are not automatically overwritten. The following section will give directions on how to Page 18 of 107 Last updated: 6/18/2015

19 import and re-import WisDOT2014 profile after the previous imports, how to maintain their preference changes made to the WisDOT204 profile, and how to create and manage their own user profile. The user should be aware that the WisDOT2014 profile import file (not the profile but the file to create the profile) is automatically updated to reflect any path or especially palette changes each time Civil 3D is started. Some of these updates will not show up until the WisDOT2014 profile is re-imported which will overwrite the existing profile. Reference the Whatsnew document for changes that may require the WisDOT 2014 profile be reimported. The Whatsnew document can be found in the WisDOT Civil 3D Environment Help dialog, or at ftp://ftp.dot.wi.gov/dtsd/bpd/methods/civil3d-2014-win7-64/whatsnew-ex.pdf There is no way to merge Settings Profiles at this time so after re-importing the WisDOT2014 profile, all user defined settings will need to be reset manually. To import or re-import the profile: 1. Type OP at the command line, and the Options dialog will open Navigate to the Profiles tab If the Current profile label does not show <<C3D_Imperial>> as current, double click on the <<C3D_Imperial>> profile in the available profile list to set it current. The wisdot2014 profile cannot be set as current during this pocess. select the Import button Browse to Select the file WisDOT2014.arg 2. In the Import Profile dialog, change the name to <<WisDOT2014>>, and verify the Include path information is checked. Select the Apply & Close button Page 19 of 107 Last updated: 6/18/2015

20 3. In the Available profiles list highlight <<WisDOT2014>> and press the Set Current button Press the Apply button at the bottom of the dialog and then press OK. Creating your own User Profile & Creating your own user Palettes (changed 04/17/2015) Below are the directions to create your own user palette, which requires that you create your own User Profile. It is not required that you create your own user palette, but without a user palette you cannot add any content to a palette. The user palettes are not shared or updated like the wisdot standards palettes and are for your own personal use. 1. Confirm the existence of the folder C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes a. If you do not have a C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes folder already created, STOP. Do not continue. Contact DOTCAE Support for assistance. 2. Launch Civil 3D 2014, and right-click in model space and choose "options" 3. Click on the Profiles tab and click "Add to list" 4. Name your new profile MyProfile 5. Select MyProfile in the list and click "Set Current" 6. Click on the files tab and remove all entries under the Tool Palettes File Locations 7. Click Browse to add the new location with the same path as above... C:\WisDOT\Stnd\users\Myc3d2014\Mypalettes 8. Click "Apply" and then go back to the Profiles tab 9. Click on "Export" and navigate to C:\WisDOT\Stnd\users\Myc3d2014 and save the.arg file as MyProfile.arg. Press OK to close the dialog. 10. Open the ToolPalette. The palette should be empty. If the ToolPalette is not empty please review the previous steps. Use the right-click-menu to rename the New Palette to MyPalette or other suitable name. 11. Close Civil 3D 12. Navigate to C:\Users\<username>\AppData\Roaming\Autodesk\C3D 2014\enu\Support\Profiles. If you find a folder named \MyProfile, open the folder and delete the file Profile.aws a. If you do not find the folder and file above just continue with the following steps. 13. Launch Civil 3D 2014 again, right-click and choose "options" and go to the Profiles tab, set MyProfile current and then Export the.arg once more as described in step Create a new palette and add objects to the palette as you need. Note: The <<WisDOT2014>> profile will always be the startup profile, and you will need to set your MyProfile as the current profile before you can access your personal palettes. The Civil 3D 2014 update process will not update your MyProfile. Project Data Page 20 of 107 Last updated: 6/18/2015