Troubleshooting

Installation and activation

PivotBreeze does not appear or does not enable

• Install the original versioned extension ZIP through Install from Disk.
• Do not install GitHub’s automatically generated source archive.
• Confirm Blender is version 4.2 or newer.
• Open Blender’s Console and keep the complete traceback from the first failed activation attempt.

An update still behaves like the previous build

Finish the active session, install the complete newer package, and confirm the version shown in Blender’s extension information. The September 15 replacement still displays 1.0.0: reinstall the new ZIP and restart Blender even when that version is already installed. Do not merge individual files from two versions. For scripts, query capabilities_get() and inspect api_version; the package filename alone does not prove API compatibility.

Pie Menu and shortcuts

Ctrl + D opens another action

Review the configured Pie Menu shortcut and its conflict details in Preferences. PivotBreeze reports matching bindings but never disables or deletes another keymap item.

A direct action does nothing

The displayed number keys are disabled storage placeholders. Choose the native mapping type and capture the desired event, enable the action, and place the pointer over a supported 3D View or UV Editor before invoking it.

An old snap activation or API example fails

The current Python API is 4. Use Bounding Box Pivot or Pivot by 3 Points in supported 3D mesh contexts. Old snap activation operators are removed; session calls use placement_mode with NONE, BOUNDS, or THREE_POINTS. Reassign empty legacy Pie Menu slots. UV supports regular activation only.

3D and UV sessions

The UV workflow is unavailable

Use Mesh Edit Mode, open the UV Editor, confirm the edited Mesh has an active UV map, and call the action from that editor. UV pivot sessions move Blender’s 2D Cursor and do not expose rotation.

Bounds or three-point placement is unavailable

These tools require a Mesh in Object, Edit Mesh, or Sculpt Mode; Edit Mesh also needs selected components. Neither is available in UV or Curve/Surface Edit Mode. The Pie Menu preserves unavailable slots as disabled entries.

The session closed after a context change

Changing the active object, selection, mode, or tool can finish a session. A changed target is applied unless the 3D helper was hidden or deleted. Esc cancels, restoring the cursor captured at session entry. Enter / Numpad Enter applies; during a native transform the first key press handles that transform.

Outside snap settings return after exit

This is expected. PivotBreeze restores the outside configuration while keeping the configuration used inside the session as shared Object/Edit/Sculpt memory and native UV-specific settings when that preference is enabled.

Geometry picking and controls

Hover or click placement does nothing

Check Pivot Placement Vertex Limit (enabled by default, 100,000 vertices). Zero or an unchecked box disables geometry picking. If the original selection exceeds the limit, picking is disabled; if only the complete visible scene exceeds it, picking stays selected-only. Bounds always use selected mesh objects. Manual gizmo transforms and UV editing remain available.

Aim does not use my old shortcut

Aim now uses fixed Shift + Left Click, without Ctrl, Alt, or the OS modifier. It is unavailable in UV and Bounding Box Pivot. Retired Aim settings do not change this binding.

The bounding box uses the wrong axes

Press R to switch Global/Local. Every new bounds session starts in Global. In Object/Sculpt, Local follows each object; Edit Mesh follows the active object.

Three-point placement does not accept a point

Coincident or collinear points cannot define a frame. Pick a different point; Backspace removes the last accepted point and R cycles the controlled axis. The third valid point applies and closes the session.

Reset and zero actions

UV Reset moves the cursor to (0, 0)

No visible UV coordinate was selected for the reset target. Reset Position uses the visible selected UV bounds center and falls back to the UV origin.

Move to Zero does not center a selected Edit or UV selection

A selected operation subtracts the current cursor position and preserves every selected point’s offset from that cursor. With no selection, complete Edit geometry or each fully visible UV island uses its own bounds center instead.

Some UV islands do not move

Reveal the complete island. A partially hidden island is skipped as a whole to avoid moving only its visible corners. Independently centered islands can overlap at the UV origin; Move to Zero is not a packing command.

A zero command is rejected

Read the reported restriction before changing the file. Depending on the path, PivotBreeze can reject linked or shared data, location locks, active constraints, animation, singular transforms, linked or animated descendants, and Sculpt Mode Dyntopo. See the Technical Reference for the exact validation rules.

Report a problem

If you run into a bug, a crash, or unexpected behavior, feel free to email me at hadzalo.dev@gmail.com. Suggestions and ideas for improvements are welcome too.

Keep your bug report short and clear. Include what you can:

• A brief description of the problem: what you tried to do, what you expected, and what happened instead.
• A few steps to reproduce it, including the Blender editor and mode you used.
• Screenshots showing the problem or error message.
• A crash log or a text file containing the complete error output, if available.
• Your PivotBreeze version, Blender version, and operating system.

You do not need every attachment to get in touch. A short description is enough to start; screenshots and logs help me understand the issue faster. If the problem happens only in one scene, mention that in your email and follow the file-sharing guidance below before sending a Blender file.

Before sharing a Blender file

Reproduce the issue in the smallest file that still fails. Preserve the relevant objects, UV maps, selection, hierarchy, constraints, modifiers, animation, and PivotBreeze preferences, but remove unrelated production content.

Delete materials, textures, render output, credentials, personal paths, client assets, and private scene data that are not required for reproduction. When the problem involves Undo/Redo, list every intervening action in order. When it involves UV, include UV Select Sync, selection mode, edited Mesh count, active UV maps, starting 2D Cursor, and the current snapping settings and placement mode.

Keep any state required to reproduce the problem, such as transforms, hierarchy, locks, constraints, animation, modifiers, shared data, editor mode, selection, cursor position, snapping, or Dyntopo. Share a .blend file only through a support channel you trust, and do not include third-party assets you cannot redistribute.