Troubleshooting

Nothing happens when I click “Run Set”

  • Check that a macro set is selected in the Macro Set dropdown.

  • Verify that the Category and Subcategory are correct.

  • Look at the system console (Windows: use Toggle Console; Linux/macOS: launch Blender from a terminal) for any error messages.

  • Expand the Requirements panel – it may list missing dependencies.

“Missing Append Assets” dialog appears

The macro set contains one or more Append Asset entries whose source .blend file cannot be found, or whose datablocks are missing from that file.

  • Click Choose Replacement File for each missing .blend and select the correct file.

  • After re‑pathing, run the set again.

Entry fails to execute (error in console)

  • If it is a property entry, try toggling the path type (absolute ↔ relative) – the target object may have a different name in the current scene.

  • If it is an operator entry, the required context (e.g. Edit Mode, active object) may not match. Ensure the scene is in the same state as when the macro was recorded.

  • Enable Debug in the Options panel and watch the console for detailed step‑by‑step logs.

Recorded property does not randomise

  • Make sure you have set Min and Max values for the property entry (using the Recorder panel).

  • In the Player panel, set the Recall Type to Random before running the set.

“No presets folder configured” message

  • Go to the Options panel.

  • Click Install Presets to create a default folder and copy example sets, or click Change Folder to point to an existing folder of your choice.

Legacy import fails / no sets imported

  • Ensure the .blend file contains text blocks whose names start with mac_. These are created by SMS Macros V1.

  • The import process does not modify the original .blend; it only reads the text blocks. If no sets appear, open the .blend in Blender and check the Text Editor for any mac_* blocks.

I see “Could not determine valid relative path” when toggling paths

Some properties (especially those deep inside modifier panels or node groups) cannot be represented as a simple bpy.context.* path because there is no direct context member pointing to them. In this case the toggle will fail. Use the absolute path instead.

Performance issues

  • Disable Debug in the Options panel when not needed.

  • If you have many macro sets, organising them into categories/subcategories may speed up dropdown population.