Marco Musy

Hi, unfortunately the booloean filter is one of the few which has always been problematic, you may want to investigate if there `pymeshlab` can do better on this. In your...

Hi @DeepaMahm, try ```py from vedo import * points_2d = np.random.rand(10000, 2)-0.5 pcloud = Points(points_2d, c='k', r=5) pcloud.cut_with_cylinder([0, 0, -1], [0, 0, 1], r=0.2, invert=True) show(pcloud, axes=1) ``` ![Screenshot from...

Hi, what about this ```py from vedo import * r = 0.2 points_2d = np.random.rand(10000, 2)-0.5 pcloud1 = Points(points_2d, c='k', r=5).rotate_x(30) pcloud2 = pcloud1.clone().cut_with_cylinder(r=r, invert=True) cyl = Cylinder(r=r, height=1).alpha(0.2) d...

The array `d

I guess #1061 is answering this ?

Consider the following: ```py from vedo import * npts = 10000 length = 10 radius = 3 # generate random numbers between [-5, 5]] points_2d = (np.random.rand(npts, 2) - 0.5)...

Hi @ldouteau that's because you have a zero range in x (or y or z). Consider this: ```py import numpy as np from colorcet import bmy from vedo import Points,...

> By the way i'm also wondering why reconstructed surface show wider range than that of the point cloud. Do you have any insight on this ? that is because...

Hi @DanKrsi yes - it's in [interactor_modes](https://vedo.embl.es/autodocs/content/vedo/vedo/interactor_modes.html#MousePan) submodule check out the example in: https://github.com/marcomusy/vedo/blob/master/examples/basic/interaction_modes1.py

You can start with that interactor with eg: `show(meshes, axes=1, mode="TrackballActor")`