Skip to content

Troubleshooting

No previews are rendered

  • Save the .blend file first. Rendered previews require a saved file for output.
  • Check the environment image. If HDRI lighting is enabled, verify the selected environment image still exists in the configured World Images folder.
  • Open a 3D Viewport. Preview rendering requires at least one 3D Viewport to be open so Blender can frame and render the target.
  • Verify assets are marked. Custom rendered previews require the target objects or collections to already be marked as assets. Mark them first using the Object Assets section.
  • Check the report panel. Expand Issues for specific error messages.

Materials are skipped

  • Missing base color. Every texture set needs at least a base color map. Check that your base color files match the expected naming keywords.
  • Requirements inference. The scanner infers required maps from what it detects across all sets. If most sets include normal maps, any set missing a normal map will be skipped. Use Dry Run to see which maps are required and which sets are being skipped.
  • Combine Root + Overrides. When enabled, this merges requirements from both sources — which can make more map types required than intended. Try disabling it if too many sets are being skipped.
  • Check the report. The report panel shows the exact skip reason for each material.

Textures not detected

  • Check naming conventions. The scanner matches by keywords in the filename. Open Texture Naming Keywords to see the current keywords and add yours if needed.
  • Check folder structure. Make sure your textures are inside the Texture Root folder or its subfolders.
  • Folder tail keywords. If your textures are inside a subfolder like maps/ or textures/, make sure that folder name is listed in Folder Tails.
  • File format. Verify your texture files are in a format Blender supports (PNG, JPEG, TIFF, EXR, etc.).

The add-on does not appear in the Asset Browser

  • Enable the add-on. Open Edit > Preferences, then use Get Extensions or Add-ons to confirm Asset Forge is installed and enabled.
  • Show the sidebar. In the Asset Browser, press N to toggle the sidebar if it's hidden.
  • Correct area type. Asset Forge only appears in the Asset Browser editor, not in the 3D Viewport or other editors.

Asset Browser selections clear after preview renders

This is a known limitation. Blender may reset the Asset Browser selection after a preview render completes. Your assets and previews are not affected — only the visual selection state in the browser.

Object assets have no catalog

  • Save the file first. Catalog writing requires a saved .blend file.
  • Check the scope. Make sure the objects you want to mark are included in the selected scope (Selected Objects, Selected Collection, or All).

UDIM tiles not grouped

  • Enable UDIM detection. Make sure Detect UDIM Tiles is enabled in Build Options.
  • Check numbering. UDIM tiles must use the standard 1001, 1002, 1003 numbering pattern in the filename.
  • Check separators. The tile number should be separated from the base name by a dot, underscore, or hyphen (e.g., wall_basecolor.1001.png or wall_basecolor_1001.png).

Dry run shows unexpected results

  • Check overwrite policy. The policy affects what the dry run reports as "would be overwritten" vs "would be skipped."
  • Check Combine Root + Overrides. This setting changes which maps are required, which affects what gets skipped.
  • Review keywords. If textures aren't being detected, the naming keywords may not match your files.

Tip

When reporting a bug, include the full report panel output — expand both Selected Report and Issues and screenshot or copy the text. This helps diagnose the problem much faster.