Previously when I used Rhino 5, I used the ‘Point Deviation’ command with a point cloud and a surface, and only the colored points/display hairs that were on the front side of the surface were displayed, and the points/display hairs behind the surface were not displayed. This was an extremely useful display option, as it allowed me to fit a surface to a point cloud, without interfering with the point cloud (resulting in a plane perfectly placed at the outer position).
With Rhino 6 however, the colored points/display hairs that are both in the front of the plane and behind the plane are displayed. This makes placing the plane at the closest outer position of the point cloud very difficult. You can see in the attached image that all points/display hairs are shown – the plane is placed about midway through the point cloud, so it is difficult to decipher how far the plane is from one side of the point cloud. (I understand you can figure this out by going in a plan view parallel to the plane, however working in an isometric view is much quicker and efficient). I am hoping to have ONLY the points in FRONT of the plane displayed.
I saw your post in the YT forum. Do we know if there is a fix for this yet? It’s not possible to achieve my current work tasks with this feature. Maybe I should look into downgrading to Rhino 5?
I’m back on this same problem again… I’m analyzing point clouds right now and it looks as though this was never fixed. I installed the latest version of Rhino 6 today and I am still not able to use the software for point clouds. You mentioned that this was fixed in a WIP, was that ever put into the full version? I think Rhino 5 is still my best bet.
The V7 evaluation works. Who should I talk to about upgrading, do you know if this is something I’d have to pay for? I’m fine with V6 other than the deviation bug.
Also side note, in V5; you can select the point clouds and the surfaces together, and you can use the “pointdeviation” command to show a deviation analysis of the clouds compared to the surfaces. In V6/V7: you have to use the “pointdeviation” command first, select only the point cloud, click enter, then select the surface, click enter, and then the analysis runs. This adds another step to the process and makes it a little more inconvenient.
Yep - the difference is, you can now extract points from objects that do not obviously have them, so surfaces can be inputs on the point side of the process. (The render mesh vertices are used as the points)
