← All ideas
  • Published 23 Mar 2020

Modeling UX needs simplification

Example 1 - How to create a new object from a part of another object

1 - select polys + click Duplicate
2 - Separate selection
Now you have selected a new object in object mode and old object in edit mode! If you want to work with a new object you have to: 1 - go to Object mode
2 - select again your new object
3 - go to Edit mode
(3 extra operations!)

Expected behavior: In edit mode select polys -> Separate and now you in edit mode with a new object

==============================

Example 2 - Subdivide (smooth) part of the object

1 - select polys which you want to subdivide
2 - remove selected polys into another object (see example 1)
3 - create subdivide modifier
4 - apply subdivide modifier
5 - merge objects
6 - bridge borders (another pain in the back)
(4 extra operations!)

Expected behavior: select polys -> click subdivide (I know, blender have subdivide operation, but it cant subdivide triangles and ngon properly)

I can go on forever. I think that a blender absolutely needs to rework the modeling pipeline in terms of UX. Modeling is the basis of work in 3D. It’s strange for me to improve the rendering, the composition, if any serious work begins with inconvenience and suffering.

100%

Development Status: Open

Upvote 8 Downvote 0
verderblich
23 Mar 2020

4 Comments

TheWizardLord

The first one could be added potentially it would be good to have as a second option with say shift-p to move with separated Selection. The reason it isn't an option is that separate has, loose parts and materials as variations and would need a system to determine which new object to switch to. I also find the separate selection useful for splitting up models into parts manually by selecting and separating multiple times. So having both would be a better solution.

As for example 2, the subdivide smooth isn't a Catmull-Clark subdivision as Catmull Clark isn't a smoothing method but a subdividing method. Subdivide smooth on the other hand is a combination of a regular subdiv method and a smoothing method what that smoothing method is I have no idea but it sucks 50% of the time. In saying this I agree with you completely it's not very clear. The edit mode subdiv should have a smoothing method and a subdiv method as separate options with there respected thresholds. A Simple Rename to Subdivide and smooth would help but having the additional options would be much better.

EzyPoly

Absolutely!

Josephbburg

I disagree with point 1 -- it would annoy me if the object switched as much as it annoys you that it doesn't. Point 2 -- I think this is a problem. This is IMO a bug, the operator should use the same code as the modifier. I also think the modifier should support vertex groups.

borschberry

* @Josephbburg * Yes I agree with you. Switch or not switch - both fine. But not one in object mode and another in edit mode. About point 2 - This is exactly what I'm talking about. It's kinda bug or maybe just old tool or maybe that's what it was intended. All modeling pipeline needs general revision and a lot of fixes