Dysfunctional meshing for binary masks

[oanegros]

As noted by youtube user @nanoastro on https://www.youtube.com/watch?v=7YcflamP23M&lc=UgxO647bjKzWHUI64aV4AaABAg
Recommendation currently is to load binary masks as volumes and use the Surfaces or add a Volume to Mesh node in the geometry nodes panel of the volume if you do not want to load Surfaces.
I'll look into making the behaviour of the Surfaces tag not set a threshold, but still load surfaces, to see if this helps with getting this as surface-to-mesh, also will look into why the skimage marching cubes fails on this.

[oanegros]

scikit-image/scikit-image#7377 if the marching cubes gets out of memory, it cannot report it

[oanegros]

This is currently not easily fixable recommended is to either:

• if it is a binary mask with multiple objects, first do connected components
• load your mask as a volume and apply a volume to mesh node or keep the Surfaces ticked

[oanegros]

better catches for this in v2.0