Always have an active object in a selection
Right now it’s possible to have a selection that doesn’t actually contain an active object. Even weirder, you can select a single object (for example with box select), and still end up in a state where that object isn’t considered active.
For me this is super confusing in daily use. It breaks the expectation that selection = what I’m working on.
This is especially confusing for newer users, because it’s hard to understand why a tool affects something that doesn’t even look properly selected. But even as someone who knows how Blender works, it still leads to unexpected behavior and mistakes.
My suggestion would be pretty simple: Always make sure there is an active object inside any selection
I think this would make Blender feel a lot more consistent and predictable. It would also help reduce a lot of “why did that happen?” moments, especially for people learning the tool.
Thanks, Chris
3 Comments
I wish I could upvote this multiple times. The way that blender moves active object to edit mode even if it's not selected is a major design oversight.
Exactly. That’s also where I notice it most often.
I too find this behavior a bit confusing in practice. IMO Active object should be always part of current selection.
I'm doing just now some CAD clean-up, and this behavior is causing issues. If I lasso select multiple objects, and Join them, the Active Object is included. It's logical, but the issues are:
So, I just cant quickly lasso select object and join them, Instead, I need to first select one of those, and then Lasso select rest. And, I constantly forgot this, and end up joining the "ghost" active object.. Quite frustrating.
I wonder if there are any use case for this behavior. Is there some workflow where it is usuful to have an Active Object that is not part of current selection.