ADS study materials
ADS study resources

ADS cheat sheet

ADS · Keep the key ideas within reach.

Quick reference

Drawings, Templates, and Layers

  • Drawing templates use the .dwt extension; QNEW creates a new drawing from the default template named in Options > Files > Template Settings > Default Template File Name for QNEW.

  • A template stores layers, linetypes, text and dimension styles, layouts, and named objects; only content in model space and paper space is inherited unless the template is saved with content.

  • Layer 0 cannot be deleted or renamed; it can be turned off, frozen, locked, or plotted/non-plotted, and objects on it inherit block insertion-layer behavior.

  • Frozen layers are excluded from regeneration and object snaps; off layers are still regenerated and can still be snapped to unless OSNAP ignores them.

  • LAYMRG merges a source layer into a target layer and deletes the source; LAYWALK isolates layers without changing their on/off state.

  • The current layer cannot be frozen, and the current layer's color, linetype, and lineweight are set to ByLayer by default for new objects.

  • LAYISO hides all layers except those of selected objects; LAYUNISO restores the previous layer state, and LAYERP reverses the last layer command.

  • Layer states saved with LAYERSTATE store on/off, freeze/thaw, lock, plot, color, linetype, and lineweight settings and can be restored per viewport when VPLAYER overrides are saved.

Quick reference

Drawing Objects and Annotation

  • MTEXT supports inline formatting codes and paragraph wrapping inside a defined width; DTEXT/TEXT creates single-line or multiline text without an embedded width boundary.

  • Fields (inserted with FIELD) update on regen, plot, or open depending on the field category, e.g., date fields, sheet set fields, and object properties.

  • Multileaders (MLEADER) combine a leader with text or a block; MLEADERSTYLE controls arrowhead, landing, and text attachment.

  • Hatch patterns can be associative; if the boundary is edited, an associative hatch updates, and non-associative hatches do not.

  • A polyline is a single object with vertices and optional arc segments; EXPLODE converts it to individual line and arc segments, losing width and global width properties.

  • Spline-fit polylines and splines differ: a spline is a NURBS curve with control vertices and fit points, while a polyline approximates curves with arc segments.

  • Tables (TABLE) are inserted as table objects with cells, formulas, and linked data; they can be broken across columns and linked to Excel data.

  • Annotative objects scale automatically according to the annotation scale assigned to the model space view or viewport.

Quick reference

Blocks, Attributes, and External References

  • The block definition table stores block definitions; INSERT places a block reference, and a block reference has a single insertion point, scale, and rotation.

  • Dynamic blocks use parameters and actions (e.g., stretch, visibility, lookup); visibility states control which geometry is displayed per state.

  • Attribute definitions (ATTDEF) inside a block become attributes on insertion; ATTDIA controls whether the attribute dialog appears, and ATTREQ controls whether prompts are suppressed.

  • ATTSYNC updates all block references after attribute definitions are edited in the block definition; BATTMAN manages attribute order and visibility.

  • XREFs are referenced, not inserted; the external file remains separate, and changes to the source appear on reload or open.

  • An xref's layers are prefixed with the xref name and a vertical bar (e.g., XREF|WALLS); VISRETAIN controls whether changes to xref layer settings persist across reloads.

  • Binding an xref with XREF BIND converts it to a block definition; the Insert option binds with the xref name prefix, and the Bind option removes the prefix.

  • Overlay xrefs are not carried forward into a host drawing when that drawing is itself attached as an xref; attach xrefs are nested.

Quick reference

Layouts, Viewports, and Plotting

  • A layout is a paper space environment with a defined plot configuration; each layout has its own page setup, plot style table, and paper size.

  • Model space viewports (VPORTS) tile the model space display; paper space viewports (MVIEW) are windows into model space placed on a layout.

  • A viewport's scale is set with the standard scale list or by entering a ratio; VPSCALE reports the current viewport scale when a viewport is selected.

  • Viewport overrides (VPLAYER) change layer properties per viewport without affecting other viewports or model space.

  • PSLTSCALE controls whether linetype scaling is based on paper space units (1) or model space units (0) in viewports.

  • Plot styles are either color-dependent (CTB) or named (STB); a drawing uses one type at a time, set in the Plot dialog or by the PSTYLEMODE system variable.

  • The plot scale is a ratio of plotted units to drawing units; 1:1 plots at full size, and fit-to-paper overrides the scale to fill the printable area.

  • Publish (PUBLISH) creates a DWF, PDF, or plot file from multiple sheets; sheet sets (SSM) organize sheets and can publish the entire set.

Quick reference

Dimensions, Tolerances, and Annotation Scaling

  • Dimension styles (DIMSTYLE) store arrowheads, text placement, extension line offsets, primary and alternate units, tolerances, and scale settings.

  • DIMSCALE sets the overall dimension scale factor; annotative dimension styles instead use the annotation scale and do not require DIMSCALE adjustment.

  • Associative dimensions update when the measured geometry changes; DIMASSOC controls associativity (0 = none, 1 = non-associative, 2 = associative).

  • Tolerance types include symmetric, deviation, limits, and basic; the tolerance tab in DIMSTYLE sets upper and lower values and precision.

  • Geometric tolerances (TOLERANCE) use feature control frames with symbols for form, orientation, location, and runout per ASME Y14.5 or ISO conventions.

  • DIMLFAC multiplies the measured value for dimensions in layouts or for scaled geometry; DIMLFAC of 0.5 halves the displayed measurement.

  • Annotation scale is assigned per model space view or viewport; annotative objects display at the scale of the current annotation scale and can have multiple scales.

  • DIMREGEN regenerates associative dimensions after changes to referenced geometry or xrefs.

Quick reference

Object Selection, Modification, and Properties

  • Selection methods include window (left-to-right, selects fully enclosed objects), crossing (right-to-left, selects touched objects), and fence, lasso, and polygon options.

  • Quick Select (QSELECT) filters by object type and property; FILTER creates a saved property filter that can be applied to selection sets.

  • Grips appear at object-specific points; a cold grip (unselected) and hot grip (selected) behave differently, and Ctrl+click cycles through grip options.

  • The Properties palette (PROPERTIES) edits common and object-specific properties; MATCHPROP copies properties from a source object to selected objects.

  • PEDIT joins polylines and adjusts width, while JOIN joins lines, arcs, and polylines into a single polyline when endpoints are coincident.

  • OVERKILL removes duplicate and overlapping objects and can merge collinear segments; it operates on the selection set and reports deleted objects.

  • The BYLAYER property makes an object inherit color, linetype, and lineweight from its layer; setting an explicit value overrides the layer setting.

  • Object isolation (ISOLATEOBJECTS, HIDEOBJECTS) temporarily hides unselected objects; UNISOLATEOBJECTS restores them.

Quick reference

Collaboration, Standards, and Drawing Management

  • Drawing standards files (.dws) store layers, dimension styles, linetypes, and text styles; CHECKSTANDARDS reports violations and can fix them.

  • A CAD Standards plug-in can be associated with a drawing so standards are checked on open or save, and notification is controlled by STANDARDSVIOLATION.

  • Sheet sets (.dst) organize drawings into subsets and sheets; sheet properties and custom properties can be used in title block fields.

  • The eTransmit feature packages a drawing with dependent files (xrefs, fonts, plot styles) and can create a transmittal report.

  • Drawing comparison (DWGCOMPARE) highlights differences between two revisions of a drawing, and the comparison can be saved or exported.

  • Digital signatures (SECURITYOPTIONS) attach a signature to a drawing; any modification after signing invalidates the signature.

  • The drawing recovery manager lists drawings that were open when a session ended abnormally and allows recovery of autosave and backup files.

  • Layer and drawing standards should be enforced by templates and .dws files rather than by manual checking to keep drawings consistent.

Quick reference

Customization, Productivity, and Best Practices

  • The CUI editor customizes menus, toolbars, ribbon panels, keyboard shortcuts, and mouse buttons; the main customization file is the .cuix file.

  • Command aliases are stored in the .pgp file (acad.pgp); REINIT reloads the .pgp file after edits without restarting the program.

  • Action macros (ACTIONS) record command sequences and can be played back, edited, and assigned to a toolbar button.

  • Script files (.scr) run a sequence of commands; SCRIPT runs a script, and a script can be used for batch plotting or repetitive edits.

  • AutoLISP routines load with APPLOAD and are stored in .lsp files; the Startup Suite loads selected routines on every session.

  • System variables can be set in a profile or startup script; a profile (.arg) stores support paths, template locations, and plotting settings.

  • Purge (PURGE) removes unused named objects such as layers, blocks, and styles; -PURGE with the All option purges all unused items in one pass.

  • Best practice for reusable content is to store blocks in a shared library and reference them with a tool palette or DesignCenter rather than copying between drawings.

Quick reference

Customization, Productivity, and Best Practices

  • Use named page setups saved in templates so every layout plots with the same device, paper size, and plot style.

  • Keep model space geometry at 1:1 and apply scale only in viewports; this preserves dimension and annotation accuracy.

  • Name layers by discipline and content (e.g., A-WALL-FULL) so layer filters and standards checks work predictably.

  • Set annotation scale before placing annotative text and dimensions so objects are created at the correct display size.

  • Use xrefs for shared base files and bind only for archival or delivery copies, since binding increases file size and duplicates content.

  • Audit (AUDIT) and recover (RECOVER) drawings before delivery to fix structural errors and reduce file size.

  • Save drawings with the same release format required by the recipient; SAVEAS controls the DWG version, and older formats may lose newer object types.

  • Record system variable changes in a startup script or profile so a workstation can be restored to a known configuration.

Quick reference

Customization, Productivity, and Best Practices

  • Keyboard shortcuts and command aliases reduce mouse travel; the .pgp alias file is the standard place to define them.

  • Tool palettes group blocks, hatches, and commands and can be shared by exporting and importing .xtp files.

  • A template with predefined layers, styles, and layouts eliminates repetitive setup and enforces standards at drawing creation.

  • Incremental save and autosave intervals are controlled by SAVETIME; set a value that balances data protection against performance.

  • Layer filters and layer states let you switch between working configurations without manually toggling many layers.

  • Use fields for title block data linked to sheet set properties so revisions propagate without retyping.

  • Batch plotting with PUBLISH and a saved sheet list is faster and less error-prone than plotting each layout individually.

  • Regularly purge and audit drawings; unused named objects accumulate and slow opening, saving, and plotting.

Quick reference

Customization, Productivity, and Best Practices

  • Store company standards in a .dws file and attach it to templates so CHECKSTANDARDS can compare new drawings automatically.

  • Use a shared support path for menus, fonts, plot styles, and templates so all workstations resolve the same files.

  • Name and version drawings consistently; a clear revision scheme makes comparison and transmittal reliable.

  • Lock xref layers that should not be edited and use VISRETAIN to keep xref layer settings across reloads.

  • Save named views and layer states for recurring detail areas to avoid repeated navigation and layer setup.

  • Use the .arg profile to transfer plotting, support path, and template settings between workstations.

  • Keep a block library and reference it with DesignCenter or tool palettes instead of copying blocks between drawings.

  • Test templates and customization files on a copy before deploying them to a production environment.

Quick reference

Customization, Productivity, and Best Practices

  • Command line input accepts command names, aliases, and coordinate entry; dynamic input can be toggled with the F12 key.

  • Object snaps (OSNAP) and polar tracking (F10) improve precision; ortho mode (F8) constrains movement to horizontal and vertical.

  • Selection cycling (Ctrl+W or the status bar) helps select overlapping objects by presenting a list.

  • The Quick Access toolbar and ribbon can be customized in the CUI editor; workspace settings are saved in the .cuix and profile.

  • Express Tools provide commands such as OVERKILL, BURST, and TEXTFIT that extend standard editing.

  • Autosave files use the .sv$ extension and are stored in the path set in Options > Files > Automatic Save File Location.

  • Backup files use the .bak extension and are created on save when the option is enabled.

  • A drawing opened read-only can be saved under a new name; the original remains unchanged.

Quick reference

Customization, Productivity, and Best Practices

  • Use a consistent layer standard such as the AIA or ISO 13567 naming convention so filters and standards checks work.

  • Place dimensions in paper space only when the measured geometry is in a viewport with a known scale; otherwise dimension in model space.

  • Set PSLTSCALE and LTSCALE together so linetypes display consistently in model space and in viewports.

  • Use named plot styles (STB) for standards-based lineweight control, or color-dependent (CTB) for legacy color-based plotting.

  • Keep title block data in attributes or fields linked to sheet set properties so revisions propagate.

  • Use eTransmit for delivery so xrefs, fonts, and plot styles travel with the drawing.

  • Purge and audit before archiving; archive the DWG plus any xrefs or bind them into a single deliverable copy.

  • Document system variable settings and customization files so a workstation can be rebuilt from a known configuration.

Quick reference

Customization, Productivity, and Best Practices

  • The Options dialog (OP) controls support file search paths, template settings, autosave, and plotting defaults.

  • Profiles (.arg) export and import these settings, allowing a standard configuration to be deployed across workstations.

  • The Startup Suite in APPLOAD loads AutoLISP routines automatically at each session.

  • Action recorder macros can be saved and assigned to a command or toolbar button for repeated tasks.

  • Script files run without user interaction and are useful for batch processing multiple drawings.

  • Tool palettes can be exported as .xtp files and shared; they reference blocks and commands by source path.

  • The CUI editor stores menu and ribbon customization in a .cuix file that can be transferred between installations.

  • System variable settings can be captured in a script or profile so a workstation can be restored after a reset.

Quick reference

Customization, Productivity, and Best Practices

  • Use a project template with predefined layers, styles, layouts, and page setups to start every drawing consistently.

  • Set annotation scale before creating annotative objects; changing it later rescales display but not the underlying geometry.

  • Keep model space at 1:1 and apply scale only in viewports to preserve measurement accuracy.

  • Use xrefs for shared base files and bind only for delivery or archival copies.

  • Purge and audit drawings before delivery to remove unused objects and correct structural errors.

  • Save in the release format required by the recipient; older formats may not support newer object types.

  • Record system variable and customization changes in a script or profile for repeatable workstation setup.

  • Use fields and sheet set properties for title block data so revisions propagate automatically.

Quick reference

Customization, Productivity, and Best Practices

  • Command aliases are defined in the .pgp file; REINIT reloads it after edits.

  • The CUI editor customizes menus, toolbars, ribbon panels, and keyboard shortcuts and saves to a .cuix file.

  • Action macros record command sequences for playback and can be assigned to toolbar buttons.

  • Script files (.scr) run command sequences without user interaction for batch tasks.

  • AutoLISP routines load with APPLOAD and can be added to the Startup Suite for automatic loading.

  • Profiles (.arg) store support paths, template locations, and plotting settings for deployment.

  • PURGE removes unused named objects; -PURGE with All purges all unused items in one pass.

  • Store reusable blocks in a shared library referenced by tool palettes or DesignCenter rather than copying between drawings.

Quick reference

Customization, Productivity, and Best Practices

  • Use named page setups in templates so every layout plots with the same device, paper size, and plot style.

  • Keep model space geometry at 1:1 and apply scale only in viewports to preserve dimension and annotation accuracy.

  • Name layers by discipline and content (e.g., A-WALL-FULL) so layer filters and standards checks work predictably.

  • Set annotation scale before placing annotative text and dimensions so objects are created at the correct display size.

  • Use xrefs for shared base files and bind only for archival or delivery copies.

  • Audit and recover drawings before delivery to fix structural errors and reduce file size.

  • Save drawings in the release format required by the recipient; older formats may lose newer object types.

  • Record system variable changes in a startup script or profile so a workstation can be restored to a known configuration.

Quick reference

Customization, Productivity, and Best Practices

  • Keyboard shortcuts and command aliases reduce mouse travel; the .pgp alias file is the standard place to define them.

  • Tool palettes group blocks, hatches, and commands and can be shared by exporting and importing .xtp files.

  • A template with predefined layers, styles, and layouts eliminates repetitive setup and enforces standards at drawing creation.

  • Autosave interval is controlled by SAVETIME; set a value that balances data protection against performance.

  • Layer filters and layer states let you switch between working configurations without manually toggling many layers.

  • Use fields for title block data linked to sheet set properties so revisions propagate without retyping.

  • Batch plotting with PUBLISH and a saved sheet list is faster and less error-prone than plotting each layout individually.

  • Regularly purge and audit drawings; unused named objects accumulate and slow opening, saving, and plotting.

Quick reference

Customization, Productivity, and Best Practices

  • Store company standards in a .dws file and attach it to templates so CHECKSTANDARDS can compare new drawings automatically.

  • Use a shared support path for menus, fonts, plot styles, and templates so all workstations resolve the same files.

  • Name and version drawings consistently; a clear revision scheme makes comparison and transmittal reliable.

  • Lock xref layers that should not be edited and use VISRETAIN to keep xref layer settings across reloads.

  • Save named views and layer states for recurring detail areas to avoid repeated navigation and layer setup.

  • Use the .arg profile to transfer plotting, support path, and template settings between workstations.

  • Keep a block library and reference it with DesignCenter or tool palettes instead of copying blocks between drawings.

  • Test templates and customization files on a copy before deploying them to a production environment.

Quick reference

Customization, Productivity, and Best Practices

  • Command line input accepts command names, aliases, and coordinate entry; dynamic input can be toggled with the F12 key.

  • Object snaps (OSNAP) and polar tracking (F10) improve precision; ortho mode (F8) constrains movement to horizontal and vertical.

  • Selection cycling (Ctrl+W or the status bar) helps select overlapping objects by presenting a list.

  • The Quick Access toolbar and ribbon can be customized in the CUI editor; workspace settings are saved in the .cuix and profile.

  • Express Tools provide commands such as OVERKILL, BURST, and TEXTFIT that extend standard editing.

  • Autosave files use the .sv$ extension and are stored in the path set in Options > Files > Automatic Save File Location.

  • Backup files use the .bak extension and are created on save when the option is enabled.

  • A drawing opened read-only can be saved under a new name; the original remains unchanged.

Quick reference

Customization, Productivity, and Best Practices

  • Use a consistent layer standard such as the AIA or ISO 13567 naming convention so filters and standards checks work.

  • Place dimensions in paper space only when the measured geometry is in a viewport with a known scale; otherwise dimension in model space.

  • Set PSLTSCALE and LTSCALE together so linetypes display consistently in model space and in viewports.

  • Use named plot styles (STB) for standards-based lineweight control, or color-dependent (CTB) for legacy color-based plotting.

  • Keep title block data in attributes or fields linked to sheet set properties so revisions propagate.

  • Use eTransmit for delivery so xrefs, fonts, and plot styles travel with the drawing.

  • Purge and audit before archiving; archive the DWG plus any xrefs or bind them into a single deliverable copy.

  • Document system variable settings and customization files so a workstation can be rebuilt from a known configuration.

Quick reference

Customization, Productivity, and Best Practices

  • The Options dialog (OP) controls support file search paths, template settings, autosave, and plotting defaults.

  • Profiles (.arg) export and import these settings, allowing a standard configuration to be deployed across workstations.

  • The Startup Suite in APPLOAD loads AutoLISP routines automatically at each session.

  • Action recorder macros can be saved and assigned to a command or toolbar button for repeated tasks.

  • Script files run without user interaction and are useful for batch processing multiple drawings.

  • Tool palettes can be exported as .xtp files and shared; they reference blocks and commands by source path.

  • The CUI editor stores menu and ribbon customization in a .cuix file that can be transferred between installations.

  • System variable settings can be captured in a script or profile so a workstation can be restored after a reset.

Quick reference

Customization, Productivity, and Best Practices

  • Use a project template with predefined layers, styles, layouts, and page setups to start every drawing consistently.

  • Set annotation scale before creating annotative objects; changing it later rescales display but not the underlying geometry.

  • Keep model space at 1:1 and apply scale only in viewports to preserve measurement accuracy.

  • Use xrefs for shared base files and bind only for delivery or archival copies.

  • Purge and audit drawings before delivery to remove unused objects and correct structural errors.

  • Save in the release format required by the recipient; older formats may not support newer object types.

  • Record system variable and customization changes in a script or profile for repeatable workstation setup.

  • Use fields and sheet set properties for title block data so revisions propagate automatically.

Quick reference

Customization, Productivity, and Best Practices

  • Command aliases are defined in the .pgp file; REINIT reloads it after edits.

  • The CUI editor customizes menus, toolbars, ribbon panels, and keyboard shortcuts and saves to a .cuix file.

  • Action macros record command sequences for playback and can be assigned to toolbar buttons.

  • Script files (.scr) run command sequences without user interaction for batch tasks.

  • AutoLISP routines load with APPLOAD and can be added to the Startup Suite for automatic loading.

  • Profiles (.arg) store support paths, template locations, and plotting settings for deployment.

  • PURGE removes unused named objects; -PURGE with All purges all unused items in one pass.

  • Store reusable blocks in a shared library referenced by tool palettes or DesignCenter rather than copying between drawings.