Troubleshooting

Things that commonly surprise new users, and what to do about them.

Loading files

Symptom	What to do
Play does nothing in the Load Mesh / Load Animation preview; the clip box says Bind Pose.	Click the animation's row in the File Info table first, then press Play.
The preview is grey.	Turn on texturing in the preview toolbar (first button).
A frame number typed into the preview's Frame box is not applied.	Press Tab after typing.
Load Animation reports joints that do not match.	Try the other Match by option (Normalized names / Hierarchy), and compare the preview on both meshes before loading.

Viewing

Symptom	What to do
The shading box says Textured but the mesh is grey.	Turn on Texturing in that viewport's toolbar.
The mouse wheel zooms too far at once.	Use one notch at a time near the mesh, or lower Zoom sensitivity in Settings > Navigation.
The model is off-centre.	Right-drag to pan, or use Fit to window.
I docked the Atlas Editor beside the LOD Editor and want the single row of tabs back.	Restarting LODinize restores the default layout.
Appearance or graphics settings have no effect.	They apply after restarting LODinize.

Timeline and refinement

Symptom	What to do
A newly loaded animation does not appear in the timeline.	Tick it in the Clips list (new clips arrive unticked), or pick it in the Clip dropdown.
After adding an animation, refining did not improve its poses as expected.	Run Generate LODs again with the clip ticked, then refine. Refinement picks frames from what the last Generate measured.
The maximum error in the header changes when I zoom the timeline.	The header shows the maximum of the visible part. Zoom out fully (fit) to read the overall maximum.
The curve always reaches the top, even after an improvement.	The vertical axis rescales to the highest value. Compare the numbers in the header.
Pressing Refine again gives the same result.	That is expected: with the same settings the result is the same. Change the frame source, K, the budget or the marked ranges to explore.
The error jumped up after Generate LODs.	Generating replaces a refined LOD set with a plain one. Refine again.
The first frame of a clip shows zero error.	Many clips start in the bind pose, which the LODs are built from.
A level shows ~ before its triangle count and - as its error.	It is not generated yet, or its target changed. Turn on Auto-generate or click Generate LODs.
A level is marked LOD n *.	It was changed after Refine with animation, so it was rebuilt without refinement. Refine again if that level matters.
The preset's name ends with *.	The LOD levels or options no longer match the saved preset. Use Save preset to update it, or Save as new preset.

Selection and masks

Symptom	What to do
My selection disappeared.	A click on empty atlas space clears it, and orbiting the camera may too. Frame the view first, then select.
Magenta, orange or teal highlights stay on the mesh.	Those are hover highlights; move the pointer off the mesh and the atlas. Colours: Highlight colours.
Removing a hidden part also removed something visible.	Both belong to the same island. Erase the visible part from the mask in the Paint tab and generate again — see the guide.
Masks have no effect.	Check Apply mask layers in the Decimate tab and that the layer is switched on.

Atlas Editor

Symptom	What to do
After generating LODs, the atlas still shows the old triangles.	Move the pointer over the atlas view; it refreshes.
The Info panel says to run Solve LOD(n) texturing again.	The repair belongs to a specific LOD geometry; it is reset when LODs are generated or refined.
I see the original's UVs, not the LOD's.	Choose a LOD in the Atlas Editor's own LOD box — it is independent of the LOD Editor.

Export

Symptom	What to do
The exported character has no texture in the engine.	Open the exported file and check whether the texture is present. If it is not, try exporting with Copy beside the .fbx and ship the texture next to the FBX.
The character is rotated or scaled wrongly in the engine.	Match Axis (Y-up / Z-up) and Units (cm / m) to your engine in the Export LODs dialog.
Export says that LOD levels were changed but are not generated yet.	Click Generate LODs (or turn on Auto-generate), so the export matches the LOD Levels table.

Benchmark

Symptom	What to do
The frame rate is lower than expected.	Make sure no other 3D view is visible (for example a docked Atlas Editor) and turn on Unlimited FPS.
I cannot see all settings in the Instanced Crowd panel.	It fills the height of the view; drag its scrollbar — the mouse wheel moves the camera instead.
How many instances can the crowd have?	Up to 2 025 (a 45 × 45 grid): drag the Count slider to its end.

Getting help

For support and updates visit www.lodinize.com. When reporting a problem, Help > About shows your version.