Historical · current compatibility unverified Original context: PME 1.18.7 with Blender 4.1, 2024.

Outcome

Build a Macro from a known native Blender action instead of guessing operator syntax.

Recipe

  1. Perform the target operation manually in the intended editor and mode.

  2. Open Blender’s Info editor or report output and copy the emitted bpy.ops... call.

  3. Test that call alone in a PME Command item, in the same context.

  4. Create a Macro with separate phases:

    1. setup (mode, selection, active object);
    2. the captured operator;
    3. optional cleanup or state restoration.
  5. Re-test from the actual hotkey, including Object mode when the workflow begins there.

If the action requires an on-screen interactive adjustment, keep that interaction as an explicit stop in the workflow rather than assuming every later Macro step will wait for it.

Pitfalls

  • A captured call describes the state in which Blender recorded it. It does not create that state when replayed.
  • Do not copy a nested operator-property dictionary blindly. Test the action by itself before combining it with selection or mode changes.
  • If a Macro works only after splitting mode switching into another Macro, record that boundary as a context dependency rather than hiding it with unrelated commands.

Re-capture and test each operator call before using this PME 1.18.7 / Blender 4.1 example in a newer setup.

Sources