Wipeouts — Use wipeouts to mask underlying objects for clarity

Historical Context & Motivation

Technical drawing has always grappled with the tension between information density and visual clarity. In hand-drafted engineering documents, drafters would use opaque correction tape or white paint to mask underlying linework before placing annotations—a physical wipeout that ensured text, symbols, and callouts remained legible against complex geometry. As CAD software replaced drafting boards, the need for an analogous digital mechanism became apparent: without selective masking, dense drawings produced overlapping annotations that were nearly impossible to interpret in print.

AutoCAD's evolution toward annotation clarity mirrors the broader software engineering principle of separation of concerns. Just as a well-designed API hides implementation details behind a clean interface, wipeouts hide distracting geometry behind a clean annotation surface. The WIPEOUT command was introduced to address a fundamental problem in documentation workflows: how to maintain both the integrity of the underlying model and the readability of the final deliverable.

The core question that wipeouts address can be stated concisely: how does one overlay textual or symbolic annotations on a complex drawing without the underlying geometry rendering those annotations illegible? This is not merely an aesthetic concern—in engineering and architectural practice, ambiguous or unreadable annotations can lead to fabrication errors, code violations, and costly rework. The wipeout object provides a declarative masking solution that preserves the underlying data while controlling its visual presentation.

Core Principles & Definitions

A wipeout in AutoCAD is a polygonal object that renders as a blank region matching the drawing background color. It functions by exploiting the draw order (z-order) system: objects drawn later in the sequence appear on top of objects drawn earlier. When a wipeout is placed above underlying geometry in the draw order, it occludes—or masks—everything beneath it, creating a clean visual canvas for annotations. Importantly, the masked objects are never deleted or modified; they remain fully editable and will reappear if the wipeout is removed.

Visual Explanation

How a Wipeout Masks Underlying Geometry

The diagram above illustrates the fundamental problem and solution. On the left, the annotation "PUMP P-101" is placed directly over a grid of structural lines and diagonal members; the text competes with the linework and becomes difficult to parse at a glance. On the right, a wipeout region is inserted between the geometry and the text in the draw order stack. The wipeout fills with the background color, effectively erasing the visual presence of the lines beneath the annotation without modifying the actual drawing data. This three-layer compositing approach—geometry, then wipeout, then annotation—is the canonical pattern for using wipeouts in production drawings.

Notice that the wipeout boundary (the green dashed rectangle in the diagram) can be toggled. Setting WIPEOUTFRAME = 0 hides the boundary entirely, making the mask seamless. Setting it to 1 displays the frame on screen and in plots, which is useful during editing but undesirable in final deliverables. The value 2 displays the frame on screen but suppresses it in printed output—a practical compromise for authoring workflows.

How Wipeouts Work — The Draw Order Engine

Understanding wipeouts requires understanding AutoCAD's draw order system. Every object in a drawing exists in a display list that determines the order in which entities are rendered to the screen and to plotted output. Objects higher in this list are drawn later and therefore appear on top. The draw order is conceptually identical to the z-index in CSS or the painter's algorithm in computer graphics: the last-painted element covers anything beneath it. Wipeouts exploit this by acting as opaque polygons in the display list, occluding all objects with a lower draw order.

The Draw Order Stack Model

The draw order mechanism in AutoCAD is managed through a linked list stored per layout. Each entity in the drawing database carries a position index in this list. When you invoke DRAWORDER and choose "Above Object" or "Below Object," AutoCAD repositions the selected entity's index relative to the reference entity. The TEXTTOFRONT command is a batch operation that iterates through all text and dimension entities and moves them to the highest positions in the display list—a useful companion to wipeout workflows because it ensures all annotations remain visible after wipeout insertion.

Internally, a wipeout is stored as a specialized raster image entity with a 1×1 pixel white bitmap. AutoCAD clips this image to the polygon boundary and renders it opaque at the background color. This implementation detail explains why wipeouts interact with the IMAGEFRAME system variable in older versions—though modern releases provide the dedicated WIPEOUTFRAME variable to separate wipeout frame visibility from image frame visibility.

Detailed Workflow & Classification of Masking Methods

Creating a Wipeout: Step-by-Step Command Sequence

1. Step 1: Type WIPEOUT at the command line and press Enter. The command prompt displays options: Specify first point or [Frames/Polyline].
2. Step 2: Pick vertices to define the polygonal boundary. Each click adds a vertex. The region must be closed—AutoCAD automatically closes the polygon when you press Enter after the last point.
3. Step 3: After the wipeout is created, use DRAWORDER to position it above the geometry you want to mask and below any annotations you want to display.
4. Step 4: Set WIPEOUTFRAME to 0 or 2 to hide the boundary in the final output. Verify by previewing the plot.

Comparison of Masking Methods in AutoCAD

The wipeout object is the most versatile of these methods because it supports arbitrary polygonal shapes, works with any entity type (not just text), and is independent of background color. The MTEXT Background Mask is often sufficient for simple text-over-geometry scenarios, but it only produces rectangular regions and cannot mask behind non-text objects like block references or custom symbols. For computer science students, the distinction is analogous to choosing between a specialized CSS property like text-shadow and a general-purpose compositing layer—each has its place, but the general tool covers more cases.

Worked Example — Masking Behind a Title Block Callout

Consider a mechanical floor plan drawing in which dense piping runs cross through a region where you need to place a callout bubble referencing Detail A on Sheet 3. The callout is a circle with text inside, and the piping lines currently run directly through the callout location, making it unreadable. We will use a wipeout to mask the piping behind the callout.

Strengths, Limitations, and Practical Considerations

Connection to Advanced Annotation Techniques

Wipeouts represent a fundamental masking strategy, but AutoCAD's annotation ecosystem extends well beyond simple polygonal occlusion. Understanding how wipeouts relate to more advanced techniques allows you to select the right tool for each documentation scenario and to build more maintainable, scalable drawing templates. The table below contrasts wipeouts with several advanced annotation and masking features available in modern AutoCAD releases.

The progression from manual wipeouts to integrated annotation properties mirrors a broader software engineering pattern: moving from imperative, manual interventions toward declarative, property-driven configurations. Just as modern UI frameworks encourage declarative component styling over manual DOM manipulation, modern AutoCAD encourages using built-in masking properties on text, dimensions, and leaders wherever possible, reserving wipeouts for cases where no built-in property exists—such as masking behind complex block references, detail callouts, or custom graphical elements. As you advance, consider building custom dynamic blocks that embed wipeouts internally, exposing clean insertion behavior that hides the masking mechanism from end users.

Practice Problems

Lesson Summary