Problems you can click
Each finding names the part, how many faces or edges it touches and why it matters. Click it and the camera flies to the spot, the faces light up, the UV editor frames the island.
- Health score per category and overall, with a grade
- Errors, warnings and notes, each with the exact elements
- Export the report to HTML to send with the asset
See the UVs the way the baker will
Checker, texel density heat-map, overlaps and padding drawn over the real texture. Open any texture full screen with a list of every map beside it.
- Padding measured at the size the texture will be
- Several UV sets, islands, overlaps, flipped shells
- Feedback cards pinned to a spot on a texture
Present the asset, not a screenshot
Pick the views - material, texel density, clay with wireframe, LOD rows - turn them all at once and render a sheet with the mesh stats and the project's name.
- Ray-traced occlusion, shadows and bounce light
- Default, black, white or your own background
- Turntables and your watermark
Every client's rules, checked every time
Make a project per client and the scan knows what "done" means there: which maps, how they are named, the normal map format, the texel density target, the limits.
- Texture sets and their naming, per slot
- Polycount, texture size and format limits
- LOD expectations and collision naming
The whole LOD chain, side by side
Load LODs from one FBX, several files or a Maya scene. Every level shows its triangle count and its drop from the one before; the project sets the targets. Collision meshes are recognised by the naming of your engine.
- Up to 7 custom slots, several files per slot
- Show all: objects in columns, LODs in rows
- Collision naming for Unreal, Unity, Godot or your own
