I have this issue where a pointcloud is being shown to be at 0,0,0 even throw it can be selected in its correct position. If I explode the clods the points will appear in the correct position.
notes this only happens when the cloud is more the 150m away from the origin.
the files contain several point clouds, not one large cloud.
I’m splitting the cloud in a script component in grasshopper:
pts = full_cloud.GetPoints()
pts_XYZ = np.array([[p[0],p[1],p[2]] for p in pts])
r = np.array([r for r in range(len(pts))])
c_cloud = []
for i,c in enumerate(pts_center):
if not c:
continue
inside_box = (pts_XYZ[:, 0] < c.X + x[i] ) & (pts_XYZ[:, 0] >= c.X - x[i]) & (pts_XYZ[:, 1] < c.Y + y[i]) & (pts_XYZ[:, 1] >= c.Y - y[i])
outside_box = np.invert(inside_box)
remove_index = r[outside_box].tolist()
new_cloud = full_cloud.Duplicate()
new_cloud.RemoveRange(remove_index)
c_cloud.append(new_cloud)
a = th.list_to_tree(c_cloud)
Yes, of course.
the gh file creates 2 clouds and export to file. one close to the origin and one 300m away from the origin. it looks ok I grasshopper but when I open the exported file the one 300m for the origin is previewed at the center of the file. If I explode the point cloud the points appear in their right position.
Hi @Japhy
Thank you for getting back to me.
I have the same behaviour when previewing in Grasshopper. But when I open up the export file. (pointcloud_export.3dm). It looks like this.
I just opened the exported file on a Windows machine. Here there is no issue. This seems to be linked to Rhino on Mac. Also, I don’t think that it has anything to do with Grasshopper as the issue also occurs when creating a cloud in Rhino. The video above was recorded on an iMac M1, could this be about Metal? Are you able to produce the error in Rhino on Mac?
