I assure you that I suffered a code injection while there was a "prove that you
are not a robot" loop.
A loop that evidently affects only Chrome, and predisposes it to receive false
aggressive notifications every time you open Chrome. However, I managed to block
them via Chrome's site blocking.
I could see the original page for half a second, then it was injected with spam.
Now I saw the includes you posted.
It is a known algorithm, I already have it, with other algorithms, on MeshLab
(see shot).
With MeshLab the transformation can be done on the 3D file. It is persistent.
The includes only do it for the PovRay render.
I need persistent, because I use the same files for 3D printing. So I thank you
but the "static" transformation method is preferable because the 3D file (povray
or STL or CAD) is already complete. Launched on PovRay it consumes infinitely
less memory. Too bad there is no example file in the zip, to see the results on
complex shapes, it also seems very complicated to implement it on each mesh of a
job.
He only shows the shot of a small job, but not how he passes the original
polygonal data to the includes.

Post a reply to this message

Attachments:
Download 'clipboard01.png' (29 KB)

Preview of image 'clipboard01.png'