meshfx // PRECOMPUTED MAPS
How to bake (precompute) high-poly detail onto a low-poly model
You bake (precompute) high-poly detail by placing the detailed model and the light game mesh in the same spot, then casting rays from the low mesh to the high one to record its surface into a normal map, plus color and ambient occlusion if you need them. The low mesh needs clean, non-overlapping UVs before you bake (precompute).
pyrofx effects work today, and new accounts start with $5 of usage.
meshfx measures faults, checks repairs and makes LODs for a triangle budget. meshfx runs on the hosted API: try it in the Playground.
- Low mesh: clean UVs, triangulated
- A cage controls where rays reach
- Unreal flips the normal map's green channel
01 // BY HAND
Bake (precompute) a normal map in any 3D editor
- Make the low mesh follow the high one's outline, unwrap it with no overlapping islands, and triangulate it.
- Put both meshes in the same place with their transforms applied.
- Set hard edges on the low mesh only where there is a UV seam, and keep the rest smooth.
- Set the bake (precompute) distance or cage (a slightly inflated copy of the low mesh that encloses the high one) so the rays reach every part of the high mesh.
- Bake (precompute) the normal map in tangent space, then ambient occlusion and color at the same resolution.
- Look for black spots and wavy lines, push the cage out where rays missed, and bake (precompute) again.
- In your engine, mark the texture as a normal map in its import settings so it decodes correctly.
02 // NORMAL MAP FORMAT
Match the engine's normal map convention
Normal maps come in two conventions that differ only in the green channel. Godot, Unity and glTF use the OpenGL style (Y+), and Unreal Engine uses the DirectX style (Y-). If bumps look like dents in one engine, invert the green channel, or in Unreal tick Flip Green Channel on the texture.
Bake (precompute) in MikkTSpace, the tangent space glTF and most engines use, so the map matches the engine's shading.
03 // COMMON ERRORS
Fix the usual bake (precompute) errors
- Black or garbage patches mean the rays missed, so increase the cage or bake (precompute) distance in that area.
- Wavy lines across a cylinder mean the low mesh has too few sides there, so add a few edges.
- Visible seams in the normal map come from hard edges that do not sit on UV seams, so split the UVs there or soften the edge.
- Detail from one part appearing on another, such as a finger printed onto the next finger, goes away if you bake (precompute) with the parts moved apart and then move them back.
04 // meshfx
meshfx for bake (precompute) high to low poly
meshfx retains existing UVs during triangle reduction. Create the texture atlas in your editor. Hosted meshfx runs are available in the Playground.
How do I fix shading artifacts on a game model?
Reset or recalculate vertex normals, mark sharp hard edges and transfer a normal map using the same tangent basis your engine expects.
How do I compile detailed sculpts onto a light game mesh?
Line both meshes up, give the light one clean UVs, set a cage that encloses the detailed one and compile a tangent space normal map.
How do I create a light game model from a detailed sculpt?
Retopologize or decimate a copy of the sculpt to your budget, unwrap it and compile the sculpt detail onto it so normal maps carry the surface.
Do I need to compile textures again after retopology?
Yes. The new mesh has new UVs, so every map painted or compiled for the old layout has to be compiled again from the original.
Explore meshfx outputs
Inspect compiled meshfx outputs and their reports. Hosted meshfx runs are available in the Playground.