Skip to content

Changelog

  • Direct 3D pivot editing in Object, Mesh, Curve, Surface, and Sculpt workflows.
  • Native UV Editor workflow for positioning Blender’s 2D Cursor.
  • Geometry picking, Bounding Box Pivot with Global/Local orientation, and Pivot by 3 Points.
  • Full, position-only, and rotation-only reset actions where supported.
  • Move to Zero and Pivot to Zero actions for 3D and UV contexts.
  • Configurable eight-direction Pie Menu and optional direct shortcuts.
  • Shared 3D snap memory and native UV settings, per-context exit/reset preferences, and custom handle/hover color.
  • Public Window Manager API for actions, runtime state, sessions, transforms, preferences, hotkeys, Pie Menu slots, configuration, and capability discovery.
  • Enter and Numpad Enter apply; Esc cancels and restores the original cursor.
  • Bounds and three-point placement replace the old snap activation presets; session APIs use placement_mode.
  • Geometry placement uses an enabled-by-default 100,000-vertex budget; Aim uses fixed Shift + Left Click.
  • Native shortcut fields capture keyboard, mouse, and other supported events. API 4 includes event values, the OS modifier, and the context-independent Pie Menu command.
  • The add-on interface is English-only in every Blender language.
  • Former shortcut and Pie Menu positions can now host Move to Zero and Pivot to Zero. Saved removed identifiers resolve to empty slots and are not converted into geometry operations automatically.
  • Documentation is published in English while the inactive locale registry retains placeholders for future complete translations.

The package version and Python API version are separate. Integrations must query bpy.ops.wm.ih_pivot_breeze_capabilities_get() and read api_version instead of inferring compatibility from the ZIP filename.

Before updating a development build, finish the active PivotBreeze session and save the Blender file. This replacement keeps version 1.0.0: reinstall the new ZIP manually and restart Blender; the version number alone cannot identify the replacement. After updating, review Pie Menu assignments and direct shortcuts, then verify Undo/Redo in the workflows used by the project.