Thank you!
I can confirm, current service release candidate have control net selection much more reliable on what we can see.
Let’s strike while the iron is hot.
… then, there is the opposite problem: the positive selection of what is not visible or occluded.
Mikko on youtrack says “there’s no occlusion culling”.
Ok. I’m not sure it is better to have selection prevented, culled, for not visible control net elements.
For sure I’d like to try it.
Most of the times I select an occluded object is by mistake!
How could I possibly volontaurly select something I cannot see?
(apart from selecting/snapping to something already selected, I can “chain” up using the yellowed control net lines, that is useful…)
But
this is wrong:
double click to select a loop of grips can result in the selection of a different, occluded, loop, if the click point is “unlucky” and near the visual intersection of 2 unrelated control net lines…
It’s tricky because the first click correctly select the visible control net line, but the second click loop-select a totally different loop.
(I’m clicking near the same control net line of my last shared file + named view, red sphere)
btw this is easily repeatable:
- select all control net grips
- visually rotate the camera until 2 unrelated loops intersect on screen (first loop visible near intersection, the second not)
- deselect all
- try to double-click select the visible loop near the on-screen intersection
- with few attempts you can loop-select the not-visible loop (toghether with a single line of the visible one)
At first attempt:
Imagine this ^ but that happens un-wantedly!
Imagine this ^ but on heavy complex SubDs: you fail selection most of the times.
… that’s why I work with camera from inside the objects…
… culling selection of occluded stuff would be cool.