Comments on: Plans for PolyVox in 2014

By: David Williams

David Williams — Mon, 03 Mar 2014 13:10:48 +0000

Thanks, it’s nice to know people appreciate our work 🙂

By: Anonymous

Anonymous — Mon, 03 Mar 2014 07:02:36 +0000

Amazing work you are doing here with PolyVox I do look forward to future releases as I am an advocate for PolyVox and try to keep up-to-date on changes. Many things I like here mainly C++11 that is a huge step forward. I also would love to see the push forward for header only to eliminate compiling the library entirely. The ability to just include it in my project would be fanominal!
Keep up the good work the both of you!

By: David Williams

David Williams — Sat, 15 Feb 2014 22:16:52 +0000

Can you elaborate on this? You mean that CMake+GCC can have difficulties building a project if that project uses some dynamic libraries and some static libraries? Do you have any links related to this?

I think in general we would like to go header only but it’s not yet clear if it’s practical. I believe C++11 does make it easier though.

By: Jesse

Jesse — Sat, 15 Feb 2014 03:46:07 +0000

All of these proposed changes sound great.

My only request is that you only drop dynamic builds if you switch to header only. CMake + gcc creates headaches when mixing dynamic and static libraries, and while there are ways around this they are tedious to maintain.

By: David Williams

David Williams — Thu, 23 Jan 2014 14:12:07 +0000

In general you should not call stuff in the CubiquityDLL class directly, but you should instead go theough the Terrainvolume.SetVoxel(…) interface.

But also I added some documentation recently about how the set the voxel values for smooth terrain. It’s only in Git at the moment but you can read it here: https://bitbucket.org/volumesoffun/cubiquity-for-unity3d/src/master/Assets/Cubiquity/Scripts/MaterialSet.cs

By: Anonymous

Anonymous — Thu, 23 Jan 2014 14:01:49 +0000

Thanks David.i asked because I get confused with the proper usage of setVoxelMC function in the CubiquityDll class.

By: David Williams

David Williams — Thu, 16 Jan 2014 09:15:46 +0000

It’s not very practical – Cubiquity’s ColoredCubesVolume only stores a color value per voxel rather than storing a material id. So although you can swap the material you don’t really have the required information to do per-block texturing.

The TerrainVolume does use material ids but it is intended for smooth terrain (not blocky) and so is designed a little differently.

By: Samuel

Samuel — Thu, 16 Jan 2014 08:52:19 +0000

in Minecraft we use block id for textures. is there any method to replace the colors in the Cubiquity Volume by textures? for instance, if u have a volume with 10 colors can i replace them by different textures.

Thanks in advance.