--- title: "A Smooth CAD View Can Hide a Faceted Equipment Model" description: "Leviathan Systems — Technical content Published 2026-10-20; updated 2026-10-20." canonical: "https://www.leviathansystems.co/articles/cad-brep-surfaces-versus-tessellated-mesh" last-updated: "2026-10-20" --- # A Smooth CAD View Can Hide a Faceted Equipment Model Leviathan Systems — Technical content Published 2026-10-20; updated 2026-10-20. Choose equipment geometry by the dimensions and changes the recipient must obtain from it. Inspect the actual surfaces or facets, the approximation basis and a representative downstream task. A smooth view cannot establish those properties. B-Rep can retain useful surface geometry, but can also contain planar facets and lack the original features. A mesh can be suitable for an agreed coordination task when its approximation and content meet that task. ## Inspect the surfaces behind the equipment view In boundary representation, or B-Rep, topology records how faces, edges and vertices connect; geometry supplies their shapes. A face is a bounded portion of a surface, and an edge follows a curve. Loops delimit faces, including openings. Autodesk's Fusion API documentation distinguishes topology from geometry and separately identifies the surface underlying a face. For a cylindrical face, useful geometry can include an axis and radius. Those properties let a recipient ask a different question from measuring distances between selected points on flat facets. The buyer should identify the intended geometric entity: the cylindrical exterior, a planar mounting face or an opening boundary, for example. An equipment silhouette alone does not explain which entities the file contains. B-Rep can contain planar or curved surfaces, including surfaces whose shape is not an analytic cylinder. A model assembled from many small flat faces can therefore be a B-Rep without containing the intended smooth cylinder. Autodesk's documented faceted mesh conversion provides a concrete example: it makes individual mesh faces into individual faces on the resulting solid or surface body. Flat faces are appropriate when the intended part is flat. Ask what the returned faces represent, as well as whether the software calls the object a body. References: [A1](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/BRepGeometry_UM.htm), [A3](https://help.autodesk.com/cloudhelp/ENU/Fusion-Mesh/files/MESH-CONVERT-TO-SOLID.htm), [A6](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/fusion_BRepFace_geometry.htm) ## Separate closed volume from dimensional fidelity A B-Rep solid encloses a volume through connected boundary surfaces. An open surface body has an exposed boundary and does not supply that same closed-volume representation. A curved equipment skin or a single panel face can still be useful as surface geometry when the task concerns that surface. It should be described accordingly. Watertightness concerns closure. Dimensional fidelity concerns how closely the represented boundary matches the geometry it is supposed to describe. Imagine a faceted cylinder with closed end caps. Closing every seam would not make its flat sides coincide with an intended circular cylinder. Conversely, a useful cylindrical surface can remain open at its ends. Agree which property the recipient needs. A task involving a closed equipment volume requires more than a recognizable outer skin. A task locating one reference face may not require a complete solid. In either case, closure alone supplies no evidence that the dimensions, product revision or represented details are appropriate. References: [A1](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/BRepGeometry_UM.htm) ## Distinguish the display mesh from the delivered mesh Autodesk's Fusion API guide describes a triangular mesh maintained for graphical display alongside the B-Rep model. Visible facets can therefore belong to a display approximation while different underlying geometry remains available. The converse is equally important: a polished display may be showing facets that are the delivered geometry. Tessellation creates a discrete approximation of a surface. A triangulated mesh describes its boundary through vertices connected into flat triangular faces. Autodesk's Netfabb 2026 help describes CAD surface sections becoming collections of triangles, with face groups retaining useful groupings. A group identifying triangles from one surface is a relationship among those triangles; the grouping alone does not supply the original surface definition. An export may carry the approximation while leaving the source surfaces behind; identify which representation the handoff actually includes. The approximation needs a geometric basis. Fusion's current tessellation documentation distinguishes maximum surface-to-mesh distance, angular normal deviation and maximum edge length. These describe different constraints. A total triangle count does not locate the approximation error at the particular curved interface the buyer needs to assess. Shading adds another layer. Autodesk's Maya Creative documentation explains that vertex normals control the visual softness between polygon faces and can change edge appearance without additional geometry. Smooth shading can make flat facets look continuous. It cannot establish the boundary's dimensional fidelity. Here, smooth normals means a shading treatment; a separate operation that moves or adds geometry would need its own assessment. Ask whether the recipient is measuring the underlying surfaces, the delivered mesh or another representation generated during import. Changing the view's appearance does not answer that question. References: [A1](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/BRepGeometry_UM.htm), [A2](https://help.autodesk.com/cloudhelp/2026/ENU/NETF/files/GUID-00AC78B7-C3A1-4BFB-B48E-BDCE38242A7A.htm), [A4](https://help.autodesk.com/cloudhelp/ENU/Fusion-Mesh/files/MESH-TESSELLATE.htm), [A5](https://help.autodesk.com/cloudhelp/ENU/MayaCRE-Modeling/files/GUID-9C257D44-924D-4B3F-ADEF-C71FAA98EAB1.htm) ## Compare 12 and 48 segments on a 100 mm radius Original example CG-281 starts with an ideal circle of radius r = 100 mm. Replace its circumference with n equally spaced, straight, inscribed segments. Every vertex lies on the circle, but each segment cuts inside the arc between its vertices. The largest radial shortfall occurs at the segment midpoint. Draw a radius to a vertex and a perpendicular from the center to the segment midpoint. The resulting right triangle has hypotenuse r and half-angle pi/n, expressed in radians. The center-to-midpoint distance is r cos(pi/n), so the maximum inward radial deviation is e = r(1 − cos(pi/n)). For n = 12, e = 100(1 − cos(pi/12)) ≈ 3.4074 mm. For n = 48, e = 100(1 − cos(pi/48)) ≈ 0.2141 mm. Four times as many segments reduces this particular deviation substantially, but both polygons still pass exactly through their vertices. Checking only those vertices would miss the intervening shortfall. If that polygon represents an equipment exterior, its boundary understates the ideal circle's outward extent between vertices. A nearby object could appear farther from the equipment than it would from the ideal circular boundary. Smoothing the lighting across the facets leaves that geometric difference intact. This is a two-dimensional cross-section calculation with equally spaced inscribed segments. The segment counts are not complete three-dimensional triangle counts, software defaults, measured uncertainty or required site clearances. Other tessellations and other shapes need their own evaluation. The example demonstrates why a numerical distance read from a model can be precise while the represented boundary remains an approximation. ## Understand what conversion can change Changing representation can make geometry available to a different set of tools. It does not, by that fact, recover information discarded earlier. In Fusion's current documentation, faceted conversion preserves individual mesh faces as individual body faces, while prismatic conversion uses face groups to infer features and merge groups into faces. These are materially different geometric results. For CG-281, merely representing the 12 flat segments as new boundary faces would leave the same cross-section shortfall. A reconstruction that instead fits a circular or other smooth shape introduces a geometric interpretation. The recipient needs evidence for that interpretation against the appropriate source and the intended use. Many different curves can pass through a finite set of points; the points alone do not identify the original designer's choice. Feature history is another requirement. A conversion feature in a timeline records a conversion operation. It does not establish that the original sketches, dimensions, constraints and construction sequence have been recovered. Likewise, a supplied B-Rep may support useful direct geometric changes without supplying the original parametric design. Specify the change the recipient must make and ask the author to demonstrate it in the receiving environment. References: [A2](https://help.autodesk.com/cloudhelp/2026/ENU/NETF/files/GUID-00AC78B7-C3A1-4BFB-B48E-BDCE38242A7A.htm), [A3](https://help.autodesk.com/cloudhelp/ENU/Fusion-Mesh/files/MESH-CONVERT-TO-SOLID.htm) ## Choose geometry for the next dimensional or editing task For a visual equipment-location discussion, a simplified mesh may supply everything the recipient needs. For a dimensional comparison at a curved interface, the approximation at that interface becomes consequential. For continued editing, the available surfaces and modeling structure matter as well. None of these tasks is settled by choosing the largest file or the smoothest screenshot. Request a representative sample that includes the difficult geometry. Identify the authoritative product input and revision, model units, reference geometry and the intended receiving software version. Have the recipient demonstrate the actual question: retrieving the intended cylindrical radius and axis, locating a mounting face, or making the agreed geometric change. Where a mesh is proposed, ask how its deviation is established at the relevant interface. Agree the acceptable difference for the task with its responsible reviewer; this article supplies no universal tolerance. Keep approximation error separate from the source's relationship to the equipment. A mesh can closely reproduce the wrong product revision. An analytic cylinder can have the wrong radius. A faithful manufacturer model can describe nominal equipment without establishing its current installed position or condition. Higher tessellation quality resolves none of those source questions. Use the related guides for capture evidence, Revit/IFC exchange and separately schedulable rack components. Those questions complement the geometry requirement: the received boundary and available editing behavior must support the stated task. Reviewing that deliverable does not authorize fabrication or installation. ## Bring the geometry requirement to the planning inquiry Use Leviathan's Physical Infrastructure Planning & CAD service to discuss equipment layouts, routing coordination and the documentation those tasks require. Explain which equipment surfaces matter, what the next recipient must measure or change, and which authorized product inputs are available. Include whether an approximation is sufficient or whether particular surface geometry and editing behavior are required. Actual software, authoring resources, supported outputs and review scope are confirmed for the engagement before a specific CAD deliverable is committed. Use the project inquiry below to describe the decision and the representative output that would demonstrate it. That gives the proposed work a concrete geometry requirement while keeping the physical planning engagement with its service owner. ## Primary sources - [A1 — Autodesk Fusion API Help — Fusion Models (B-Rep and Geometry)](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/BRepGeometry_UM.htm). Checked 2026-10-20. Current API help, copyright 2026; no numbered release shown. Explains boundary structure, geometry, closed solids and display meshes. - [A2 — Autodesk Netfabb 2026 Help — About face groups](https://help.autodesk.com/cloudhelp/2026/ENU/NETF/files/GUID-00AC78B7-C3A1-4BFB-B48E-BDCE38242A7A.htm). Checked 2026-10-20. Netfabb 2026 help, marked as applying to the 2025.0 Update and later. Explains how CAD surface sections become triangle groups and how those groups support later interpretation. - [A3 — Autodesk Fusion Help — Convert a mesh body to a solid body](https://help.autodesk.com/cloudhelp/ENU/Fusion-Mesh/files/MESH-CONVERT-TO-SOLID.htm). Checked 2026-10-20. Current unnumbered Fusion help. Describes faceted and inferred prismatic results, plus the conversion feature recorded in a timeline. - [A4 — Autodesk Fusion Help — Convert a solid body to a mesh body](https://help.autodesk.com/cloudhelp/ENU/Fusion-Mesh/files/MESH-TESSELLATE.htm). Checked 2026-10-20. Current unnumbered Fusion help. Defines surface deviation, normal deviation and maximum edge length as separate tessellation controls. - [A5 — Autodesk Maya Creative Help — Polygon normals](https://help.autodesk.com/cloudhelp/ENU/MayaCRE-Modeling/files/GUID-9C257D44-924D-4B3F-ADEF-C71FAA98EAB1.htm). Checked 2026-10-20. Current unnumbered Maya Creative help. Explains face and vertex normals and their effect on polygon shading; useful for interpreting visual smoothness. - [A6 — Autodesk Fusion API Help — BRepFace.geometry Property](https://help.autodesk.com/cloudhelp/ENU/Fusion-360-API/files/fusion_BRepFace_geometry.htm). Checked 2026-10-20. Current API help, copyright 2026; property introduced August 2014. Identifies the underlying surface geometry separately from the face. ## Related Leviathan resources - [Physical Infrastructure Planning & CAD](/services/engineering-design) - [Existing drawings or a point-cloud survey?](/articles/gpu-cabling-existing-drawings-point-cloud-survey) - [Define a usable Revit or IFC exchange](/articles/gpu-cabling-revit-ifc-deliverable-brief) - [Separately schedulable rack components](/articles/gpu-rack-revit-family-schedulable-components) - [Choose useful model development](/articles/gpu-cabling-bim-level-of-development) ## Define the Equipment Geometry Your Planning Task Needs Describe the equipment interface, intended dimensions or edits, receiving environment and available authorized inputs so we can discuss the planning scope and supported outputs. [Discuss the scope](/contact?service=engineering-design&from=/articles/cad-brep-surfaces-versus-tessellated-mesh)