Thank you for using AutoCAD® Civil 3D® 2013.
This Readme contains important information about AutoCAD® Civil 3D® 2013 that may not be included in Help. For reference, save or print this document. It is strongly recommended that you read this entire document before you install.
Because AutoCAD Civil 3D is built on AutoCAD® and AutoCAD® Map 3D, it is recommended that you also review the AutoCAD and AutoCAD Map 3D Readme files at the following locations.
You are invited to help guide the direction of Autodesk design software.
If you participate in the Customer Involvement Program (CIP), specific information about how you use AutoCAD Civil 3D is forwarded to Autodesk. This information includes what features you use the most, problems that you encounter, and other information helpful to the future direction of the product.
See the following links for more information.
When you join, you will be able to view reports that can help you optimize your use of AutoCAD Civil 3D.
To turn the CIP on or off
Support for 64-bit Operating System requires database migration
Due to the requirement to support a 64-bit operating system, existing external project point databases and survey database files must be migrated to Microsoft® SQL Server® Compact 3.5 format from Microsoft Access Database format.
Support for 64-bit Operating System requires Vault project migration
Vault projects must also be migrated due to the requirement to support a 64-bit operating system.
When you perform the migration, Vault checks the project out, migrates the files, then checks them back in, and the version number is incremented.
The migrated project files are not backwards-compatible with previous versions of AutoCAD Civil 3D.
On the Prospector tab in Toolspace, expand the Projects collection. An item that requires migration displays the "out-of-date" icon to provide a visual cue that it requires migration. To complete the migration, right-click the item and select the migration command.
Data files
Data files are stored in the following folders.
Note: The ProgramData folder may not be displayed by default. To display the ProgramData folder, click the Start button > Control Panel > Folder Options. In the Folder Options dialog box, on the View tab, ensure that Hidden Files And Folders > Show Hidden Files And Folders is selected.
Open Source components can be found at the following location:
http://www.autodesk.com/lgplsource
Porting Code to AutoCAD Civil 3D 2013
COM API: If you are using the AutoCAD Civil 3D 2013 COM API, you need to update the object version to 10.0 (from 9.0 used in AutoCAD Civil 3D 2012). The objects and interfaces exposed have remained the same, but you should reference the new libraries, which are installed by default to: "C:\Program Files\Common Files\Autodesk Shared\Civil Engineering 100".
.NET API: In AutoCAD Civil 3D 2013, we introduced a namespace restructuring that will simplify referencing objects moving forward. The "feature" part of the namespace has been removed, so you will have to update your "using" statements to include the new namespace. As an example, previous releases will expose "Land" related classes and types in the "Autodesk.Civil.Land.DatabaseServices" namespace. In AutoCAD Civil 3D 2013, these classes and types will be in the "Autodesk.Civil.DatabaseServices".
Points
Surfaces
Profile Views
Labels
Pressure Pipes
Transportation
Survey
Other
COM Interop Changes
Interop DLLs are no longer registered as Primary Interop Assemblies (PIAs), and are deployed in the AutoCAD Civil 3D installation folder rather than the Global Assembly Cache (GAC). This means that these assemblies must now be added to Visual Studio projects using the Browse tab of the Add Reference dialog box, rather than from the COM tab as was done previously.
To compile previously written projects against AutoCAD Civil 3D 2013, you will need to remove references to all interop assemblies from your project, and then re-add them using the Browse tab.
The assemblies required for COM interop are:
Where <domain> is one of the four AutoCAD Civil 3D 2013 COM domains: Land, Roadway, Pipe, or Survey.
We recommend that you set the "Embed Interop Types" property for each interop assembly to True, as this will embed all referenced types into your target assembly, and the referenced interop DLLs are therefore not required at runtime.
Data Shortcut management through Windows Explorer
AutoCAD Civil 3D Project folders can be copied manually through Windows Explorer, including the associated "_Shortcuts" folder. This allows for a modest amount of project management, including elementary project phasing, or automated file structure creation. For example, if an AutoCAD Civil 3D project was created: "C:\Civil 3D Projects\Job123," and a set of base plans were developed utilizing Data Shortcuts, the entire project folder structure could be copied to "C:\Civil 3D Projects\Job123_Concept1."
In the above example, the _Shortcuts folder would be copied, but the project associations would still be pointing back to the original project: "C:\Civil 3D Projects\Job123." AutoCAD Civil 3D needs to re-create the project association.
Supported file types for Import in AutoCAD Civil 3D are a subset of the supported file types in AutoCAD
When importing a file using the Import command on the Insert ribbon, you may notice that there are fewer supported file types available in AutoCAD Civil 3D than are available in AutoCAD. When referring to the AutoCAD Civil 3D Help the list of formats supported by AutoCAD are documented even though those formats are not available in AutoCAD Civil 3D.
The VIEWBASE command in Help
The VIEWBASE command is described in the AutoCAD Civil 3D Help; however, this command is not available in AutoCAD Civil 3D.
AutoCAD Map 3D commands in AutoCAD Civil 3D
The following is a list of AutoCAD Map 3D commands that are not available in AutoCAD Civil 3D:
Installation of Storm and Sanitary Analysis 2013 fails if the installation path contains special characters
During installation when you choose to install Storm and Sanitary Analysis an error message will be generated if the installation path contains non-ASCII characters. To resolve this issue either de-select Storm and Sanitary Analysis from the install or modify the installation path to contain only ASCII characters.
Prior to installing AutoCAD Civil 3D 2013 and Storm and Sanitary Analysis 2013 all folders and all files from Beta versions of Storm and Sanitary Analysis need to be removed. The folders or files associated with Beta versions may cause issues as a result of invalid files left behind.
Installation of Storm and Sanitary Analysis 2013 after installing AutoCAD Civil 3D 2013
To install Storm and Sanitary Analysis after AutoCAD Civil 3D 2013 has already been installed it is required to restart the AutoCAD Civil 3D install and add Storm and Sanitary Analysis. It is not possible to add Storm and Sanitary Analysis as a feature through the Windows Control Panel.
Installation of Subassembly Composer 2013 after installing AutoCAD Civil 3D 2013
To install Subassembly Composer after AutoCAD Civil 3D 2013 has already been installed it is required to restart the AutoCAD Civil 3D install and add Subassembly Composer. It is not possible to add Subassembly Composer as a feature through the Windows Control Panel.
Microsoft .NET Framework 4.0 requires Windows Imaging Component
If the Autodesk Installer prompts you to install the Microsoft .NET 4.0 Framework, the .NET 4.0 Framework installer may prompt you to first install the Windows Imaging Component (WIC). This can occur if you do not have the latest Microsoft Windows updates or service packs. You are most likely to need WIC if you are running Windows XP SP2 without certain Windows Updates installed. If required, the Microsoft WIC installers are available at the following locations:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=f64654ac-6e26-41d9-a90a-0e7783b864ee
Uninstall order
When uninstalling AutoCAD Civil 3D 2013 it is important to observe proper order to avoid possible errors when removing products. Please uninstall in the following order:
It is recommended that text not be used in blocks assigned to fitting and appurtenance styles. The text in these blocks may become upside down and backwards as parts are rotated into position during layout. Label styles should be used instead to display any text required for fitting and appurtenance symbols.
Deleting a pressure network with the Fitting or Appurtenance vista open in the Panorama window may cause AutoCAD Civil 3D to close unexpectedly.
The Minimum Radius value for a curved pipe is not calculated correctly when the pipe size has been changed during the layout command.
The Follow Surface command may leave pipe segments at their original elevation for the first and last pipes selected if the alignment and profile view were created in the opposite direction than the pressure network parts. If this occurs, create a temporary alignment and profile view in the same direction of the pressure network and use the Follow Surface command in that profile view; the temporary profile view may be deleted afterwards.
Continuing the layout of a pressure network that has an alignment created from it may cause unexpected results if the new pressure parts that are created are perpendicular to an existing station of the alignment. The addition of new parts in this situation may cause the alignment to be created incorrectly. If only one pressure network part has been added, then you can grip edit a previous pressure network part along the alignment to resolve this issue. If multiple pressure network parts have been added, then you can recreate the alignment from the pressure network to resolve this issue.
Some unexpected results may occur when working in a UCS that is not set to World:
Some Feature and Command Settings are inconsistent with other AutoCAD Civil 3D objects:
Copyright ©2012 Autodesk, Inc.