Every render, animation and web viewer starts with a model. A clean model makes every later stage — UVs, texturing, rigging, rendering — faster; a messy one makes every stage fight back. These are the fundamentals we apply to every product and architectural model, whatever the software.
Polygons, subdivision surfaces or NURBS?
- Polygons — flexible and universal: the format of games, real-time viewers and most rendering pipelines.
- Subdivision surfaces — a low-resolution polygon cage that the software smooths at render time. Ideal for smooth product shapes and organic forms.
- NURBS and CAD surfaces — mathematically exact curves, used where dimensions must be precise for manufacturing. They are converted (tessellated) to polygons for rendering.
Most product visualization mixes them: engineering data arrives as CAD, and the rendering model is built or cleaned up as polygons.
Step by step
Set units and scale
Work in real-world units from the first click — millimetres for products, metres for architecture. Lighting, depth of field and simulations all depend on correct scale.
Gather references
Load orthographic reference images or drawings aligned to the front, side and top views. For architecture, work from plans and elevations with known dimensions.
Block out the big forms
Start with primitive shapes and get the proportions right before adding any detail. Most modeling mistakes are proportion mistakes.
Keep topology clean
Use evenly spaced quads and edge loops that follow the form. Avoid long thin triangles and n-gons on curved surfaces — they cause shading artifacts under subdivision.
Control edges with bevels or support loops
Nothing in the real world has an infinitely sharp edge. Small bevels catch highlights and make a render read as a real object instead of CG.
Check normals and shading
Recalculate normals, look for flipped faces, and inspect the model with a glossy material — shading problems that hide under matte grey show up immediately.
Name, group and clean up
Name parts, apply transforms, and delete hidden history and unused geometry. The next person to open the file — often you — will thank you.
Architecture specifics
- Model walls, floors and openings with real thickness, not single planes — light behaves differently around thin geometry.
- Keep repeated objects such as chairs, windows and plants as instances; it saves memory and render time.
- Use a consistent origin and orientation across files, so linked models line up.
Common mistakes
- Modeling detail the camera will never see.
- Mixing units between imported files.
- Leaving boolean operations uncleaned, which produces broken shading.
