Ah I see. The recent viewport refactor created a few base concepts such as the split between picture and overlays, the latter being whatever’s applied on top of the rendered picture : helpers, non-renderable objects, wireframes or render border, and so on fall into this category. Gizmos were split out from those for the sake of practicality, so that the user can disable just them, but keep the overlays on, but technically they’re overlays as well.
Yes, the interface should not be a split of technical of code terminology even in this case seems artificial like you say. By that logic Eevee should be in a render “department”. What matters is the function it performs: visualization. I sometimes want to show the mesh in wireframe others shaded with wireframe, others only shaded, etc.
I see in many situations the problem is the Language - Logic. Yes the meaning of words that we use to discriminate to justify that this should be here, that should be there. If i would be the master of Blender interface the first thing would be to choose the fewest words possible to describe it.
An example is road traffic rules, it is an excellent example of a language-logic that pretty much everyone can understand. It’s coherence achieved universal acceptance.
Hmmm I never said that. Tbh I don’t have a strong opinion. I think those settings are rather easily findable. Good blending, don’t hesitate to ask for assistance in your learning.
When you said they are technically overlays as well.
Ahhh yes, my bad I meant the opposite excuse my english : they were split out for convenience rather than technicality. Up to the beta I believe they were under a single toggle which made it quite inconvenient to disable one while keeping the other.
I think you have to get used to the fact that each software has a different philosophy and way of organizing displays. Not to mention completely different feature sets. In Blender’s case, they made the choice for this to be an overlay when made globally. Which makes more sense than it being a shading option. Wires have nothing to do with shading because they can be visible in all shading modes. By your way of thinking, we would have two options for each shading mode. As it is the option is still right there in the top corner right next to shading options with wording that is real clear as to what it does in the little pop up hints.
In many other software you are very limited in your choice. It is either wireframe, sold, wireframe solid, then textured and lit and so on. That is why they are listed together.
Blender’s way of doing it is different. So in this case it makes complete sense for it to be non obvious since it is a feature. Not a UI decision.
I do recall reading in the Modo forum as to how people were impressed when their models looked a lot more pleasing to the eye in Blender 2.8 than Maya and also their native Modo (because of more modern drawing features even for things like solid mode).
The tricky part is convincing the industry to leave the legacy workflows and displays (that pros have been accustomed to and comfortably using since the 1990’s) behind, sometimes a new workflow is embraced like PBR, but not always. Not only that, but it is tricky to encourage them to pick up potentially useful features they never encountered before (ie. Blender’s 3D cursor, which actually saw significant improvements in the last few years).
It is true that some new ways of working just didn’t work (like right-click select), so I’m not saying that everything that is ‘new’ will be superior, but many other times it is superior or has the potential to become so.
Heh, you should give it a try
I did… and the more I do, the more I hate it…
It has lots of shortcomings, and with a little love it could be much better I agree to that. Hopefully some fund money goes into it, along with the snapping improvements, that could hange the way we model in Blender.
I disagree Richard . Your text imo also makes it clear. It is the propose, placement in workflow that matters.
For example why Eeeve is now there in viewport icons instead of solely a propose build menu?
Answer: Its speed makes it possible to use it for creative proposes in many workflows. So it can be used often. In the past a render engine like that would be a more formal thing because it would be much slower.
It is still a render engine, but a change in performance made to change its placement in interface.
lol well you can disagree with me. But don’t kill the messenger. Wireframe is not a shading option in Blender, like it is in other apps. That is just how it is. You wanted it to be easy to discover. And if it was a shading option, it would have been right there where you expected it.
This is one of those many cases where choices made to offer more options and flexibility require an interface that makes those options available. As cleanly as possible. And in this particular case. Blender actually has it right. One place to add a wireframe overlay over all shading options.
Look. You see, stick around long enough to get to know me. I am not being a Blenderhead fanboy. Anyone here can vouch for that. So please don’t assume I am just trying to defend Blender against all odds.
Moving on to other subjects, I am sure you and I will find other points of agreement.
It is true on this particular point, Blender has moved forward. And this means a new way to address it in the interface. And of course tripping people up.
But this is always why I make it a point to read the manual on the interface when I learn a new app. There is always a convention that is different from app to app. And it is good to get over that ASAP.
I don’t dislike the 3D Cursor, but I do think it is wasted potential. To me the 3D Cursor needs two things to become an incredibly useful tool.
Create a free transform gizmo for the 3D Cursor so the user can move it anywhere he or she pleases with more precision. This does multiple things. The user can now put the 3D Cursor anywhere they want, even inside models, and they can now add new meshes and more anywhere. This also indirectly improves all the gizmos, since users now can move them freely thanks to Blender already having a follow 3D Cursor option.
Add the ability to add and save multiple 3D Cursor positions in a scene. Also, add Transform gizmo support so you can have multiple gizmos for different purposes instead having to manually move it every time.
Add those and the 3D Cursor will be incredible. I would even want to have it in Sculpt Mode then.
Entirely agree. The “3D cursor tool” should straight up activate the transform gizmo by default (translation+rotation). I don’t think it would even be that complicated code-wise…
Concerning your second point there used to be an addon called enhanced 3D cursor which let you store different positions and recall previous ones through a history, that was great. It hasn’t been updated though. Basically turn it into a “favourite pivots” feature.
It would indeed be useful to upgrade it to a full scene object that can still do the things we want it to do (ie. tool pivot and object placement with/without rotation). As a full-fledged object, it would do things like snap to vertices when a key is held down (in addition to the easier transformation).
Richard Culver in my world disagreeing with someone is not killing the messenger. Neither i think you are or not are a Blender fanboy, even if you are, a fanboy can bring a valid point. I also wish we can just discuss the points.
That’s already the case, shift+RMB moves the cursor and holding ctrl snaps it. However I don’t think making it into an actual object makes a lot of sense, or to put it differently, it’s probably overkill : I think all the features that we’re fantasizing for it can be achieved with the regular tool.
Yes it is. But, the starting point was this - Blender 2.49:
Possibly the least discoverable user interface known to man. See that toggle button just called ‘A’ as an extreme example.
Other examples are things like this X button, which of course has nothing to do with the X axis - the examples are many.
Prior to Blender 2.30, there were no menus, so users would have to know all the keyboard shortcuts by heart as literally the only way to perform actions. Also no undo whatsoever. In case you made a mistake, you had better have saved.
In Blender 2.79, the current version just a year ago, if you would simply click on objects in the viewport, it would not select anything. Instead, it would move around a lifebuoy symbol. To select items, you would have to use the right mouse button, if your mouse even has one.
Contextual menus would appear not by pressing the right mouse button, but by pressing the W key on the keyboard.
So, with the above in mind, I think you’ll agree that at least things are becoming more discoverable over time.