It’s sooo good to hear that you’re working on the Outliner again! I haven’t read all of the 540 messages, so I’m probably late and pointing out doubles.
My top pain points:
Drag and drop between Parents (like empties) should be just as comfortable as drag and drop between Collections. Sometimes there is just no way around building scene graphs with that structure (e.g. for Game development), and at least with 2.83 this behavior is pretty much broken. Esp when reparenting (Dragging with shift) between Collections.
I firmly believe that all drag-operations should ALWAYS include all children. Everything else just feels broken. If the outline uses a folder-tree metaphor, dragging something should always included its content. There could be an option to drag an element without it’s children, but it should not be the default.
I hope that the “Delete” shortcut will eventually work not only for Collections when hovering the outliner.
Some interactions in the 3d-view should focus (scroll into view) the resulting new objects (like Mesh->Separate->By selection).
[Content removed to avoid possible copyright infringement]
Thanks again for your great work! I’m not in charge, but you get plenty of Karma points from me
Hi @natecraddock,Thanks for your great work!
Here is my wanted function that is coding by python.
How do you think of the operation logic to multi-select objects of collections?
First because it is an unnecessary investment … 2.83 is destined to be abandoned to expiration,
Second reason because this new code will have to mature (solid debugging and optimization) …
You have to wait for the next LTS.
I tried also to simplify the restriction toggles.
It happened to me and probably to many beginners to render a scene and see all the objects that I have hidden.
Because I didn’t know I had to toggle in EVERY hidden object to “hide in the render scene”.
This double step is unfamiliar, unintuitive, and time taking.
I rendered an animation yesterday and I forgot an object toggled, I lost 4h of work because I realized it only at the end.
My proposal is this:
Wouldn’t be more intuitive to render ONLY what I see in the viewport (like every software out there)
and set the (advanced and way less common) behavior of hiding or viewing a specific object even if it’s hidden in the viewport as a restriction (exception) toggle?
Basically you won’t need to toggle every time the “disable in render” button but only when is an exception.
The ability to sync eye-monitor-camera icons could also be mapped to a modifier key, say I press Alt+Click on the eye (or camera, or monitor) and all them go along together on or off
I suggested this here, but it doesn’t seem very popular (Blender is a tool for experienced Blender users, it’s not built to be an intuitive tool for beginners to learn unfortunately):
I agree. And not only for beginners. It is even worse since the default has been changed to hide the renderability toggles. Many people will not even know why their hidden objects are still rendering.
I have a archviz project right now, which is heavily nested.
eg. every peace of furniture is in separate blend file linked into a scene, which is itself linked into another scene containing all the render setting and environment.
I constantly fix problem related to restriction toggles. Еighter something is missing, or some object that is supposed to be hidden is visible. What makes things worse, previewing the render with Cycles in the wiewport uses viewport settings and you cannot catch the mistake before doing F12 render.
I do not agree that complex use equals “advanced”, and I do not consider myself a beginner.
Right now visibility toggles require constant management by the user. I had a proposal trying to fix the problem, where I point out the problems with the current system.
the proposal from @Breccia has some merit. There are way too many toggles.
I would also really like to be able to link viewport and render visibility so I can only use one column
Is this also mentioned?
When relocating objects with parented objects inside you need to select all objects that inside to relocate properly. It’s so inconvenient and (if I not wrong) it only blender have such “feature”…
this…
Outliner_Relocating_Parented_01
should work like this one except selecting all stack
Outliner_Relocating_Parented_02
or I something not understand with this links feature?
Also here is a bug or what is it?
If I drag and drop object with parented objects to another object (in other collection), it drop some parented object also.
Outliner_Relocating_Parented_03
and the question with the last video:
How to relocate Object with parented objects to another object completely, without making links…?
Man good thing you look at these issues!
This drives me mad sometimes, your suggestion is much better, drag the parent to another collection should bring the childs along by default, otherwise it just seems broken, imho.
viewport and render visibility so I can only use one column
)
