BOGO with Red Transit

Steve Hill, an Autodesk Authorized Developer and owner of Red Transit Consultants, LLC,  has informed me that he has an offer to extend to the public a purchase for 1 license and receive a second license for free!!

For any of his apps, with the exception of Pipe Network Productivity Tools, if you purchase 1 license he will provide a second license for free.

https://apps.autodesk.com/en/Publisher/PublisherHomepage?ID=22SPPLFQU42A

For Pipe Network Productivity Tools – Purchase 10 licenses, get 1 free get 2 free, Purchase 15 licenses, get 2 free get 3 free, Purchase 20 licenses, get 4 free get 5 free.​ See the attached ROI document if you’re interested.

https://apps.autodesk.com/CIV3D/en/Detail/Index?id=5524458269357786704&appLang=en&os=Win32_64

To take advantage of this offer, login to the Autodesk App Store and purchase the apps from their respective pages and select the quantity you desire. Send Steve an email after you make the purchase, and he will credit your account with the free licenses in addition to the purchased licenses.

**This offer is not valid with any previous purchases of apps prior to the date of this email. This offer is only valid through Friday June 30th, 2017**

Steve Hill’s email address is Steve@RedTransitConsultants.com.

Civil 3D 2018: What’s New

Another year has come and gone, but it brings forth new technology and excitement to dive into. In this blog, I will cover the new features of Civil 3D 2018.

The first thing I want to mention is the new drawing format. I think many of you became spoiled with the backward compatibility that Civil 3D offered with versions 2013-2016. Let’s face it; Civil 3D was NEVER backward compatible until the aforementioned versions. So, what’s the big deal, right? All the AutoCAD based products have this new format. If you’re moving to 2018, make sure you are willing to stay on 2018.

So let’s take a look at these nice new features…

Drawing format

Below you will see that nice, new drawing format:

2017-04-17_14-02-50

Offset Profiles

You can create dynamic offset profiles using the same command you use to create offset alignments. The profile geometry is offset using a default cross slope which you can modify by editing the profile properties.

In the offset profiles the geometry of the parent profile is replicated in cases where there is a consistent cross slope from the parent profile. For example, a vertical curve in the parent profile is a vertical curve in the offset profile when the cross slope that is specified for those stations is consistent, as shown in the following illustration.

2017-04-17_14-08-08

Note: Vertical curves in offset profile geometry are tessellated as multiple straight segments as shown below when the profile is superimposed onto another profile view. For reviewing and editing the offset profile geometry, insert the offset profile into its own profile view by using the Create Profile View command and selecting the offset alignment.

2017-04-17_14-08-24

In areas of the offset profile where there are vertical curves and there is a transition between one cross slope to another cross slope, as specified in the Offset Parameters tab of the offset profile properties, the vertical curve geometry that was replicated from the parent profile will not be preserved. Instead, straight lines are added between control points to approximate the curve as shown in the following illustration.

2017-04-17_14-08-41

Offset profiles are created in a dynamic state by default. A dynamic offset profile automatically updates to reflect changes in the elevation or geometry of the parent profile and parent alignment. When an offset profile is dynamic, you can add cross slope regions on the Offset Parameters tab, but the profile geometry cannot be edited.

You can change the update mode for an offset profile on the Profile Data tab of the Profile Properties dialog box.

Relative Feature Lines

Feature line elevations can be obtained from a surface and can also be relative to a surface, so if the surface is updated, the feature line is updated.

The update behavior of relative feature lines is different depending on whether the feature line was set to be relative to a surface when it was created, or whether it was created at absolute elevations and then set to be relative.

The following illustration shows a feature line in green drawn so that it is follows the surface elevations (shown in a dashed gray line) at a positive elevational offset. This feature line was created so that it is relative to the surface.

2017-04-17_14-14-20

If the surface is edited, the feature line is updated automatically and maintains the elevational offsets, as shown in the following illustration.

2017-04-17_14-14-35

Behavior of feature lines created at fixed elevations, and then set to be relative
The following illustration shows a feature line that was drawn at fixed elevations with no relationship to the surface. If the surface below it is edited, the feature line elevations will not update.

2017-04-17_14-14-47

The feature line is then set to be relative to the surface. This creates a relationship between the feature line and the surface but does not reset the feature line elevations to follow the surface.

2017-04-17_14-14-59

However, the relative elevational offsets between the feature line and the surface will now be maintained if the surface is edited, such as if the elevation is lowered, as shown in the following illustration.

Note: Feature lines created at fixed elevations, or from grading objects, or that were draped on a surface but not relative to it all share the behavior described in this section if they are subsequently set to be relative to a surface. If you want to reset the elevations of feature line to fully follow a surface, you can use the Elevations from Surface command.

Using relative feature lines as data in surface definitions:

  • If you want to use a relative feature line as breakline or boundary data in a surface, make the feature line relative before defining it as a breakline or a boundary. A non-relative feature line that is defined as data in a surface cannot be made relative to any surface.
  • If a relative feature line is defined as breakline or boundary data in a surface, its relative surface association cannot be changed.
  • Avoid adding a relative feature line as a breakline or a boundary to the same surface to which it is relative.
  • Issues can occur as a result of circular dependencies if feature lines that are relative to different surfaces are then added as breaklines or boundaries to each other’s surface definitions. For example, if Feature Line 1 is relative to Surface 1, and Feature Line 2 is relative to Surface 2, issues can occur if Feature Line 1 is defined as data in Surface 2 and Feature Line 2 is defined as data in Surface 1. In such a situation, rebuilding each of the surfaces will cause the other one to become out of date.

Editing relative feature lines:

Feature line editing commands are supported for relative feature lines.

When you open the Grading Elevation Editor for a feature line that is set to be relative to a surface, you will see the selected surface listed in the Grading Elevation Editor, and the editable feature line points will be shown as being relative to the surface.

You can specify relative elevation options by using the following features in the Grading Elevation Editor.

2017-04-17_14-15-14

For a feature line that was not previously set to be relative to a surface, when you open the Grading Elevation Editor and then select a surface from the Relative to Surface list, the Elevation Derived From column is initially set to Absolute Elevation for all points and does not automatically change to Relative to Surface. Use the drop-down list to select Relative to Surface for the points that you want to be relative.

Updating elevation points on a relative feature line:

When you create a feature line and assign elevations based on a surface, you can select the Insert Intermediate Grade Break Points check box. This creates elevation points along the feature line where the feature line crosses surface TIN lines. These points are shown as green circles in the following illustration.

2017-04-17_14-15-26

If you edit or otherwise move a relative feature line, or if the surface it is relative to is updated, elevation points are not automatically added or removed on the feature line to match the surface TIN lines, as shown in the following illustration.

2017-04-17_14-15-37

You can update the elevation points on the feature line by using the Insert Elevation Point and Delete Elevation Point editing options in the Grading Elevation Editor or on the Edit Elevations panel of the Feature Line ribbon tab.

Connected Alignments

You can use the connected alignments feature to create an alignment that transitions between two intersecting alignments and to create a profile that transitions between their profiles.

You can use this feature to create a curb return, an exit ramp, a merging/diverging road, or you can connect an existing road with a proposed road.

The connected alignment is created between the two intersecting alignments at a specified radius.

The geometry of the connected profile is automatically generated from the parent profiles that you select. The start and end elevations and slope are taken from the parent profiles, and the middle section of the connected profile is calculated depending on whether extensions of the parent profiles intersect.

2017-04-17_14-25-59

Editing the geometry of a connected alignment or profile:

When you create a connected alignment and associated profile, by default they are set to dynamic state, which means that they will partially update if their parent alignments and profiles change. You can change the update mode to static if you want to prevent any updates from occurring and if you want full editing control over the alignment and profile.

  • The geometry of the overlapping parts on both the connected alignment and profile is locked to the parent alignments and profiles when in a dynamic state and cannot be edited. These overlapping segments will update if the parent alignments and profiles update.
  • The stations between the overlapping parts of a dynamic connected profile can be edited.
    Important: This area will not be dynamic to the parent alignments and profiles and will not update if they update.
  • A dynamic connected alignment can be edited in the following ways:
      1. Radius: You can use the circular grip at the center of the curve to edit the curve radius, or you can specify a different radius value on the Connection Parameters tab of the Alignment Properties dialog box.
      2. Overlap: You can use the diamond-shaped grips at the ends of the connected alignment to increase or decrease the overlap. 

Note: Editing the geometry of a connected alignment in the Layout Parameters window is not supported.

You can change the update mode for a connected alignment on the Connection Parameters tab of the Alignment Properties dialog box.

You can change the update mode for a connected profile on the Profile Data tab of the Profile Properties dialog box.

Corner Cleanup for Corridors

At some locations on corridor models, the corridor links can cross each other, resulting in bowtie-like configurations.

The following illustration shows a corridor with a bowtie configuration at the corner.

2017-04-17_14-32-29

Automatic and command-based corner cleanup:

In some situations, such as where corridor tangents intersect at a corner, and where the corridor is created at a fixed width, bowties can be cleared automatically. You can control which types of bowtie intersections are cleared automatically by changing the Automatic Clear Bowtie Options in the Edit Feature Settings – Corridor dialog box.

In other situations, such as when the corridor is created at a variable width (such as when daylighting to a surface), you can use the Clear Corridor Bowties command.

Conditions where automatic corridor cleanup behavior is applied:

The automatic AutoCAD Civil 3D corridor cleanup behavior can be applied at tangent-tangent, tangent-curve, and tangent-curve-tangent intersection locations in corridors that use feature lines or alignment/profiles as baselines, and the assemblies have consistent widths as set by shapes within the assembly.

For example, where corridor tangents intersect at a corner, and where the corridor is created at a fixed width, the corners are cleaned up as follows:

2017-04-17_14-34-29

The point where the inner corners meet is calculated and radial lines are extended from that location, using the insertion frequency along the baseline as defined in the Frequency to Apply Assemblies dialog box.

In addition, one station is also added at the corner if the At Horizontal Geometry Points option is selected in the Frequency to Apply Assemblies dialog box:

2017-04-17_14-34-40

The subassembly width value is overridden at the radial stations; the width is calculated to produce a corner solution that is similar to the AutoCAD Offset command.

For more examples of automatic corner cleanup, see “Corner cleanup examples” below.

Note: You can control which types of bowtie intersections are cleared automatically by changing the Automatic Clear Bowtie Options in the Edit Feature Settings – Corridor dialog box. By default the option to clear bowties at tangent-tangent intersections is set to Yes and the option to clear bowties at tangent-arc and arc-tangent intersections is set to No. If you choose not to enable the Automatic Clear Bowtie Options for fixed width corridors, you can use the Clear Corridor Bowties command on those corridors.

Using the Clear Corridor Bowties command:

Use the Clear Corridor Bowties command in the following conditions:

  • In conditions where corridor shapes widen (for example, where the footing in a retaining wall has a variable width which depends on the retaining wall height).

2017-04-17_14-34-56

  • When daylighting to a surface.

2017-04-17_14-35-24

For more examples of command-based corner cleanup, see the following section.

Corner cleanup examples:

The following table shows different corridor corner examples which can occur in fixed width and variable width corridors.

  • If automatic is listed in the table as the cleanup type it means that for new corridors the clean up occurs automatically. If you are bringing forward such a corridor from a prior version of AutoCAD Civil 3D, and the corners need to be cleaned up, you can simply make an edit to the corridor (such as a change to the corridor properties) and then rebuild it.
    Note: You can control which types of bowtie intersections are cleared automatically by changing the Automatic Clear Bowtie Options in the Edit Feature Settings – Corridor dialog box. By default the option to clear bowties at tangent-tangent intersections is set to Yes and the option to clear bowties at tangent-arc and arc-tangent intersections is set to No. If you choose not to enable the Automatic Clear Bowtie Options for fixed width corridors, you can use the Clear Corridor Bowties command on those corridors.
  • If command-based is listed in the table as the cleanup type it means that corner cleanup can be done using the Clear Corridor Bowties command.

2017-04-17_14-39-31

2017-04-17_14-40-03

Corner elevation value after clearing a bowtie:

The elevation value that is used for the corner after bowtie resolution is obtained from one of the inner points of the bowtie as shown in the following illustrations.

The following illustration represents a corner prior to clearing the bowtie. The corridor baseline is shown in red.

2017-04-17_14-43-15

The following illustration represents a corner after clearing the bowtie.

2017-04-17_14-43-32

Points 3 and 4 are moved to the location of point 5, and the elevation of point 4 is now used in that location. The locations and elevations of points 1 and 2 are unchanged.

Resolving other corner cleanup issues:

Corner cleanup does not get applied at the end point of a closed feature line-based corridor if the start and end of the feature line meet at the corner, as shown in the following illustration on the left.

To work around this, it is recommended that you draw the feature line so that it starts and ends at a location other than a corner as shown in the following illustration on the right.

2017-04-17_14-43-44

To resolve other corner cleanup issues that are not cleaned up automatically and which cannot be addressed with the Clear Corridor Bowties command, you can extract a dynamic feature line from the corridor and use the grading tools to grade from that feature line. The following is an example of adding grading to the right side of the corridor.

2017-04-17_14-43-55

Move Section Views to a Different Section View Group

You can move one or more section views into a specified section view group.

  • The section views that you want to move and the destination section view group must share the same sample line group.
  • Section views can be moved from the individual section views collection to a section view group, or from one section view group to another section view group.
    Note: Section views cannot be moved into the individual section views collection.

When you move section views to a different section view group, the following occurs:

  • The section views are inserted into the section view group in order of their stationing. They are inserted between existing section views in the group as needed so all the section views are in order.
  • If the styles are different, the section views you are moving can keep their existing styles, or they can use the style of the destination section view group.

In the following example, an individual section SL-25 needs to be moved into the section view group. Its station is 1+75 so it will be inserted between the sections for station 1+50 and 2+00.

2017-04-17_14-55-44

The following illustration shows the section view inserted into the section view group. You can choose to keep the existing stylization, as shown in this example, or you can choose to apply the stylization of the destination section view group to the moved sections. The section view for station 3+00 was moved to the next sheet.

2017-04-17_14-56-10

Section View Drafting Buffers

Section views are created with drafting buffers. When you add AutoCAD annotation or drafting elements or AutoCAD Civil 3D note labels within or crossing the drafting buffers, they are bound with the section views, and are moved with the section views if they are moved.

In the following illustration, the drafting buffers around the section views are shown in magenta. Drafting elements that were added to the sheet are shown in red.

2017-04-17_15-01-07

When the section views for station 2+50 and 3+00 are moved up or off the sheet, the drafting elements that are inside the drafting buffers are moved with the section views. The text that notes the lane slope is not moved because it was outside the drafting buffer area.

Binding drafting elements with a section view:

Drafting elements become bound to a section view when they are added or modified within or crossing the drafting buffer.

  • Any new or existing drafting elements that are added or moved within or crossing a drafting buffer become bound to the section view.
  • If you make a drafting buffer larger to encompass or cross existing drafting elements, those drafting elements become bound to the section view after you make an edit to them.
  • If you make a drafting buffer smaller, drafting elements that were previously inside or crossing the drafting buffer remain bound to the section view until you make an edit to them.

Drafting buffer grips:

You can use the grips on a drafting buffer to increase or decrease its size. The following illustration shows the grips and the value of the right drafting buffer margin (50.0000) when you hover over that grip. You can select the grip and drag it to resize the drafting buffer, or you can and enter a new value at the command line.

2017-04-17_15-03-01

Note: Resizing a drafting buffer after drafting elements already exist does not automatically change the binding behavior of the drafting elements relative to that drafting buffer. For more information about the binding behavior, see “Binding drafting elements with a section view” above.

Settings and styles related to drafting buffers:

Settings and styles that impact drafting buffers are as follows:

  • CreateSectionView and CreateMultipleSectionView command settings: Use the Drafting Buffer settings to control the initial margins of the drafting buffers when the section views are created. For more information, see Edit Feature Settings – Section View Dialog Box.
    Note: After a section view is created with a drafting buffer, you can grip edit the drafting buffer to change its size.
  • Array tab of the Group Plot Style dialog box: Use the Add Drafting Buffer Size to Space Between Views setting to control whether the column and row spacing is applied between the edges of the drafting buffers or between the edges of the section views.
  • Display tab of the Section View Style dialog box: Use the Drafting Buffer Outline setting to control the appearance of the drafting buffer.

Behavior when changing the direction of section views or deleting section views:

Changing the direction of section views that have drafting elements

If you edit the style of a section view so that the section view direction changes, the drafting buffer is changed to accommodate the new direction, but the drafting elements that are inside or crossing the buffer are not moved. If this results in existing drafting elements being displayed outside of the buffer, the drafting elements will still be bound with the buffer unless you move them to a different location outside the drafting buffer. For more information about the binding behavior, see “Binding drafting elements with a section view” above.

Deleting section views that have drafting elements

If you delete section views that have drafting elements within a drafting buffer, you have the option to delete the drafting elements or preserve them. A task dialog box is displayed with options you can select.
Note: If you select the Always Use My Selection in the Future check box in the task dialog box, and you want to change the behavior in the future, you can edit the Hidden Messages Settings on the System tab of the AutoCAD Options dialog box.

Plan-Plan/Profile-Profile Sheets

Two new templates for Plan Production have been added for Plan over Plan and Profile over Profile…

2017-04-17_15-07-37

Autodesk InfraWorks Ribbon

The new Autodesk InfraWorks ribbon has more options than before. See illustration below…

2017-04-17_15-17-30

There are some more new features in this release. I will hold off posting them for now. Stay tuned for more features, tutorials, and webinars.

Civil 3D to Stingray In-house Seminar

You’re invited to the

Civil 3D to Stingray Seminar

Date: Tuesday, April 4th, 2017

Time: 9:00 AM- 12:00 PM

Location: Graitec USA Office

Bring your Civil 3D projects into Autodesk Stingray.

In this seminar, we will demonstrate the workflow for creating a real-time, interactive environment of Civil 3D project sites using the Stingray engine. Discover how you can bring your design visualization projects to life with the Autodesk Stingray design engine, which offers a direct connection to 3ds Max and real-time rendering. Autodesk Stingray creates 3D games, real-time design visualizations, and virtual reality experiences.

Graitec USA, Inc. | 480 N. Sam Houston Pkwy. E., Suite 234, Houston, TX 77060 http://www.graitecUSA.com

Civil 3D to Stingray

Bring your Civil 3D project into Stingray

You’re invited to the

Civil 3D to Stingray

Webinar

Date: Wednesday, March 22nd

Time: 10:00 AM- 11:00 AM

Location: Online

Bring your Civil 3D projects into Autodesk Stingray.

Bring your design visualization projects to life with the Autodesk Stingray design engine, which offers a direct connection to 3ds Max and real-time rendering. Autodesk Stingray creates 3D games, real-time design visualizations, and virtual reality experiences. Join us in this one-hour webinar as we demonstrate the workflow for creating a real-time, interactive environment of Civil 3D project sites using the Stingray engine.

Graitec USA, Inc. | 480 N. Sam Houston Pkwy. E., Suite 234, Houston, TX 77060 http://www.graitecUSA.com

Civil 3D to Stingray

As promised from last week, I am taking a Civil project and bringing it in to Autodesk’s Stingray, which is a gaming engine. This is a pretty neat workflow. A big thanks to Andy Carter with CivilE for showing me this workflow.

Hopefully you will get a lot out of this and maybe start using it. I have shown how to use a vehicle in the scene. You can also use the standard person to use in your scene as an alternative.

See video below…

Are You Using Civil View? You Should Be…

I’m sure many of you have noticed when installing Civil 3D (especially if you have a suite or collection), that there is a plug-in called Civil View. This is a plug-in for 3ds Max. If you’re not using this, YOU SHOULD BE! This is an easy way to present to a client or stakeholder your proposed road design animated with cars, signs, lights, etc. 

The most common phrase I hear is, “I don’t have time to learn 3ds Max”, and “It’s a too convoluted to learn”. This is a big misconception. Reason being, is that you don’t have to learn or know 3ds Max, you just use the Civil View plug-in to do it for you.

In the 20 minute video below, I show you how to create a design road in InfraWorks 360, bring it in to Civil 3D, build a corridor, export it out to 3ds Max, then create an animated presentation. This process literally took me 20 minutes to do. Hopefully this will aid you in starting to use your Infrastructure Design Suite or AEC Collection to it’s full potential.

Once you view the video, if you have any questions, please feel free to contact me at trogers@tcadsys.com, or you can call our office at (281) 445-6161.

Are You Struggling with Civil 3D Performance?

I have had a lot of calls on Civil 3D taking forever to open, and there is finally a fix. You will have to follow the directions from here. Once you have followed the instructions, open the problematic drawing. It will still take forever to open. However, once it’s opened and saved, the problem goes away.

Thank you to Steve Hill at Red Transit Consultants for reminding me to edit this post.

Make sure you do this on ALL machines. Otherwise the issue will keep reoccurring.

Take a stop over at Red Transit Consultants if you are interested in some awesome add-on tools for Civil 3D, Map 3D, AutoCAD, and much more.

AutoCAD Civil 3D 2017 Service Pack 1.1

So in case you haven’t noticed, Autodesk pulled Service Pack 1 and recently released Service Pack 1.1. Below are the issues fixed in the new service pack…

API

  • The API has been extended to enable match line and view frames.
  • The .NET API has been extended to enable write access for setting cant on a railway alignment.
  • An API has been added to create a siteless feature line :
    static NAMESPACE_ACDB::ObjectId Create(System::String^ featurelineName, NAMESPACE_ACDB::ObjectId idCreatedFrom);
  • An API has been added to move a feature line to none site:
    static void MoveToNoneSite(NAMESPACE_ACDB::ObjectId featureLineId);
  • An API has been updated to allow a feature line to be moved to none site:
    static void MoveToSite(NAMESPACE_ACDB::ObjectId featureLineId, NAMESPACE_ACDB::ObjectId destinationSiteId);

Alignments and Profiles

  • Use of object snaps has been enabled for profile view lines.
  • An issue where a drawing created in AutoCAD Civil 3D 2016 would display station numbers with extra characters when opened in AutoCAD Civil 3D 2017 has been resolved.
  • An issue that caused the superelevation diagrams to display a design check warning with a blank tooltip has been resolved.
  • An issue that caused the Superelevation Tabular Editor to display a rate of change warning with a blank tooltip has been resolved.
  • An error is no longer reported when moving a data-referenced alignment to a different site.
  • An issue has been resolved where a blank meny woould appear when right-clicking on a data-referenced object that had its source drawing renamed.
  • When using the Export to Civil 3D Drawing command, alignments are now exported as polylines as they have been in previous releases of AutoCAD Civil 3D.

Corridors

  • An issue that prevented use of the command line to input a station range when using the Export Corridor to Solids command has been resolved.
  • An unexpected error is no longer generated when erasing an intersection while the Intersection Offset Parameter dialog box is open.

Export to DWG/DGN

  • An issue that prevented a successful drawing export to Microstation® DGN format has been resolved.
  • An error is no longer generated when exporting from a drawing that has been saved at the root directory of the local disk.
  • An issue has been resolved where the file browse dialog box for selecting a DWS file when exporting to DGN was not displayed.

General

  • An issue has been resolved where grading criteria sets were duplicated when attaching a referenced template.
  • An unexpected error is no longer generated when erasing a profile while the Profile Layout Tools toolbar is open.
  • An issue that prevented the Miscellaneous Utilities in the Toolbox from being run at the command line has been resolved.

Grading and Feature Lines

  • Running the AUDIT command after moving an overlapping feature line in a site no longer causes errors to be reported.
  • An issue that caused a grading object to not respond to changes in a feature line after a drawing audit has been resolved.

Hydraflow Extensions

  • An issue has been resolved that caused the inlet grade dimensions to not match between the Hydraflow Storm Sewers extension and the Hydraflow Express extension.
  • When plotting an Inlet Section Table the “Inlet Depth” and “Inlet Spread” column headers have been changed to “Bypass Depth” and “Bypass Spread”.
  • An issue has been resolved that caused an error when applying changes after adding an empty column to a custom report in MyReport.
  • The Hydraflow Storm Sewers extension and the Hydraflow Express extension have updated calculations for gutter spread depth of curb inlets in sag.
  • The Hydraflow Storm Sewers Help has been updated so that definitions are consistent with the current behavior.
  • The Bypass Spread depth values in the Hydraflow Express extension now use the same rounding as in Hydraflow Storm Sewers extension.
  • The Hydraflow Storm Sewers extension and the Hydraflow Express extension have updated calculations for gutter spread depth of curb inlets in sag.

Hydrology and Hydraulics

  • Linetypes that include blocks and text now are displayed correctly when used for catchment boundaries or flow paths.

Labels

  • A feature has been added where a glyph and tooltip are shown when a label component has had its contents and/or format overridden.
  • An issue has been resolved where the default projection label style that was specified in the ProjectObjectsToMultiSect command settings was not retained when the Project Objects to Multiple Section Views command was run.

Pipe Networks and Pressure Networks

  • An issue that caused unexpected behavior when using grips to edit pressure network pipes in profile view has been resolved.
  • An issue has been resolved where some changes in a pressure network data shortcut were not synchronized to the referenced drawing.
  • An issue has been resolved where edits to the elevation of a pressure network were not retained when the pressure network was data-referenced.
  • An issue has been resolved where pipe network styles were overwritten when synchronized in paper space.

Autodesk® Vault

  • An issue has been resolved that caused an error where checking in a drawing that has a TIFF XREF that is checked out.

AutoCAD Civil 3D 2017 Service Pack 1

Autodesk has released Service Pack 1 for Civil 3D 2017. Keep a look out in your Autodesk Desktop App for the download.  The issues addressed in the service pack are listed below…

API

  • The API has been extended to enable match line and view frames.
  • The .NET API has been extended to enable write access for setting cant on a railway alignment.
  • An API has been added to create a siteless feature line :
    static NAMESPACE_ACDB::ObjectId Create(System::String^ featurelineName, NAMESPACE_ACDB::ObjectId idCreatedFrom);
  • An API has been added to move a feature line to none site:
    static void MoveToNoneSite(NAMESPACE_ACDB::ObjectId featureLineId);
  • An API has been updated to allow a feature line to be moved to none site:
    static void MoveToSite(NAMESPACE_ACDB::ObjectId featureLineId, NAMESPACE_ACDB::ObjectId destinationSiteId);

Alignments and Profiles

  • Use of object snaps has been enabled for profile view lines.
  • An issue where a drawing created in AutoCAD Civil 3D 2016 would display station numbers with extra characters when opened in AutoCAD Civil 3D 2017 has been resolved.
  • An issue that caused the superelevation diagrams to display a design check warning with a blank tooltip has been resolved.
  • An issue that caused the Superelevation Tabular Editor to display a rate of change warning with a blank tooltip has been resolved.
  • An error is no longer reported when moving a data-referenced alignment to a different site.
  • An issue has been resolved where a blank meny woould appear when right-clicking on a data-referenced object that had its source drawing renamed.
  • When using the Export to Civil 3D Drawing command, alignments are now exported as polylines as they have been in previous releases of AutoCAD Civil 3D.

Corridors

  • An issue that prevented use of the command line to input a station range when using the Export Corridor to Solids command has been resolved.
  • An unexpected error is no longer generated when erasing an intersection while the Intersection Offset Parameter dialog box is open.

Export to DWG/DGN

  • An issue that prevented a successful drawing export to Microstation® DGN format has been resolved.
  • An error is no longer generated when exporting from a drawing that has been saved at the root directory of the local disk.
  • An issue has been resolved where the file browse dialog box for selecting a DWS file when exporting to DGN was not displayed.

General

  • An issue has been resolved where grading criteria sets were duplicated when attaching a referenced template.
  • An unexpected error is no longer generated when erasing a profile while the Profile Layout Tools toolbar is open.
  • An issue that prevented the Miscellaneous Utilities in the Toolbox from being run at the command line has been resolved.

Grading and Feature Lines

  • Running the AUDIT command after moving an overlapping feature line in a site no longer causes errors to be reported.
  • An issue that caused a grading object to not respond to changes in a feature line after a drawing audit has been resolved.

Hydraflow Extensions

  • An issue has been resolved that caused the inlet grade dimensions to not match between the Hydraflow Storm Sewers extension and the Hydraflow Express extension.
  • When plotting an Inlet Section Table the “Inlet Depth” and “Inlet Spread” column headers have been changed to “Bypass Depth” and “Bypass Spread”.
  • An issue has been resolved that caused an error when applying changes after adding an empty column to a custom report in MyReport.
  • The Hydraflow Storm Sewers extension and the Hydraflow Express extension have updated calculations for gutter spread depth of curb inlets in sag.
  • The Hydraflow Storm Sewers Help has been updated so that definitions are consistent with the current behavior.
  • The Bypass Spread depth values in the Hydraflow Express extension now use the same rounding as in Hydraflow Storm Sewers extension.
  • The Hydraflow Storm Sewers extension and the Hydraflow Express extension have updated calculations for gutter spread depth of curb inlets in sag.

Hydrology and Hydraulics

  • Linetypes that include blocks and text now are displayed correctly when used for catchment boundaries or flow paths.

Labels

  • A feature has been added where a glyph and tooltip are shown when a label component has had its contents and/or format overridden.
  • An issue has been resolved where the default projection label style that was specified in the ProjectObjectsToMultiSect command settings was not retained when the Project Objects to Multiple Section Views command was run.

Pipe Networks and Pressure Networks

  • An issue that caused unexpected behavior when using grips to edit pressure network pipes in profile view has been resolved.
  • An issue has been resolved where some changes in a pressure network data shortcut were not synchronized to the referenced drawing.
  • An issue has been resolved where edits to the elevation of a pressure network were not retained when the pressure network was data-referenced.
  • An issue has been resolved where pipe network styles were overwritten when synchronized in paper space.

Autodesk® Vault

  • An issue has been resolved that caused an error where checking in a drawing that has a TIFF XREF that is checked out.

Civil 3D 2016 Service Pack 3

Autodesk has released Service Pack 3 for Civil 3D 2016.

The following issues have been resolved in Autodesk AutoCAD Civil 3D 2016 Service Pack 3:

API

  • The API has been extended to enable match lines and view frames.
  • An API has been added to create a siteless feature line:
    static NAMESPACE_ACDB::ObjectId Create(System::String^ featurelineName, NAMESPACE_ACDB::ObjectId idCreatedFrom);
  • An API has been added to move a feature line to none site:
    static void MoveToNoneSite(NAMESPACE_ACDB::ObjectId featureLineId);
  • An API has been updated to allow a feature line to be moved to none site:
    static void MoveToSite(NAMESPACE_ACDB::ObjectId featureLineId, NAMESPACE_ACDB::ObjectId destinationSiteId);

Alignments and Profiles

  • An issue that caused the superelevation diagrams to display a design check warning with a blank tooltip has been resolved.
  • An issue that caused the Superelevation Tabular Editor to display a rate of change warning with a blank tooltip has been resolved.

Corridors

  • An issue has been resolved that caused an error when creating an intersection using the Create Intersection command from the ribbon.

Export to DWG/DGN

  • An error is no longer generated when exporting from a drawing that has been saved at the root directory of the local disk.
  • An issue that prevented a successful drawing export to Microstation® DGN format has been resolved.

General

  • An issue has been resolved that caused an error when trimming or extending lines that are labeled with a label style that uses a block reference.
  • An issue has been resolved where in some cases a structure label would become immovable and could not be grip edited.
  • Performance when opening a drawing has been improved.

Grading and Feature Lines

  • An issue has been resolved where the elevation point grips of feature lines that are associated with a site were deleted unexpectedly after a drawing audit.
  • The default site for a newly created feature line is now the last site that was used.
  • An issue has been resolved where changes that were made to a feature line’s style on the Feature Lines tab of the Corridor Properties dialog box were not retained.
  • An issue has been resolved where an alignment that was inserted as a DREF was no longer visible if moved to a different site.
  • Moving multiple feature lines to or from the <None> site selection no longer results in unexpected elevation interaction between the feature lines.
  • An issue that caused a grading object to not respond to changes in a feature line after a drawing audit has been resolved.

Hydraflow Extensions

  • When plotting an Inlet Section Table the “Inlet Depth” and “Inlet Spread” column headers have been changed to “Bypass Depth” and “Bypass Spread”.
  • An issue has been resolved that caused an error when applying changes after adding an empty column to a custom report in MyReport.
  • An issue has been resolved that caused the inlet grade dimensions to not match between the Hydraflow Storm Sewers extension and the Hydraflow Express extension.
  • The Hydraflow Storm Sewers Help has been updated so that definitions are consistent with the current behavior.
  • The Bypass Spread depth values in the Hydraflow Express extension now use the same rounding as in Hydraflow Storm Sewers extension.
  • The Hydraflow Storm Sewers extension and the Hydraflow Express extension have updated calculations for gutter spread depth of curb inlets in sag.

Hydrology and Hydraulics

  • Linetypes that include blocks and text now are displayed correctly when used for catchment boundaries or flow paths.

Labels

  • An issue has been resolved where the default projection label style that was specified in the ProjectObjectsToMultiSect command settings was not retained when the Project Objects to Multiple Section Views command was run.

Pipe Networks and Pressure Networks

  • An issue has been resolved where pipe network styles were overwritten when synchronized in paper space.
  • An error is no longer generated when placing a structure during pipe network layout.
  • An issue has been resolved where some changes in a pressure network pipe data shortcut are not synchronized to the referenced drawing.
  • An issue that caused unexpected behavior when using grips to edit pressure network pipes in profile view has been resolved.

Storm and Sanitary Analysis

  • An issue has been resolved where the surface type for a flow path in catchment is transferred incorrectly from AutoCAD Civil 3D to Storm and Sanitary Analysis.
  • An issue has been resolved where AutoCAD Civil 3D was not applying the custom inlet attributes from the customized XML part mapping file.

Surfaces

  • An issue that affected the appearance of the elevations in grid volume surfaces has been resolved.

Autodesk® InfraWorks® 360 Interoperability

  • An issue has been resolved where alignments that were brought into AutoCAD Civil 3D from InfraWorks 360 were offset in AutoCAD Civil 3D when the drawing’s coordinate system was set using the Open InfraWorks 360 Model dialog box.

Autodesk® Vault

  • Performance has been improved when opening as read-only a drawing that has XREFs.
  • An issue has been resolved that caused an error when checking in a drawing that has a drawing XREF that is checked out by another user.
  • An issue has been resolved that caused an error when checking in a drawing that has a TIFF XREF that is checked out.