ForgeFX Simulations
3D Asset Inspection / Ed Rojas / WD6 Manifold

Imports Cleanly.
Geometry Needs Review.

The FBX opens successfully and contains a lightweight static mesh. It is usable for inspection, but I would not call it bake-ready or engine-ready until the open boundaries, disconnected shells, degenerate faces, UV intent, and transforms are confirmed.

5,388Triangles
35Connected shells
356Open boundary edges
4UV sets

Visual Proof

These are real renders from the uploaded FBX. The object is small and elongated, so the close crops keep the suspected detached fragment and strand endpoints visible.

Neutral Eevee close render of WD6 Manifold
Neutral surface renderMaterial and silhouette check
Wireframe close render of WD6 Manifold
Wireframe renderTopology and disconnected-piece check

What Matters

Verified measurements are separated from interpretation. Some boundaries and shells may be intentional because this appears to be a manifold/tube assembly.

Review before delivery

Open + Disconnected Geometry

The mesh contains 356 boundary/non-manifold edges across 35 connected shells. No loose edges or loose vertices were found. Open tube ends and separate fittings may be intentional, but the small detached-looking piece should be confirmed.

Cleanup

Degenerate + Coincident Geometry

There are 6 zero-area/degenerate faces and 6 extra vertices at coincident positions. Those are the strongest cleanup candidates before normal generation, AO baking, collision, or engine import.

Transform

Scale + Rotation Are Unapplied

The mesh imports with 0.01 scale and approximately 90° X rotation. That can be valid FBX conversion metadata, but applying transforms on a working copy will make downstream baking and engine behavior more predictable.

Healthy signals

Lightweight Static Asset

One static mesh, 2,892 vertices, 5,388 triangles, one material, no armature, no animation, and no loose geometry. The file imports without a fatal FBX error.

UV + Material Read

UV bounds show placement, not overlap quality. An overlap/padding pass is still required before selecting a bake channel.

UV setObserved boundsOutside 0–1Practical read
UVChannel_10–1 in U and VClean boundsBest initial candidate for AO/lightmap baking; still verify overlap and padding.
uvSet1U reaches 1.02570 loopsSlight tile overflow. Confirm whether intentional before clamping or repacking.
UVSet0U −1.216–11.872 / V 0–8.3417,159 loopsHeavily tiled layout; likely material UVs, not a unique bake atlas.
map1U 0–0.162 / V 0–1Inside tileUses a narrow strip of the tile. Valid, but unusually inefficient if intended as a unique atlas.
Material check: one material is present, but the FBX contains no embedded image textures. That is not an import failure; it means faithful texture review requires the external texture files if they exist.

Recommended Next Pass

No source asset was modified during this inspection.

Confirm construction intentDecide whether the 35 shells, open tube ends, and detached-looking small piece are authored parts or cleanup defects.
Clean verified defectsRemove the 6 degenerate faces and weld coincident vertices only where doing so preserves intended seams and separate parts.
Apply transforms on a copyNormalize scale and rotation, then compare world dimensions and silhouette against the original before export.
Select the bake UVStart with UVChannel_1, then run overlap, padding, and checker-density validation before AO or normal baking.