edit: Okay nevermind. I may have to go up to widith + 1.

More edit: Well, it works for me when I only go up to width - 1. I do need to update the neighbor region when I dirty boundary values. I don't think going up to width + 2 solves this problem because for 0th element you are relying on the neighbor to generate the value, thus when you change that element you have to ask the neighbor to generate the surface. I could be wrong. Anyhow, going only up to width - 1 works for me.

As for the decimation thing, I will try to get you a screenshot. It's just I'm int he middle of refactoring and I have taken out that piece of code.

Thanks Beyzend.

I had overlooked the issue of border values changing meshes on both sides of the region boundary. Previously it was probably OK for me due to the duplicate faces bug, but now meshes will definitely only be generated for faces on the side containing voxels.

I will need to update my chunk manager to check for boundary value changes to re-generate the neighbors mesh also...

I'm just going thgouh the bugs - I think I can close this one as I've applied DefiniteIntegral's change.