Great, glad you got it working

Thank you!

I created a github repo if someone is interested of my experiments: https://github.com/kalwalt/sverchok_nodes_collection/tree/master/blend

and issue on sverchok https://github.com/nortikin/sverchok/issues/1168#issuecomment-274850616


Only a question: i have some troubles with the indices of the mesh, in the sense i can't figure out how they are stored. Since i do not put the indices in a vbo i have to recreate the list of edges or polygons by code. How shoul i manage them?

i solved that issue, polyvox output tris so was easy to fix it. Now we have a polyvox voxilized sphere inside blender!!
A new era began....

Wow, cool stuff! I've never seen PolyVox in Blender before

There is always a first time!

i tried to import also the LargeVolume but it seems that something is broken at that point of the commit i was receiving an error conceirning a compressor not assigned, this the output from the Paging example:



Did you remember maybe when this bug has fixed?

I'm not sure this is a bug (though I guess you can say it is a bug if it occurs in the example). The idea used to be that you had to provide an object implementing a compression algorithm which would be used when the LargeVolume became low on space. At different points in PolyVox's history this was compulsory or not compulsory, but there should at least be a default compressor implementation somewhere in PolyVox?

At any rate, I wouldn't worry too much about the LargeVolume. It adds some complications compared to RawVolume and is not really needed until your volume are bigger than about 512x512x512 voxels. In my experience it is actually the size of the generate mesh data which becomes a problem first.

yes maybe i don't need a Large Volume, i'm primarly focused to create small meshes ( but with high number of polygons), I would be interested also to add directly a material to the voxel, As i remember and i looked at the Api it should be possible use RawVolume with MaterialDensityPair, but i can't found in the python bindings ,Maybe is implemented in another way or there is a different way? You should in theory assign the value voxel with setDensity() method and setMaterial(), Unfortunately the docs in that commit wasn't so clear ( maybe was broken at that he moment) so it's difficult fro me to understand if it's a possible thing or not.

This is how it should be done, but unfortunately I don't know if it is possible through Python. The problem is that PolyVox makes heavy use of templates but these are not supported by Python. So in the SWIG files for the bindings we have to explicitly define every combination of volume and voxel type which we want Python to support. You can have a look at the '*.i' files to see if it is in there? But I suspected using class types such as MaterialDensityPair is trickier than adding basic types such as int.

This is why I will try to avoid using templates in the public interface of future projects, as it makes writing bindings quite complicated. I've learned a lot of stuff from writing PolyVox!

Unfortunately i can't find such def in the *.i files. I think it's time to solve the python bindings definetevely. I have already a fork of polyvox_bitbucket, i will create a new branch in my repo and will continue the discussion there. At the moment i'm in stuck with the cubic and MC extractor, I think the Swig template def are not correct. i will post here the link fo the new branch. Actually you can find my polyvox fork here

I created a pull request on your repo, so we can collaborate there!