# AssetBake troubleshooting

> Fix AssetBake problems in Blender: Quad-dominant not available, fallback to Game, size limits, missing textures, empty bake, GLB export errors and known limits.

- Page: https://mendboxstudio.com/docs/assetbake/troubleshooting
- Updated: 2026-11-20
- Publisher: Mendbox Studio (Dynamic Flower Unipessoal LDA, Portugal)

## Before you start

Most messages appear in the **Result** panel under the settings, or at the bottom of the Blender window. Warnings do not stop the job. They tell you what to check. If something here does not help, write to support@mendboxstudio.com and include the log file path (see [A job failed](#a-job-failed)).

## The panel and the button

### Select one or more mesh objects

Nothing usable is selected. AssetBake works on mesh objects only. Select your model in Object Mode. Helper shapes that Blender uses to draw bones, and assets that AssetBake made, are not used as a source. If you selected only assets, press **Select Source** to select the originals.

### The selected meshes have no faces

The selection holds meshes without faces, for example only vertices or edges. Select a mesh that has faces.

### Go to Object Mode to make an asset

AssetBake works in Object Mode. Press `Tab` to leave Edit Mode. A job that is already running keeps running while you are in Edit Mode, and the asset appears when you return to Object Mode.

### Done - return to Object Mode to get the result

The job has finished and is waiting. Go to Object Mode and the asset is added to the scene.

### Too large: the limit is 8,000,000 triangles

The selection has more than 8,000,000 triangles. AssetBake will not start. Decimate the source first (Modifiers > Decimate), apply the modifier and run AssetBake again.

### Large input: this takes several minutes and several GB of memory

Above 5,000,000 triangles the job is allowed but slow and heavy. Close other programs, or decimate the source first if your computer runs short of memory.

### Texture with unsaved changes

A texture of your model was changed in Blender and not saved or packed. The bake would use the old picture from disk. Save or pack the image and run the job again.

## Quad-dominant

### Quad-dominant is not available on this system yet

The panel shows this, with the name of your system, when there is no Quad-dominant build for it. Quad-dominant works on macOS (Apple Silicon) and Windows (x86-64); Linux is not confirmed yet. Intel Mac is not supported yet. Game mode works everywhere. If a file saved with Quad-dominant is opened on such a system, AssetBake makes a Game asset and says so.

### Quad-dominant needs Python 3.11 or newer inside Blender

Your Blender uses an older Python. Blender 4.2 and newer meet this. Update Blender, or use Game mode.

### Quad-dominant needs at least 5,000 faces

The face budget is too low. Raise the budget to 5,000 or more, or use Game mode. Below 10,000 faces the quad share drops and a fallback to Game is more likely, so 10,000 or more is the safe choice.

### Quad-dominant was not possible here, a Game asset (triangles) was made instead

The result is a normal Game asset. The message ends with the reason. The common reasons are:

- **Most of the surface is thinner than one quad at this budget.** Thin sheets, leaves, cloth and shells cannot be made of quads. Raise the budget, which makes the quads smaller, or accept the Game asset.
- **The model is over 2,000,000 triangles.** Decimate it first (Modifiers > Decimate), apply the modifier and try again.
- **The quad mesh fell into more pieces than the source, has open edges where the source is closed, or does not cover or follow the source well enough.** The quad mesh did not pass AssetBake's checks, so it was not handed out. Try a neighbouring budget, for example 20,000 instead of 10,000. The result can change from one budget to the next.
- **Quad clean-up or seam repair did not settle.** Try another budget.
- **Layers inside the model.** Some AI models have a second skin under the visible one. With **Remove hidden surface** on, AssetBake leaves those inner layers out. With it off, such a file becomes a Game asset.

About one model in eight that is thick enough still falls back for a small local defect. This is a known limit. The Game asset is still a full, textured result.

### The budget is X faces, the asset has Y

The quad mesh did not get closer to your budget. The asset is usable. Try a different budget if the count matters.

### Expect about X-Y % quads, or a fallback to Game: many thin parts

This is the estimate before the run, not an error. Many thin parts will become triangles, and the run may fall back to Game.

## Messages after a job

### The budget is X triangles, the asset has Y

Game mode could not reduce the mesh further. What is left are tangled or separate pieces that fall apart when merged more. The asset is usable. Raise the budget if you want a cleaner result.

### The budget is X triangles, the asset has only Y

The asset has fewer triangles than the budget. Either the visible surface left after hidden surface was removed is small, or the source has no more usable triangles after cleaning. Untick **Remove hidden surface** to get closer to the budget.

### The source already has fewer triangles than the budget

Nothing needed reducing, so the geometry is kept as it is. UVs and textures are still made. Since 0.2.6, Game mode says so before the run: "The source has N triangles, under the budget of M: nothing to reduce, it is kept as it is."

### The low mesh leaves the source shape by X % of the size. Try a higher budget

The new mesh differs noticeably from the source. Raise the triangle budget.

### Parts of the source are tangled

Some faces share an edge with several neighbours or touch at single points. To keep your budget, AssetBake merged points that are close together. Those places can look rougher than the rest. Raise the budget or clean the source in Blender.

### X of the surface is enclosed by other surface and was removed

Hidden surface was removed, so the mesh is open there. Untick **Remove hidden surface** if you want it kept.

### The bake found no source surface: the textures are empty

Nothing was found to bake from. Check that the source has visible faces and that you did not select the wrong objects.

### Parts of the texture look smeared or filled in

A small part of the texture could not be baked and was filled from its neighbours. The back-of-surface message appears on one-sided sheets and where parts almost touch. A few percent are normal. If the texture looks wrong, try a higher budget or a bigger texture size.

### Tiny triangles have no texture

A few tiny triangles have no space on the texture. This is reported as a count and does not change the look.

## Materials and textures

### Texture file not found

The source refers to an image that Blender cannot find on disk. Restore the file or pack it into the .blend file, then run the job again.

### Material(s) have no Principled BSDF or Emission shader and were baked as plain grey

AssetBake reads the Principled BSDF or Emission shader on the surface. A shader inside a node group is not read. Move the shader out of the group, or replace the material with a plain Principled BSDF.

### Faces without a readable material were baked from the vertex colours

Information only. Models from some AI services carry their colour in vertex colours, and AssetBake used it.

### Unlit material(s): the emitted colour was baked as the base colour

Information only. The material emits its colour without lighting, and that colour became the base colour.

### Transparency is baked as a cut-out

Alpha is stored as a cut-out. Half-transparent surface such as glass becomes solid or a hole. There is no partial transparency in the result.

### The source has transparent parts, so surface behind them was kept

Information only. Surface behind transparent parts is not treated as hidden.

## Rigs, shape keys and modifiers

- **The source is rigged.** The asset is built from the rest shape. The armature, the weights and the animation are not carried over. AssetBake gives you a static asset.
- **The source has shape keys.** The basis shape is used and the shape keys are dropped.
- **Modifiers of the source were applied for the asset.** The source itself is not changed.
- Linked objects from a library are not handled as a source.

## Scope messages

- **The selection has too many separate parts for one asset each: one asset was built for the whole selection.** With **One asset per part**, AssetBake built a single asset because there were too many parts.
- **The selection falls into more than 2,000 loose pieces: one asset was built for the whole selection.** Same result for the same reason.
- **Small loose pieces were kept with the nearest large part.** Information only.

## Select Source

- **Select an asset made with Make Game Asset first.** Select an asset that AssetBake made.
- **This asset does not remember its source (it was made with an older version).** Unhide the original objects in the Outliner.
- **The source is not in this scene any more.** The original was deleted, or renamed after the file was reopened. Bring it back or select the model again by hand.
- **The source is in a collection that is hidden or switched off.** Show the collection, then try again.
- **Selected X of Y source objects; ...** Some sources could not be selected. The text after the semicolon says why.

## Export GLB

### Select an asset made with Make Game Asset

Nothing exportable is selected. Select an asset that AssetBake made, or run a job first. With nothing selected, the assets of the last run are exported.

### Blender's glTF 2.0 add-on is switched off

Open **Edit > Preferences > Add-ons**, find the glTF 2.0 add-on (Import-Export: glTF 2.0 format) and switch it on.

### Export failed

The file could not be written. Check that the folder exists, that you may write to it and that the disk has room. The message includes Blender's own reason.

### The asset was edited after it was made

The triangles of the asset no longer match the ones the textures were baked on, so the normal map can show small errors where faces changed. For an exact result, make the asset again from the source.

## A job failed

If a job fails, the Result panel shows "The job failed" with a short reason and a **Copy log path** button. The button copies the location of a log file. Attach that file to an email to support@mendboxstudio.com and include your Blender version, your system and the size of the model. Reply time is within 24 hours.

If the message is "Could not start the background job", Blender could not create its working files or start the second Blender that does the work. Check free disk space and that Blender is allowed to write to its temporary folder.

If you press **Cancel**, the panel says "Cancelled. Nothing was changed." The job stops and the scene stays as it was. If you open another .blend file while a job runs, the job is cancelled.

## Known limits

- Hard edges that a glTF file stores only as custom normals are lost. Edges sharper than 30 degrees survive only on sources with flat faces or marked sharp edges.
- Tiny parts can get no UV area.
- Alpha is a cut-out only.
- Export is GLB only. There is no FBX export and there are no engine presets.
- The result has no rig and no animation.
- Quad-dominant does not rebuild clean edge flow. It is not retopology. The seam triangles between quads and thin parts are closed but can be stretched.
- Intel Mac: not supported yet. AssetBake Lite is not tested on Windows.

## Related

- Product page: [AssetBake](https://mendboxstudio.com/addons/assetbake)
- [Install](https://mendboxstudio.com/docs/assetbake/install)
- [Panel reference](https://mendboxstudio.com/docs/assetbake/panel)

---
Source: https://mendboxstudio.com/docs/assetbake/troubleshooting
