Oras Phongpanangam

Yep. Here's a json and the code to visualize it. [voxels.zip](https://github.com/marcomusy/vedo/files/7636496/voxels.zip) ```python import json import vedo with open('voxels.json') as fin: voxels = json.load(fin) volume = vedo.Volume(voxels) lego = volume.legosurface(vmin=0.5, vmax=1.5)...

Looks good, thanks! That was super quick. It seems like the colors are wrong though? The value is 1 so shouldn't it be orange? 

Thank you! Let me see if I can make a reproducible code to show the slowness.

This is all I'm doing in Jupyter ```python import trimesh import vtkplotter body_mesh = trimesh.load_mesh('censored_scan.obj') vtkplotter.show(body_mesh) ``` Took about 10 seconds to display with k3d. If I use Trimesh's threejs...

Interesting. I duplicated your code here, and it took about 1 second for the display to show up. However, my Jupyter screen froze for about 10 seconds after that before...

k3d examples didn't give me any trouble. In fact, doing ```python body_mesh = trimesh.load_mesh('censored_scan.obj') plt = k3d.plot() mesh = k3d.mesh(body_mesh.vertices, body_mesh.faces) plt += mesh plt.display() ``` also showed the result...

Update. 1) I replicated the same behavior in Chrome, Safari, and Firefox on Mac OSX 10.14.5 so it's not a browser specific issue. 2) Compared to my bare bone k3d...

This worked perfectly for me, thank you! I'm still surprised your machine could actually still run the scene smoothly with all the vertex colors. To clarify, did vtkplotter use to...

Tried running code from sphere.ipynb and got no problem. My mesh has about 6000 vertices or so. I'm suspecting that 6000 colors are just too much to calculate. Also ran...

Tried the same example above, and was fast as well. My info box says - Js version: 2.7.0 - Python: 2.7.0 Are these the versions of vtkplotter or the Python...