AutoCAD Civil 3D and Subassembly Composer—

Real-World-Practice Tips and Tricks (CI123653)

Jowenn S. Lua
Senior Civil 3D Designer - ARCADIS

Join the conversation #AU2017

Learning Objectives

 Importance of customizing a code set style

 Create a smarter custom subassembly, and learn how to create multilink solid
transitions
 Extract solid from a corridor that can transition link to zero
 Gain valuable AutoCAD Civil 3D tips and tricks
Importance of customizing a code set style
Code Set style

 Control the visual appearance of a code set

o Point Code
o Link Code
o Shape Code
 Type of object that uses code set style
o Assembly and Subassembly
o Corridor
o Section View
Code Set style

 Flexibility
 Standardized
 Auto Labels
 Workflow improvement
 Less CAD re-work
 Improves performance

Photo Credit: http://www.benefitspro.com

Subassembly Codes

 Point, Link and Shape Codes

Clients requirements in Civil 3D Model

 Model submitted as Genio format (String model)

 XS to reflect string labels
 Create solid model and add attributes

Images taken from: Mainroads Western Australia website

Clients requirements in Civil 3D Model
Clients requirements in Civil 3D Model
Traditional XS from Surface vs XS from Corridor
Code Set Style - “That works for us”
Code Set Style - “That works for us”
Code Set Style - “That works for us”
Code Set Style - “That works for us”
Code Set Style - “That works for us”
Tips Revealed - Useful Shortcut / Links

 %AppData% and %LocalAppData%

Tips Revealed - Useful Shortcut / Links

 For Local C-drive Autodesk Support

%AppData%\Autodesk\C3D 2018\enu\Support
 For Civil 3D Tool Palette Images
%AppData%\Autodesk\C3D 2018\enu\support\toolpalette\Palettes\images
 For Civil 3D default template location
%LocalAppData%\autodesk\c3d 2018\enu\template
Tips Revealed – Use dynamic input

 Dynmode set to 3 to Turn on

 This allows you to enter specific chainage or station

Live Demo 1
Create Smarter Custom Subassembly and
Create Multi Link Solid Transition
Components of Smarter Custom Subassembly

 Useful and can be re-used

 Define point, link and shape codes
 Input parameters
 Output parameters
 Target parameters if required
 Can adapt any code set style
 Chm help file (Compiled HTML file format)
 Image
 Version control
Photo Credit: https://www.emaze.com/@ALWCICQT/NSE-2015
Subassembly Composer

 Tool used in creating a complex subassembly without a need of programming.

Photo Credit: http://www.triplesystems.co.th/

Subassembly Composer – Data Management

 Create a SA with unique name

 Create a folder for all PKT
 Create a legend or identifier
 Create a subassembly register or log sheet
Multi-Link Transition (MLT) Subassembly
 Hard to close to exact start point.
 Fixed static shape unless you use
number transform and parameter
reference.
 All Points are using the same point
code by default.
 All links are using the same link code
all throughout.
 Can transform from one polygon to
another polygon.
 User defined point, link, shape
code(s).
 User can see how your subassembly
will look like in any part of the region.
 Can define Top and Datum link
separately.
 Can extract solid shape.
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly

`
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly
Multi-Link Transition (MLT) Subassembly
Sample Multi-Link Transition (MLT)
Sample Multi-Link Transition (MLT)
PKT – Formula Math Concept
PKT – Formula used
PKT – Formula used
PKT – Formula used
PKT – Formula used
PKT – Layout view concept
Live Demo 2
Create solid that transition to Zero
Ways to create horizontal transition to zero

 Using Horizontal Target

o Polyline target
o Feature line target
o Offset Alignment target
 Using Parameter reference
o Slope transition (Peter Funk, Au 2011)
o Number transformation (Stack Subassembly)
Sample Scenario: 3 Lanes to transition to 2 Lanes

Assembly to use:
Sample Scenario: 3 Lanes to transition to 2 Lanes

1. Create 3 lanes
Sample Scenario: 3 Lanes to transition to 2 Lanes

2. Split region into 3 regions

Sample Scenario: 3 Lanes to transition to 2 Lanes

3. Change assembly (3 Lanes, Trans, 2 Lanes)

Sample Scenario: 3 Lanes to transition to 2 Lanes

4. Create top surface tin

Sample Scenario: 3 Lanes to transition to 2 Lanes

5. Extract solid from corridor – Missing Solid

Live Demo 3
AutoCAD Civil 3D Tips and Tricks
Ways to manage and share custom subassembly

 Content Browser and tool catalog

 Share Package File (PKT)
 Export/Import Tool Palette Files (XTP)
 Export/Import Tool Palette Group Files (XPG)
 Copy local Imported tool and paste to another computer in the same location
 Tool Palette Pushout
Tool Palette Pushout (TPP)

Workflow we use to share and manage our custom subassembly.

 Requirements for TPP

o Shared Server o CHM Help folder
o Bat file for C3D Admin o Imported Tools folder
o Bat file for C3D Users o Template folder
o Instruction Manual o Palettes folder
o Profile folder
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
Target:
"C:\Program Files\Autodesk\AutoCAD 2018\acad.exe" /ld
"C:\Program Files\Autodesk\AutoCAD 2018\AecBase.dbx" /p
"ARCADIS_SYD_r2018_C3D_RMS" /product "C3D“

Start in:
"C:\Program Files\Autodesk\AutoCAD 2018\UserDataCache\"
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – Shared Server

Sample server folder structure

 C:\_AU2017\Sample_Server
TPP – C3D Admin Bat File

 xcopy "C:\ProgramData\Autodesk\C3D 2018\enu\Imported Tools"

"C:\_AU2017\Sample_Server\Subassemblies" /Q /Y /I /E
 xcopy "C:\Subassemblies CHM Help"
"C:\_AU2017\Sample_Server\Subassemblies CHM Help" /Q /Y /I /E
TPP – C3D Users Bat File

 xcopy "C:\_AU2017\Sample_Server\Subassemblies" "C:\ProgramData\Autodesk\C3D

2018\enu\Imported Tools" /Q /Y /I /E
 xcopy "C:\_AU2017\Sample_Server\Subassemblies CHM Help" "C:\Subassemblies CHM
Help" /Q /Y /I /E
 xcopy "C:\_AU2017\Sample_Server\Palettes\Global Generic\Images"
"%AppData%\Autodesk\C3D 2018\enu\support\toolpalette\Palettes\images" /Q /Y /I /E
 xcopy "C:\_AU2017\Sample_Server\Palettes\RMS\Images" "%AppData%\Autodesk\C3D
2018\enu\support\toolpalette\Palettes\images" /Q /Y /I /E
TPP – C3D Users Bat File

 xcopy "C:\_AU2017\Sample_Server\Templates\Plan Production"

"C:\_AU2017\Sample_User\Template\Civil3D2018" /Q /Y /I /E
 xcopy "C:\_AU2017\Sample_Server\Templates\_C3D_2018_Arcadis_RMS.dwt"
"C:\_AU2017\Sample_User\Template\Civil3D2018" /Q /Y
TPP – Flowcharts C3D Admin and Users
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
TPP – Flowchart
Tips Revealed – Bonus Corridor Workflow

 Alternative approach
Live Demo 4
Summary

 We’ve learned:
o Importance of Code Set Style
o Smarter subassembly / Multi Link Transition
o Solid that transition to Zero
o Civil 3D Tips and Tricks
 %appdata% and %localappdata%
 Tool palette pushout (TPP)
 Null assembly and “0001 Method”
Be heard! Provide Au session feedback.

 (CI123653) AutoCAD Civil 3D and Subassembly Composer—

Real-World-Practice Tips and Tricks
 Via the survey stations, email or mobile device
 Chance to win AU 2018 Pass each day
 Best to do it right after each session
 AU speakers will get feedback in real-time
Autodesk and the Autodesk logo are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the
right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.
© 2017 Autodesk. All rights reserved.