AreaDWG save data loss & save report
v1 Behavior & ReasonAn untouched DXF is preserved as-is, whereas saving DWG is not guaranteed lossless and can lose data the engines do not understand.
How It Appears to UsersEvery DWG save shows a report of what changed or was omitted.
AreaEditing imported 3D solids
v1 Behavior & Reason3D solids imported from DWG can be viewed and kept when saving, but are not editable in v1. Older R13–R2000 3D solids are kept in the file on save and counted in the report, though not drawn on screen. Solids created in MoonCAD are editable.
How It Appears to UsersAttempting to edit an imported solid shows a clear notice; R13–R2000 solid counts appear in the save report.
AreaMultileader (MLEADER) creation
v1 Behavior & ReasonMLEADER is not included as a creation command in v1 because multileaders require their own style table, multi-leader landing/dogleg layout, and block/text content subsystem; use LEADER and QLEADER for leader callouts. Existing MLEADER and MULTILEADER entities in opened files still display, stay in the origin records, and come back on save.
How It Appears to UsersStated on the Compatibility page and command reference.
AreaGroup (GROUP) selection mode
v1 Behavior & ReasonSelecting by group (G) at selection prompts answers UNSUPPORTED in v1 because no group-creation command is in v1 scope; existing GROUP objects in opened files are preserved on save.
How It Appears to UsersReported on the command line when G is entered during selection.
AreaAssociativity for dimensions, hatches, and arrays
v1 Behavior & ReasonNewly created dimensions, hatches, and arrays are plain geometry and do not automatically update when adjacent objects move.
How It Appears to UsersListed as partial on DIM*, HATCH, and ARRAY* on the Compatibility page.
AreaOne document per browser tab
v1 Behavior & Reasonv1 opens one drawing per browser tab; use browser tabs for multiple drawings. FILETAB toggles the top document tab strip.
How It Appears to UsersDocumented here in the user manual.
AreaPersonal API key on public deployments
v1 Behavior & ReasonOn public deployments without a server access token, the AI copilot runs with the user's own API key entered in the settings dialog.
How It Appears to UsersShown in the AI panel (MOONAI) settings.
AreaUndo history across .mcdz reopens
v1 Behavior & ReasonUndo history survives crash recovery within a session, but resets after closing and reopening a .mcdz file to keep files small.
How It Appears to UsersDocumented here in the user manual.
AreaGrip editing modes
v1 Behavior & ReasonStretch and Move grip modes are supported; use ROTATE, SCALE, and MIRROR commands for rotation, scaling, and mirroring.
How It Appears to UsersListed as partial on the Compatibility page.
AreaDynamic input tooltip
v1 Behavior & ReasonThe floating cursor tooltip is off by default; all coordinate entry rules work in the bottom command bar.
How It Appears to UsersListed as partial on the Compatibility page.
AreaBrowser coverage
v1 Behavior & ReasonFull verification runs on Chromium-based browsers; Firefox and Safari receive basic smoke checks.
How It Appears to UsersStated on the Compatibility page.
AreaCloud accounts & real-time collaboration
v1 Behavior & ReasonNo user accounts, cloud storage, or multi-user servers; files remain local on your machine.
How It Appears to UsersZero sign-up required.
MoonCAD checks supported file formats (DWG, DXF, PDF, SVG, STL, STEP) with independent file readers and geometry checkers, and publishes the pass, partial, or absent status of each command and entity type on the Compatibility page.