Anatomy of a 3D Model
Introduction
In the previous sections, we've ended with a cube that we can move, scale, and rotate, and we learned that this 3D model is basically a cloud of data points (vertices) connected by edges to form faces.
But a mesh is more than just a surface. Looking at a model without understanding its underlying connections is like looking at a building and judging how stable it is just by its visual appearance. The 'skeleton' of the mesh dictates its reliability, its flexibility, and sometimes its origin. Let's look at what the structure of the data is actually telling us.
Key Insights
- The Big Three: Geometry, Topology, Poly-count
- Mesh integrity: Manifold vs Non-Manifold
- Normals and surface orientation
- Common mesh problems and fixes
The Core Attributes of a 3D Model
Every model you create or import is defined by specific data sets. We prioritize three attributes above all others:
| Attribute | What It Is | Why It Matters |
|---|---|---|
| Geometry | The overall shape and form | Accuracy of representation |
| Topology | How vertices, edges, and faces connect | Editability and deformation |
| Poly-count | Number of polygons in the mesh | Performance and manageability |
Secondary attributes (UVs, materials, textures) matter but are not our primary concern for now.
BVI Interactive
In the 'Active Lesson' pulldown menu you can see a visual example of the topics described below.
Geometry: The Shape
Geometry is what you see: the shape being represented. A building, a scene, an object, a landscape. This is the most obvious aspect of a model and the shape must accurately represent what you're documenting.
Sources of Geometry: Modeled vs. Captured
Understanding where your geometry comes from is useful because it determines what constitutes "good" topology.
Modeled Geometry (Created) This is where quad-based topology matters. Quads allow for clean subdivision, predictable deformation, and ease of editing. Good edge flow follows natural contours and features.
Captured Geometry (Scanned) This comes from photogrammetry, LiDAR, structured light scanning, or similar technologies. Captured geometry almost always consists of triangles. This is not a flaw, it's optimal for this kind of representation. The triangles represent actual measured data points. A scan of a scene or object, in most cases, can or should remain triangulated; "bluntly" converting it to quads (by a process called remeshing) introduces computational interpretation and potential error. If your scene or object demands real time use, we can however apply a high poly to low poly workflow like is used for game assets, where we use the high poly model as a base and bake the details into a normal and/or height map. For now that is too advanced, but it is good to know that it is an option when a scene demands rigerous optimization.
Key Distinction: Bad topology for editing ≠bad topology for evidence. A perfectly photoscanned captured triangle mesh may be "bad" for manipulation but excellent for forensic analysis. Carefully consider "improving" scanned geometry by retopologizing, and do so when you have explicit reasons to.
Topology: The Structure
The network of vertices, edges, and faces, and the relational organization that defines the continuity of a surface.
Topology governs how a model behaves when:
- Transformed or deformed
- Subdivided or simplified
- Processed by modifiers
- Used for simulation or analysis
The Building Blocks: Tris, Quads, and N-Gons
| Face Type | Sides | Use Case |
|---|---|---|
| Triangle (Tri) | 3 | The GPU's native format; used in a quad based mesh they will influence/disturb edge flow & possibly shading |
| Quad | 4 | Preferred for modeling; subdivides cleanly |
| N-Gon | 5+ | Avoid when possible; used in a quad based mesh they will influence/disturb edge flow & possibly shading |
Good Topology vs. Bad Topology
Within the 3D modeling world there is an evergreen discussion about what is "good" topology and what is "bad" topology. A common misconception is that a "good" model consists of Quads only. In reality, if topology is good or bad depends on what the intended use of the model and the intended use of its topology. I'd like to think more along the lines of clean vs. dirty topology. When topology is clean it adheres, as best as it can, to the rule of Quad topology (with some tri's and Ngons here and there). In contrast topology can also be dirty, or a mess. Even when dirty it can still do the job you want it to do and is acceptable for the situation and the context of an investigation. You can use it, even when it might not be considered 100% clean/good.
For modeled geometry, clean topology means:
- Quad-based modeling: Faces are primarily (!) four-sided (quads), but well placed triangles and poles are not an issue and often necessary. The reasons for this are that
- Quads deform predictably when subdivided
- Shading is stable
- the model is easier to interpret
- the model is easier to manipulate
it's a standard in professional workflows.
- Logical edge flow: Edges should follow natural contours and features of the object. Clean topology makes models easier to edit and interpret and offer a lot of flexibility.
For captured geometry: Usually scanned topology consists of (a (very) large amount of) triangles, and therefor has no flow. But when the mesh depicts the original object or scene accuratly this doesn't have to be a problem. Triangles from a scan are data, not flaws.
Poly-count: The Weight
Poly-count is the total number of faces and/or triangles in your mesh. This amount directly affects rendering performance, file size, and editability.
Common terminology
| Density | Appearance | Trade-offs |
|---|---|---|
| High Poly | Smooth, detailed | Heavy computation, hard to edit |
| Low Poly | Blocky, simplified | Fast performance, easy to edit |
Low poly typically means using the minimum number of polygons necessary to accurately represent a shape's geometry . No more, no less.
Why it matters: A "light" scene allows you to import hundreds of objects (vehicles, buildings, witnesses, multiple scans) without crashing your, or others' computers when sharing or collaborating. Working with bloated geometry slows down your viewport and therefore your analysis, makes files unnecessarily large, and renders slower.
Modern considerations: With modern GPUs, polygon count has become less of a bottleneck than in the past, today's hardware can handle much higher poly counts efficiently. However, keeping geometry clean and efficient is still always a good practice. Efficiency matters not just for performance, but for file management, collaboration, and workflow speed.
Finding Balance: The goal for any model or scene is not "as few faces as possible" or "as many faces as possible," but as many faces as are required. Ask yourself: What level of detail do I need, and is this topology actively participating in adding the detail I aim for?
In practice: In most visual investigation use cases, you would stick to a low-poly to mid-poly baseline. This provides sufficient detail for analysis while maintaining performance and editability. High-poly models are certainly used, but typically reserved for when you need more detail, such as recreating an intricate construction of a specific object that's central to your investigation.
Context matters: If you're documenting a distant building, facade details or using a million-poly photoscan may be unnecessary. If you're reconstructing a scene with specific objects that play a useful role in answering your research question, precision matters. Also consider that silhouettes really help when photo-matching, so if you need more faces to establish a better silhouette, don't hesitate to add them.
Normals: The Orientation
In 3D space, a face is infinitly flat, there's no way to distinguish between "front" and "back" because it's purely geometric with no directional information. To establish this every planar face has a normal vector, a direction perpendicular to the plane. Normals determine how light interacts with a surface, it tells the render engine in which direction light should bounce of the surface.
Incorrect, or "flipped" normals cause inverted shading, making a mesh appear glitchy. They also influence modeling, as certain procedures and modifiers rely on 'knowing' if the faces of a mesh point in the right direction.
Mesh Integrity: Manifold vs. Non-Manifold
"Manifold" is a mathematical term describing a geometry that can physically exist in the real world as a continuous surface. In Blender, "Non-Manifold" covers two very different categories: Intentional Surfaces (useful) and Corrupt Data (harmful).
Intentional Non-Manifold (Open Surfaces)
This is when a mesh has open edges (holes) but structurally sound connections.
- Example: A single plane representing a wall, or a terrain surface.
- Status: Valid
- Use Case: Line-of-sight reconstruction, background environments, and lightweight visualization. You do not need to add "thickness" to a wall just to make it manifold if you just want to use it for visibility. In the real world a wall without thickness could not exist, but in a scene we don't need to give a wall thickness if we are not going to use this thickness in some way, shape or form.
Practical optimization: Consider a building within a larger scene: if its floor is never visible from any camera angle or viewpoint in your investigation, you could decide to leave it out entirely. This technically makes the model non-manifold, but since you'll never see the "hole," it doesn't matter for your use case.
When optimizing, you can follow the principle: "If you can never see it, remove it (or don't add it)." That said, if the model is low-poly anyway, you might as well include these faces for completeness, it won't significantly impact performance and keeps the geometry clean and predictable.
Corrupt Non-Manifold (Broken Geometry)
This is when the mesh contains topological errors that cause rendering glitches, shading artifacts, and calculation failures. This should always be fixed, regardless of the use case.
-
Internal Faces (T-Junctions): When a third face extrudes from an edge that is already connecting two other faces. The software gets confused about which side is "inside," causing black shading artifacts.
-
Overlapping Geometry (Doubles): When two vertices or faces occupy the exact same coordinate space.
- The Consequence: Z-Fighting. The renderer cannot decide which face is in front, causing the surface to flicker or strobe between the two. This makes a mesh look glitchy.
Why Integrity Matters
Even if you aren't doing physics simulations, corrupt Geometry may hurt a mesh:
- Visual Noise: Z-fighting (flickering) can influence the capability to edit a mesh.
- Shading Errors: Bad normals from internal faces can make a surface look dark or shadowed when it should be lit, potentially affecting lighting.
- Tool Failure: Boolean operations (e.g., cutting a "sightline" hole through a wall) will fail if the wall contains corrupt non-manifold data.
First Aid Integrity Checklist
Blender offers some built-in tools to identify non-manifold aspects of a mesh.
- Check for Doubles: Edit mode, Select All
A>M> Merge by Distance. (Fixes overlapping/Z-fighting). - Check for Internal Faces: Edit mode, Select All
A> Select Menu > Select All by Trait > Interior Faces. (Delete these). - Visual Check: Look for "shimmering" textures or black spots on the mesh surface.
- The 3D Print Toolbox (a built-in Blender addon) is a powerful diagnostic tool, even if you never intend to print a physical object.
Summary
A good 3D model balances visual recognizability with technical efficiency. These concepts are foundational not just for "modeling well," but for creating and identifying clear, interpretable, and robust models within Blender.
| Concept | Key Takeaway |
|---|---|
| Geometry | The shape: what you're representing |
| Topology | The structure: how edges flow determines editability |
| Poly-count | The weight: use only what is needed based on shape and detail demands |
| Normals | The orientation: tells light which way to bounce |
| Manifold | The integrity: required for simulations and printing |