When working on complex scenes, positioning objects is hard when you can’t snap to them.
I have tried SnapToOccluded but it is cumbersome; trying to snap after turning it on is a nightmare as Rhino starts calculating all kinds of hidden snaps.
Not really, not sure who would find snap ONLY to selected object useful.
Usually one is trying to position an object in respect to another: For instance, Move, the most basic and used function of them all, needs two points, that means two snaps. Start (on selected object) and End (usually snapping to another object, grid, line point or w/e).
Also as it currently is, it makes no sense whatsoever to display in wireframe my select object in shaded mode when it’s occluded, without letting me snap to it by default.
If you are showing something I should be able to snap to it when snapping is on.
Well, keep in mind that you can have objects selected while you draw a line, say. That is what this setting is for, I would say.
Selection nside the Move command - or any transform command - is a different thing I would say, since you are acting direcrly on the selection.
Here if I make a box, with SnaptoOccluded disabled, in a shaded vp, I get to snap to the box in its original position (ghosted wireframe) even if that location is currently occluded by other objects.
Is that good or bad or just not relevant in the context of your question?
I think its awesome we can snap to selected despite occluded.
What I am saying is.
This is so awesome it should be default.
Snap to selected should not be ‘only’.
I actually encounter a similar scenario to the one you showed daily:
Now I need to place the selected box on top of the other boxes. So I would like to snap its corner, move from there and snap to the corner of another box.
But I can’t because I need to change settings in preference or run macros mid move command.