▶You run Create Solids from Surfaces between the design and the ground, and AutoCAD returns Modeling Operation Error. Or worse: it finishes, but delivers half — the fill comes out and the cut does not, nothing on screen complains, and volume is missing.
It is not a random defect, and it is not your drawing. There is a cause, and it explains why no update has fixed it yet.
The native command builds a mesh of triangles between the two surfaces and asks AutoCAD's modelling kernel — ACIS — to convert it into a solid.
But a mesh is a list of loose triangles. Nothing in it records which face borders which, and a solid is exactly that: faces, edges and the relationships between them. So ACIS has to guess back the topology that was discarded. In earthworks — kerbs, bench steps, slope crests and toes — that guess runs into facets meeting at 0.003° and faces one micrometre wide. It turns ambiguous, and ACIS refuses. The error name is literal: eAmbiguousInput.
Drag sideways to see the whole diagram.
There are four official Autodesk support articles on the same failure, each with its own code:
| Code | Official article | Recommended workaround |
|---|---|---|
18030 | Cannot extract 3D Solids between two surfaces | Move one of the surfaces 1 millimetre |
83028 | No solid can be created based on surfaces | Export LandXML, reimport into a fresh DWG, delete bad triangles |
83027 | Cannot extract 3D Solids between two surfaces | Crop the surface and try it in pieces |
18028 | Error 18028 running 3D Solid commands | Rebuild the solids |
The vendor's official recommendation, in the first case, is to nudge the terrain by one millimetre and try again.
In 2021 an Autodesk employee filed the idea More information about the boolean failure in Civil 3D, quoting error 18027 and writing that users have to do "very tedious work… usually, this is a trial and error method that not always brings positive results." It has been Under Review since 2022, with comments through December 2025. The oldest public report we found is from 2016.
SCENG Solids does not take that path.
The step that fails in the native command — rebuilding by guesswork information that had already been thrown away — simply does not exist in our engine. Without it, there is nothing to turn ambiguous and nothing to refuse.
How we get there is our problem. What matters to you is what can be measured — and that is what follows.
A piece of 10,838 faces, 47.2080 m³, measured in Civil 3D 2026:
| Path | Time | Result |
|---|---|---|
| Mesh conversion (native) | 2.3 s | Refused — eAmbiguousInput |
| SCENG Solids | 0.6 s | Solid of 47.2080 m³ — ratio 1.000000 |
Same volume, to the sixth decimal, on a piece the native path had just refused.
And it is not a one-off: across 28 logged runs, 247 acceptances and no refusals. The latest production run delivered 145 solids in 43.9 seconds, without a single call to the mesh converter and with no volume missing — five of those cases would have been refused by the native command.
Three uncut screen recordings.
▶The error happening on the native command and not happening on ours, on the same pair of surfaces.
▶The time for both, in the case where the native command does finish.
▶The command end to end.
SCENG Solids from Surface is a single installer for Civil 3D 2026 (update 25.1.179 or later) and 2027. One command: SCENG_SOLIDSSURFACE. Every solid is born with the IFC 4.3 quantity set of its class — Qto_EarthworksFillBaseQuantities and Qto_EarthworksCutBaseQuantities — with the volume read automatically from the solid itself.
It also ships inside SCENG Tools, for anyone already using the suite.
The SCENG team — always innovating to make your work in Civil 3D easier.
Comments are open to registered users.
No comments yet. Be the first.