I’ve been thinking more about how this could fit cleanly into Nomad’s existing logic, and I see two possible directions that would both stay consistent with the current design:
1. Extend the Target palette (Cible) with per‑object behavior
Right now Target controls what level the tool acts on (Vertex / Object / Group / Instance), but not how it behaves on a multi‑selection.
A simple extension could be:
- Keep the current behavior as Group (global): one shared pivot for the whole selection, actions like “Bottom”, “Move origin”, transforms etc. behave as they do now.
- Add an Object (per‑object) behavior: when enabled, actions that logically can be applied per mesh (Pivot bottom, Move origin, maybe Align, etc.) would be executed once for each object in the selection, instead of treating the whole selection as a single block.
That would make it very powerful for workflows like mine (many separate meshes for architecture / assets), without breaking existing habits: if users don’t touch this option, Nomad works exactly as today.
2. Add a dedicated option to the Selection tool
Alternatively (or additionally), this could live as an advanced toggle in the Selection tool, something like:
- “Apply actions per object on multi‑selection” (checkbox), or
- A “Per‑object” sub‑mode for multi‑selection.
When this is enabled, commands such as “Set pivot to bottom” or “Move origin to world center” would loop over each selected object and apply the operation individually, instead of using a single common pivot.
From a user point of view, both approaches would solve the same pain point:
- Quickly set correct pivots (e.g. bottom) for a batch of meshes.
- Quickly recenter a whole set of meshes via Move origin, but each to its own center, not as one big cluster.
And because this behavior would be explicitly opt‑in (Target mode or Selection option), it wouldn’t surprise existing users.
TL;DR: It would be great to have an optional “per‑object” mode for multi‑selection so actions like “Pivot bottom” and “Move origin” run on each mesh individually instead of using one shared pivot for the whole selection.