AEC 3D Viewers: What 32 Tools Chose, and a 5x Speed Gap
Over the past year I built five different 3D viewers for AEC work - routing, structural review, tunnel sections, a Revit perspective tool, a spreadsheet-to-3D viewer. Before I trusted my own instincts about how to build them, I did two things: I profiled all five on the same GPU, and I studied how 32 other AEC 3D tools - Autodesk Forma, Speckle, TestFit, xeokit, Bentley iTwin, and more - solve the same problem. This post is both halves: what the industry chose, and then what my own measurements showed. The short version is that rendering is a commodity, and the interesting decisions are everywhere else. Part 1 - What 32 AEC viewers actually chose I expected a mess of proprietary engines. Instead the choices collapse into six patterns, and the deciding question is never "which renderer is best" - it is "what is our actual moat." Pattern Who Why Outcome A. Off-the-shelf web engine (three.js / Babylon) Forma, Speckle, That Open, VIM, Snaptrude "Rendering is a ...