Studio Matrx Monthly · Volume 1 · Issue 2 · July 2026
Amogh N P
 In loving memory of Amogh N P — Architect · Designer · Visionary 
A macro shot of a real carved wooden jaali screen backlit by a window, its pierced lattice pattern crisp against the bright light, warm teak tones
Unit IIIInterior Computer Studio II — 3D Modelling & Visualization

Modelling Workflow & Interoperability

The silent interop trap, the units problem, and the silhouette rule

A model rarely lives in one program. It gets exported to a renderer, handed to a consultant, sent to a fabricator — and every one of those moves is a translation that quietly drops something. This unit is about surviving that journey: which format carries what, why the losses are silent, the units mismatch hiding behind the famous 1/25.4, and the single most useful rule in the whole course — the silhouette tells you what must be real geometry and what can be a normal map.

Learning objectives

By the end of this lesson, you will be able to — mapped to the course outcomes for Interior Computer Studio II:

1
CO3 · Understand

Explain why interoperability formats lose data SILENTLY, and why you check the receiving end, not the sending one.

2
CO3 · Apply

Choose the right format for a given hand-off — render, web/AR, 3ds Max, fabrication, coordination.

3
CO3 · Understand

Explain the units problem behind the 1/25.4 scale error and how to avoid it.

4
CO3 · Apply

Apply the silhouette rule to decide what must be real geometry and what can be a normal map.

5
CO3 · Analyse

Explain why 'more polygons is always better' inverts at the top end, and what that implies for a scene.

6
CO1 · Understand

Explain what PBR is and why metallic-roughness made materials portable between engines.

Silent loss

The interop trap

The danger is not that a format loses data — it is that it loses it with no warning. Know what each carries, pick the right one for the destination, and check the receiving end. And set your units first.[1, 2, 3]

The loss is silent. your scene · geometry · cameras · lights · animation · hierarchy OBJ export no dialog. no warning. what arrives · geometry · cameras · lights · animation · hierarchy dropped — no warning The sending app still looks correct, because it still has everything. So CHECK THE RECEIVING END. OBJ also declares NO units — the commonest cause of a model arriving 25.4× too big or too small. SketchUp → V-Ray or Enscape? Don't export at all — the renderer reads the model live.
DiagramA model carrying geometry, cameras, lights and animation exported through OBJ, arriving with only geometry and the rest dropped without warning
The 1/25.4 mystery is a units mismatch. 1 unit tagged "inches" SketchUp works in inches 1 unit read as "mm" 3ds Max default unit is also inch 1 in = 25.4× the same cube, read in the wrong unit The rule is boring and reliable Set your system units BEFORE import. Never change them mid-scene. Check the RECEIVING end, not the sending one. The model is not cursed — it was told inches and read millimetres.
DiagramTwo identical cubes, one read as inches and one as millimetres, showing the 25.4 factor behind the mysterious scale error

The danger is not loss — it is silence

Every exchange format loses something, and if that were the whole story it would be manageable. The real trap is that formats lose data SILENTLY. Export a scene to OBJ and your cameras, lights, animation and scene hierarchy are simply gone — with no dialog saying 'I dropped your cameras.' The model opens, the geometry is there, everything looks fine, and the work you cannot see is missing. So the professional habit is precise: know what each format carries before you use it, and CHECK THE RECEIVING END, not the sending one. The sending application always looks correct, because it still has everything.[1]

Try the interop matrix

What dies in transit

Pick where the model is coming from and where it is going, and watch exactly which properties are dropped silently — coloured the alarm colour, because no export dialog will ever warn you.

File-format interop matrix · what dies in transit

SKPOBJ (+MTL): dropped silently

Textures embeddedCamerasScene hierarchyUnits declared

No export dialog warns you. The sending app still shows everything — you find out at the receiving end. Per the Blender manual, OBJ carries geometry, UVs, normals and MTL materials — and silently drops cameras, lights, animation, armatures, parenting, transforms and vertex colours. Its MTL material model is Phong-era: no roughness, no metalness. And OBJ declares NO UNITS at all — the single commonest cause of a model arriving 25.4× too big or too small.

FormatGeometryNormalsUVsPBR materialsTextures embeddedCamerasLightsAnimationScene hierarchyUnits declaredSemantics (BIM data)
OBJ (+MTL)
FBX
glTF / GLB
DWG / DXF
SKP
IFC
STL
3DS (legacy)
carries lost silently n/a

The danger is not that formats lose data — it is that they lose it SILENTLY. Know what a format carries, and check the receiving end, not the sending one. Compiled from the Blender import/export notes and the glTF 2.0 specification.

Real geometry vs normal map

The silhouette rule

A normal map fakes surface relief for light but moves no vertices, so it is invisible at the edge. Break the outline — a jaali, a cornice, carved teak — and it must be real geometry; leave the surface flat — plaster, weave, grain — and a map suffices. And “more polygons is better” inverts once triangles shrink below a pixel.[4, 5]

The silhouette decides. backlight carved jaali — real geometry the pierced EDGE breaks the outline normal map on a flat plane the silhouette stays dead straight Real geometry: cornices, skirting, jaali, carved teak, turned legs — you see their edge against the light. Normal-map instead: plaster texture, fabric weave, wood grain, grout lines — they never change an outline.
DiagramA carved jaali whose pierced edge breaks the outline as real geometry, beside a flat plane whose normal-mapped texture leaves the silhouette straight
More polygons ≠ better. visible quality polygon count → gain, while it lasts flattens at pixel size up to 8× shading, 0 gain triangles shrink below a pixel; the GPU shades each covered pixel several times over — Fatahalian et al., SIGGRAPH 2010 Past pixel density, extra polygons cost shading work and give nothing back. Which is exactly why bake-high-to-low and normal mapping exist: capture the detail once, carry it on light geometry.
DiagramA quality versus polygon-count curve that rises then flattens at pixel size, past which shading costs up to eight times for no gain

The silhouette is the dividing line

This is the single most useful modelling rule in the course. A normal map fakes surface relief for the way light hits a face, but it does not move a single vertex — so it is invisible at the edge. Anything that changes the SILHOUETTE, the outline you see against the light, must be REAL geometry; anything that only changes how a flat surface catches light can be a normal map. Get this right and your scene is both convincing and light; get it wrong and you either waste geometry on things nobody sees at the edge, or you flatten a profile that should have caught the light.[4]

Carry, lose, and where to spend geometry

At a glance

AspectOne sideThe other
OBJGeometry, UVs, normals, basic materialsSILENTLY drops cameras, lights, animation, hierarchy — and declares NO units
glTF / GLBPBR materials, cameras, lights, metres, +Y upA delivery format — no NURBS, no editing history
FBXRich: cameras, lights, animation, hierarchyProprietary, version-cursed; PBR translation lossy
SketchUp → rendererDON'T export — the renderer reads the model liveEvery export is a chance to lose something
The 1/25.4 errorA units mismatch — inches read as millimetresSet system units before import; never change mid-scene
Silhouette-breaking detailCornice, jaali, carved teak, turned legs → REAL geometryPlaster, weave, grain, grout → normal map
More polygonsBetter only up to pixel densityPast that, up to 8× shading cost for ZERO visible gain
Vocabulary

Key terms

Interoperability

Moving a model between different software. Every format is a translation, and every translation drops something — often silently.

glTF / GLB

The modern PBR-native delivery format. Declares metres and +Y up, carries metallic-roughness materials — so a material transfers intact. Not for editing/CAD.

Normal map

A texture that fakes surface relief for lighting without moving geometry. Invisible at the silhouette — which is exactly where its limit lies.

Silhouette

The outline of an object against its background. The dividing line: break it and you need real geometry; leave it flat and a normal map suffices.

PBR

Physically Based Rendering — materials described by physical parameters (roughness, metallic) so they behave consistently and transfer between engines.

Roughness

The statistical width of a surface's microfacet distribution. 0 is a mirror; 1 is fully diffuse. A distribution, not a bump map.

Tessellation / triangulation

Converting a surface to triangles for rendering. Past pixel density, tinier triangles cost shading work for no visible gain.

System units

The internal unit a program measures in — an inch in SketchUp and default 3ds Max. Set it before import; the 1/25.4 error is a units mismatch.

IFC

ISO 16739-1:2024 — a semantics-carrying data format for multi-discipline coordination. Literacy for an interior designer, not a deliverable.

Bake (high-to-low)

Capturing a high-detail model's surface into maps applied to light geometry — the workflow the polygon-count myth ignores.

Apply it

Study task

Take one room you have modelled and make two lists. First, the hand-off: name every tool the model will pass through from your desk to a finished client image, and for each transfer say which format you would use and one thing it will drop. Second, the geometry budget: list ten surfaces in the room — a cornice, a jaali, a rug, a plaster wall, a turned table leg — and mark each “real geometry” or “normal map” using the silhouette test alone. Then check yourself: is anything you marked “real” actually flat at the edge, and anything “map” actually breaking the outline? Fixing those two mistakes is most of what makes a model both convincing and light.

Check your understanding

Self-assessment

1. What is the real danger when you export a model to another format?

2. A model imports into 3ds Max 25.4 times too large. What happened?

3. You are modelling a carved jaali screen. Real geometry or normal map, and why?

4. Why is 'more polygons is always better' false at the top end?

In a nutshell

Recap

Formats lose data SILENTLY — OBJ drops cameras, lights, animation and units with no warning. Check the RECEIVING end, not the sending one.
Pick the format for the destination: don't export SketchUp→renderer; glTF for web/AR; FBX (units first) to 3ds Max; STL/DXF to fabrication; IFC to coordination.
The 1/25.4 error is a units mismatch — inches read as millimetres. Set system units before import; never change mid-scene.
PBR (roughness + metallic) made materials PORTABLE via glTF metallic-roughness — the real reason it won was transfer, not prettier pictures.
The silhouette rule is the course's most useful: break the outline → real geometry (cornice, jaali, carved teak); flat surface detail → normal map (plaster, weave, grain).
'More polygons is better' inverts past pixel density — up to 8× shading cost for zero gain (Fatahalian, SIGGRAPH 2010) — which is why baking and normal maps exist.
The evidence

References & further reading

  1. [1]Blender Foundation. Blender Manual — Import & Export (OBJ, FBX, glTF 2.0, etc.), on what each format carries and drops. docs.blender.org. https://docs.blender.org/manual/en/latest/files/import_export.html
  2. [2]Khronos Group. glTF 2.0 Specification: 'The units for all linear distances are meters'; 'glTF uses a right-handed coordinate system … +Y is up.' Metallic-roughness PBR material model. https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html
  3. [3]Autodesk & Trimble product documentation on internal/system units (3ds Max default system unit = inch; SketchUp works internally in inches). On the 1/25.4 import-scale error.
  4. [4]Cignoni, P. et al. (1998). A general method for preserving attribute values on simplified meshes (IEEE Visualization 1998) — the ancestor of the bake-high-to-low normal-mapping workflow. https://doi.org/10.1109/VISUAL.1998.745285
  5. [5]Fatahalian, K. et al. (2010). Reducing shading on GPUs using quad-fragment merging. ACM SIGGRAPH 2010: 'when the scene is tessellated into pixel-sized triangles, a GPU will shade each covered pixel more than eight times.' https://doi.org/10.1145/1833349.1778792

Further reading

  • Cline, Lydia Sloan — SketchUp for Interior Design (2nd ed.). Wiley, 2023.
  • Akenine-Möller, T., Haines, E. et al. — Real-Time Rendering (4th ed.). CRC Press. ISBN 9781138627000. Reference shelf for the geometry-and-shading chapters.
  • Poly Haven and ambientCG — genuinely CC0 PBR material and HDRI libraries (no attribution required). The practical texture source.

Sources gathered and fact-checked June 2026. Published values vary by source, sample and method — treat as indicative and confirm against the cited standard before structural use.

A

The author

Amogh N P

Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.

More about Amogh →