MODIFY COMMAND FIXES

How to Fix FILLET and CHAMFER Not Working ('Lines Are Non-Coplanar' or 'Radius Too Large')

Resolve every reason why FILLET or CHAMFER fails in GstarCAD and AutoCAD: non-coplanar Z elevations, TRIMMODE=0, locked layers, or polyline arc segment conflicts.

⚡ Quick Engineering Answer (TL;DR)

If FILLET says 'Lines are non-coplanar', flatten both objects to Z=0 (set Start Z = 0, End Z = 0, Elevation = 0 in Properties) and set OSNAPZ=1. If FILLET creates the arc without trimming the corner, type TRIMMODE and set it to 1. Hold the SHIFT key while picking two lines to force a sharp 0-radius corner.

1. Root Cause & DWG Database Symptom Analysis

When FILLET or CHAMFER refuses to join two intersecting walls or mechanical edges, the command line usually prints one of three diagnostic messages: "Lines are non-coplanar", "Radius is too large", or "Cannot fillet between these two entities".

2. Step-by-Step Resolution in GstarCAD & AutoCAD

Cause 1: 'Lines are non-coplanar' (Mismatched Z Coordinates or Extrusion Normals)

Even a $0.0001\text{ mm}$ difference in `Start Z`, `End Z`, or `Elevation`—or an inverted extrusion direction `DXF 210 = (0 0 -1)` from a 3D mirror—prevents a 2D fillet. Select both objects, open Properties (Ctrl+1), set Start Z = 0, End Z = 0, and Elevation = 0, or run FLATTEN.

Cause 2: Fillet Arc Draws But Original Corner Lines Do Not Trim (TRIMMODE = 0)

If GstarCAD draws the fillet arc but leaves the sharp corner extensions intact, type TRIMMODE at the command prompt and change it from 0 to 1 (or choose Trim → Trim inside the `FILLET` prompt).

Cause 3: Pro Tip — Hold SHIFT to Force a Zero-Radius Corner Join

You never need to change `FILLETRAD` to `0` just to close a sharp corner! Keep your working `FILLETRAD` (e.g., `5.0 mm`), launch FILLET, and hold down the SHIFT key while clicking the second line—GstarCAD temporarily overrides the radius to `0.0` for that click.

3. System Variables & Command Diagnostic Table

Variable / Command Default / Target Value Diagnostic Function & Fix Behavior
TRIMMODE 1 (Registry) 1 = Trims intersecting lines at fillet/chamfer; 0 = Leaves original lines
FILLETRAD 0.0 (or Design R) Stores current fillet radius inside the drawing
SHIFT + Click Temporary Override Forces a sharp R=0 corner join without erasing your saved FILLETRAD
DXF Group 210 (0.0 0.0 1.0) Normal vector; run FLATTEN if an entity has inverted (0 0 -1) normal

4. One-Click AutoLISP Fix Script (AutoLISP Coplanar Normalizer & Trim-Enabled Fillet Reset)

(defun c:FIX-FILLET-STATE ()
  (setvar "TRIMMODE" 1)
  (setvar "OSNAPZ" 1)
  (setvar "ELEVATION" 0.0)
  (princ (strcat "\n[Fillet Doctor] TRIMMODE=1 (Trim On), OSNAPZ=1, Current FILLETRAD="
                 (rtos (getvar "FILLETRAD") 2 2)))
  (princ)
)

Enterprise AC1032 Database Internals & Cross-Version Diagnostics

In multi-office engineering environments operating across GstarCAD 2027, GstarCAD Mechanical, GstarCAD Architecture, and legacy AutoCAD (2018–2027) seats, mastering How to Fix FILLET and CHAMFER Not Working ('Lines Are Non-Coplanar' or 'Radius Too Large') requires understanding how the underlying AC1032 DWG binary database serializes entity handles, symbol table records, and Named Object Dictionary (NOD) pointers.

1. DWG Header & Registry Persistence Scope

Variables and object properties fall into three persistence scopes: Drawing-Saved (DXF Header) variables that travel with the .dwg file to subcontractors, Registry-Saved (Profile .arg) settings that persist per Windows workstation user, and Session-Volatile states that reset on every launch unless locked inside acaddoc.lsp. Always verify persistence scope via SYSVDLG before issuing sheets to an ISO 19650 Common Data Environment (CDE).

2. Multi-Core Regeneration & Memory Hygiene

When processing large civil corridors, dense plant P&IDs, or 50-sheet architectural Xref trees, unpurged Registered Application IDs (REGAPP), orphaned DGN stroke dictionaries, and redundant annotation scales degrade spatial index (INDEXCTL = 3) lookup speed. Executing a pre-submittal AUDIT, command-line -PURGE → Regapps, and OVERKILL pass keeps file open times under 2 seconds on GstarCAD's multi-threaded graphics kernel.

3. Hybrid AutoCAD + GstarCAD Team Coexistence

Because GstarCAD reads and writes native AC1032 binary records without intermediate import/export translation, dynamic block grips, associative hatches, XData payloads (DXF groups 1000–1071), Paper Space viewport layer overrides (VPLAYER), and X.509 digital signatures round-trip losslessly between AutoCAD and GstarCAD seats on shared SMB/BIM cloud folders.

Production Field Verification Protocol (ISO 9001 / ISO 19650 Gate)

  1. Baseline Template Audit: Confirm that the active drawing inherits layer naming, linetype scales (PSLTSCALE = 1, MSLTSCALE = 1, LTSCALE = 1.0), and dimension styles from the enterprise .dwt / .dws standards file via CHECKSTANDARDS.
  2. Coordinate & Unit Integrity: Run -DWGUNITS or check INSUNITS, LUNITS, and MEASUREMENT to guarantee 1:1 metric (`mm`/`m`) or imperial (`in`/`ft`) block and Xref insertion scaling, with OSNAPZ = 1 preventing unintended 3D elevation drift.
  3. Submittal Packaging & Mobile Review: Lock all Paper Space viewports (`DisplayLocked = Yes`), bind or relative-path all external references via ETRANSMIT, and verify final plotted PDF/A lineweights (`ISO full bleed`) alongside DWG FastView mobile cloud markup links.

Related Engineering Guides, Courses & Troubleshooting FAQs

Continue building your CAD engineering mastery with these related GstarCAD Academy technical references:

Need 100% Native DWG Compatibility Without Subscription Lock-In?

Engineered by Suzhou Gstarsoft Co., Ltd. (SSE: 688657), GstarCAD 2027 opens, repairs, and plots AC1032 DWG files with full command and AutoLISP parity.

Download Free 30-Day Trial → All Troubleshooting FAQs AutoCAD Migration Hub