MeshLab 2023.12 is out! #1449

Same as the older versions: 12d is built with double precision floating point (the default one used by pymeshlab).

I had this same question and, and it would be nice to have this documented somewhere more discoverable. Maybe on the Releases page itself (when you're trying to figure out which release asset to download) or in the Readme?

And 12 is built with single-precision float? 64-bit integer discretization? Throwback high performance 8-bit integers? As a new user, I'm not familiar with the old version naming scheme. And it's still not entirely clear what the difference is or why someone might want a double precision vs. whatever the other one is.

@cod3monk3y did you ever determine this? If not, @alemuntoni could you clarify?

single precision float. The reason you would want the "d" is for pymeshlab.

https://www.embree.org/

It is a library for ray tracing, used by the new plugin filter_embree.

I assumed that. But I don't see that filter anywhere in the UI menus, buttons, etc.

If you search embree in the search bar, it should find the filters that use the library (the library is mentioned in the description of the filters). Right now there are filters like ambient occlusion and obscurance that will likely replace the older ones that run on GPU (and create lot of portability issues).

OK, I see. Thanks!

Did you try the appimage?

Nope. Python 3.7 reached the end of life on June 2023.
If you need pymeshlab for python 3.7, you'll need to build it by yourself.

The log file reports an error:

CMake Error at src/CMakeLists.txt:88 (add_subdirectory):
The source directory

D:/meshlab-main/src/vcglib

does not contain a CMakeLists.txt file.

It seams like the source of vcglib is missing. You probably need to clone https://github.com/cnr-isti-vclab/vcglib into D:/meshlab-main/src/vcglib and then try to rebuild meshlab.

Thanks for reply me, I fixed that isssue, but I face with new problem, can u help me

Link: #1483