There are a couple of display issues I’m experiencing. One of them has been ongoing since the earliest days of the v6 WIP. The other, I’m not so sure whether it is a new problem or not.
1- Often when using tools across different viewports, viewports fail to ‘activate’ by simply moving the cursor over them. For example, a tool such as
moveEdge, you might select the edge in one viewport and then use a second viewport to control the actual transformation. When doing this, often (~50% of the time) the second viewport fails to become active until I click on the viewport title.
I’ve been trying to capture this on a video, but it seems that when activating the screenshot screen recording that the problem does not occur. I’ll keep trying, but this is really weird.
2- When using clipping planes to reduce visual clutter when modelling (for example, limiting to only seeing the middle floor geometry on a 3 storey building), snapping aids do not display in the viewport if using the ‘project’ snapping option. I assume this is because the cursor snapping is taking place on a CPlane that is outside of the clipped view. Whilst I understand what it’s doing, it is definitely undesirable. For example, there might be a column that extends from ground floor all the way up a building. The top and bottom of it might be clipped, but the geometry still exists in the visible parts of geometry. Perfectly reasonable to snap to it. But then the snapping UI doesn’t appear.
I’d say that snapping UI cues / aids should be visible regardless of clipping planes. I appreciate that this could be resolved with setting up multiple CPlanes, but I prefer not to work with these. And it doesn’t get away from that when the cursor is snapping that it should have the UI to show it is.
It seems to me that this 2nd point is perhaps linked a bit to this topic in that it is about displaying sections / snaps correctly for effective and easy modelling: Rhino v6 selected edge display issue
Both of these seem to me to be really basic fundamental requirements for effective modelling across multiple viewports.
All of these problems are essentially viewport related.