Hello,

When filling a volume with data like this:


When surface extracting the 1 voxel(data 1) on the first x row, and 4 voxels(data 4) on the first z row have an issue with the outer voxel face not being built. I am using the CubicSurfaceExtractorWithNormals<SimpleVolume,MaterialDensityPair44>

I'm trying to setup loading and saving Voxel data for assets, so my regions for this purpose need to be tight. I would rather not use magic numbers or hacky larger regions to get it to work.

Yeah, I'm actually aware of this. You should switch to the regular CubicSurfaceExtractor if you can as this handles the edge cases correctly. It also performs decimation of the resulting mesh and is generally faster/better.

I only really intended the 'WithNormals' version to be used while people are becoming familier with PolyVox, as they may be confused by having to generate the normals themselves in shader code. I could fix the edge cases but it complicates the code (making it harder to learn from and maintain).

Can you switch to the regular CubicSurfaceExtractor?

I am using vertex colouring instead of textures for my project so I shouldn't need the normals anymore. (Previously I was generating UVs and not using a shader for texturing)

I will try it when I get home. I was also having trouble getting mesh decimation to work properly so it's good to hear the regular CubicSurfaceExtractor will solve my issues.

Thank you for the quick response

Ok, Just converted it so I am using the CubicSurfaceExtractor<SimpleVolume,Material8> and it handles the region edges fine now.


I wonder if anyone with ogre experience might know why
I am having an issue with using meshdecimation (bMergeQuads).
When it's enabled and I move the camera around I see little flickers of holes(about the size of a pixel) in the mesh.

Thanks again for the help David

Those holes are the result of t-junction problems. I don't think there is a way to resolve it unless you fix it by using skirts or split the polys properly. I'm currently using skirts and it reduces the problem to a barely noticeable level. But the way I'm using skirts is hackish so I may improve it later.

Another method is perhaps use tessellation if you have dx11 to get rid of t-junction.

thanks for the info, since my game is simple I don't want to use dx11 because despite being 2011 people still run winxp :{

I think for now I will just not use decimation and revisit this at a later time.

Thanks for the info

Interesting... I wasn't aware that there was a problem with t-junctions in the decimated mesh. But logically it does make sense that they could occur. Maybe I haven't seen them due to having antialiasing on or something.

Anyway, I would consider this to be a bug in PolyVox. Not sure if/how it can be fixed but I'll investigate. I'll also move this to the bugs forum.