Automatic Point Group Updates

Automatic Point Group Updates sometimes happen on a delayed basis. As an example, this happens when using the Survey Tab in Toolspace to Import, Reimport, or "Insert to Drawing".

CreateAlignProf

When the source object is a Feature Line, the CreateAlignProf command ignores curves, and creates a tangent segment that cuts directly from end to end of the curve. However, the CAPFeature or CAPSurface command may work instead. C3D 2016, SP2 only: There is an issue in the API that creates profiles. Before running one of the Sincpac commands which creates a profile, please manually create a new Site, then run the command. You may safely delete that Site (providing it was used for the new alignment) after the command completes. Autodesk is aware of this issue and working on a fix.

Dynamic Links

Deleting a PVI with a Dynamic Link will cause that Dynamic Link to jump to an adjacent PVI, if that adjacent PVI does not already have a link. This is a side-effect of the way that Profiles are defined in Civil-3D. Currently, the only workaround is to delete the Dynamic Link before deleting the PVI.

If the option is turned on for displaying update messages when Dynamic Links are being updated, the message does not appear in the command window until after the update is complete.

There is also an issue where Corridors do not always get flagged as being "dirty" when Dynamic Profile Links update, which means automatic corridor rebuilds will not be triggered. In this situation, rebuild the Corridor by right-clicking on the Corridor in Prospector and selecting "Rebuild Corridor".

Entity Tracker

The EntityTracker sometimes returns odd results when hovering the cursor over Civil 3D elements such as Corridors and Surfaces.

Point Group and Style information cannot be displayed for Cogo Points that are in XREFs.

Layer commands

The layer commands (SPLayOff, SPLayFrz, SPLayIso, SPLayMch) currently do not work on all entities. Most notably, they do not work on C3D Surfaces - instead, they work on the overall Surface object layer, just like the default AutoCAD layer commands. They also do not currently work on entities found in XREFs.

ParcelOffset

The ParcelOffset command does not return correct results in all cases. It can be confused by very short segments, or may create erroneous loops in some situations, and does not detect narrow strips where the offsets from either side overlap each other.

Perp2d/3d Osnap toggle

When this is set to "Perp2d Osnaps" there are some AutoCAD commands which get confused. One such command is Circle by TTR. Setting this toggle back to the normal AutoCAD perp osnap (3d) will then allow these commands to function as expected. Either toggle it using the 3d/2d icon in the tray or with the command Perp2dtoggle.

PerpCheck

The PerpCheck command cannot identify all errors in Parcels. There are some errors that appear to be created by floating-point precision error. The gap appears to be closed, but the Parcels cannot correctly-form. In this situation, the PerpCheck command is also unable to find the error.

If you can find the location of this error, it can usually be fixed by grabbing a Parcel line and using OSNAPs to snap it to the linework it should attach to. This usually fixes the problem with the Parcels. The hard part is finding the location of the problem, since the PerpCheck routine cannot detect it.

PLProfile

The PLProfile command currently cannot create Profiles with vertical curves. The Profile must be created from linework that runs from PVI to PVI, then the vertical curves can be added.

The Ribbon Interface

Currently, the Ribbon Interface is force-loaded into the current Workspace. Some commands (such as the CUI command) will remove the Sincpac-C3D tab from the Ribbon. If this happens, you can get the Sincpac-C3D tab back by reloading your current Workspace. You may also use the SPRibbonEnabled command to refresh the Sincpac-C3D tab in the Ribbon. (Note: the Ribbon Interface is not available in the 2008 and 2009 versions.)

SPParcelInverse

The very first time this command is used, the palette does not display the contents completely. Just slightly adjust the size of the palette and it will then display correctly thereafter.

StakeFeatures

Intervals for the StakeFeatures command use the 3D length along 3D-Polylines, instead of the 2D length. Intervals are correctly measured along standard polylines, Feature Lines, and Survey Figures.

Quicksets

When Importing and Exporting Quicksets between drawings, items referred to in Quicksets are not imported/exported. In particular, Styles and Layers are not imported/exported with the Quickset, but must be transferred separately (i.e., drag and drop Styles in Toolspace, and use Design Center to drag and drop Layers).

General Alignment and Profile issues

Currently, some commands that involve entering stations on alignments only work with the Raw Station as input. For example, the StationEquation command only understands raw stations as input.

There is a general issue with Profile Labels in Profile Views.

In Civil-3D 2009, Profiles created through the API are erroneously flagged as being "From File", and display the "From File" icon instead of the "Finish Grade" icon. For many usages, this does not make a difference. But for some usages, these Profiles are not available. For example, these Profiles are not available when placing vertical geometry labels on Alignments. Currently, the only workaround is to create a new FG Profile on the Alignment. Then right-click on the "bad" Profile, select "Edit Profile Geometry", and use the "Copy Profile" button to copy the "bad" Profile into the empty FG profile. Then delete the "bad" Profile. Hopefully this issue will be addressed with a service pack from Autodesk.

Large Fonts

The display of some controls is incorrect when Large Fonts are enabled (120dpi on Windows Vista or greater than 100% on Windows 7).

Installation Issues

A crash may result if the Sincpac-C3D is not loaded during Civil 3D startup. To avoid this issue, either make sure the Quux.SincpacC3D.dll is loaded from the acad.lsp file, or use the installer package, which configures the Sincpac-C3D to load automatically during Civil 3D startup.

Windows Vista/7 may complain if you leave the Sincpac.CUI file in the Sincpac-C3D installation directory. To get around this problem, copy the CUI file to the same directory as your other CUI files, then add it as a Partial CUI.