If you’ve ever applied a hatch pattern in AutoCAD only to watch it bleed straight through a sink, toilet, or door swing that was supposed to stay untouched, you’re far from alone. This is one of the most persistent frustrations reported on the Autodesk forums, and it stems from how AutoCAD’s hatch boundary detection interprets geometry — not from a bug you accidentally triggered. Understanding why this happens, and which fixes actually work, can save hours of rework on architectural and MEP drawings.
The issue typically surfaces when a user hatches a floor plan or wall section and finds the pattern ignoring objects that should act as “islands” — areas excluded from the fill. Even when those objects are outlined with a single continuous polyline, the hatch can still spill across boundaries or refuse to trim properly. Below is a breakdown of why this happens and the practical workarounds the AutoCAD community has tested over the years.
Why AutoCAD Hatch Boundaries Fail in the First Place
A user named zeulrick described the problem clearly on the AutoCAD forum: after upgrading his PC, hatching improved slightly, but a tile pattern still spilled into objects that weren’t supposed to be hatched, even though those objects were enclosed in continuous polylines. He noted that filling problem objects with a white solid hatch sometimes worked as a workaround, but it added extra steps to an already repetitive task.
Community member s.borello asked the key diagnostic questions that anyone troubleshooting this issue should ask first: did you select the object or pick an internal point, and how is your island detection configured? These two settings — selection method and island detection mode — are usually where the root cause hides.
Internal Point Selection vs. Object Selection
When using the HATCH command, AutoCAD offers two main ways to define a boundary: clicking an internal point or selecting objects directly. Zeulrick reported using internal point selection with island detection set to “Outer,” which works well most of the time but becomes unpredictable depending on the shape of the surrounding geometry.
This unpredictability isn’t random. Forum contributor Scot-65 offered a surprisingly specific rule of thumb: internal point selection tends to succeed reliably when the final hatch boundary resembles certain capital letters — C, E, F, G, H, I, J, K, L, M, N, S, T, U, V, W, X, Y, and Z — but becomes stubborn with shapes resembling A, B, D, O, P, Q, or R. In practical terms, this means boundaries with simple, open silhouettes are easier for AutoCAD’s analysis engine to read correctly, while shapes with enclosed loops or complex curves are more prone to misdetection.
Scot-65 also recommended drawing temporary “defpoint” lines (lines on the DEFPOINTS layer, which never plots) from problem areas — like the underside of a mirror to the top of a lavatory, or from a grab bar to a view box — to help the hatch analysis correctly separate islands. Leaving these defpoint lines in the drawing, rather than deleting them after hatching, helps maintain the hatch’s associativity if the geometry shifts later.
The Real Fix: Clean, Closed Polylines Without Duplicate Geometry
The breakthrough in this particular forum thread came when zeulrick shared an actual DWG file for community review. The accepted solution, posted by an anonymous AutoCAD user, identified the true culprit: duplicated geometry along the toilet’s perimeter. The drawing had both a closed polyline AND separate, overlapping line segments tracing roughly the same outline. AutoCAD’s hatch engine doesn’t always know how to interpret overlapping boundary geometry, which causes it to either skip the island entirely or hatch through it.
The fix was straightforward once identified: delete the redundant line segments, keep only the single closed polyline as the object outline, and then hatch using non-associative mode with outer island detection and the “Pick Points” option. With clean, non-duplicated geometry, the hatch respected the boundary correctly every time.
This solver also shared a genuinely useful technique that doesn’t get enough attention: the BOUNDARY command with the Polyline option. Instead of manually joining a scattered collection of arcs, lines, and other segments into a single closed polyline (which is tedious and error-prone with PEDIT), the BOUNDARY command automatically traces a closed polyline around any enclosed area, internal point included. For complex object outlines made of many small segments, this is almost always faster and more reliable than manual joining.
Other Practical Troubleshooting Steps
A few additional tips from the thread are worth keeping in your AutoCAD workflow:
- Always use closed polylines as boundary objects rather than relying on disconnected lines and arcs that visually form a closed shape but aren’t actually joined.
- Check for duplicate or overlapping geometry before hatching — this single issue resolved the entire problem in the case study above.
- If you see red circles after analyzing the boundary, AutoCAD is flagging gap errors; increasing the HPGAPTOL system variable can help the hatch tolerate small gaps in the boundary outline.
- Use the BOundary command (Polyline option) to generate a clean, closed boundary from messy or fragmented line work before hatching.
- Avoid associative hatch on complex, overlapping geometry — switching to non-associative hatch removed one variable that was contributing to the failure in the reference case.
Years later, another forum member, DavidRRUMCC working in the precast concrete industry, echoed how common this frustration remains, noting that unreliable island detection had led him to avoid hatches altogether except when absolutely necessary — despite needing concrete hatch patterns consistently across his sections. This reflects a broader sentiment among long-time AutoCAD users: the tool’s hatch boundary detection hasn’t fundamentally changed across many releases, so understanding these manual workarounds remains essential rather than optional.
Key Takeaways for Reliable Hatching in AutoCAD
Hatch boundary problems in AutoCAD almost always trace back to one of three issues: open or improperly joined polylines, duplicate/overlapping boundary geometry, or a mismatch between your selection method (internal point vs. object selection) and island detection setting. Before hatching a complex drawing, it pays to audit your boundary objects first — use the LIST command or simply zoom in to check for stray duplicate segments, and run the BOUNDARY command when you need a guaranteed closed polyline from existing linework.
If hatching still spills or refuses to trim, don’t default to covering the problem object with a white solid fill — that’s a workaround, not a fix, and it adds unnecessary clutter and extra editing steps down the line. Instead, clean up the underlying geometry first. As the community consensus in this thread shows, a five-minute geometry audit usually solves what looks like a stubborn AutoCAD “bug.”
For anyone still running into this issue, the original Autodesk forum thread remains an active resource where users continue to ask follow-up questions, suggesting this remains a live pain point even in recent AutoCAD releases.
References
- Autodesk Community Forums – “Hatch, hatching problems, hatch boundary, polyline” thread, AutoCAD Forum, posted March 12, 2019: forums.autodesk.com/t5/autocad-forum/hatch-hatching-problems-hatch-boundary-polyline/td-p/8653906
- Autodesk Knowledge Network – Hatch Boundaries documentation, AutoCAD Architecture Help: knowledge.autodesk.com
- Autodesk Knowledge Network – AutoCAD Troubleshooting Resources: knowledge.autodesk.com/support/autocad