To compare two versions of an asset, you need to see them from the same angle, at the same moment, then compare their numbers: silhouette, triangles, UVs, materials and scale. Opening the files one after another forces you to remember what you have just seen. Placing them side by side, with cameras that move together, makes the differences stand out on their own.
The need comes up constantly in a game project. An artist re-exports a character and you want to know what has changed. A sculpted model has just been retopologised. A LOD chain arrives from a freelancer, or you are torn between Rock_v02 and Rock_v03. The good news: the check takes a few minutes when you know what to look for.
Three situations come up most often.
It is also the right reflex for choosing between two duplicates when you tidy up, as our guide to organising your 3D game asset library suggests.
Level of detail (LOD) means replacing a mesh with a simpler version when it takes up less space on screen. The three major engines each approach it in their own way:
| Engine | Documented principle |
|---|---|
| Unity | LOD 0 is the level closest to the camera, and therefore the most detailed. A LOD Group component accepts up to eight levels, and switching depends on the object's height on screen relative to the total screen height. A cross-fade between levels is possible. |
| Unreal Engine | LOD0 is the mesh's base LOD. Switching is calculated not from distance but from screen size. Each level can be imported from an FBX, and given its own material. |
| Godot | For imported scenes (glTF, .blend, Collada, FBX), Godot generates LODs automatically on import. For hand-made LODs, the documentation recommends visibility ranges instead. |
As for naming, Unity offers a simple convention: add the suffix _LODX to the name of each mesh, X being the level index, for example Barrel_LOD0 for the most detailed. Exported to FBX and then imported, the model automatically receives a configured LOD Group.
Comparing a LOD chain therefore means checking that each level stays faithful to level 0 while genuinely lightening the mesh.
| Point | What you are looking for | Where to see it |
|---|---|---|
| Silhouette | The outline remains recognisable, with no spikes or holes | Side by side, untextured or MatCap |
| Triangles | Each level genuinely lightens the previous one | List view, Triangles column |
| UVs | The number of UV sets is consistent between versions | List view, UV column |
| Materials | The same textures in the same places | Side by side, textured mode |
| Scale and origin | Same dimensions, same origin point | List view, dimensions and origin offset |
Two useful clarifications. On UVs, Unity uses the second channel (UV1) for lightmap UVs: if one version has two sets and the other only one, that is a difference to check before replacing the file. On scale, units differ from one format to another: the glTF specification sets all distances in metres, while Unity offers a unit conversion option and a scale factor when importing an FBX. A version twice the size of the other is therefore spotted first in the dimensions.
The side-by-side comparison in Eyemesh places two models in a split view, each in a full viewer you can rotate and zoom in real time. There are two ways to start it:
The two files can be in different formats: an FBX next to its GLB, an OBJ next to a USDZ.
The link-shaped button turns on linked cameras: rotate one model, and the other follows the same orbit and the same angle. Zoom is synchronised in relative terms, with each model staying framed according to its own size. This way you compare two shapes from the same viewpoint, even if their scales differ. The Blender-style view keys help too: 1 for the front, 3 for the right side, 7 for the top, with Control for the opposite view. The linked camera follows. To inspect a detail on one side only, unlink the cameras, then link them again.
Each viewer keeps its own lighting and background, and plays its animations on its own timeline. Handy for checking that a re-export has not damaged a clip: the details are in checking animations and the skeleton.
The comparison shows the shapes, the list view gives the numbers. Open the folder that contains your versions or LODs, switch to list view, then right-click the header to choose the columns: meshes, vertices, triangles, UVs, width, height, depth, centre and origin offset. Clicking a header sorts that column.
With files named _LOD0, _LOD1, _LOD2, sorting by triangles puts the chain in the expected order. A level that does not go down, or goes back up, stands out immediately. The dimension columns then show whether all the levels share the same size, and the origin offset whether the pivot point has stayed in the same place: since LOD levels replace one another at the same position, a moved pivot would show at the moment of switching.
Are your LODs spread across several subfolders? The flat view brings all the files in the folder tree together in a single list, and the type filter isolates one format. The info panel of a model opened on its own also shows the geometry, the dimensions and the skeleton.
Render modes apply to both sides of the comparison at once. The V key cycles through them: textured, untextured, wireframe, MatCap.
V: untextured for the silhouette, wireframe for the mesh, textured for the materials.1, 3 and 7 to cover the front, side and top.The same routine works before a delivery: see checking a folder of 3D files before delivering it to a client.
Yes. Eyemesh loads each side with the reader suited to its format: an FBX can be placed next to its conversion to GLB or USDZ. It is the most direct way to check a conversion.
Linked cameras synchronise the angle and a relative zoom: each model stays framed according to its own size, so that both shapes remain readable. To compare scale, rely on the dimension columns in list view.
It depends on the engine and the target. Unity accepts up to eight levels in a LOD Group, Unreal counts its LODs from LOD0, and Godot can generate them itself on import. Above all, compare each level with LOD 0 from the angle at which the player will see it.
Place the original and the retopologised version side by side, with linked cameras, in untextured mode or with the Clay MatCap. Then switch to wireframe to see how the polygons are distributed, and check the drop in the triangle count in list view.
Yes. Each viewer keeps its own lighting preset and background. For a fair comparison, set them the same way.
Open your asset folder in Eyemesh, select two versions and compare them side by side, with linked cameras. 7-day free trial.