Yes, somewhat - I did find out (or better - was reminded) about them later. The nodal operators donât save the last setting, do they? Also at least âOnly selectedâ does not seem to be reachable by nodal shortcuts and to me it feels weird that there are operators which are simply only reachably by keyboard only. But if thatâs by design then thatâs the way it is. I also found out that [Alt] followed by [K] invokes the tool instead of the nodal which I found out by total accident. If the tool would display it somehow like C4D does (âAlt ~ Kâ) then at least this would have been clearer. Maxon use â~â as a way to communicate a key succession as opposed to a Key combination.
Itâs okay now that I know but it certainly wasnât too intuitive to find out.
ON a totally different note (maybe I will be corrected here as well): Adaptive grid size seems to be not working in 3D view.
In orthographic view the grid adjusts when zooming in and out and also displays the current measurement of the grid. Cool!
In 3D view it doesnât. If you want to work in perspective with a smaller grid (in centimeters for example) you have to adjust the size in the viewport overlay. Which in turn screws with the display in orthographic again (because it shows an adjusted value).
Same goes for moving objects, it seems. If you select a hierarchy, and then drag it over to another collection in the outliner, only a single object will be moved.
If you, however, use âmove to collectionâ in the viewport, they all move over.
My man Red wax once requested an alpha option in the themes for that selection highlight so we could be able to turn that off if we wished so, but still no love.
The text in the outliner already changes color when selected, why on earth do I need those giant bar highlights. Thatâs just too much clutter to me.
On the Outliner I can assign any shortcut to the Delete operation, but sadly the Delete key after being assigned it doesnât work, but if I assign the Backspace key then it works⌠Bug, limitation, design?
You could call it a key conflict or you could call it poor design. Instead of having one operator to delete anything in the Outliner there is a separate operator for deleting objects and for deleting collection (poor design) and if you bind both to the same key then you get a key conflict. As a workaround you can set one of them to activate on Press and the other to activate on Release.
Did that proposal ever make it onto Right Click Select? It seems to me that the GSoC 2019 threads are no longer a good forum to bring up issues since it is over.
Itâs a bit Sisyphean I guess. Which void would you like to shout into? A GSoC thread that is no longer read or a focused RCS proposal that is ignored?
Thanks for pointing out. Funny how there canât be an "universal " delete key like in any other software, from excel to PowerPoint to photoshop for example.
Is this a bug or I remember it wrong that it behaved correctly before?
If I set the Viewport Shading Background to World I expect the background to use the World background (just like in material preview and rendered modes)
Otherwise whatâs the purpose? It just changes slightly from the theme grey to a lighter grey.
Thanks a lot.
Itâs logical⌠perhaps⌠but not at first sight. Itâs hidden.
We use nodes by default which is great - but if I turn that off, the viewport display syncs with the color above. Makes sense, sure.
But can it be a paper-cut request that it still syncs in node mode as long as itâs just a single color?
Donât know if this is still considered UI:
Any kind of edge marking could really benefit from an additional âmark selection borderâ.
Otherwise itâs always select boundary loop first, then select edge sharp, seam etc.
Despite 2.8 cutting down on shortcuts, I still managed to trip a shortcut booby trap today. Can you guess why all objects move instead of just one here?
The first part is just visual chaos (whyyyyy, designers, whyyyy?), but the second part should give you a clue.
Spoiler
The proportional editing was on, because I accidentally hit O. Now, luckily thereâs actually a highlight on the proportional editing icon that I should have spotted, but two important things:
The circle was so large that it was outside my entire viewport, and hence invisible!
Imagine instead if there would have been a heat map colorization on the influenced objects.
