Is the usage of Int8Array instead of Uint8Array intentional?

[nakedible]

I am wondering if the usage of Int8Array as the underlying voxel array type intentional? This means that materials > 127 will end up as negative values, which means they cannot be used directly as indexes to any materials array lookup. A simpler choice would seem to just declare it as Uint8Array.

Perhaps there is some magic performance reason for this, but I do not know of any.

[max-mapper]

good point! it isn't intentional -- we were using Float32Arrays before and storing hex colors for voxels (before we implemented textures) and just switched it to storing integers to lower memory footprint. At this point you can actually use any typed array/native array that you want. i'll close this when we switch the default type

[max-mapper]

now there is game.arrayType max-mapper/voxel-engine@9ca141f todo: pass it into the voxel module

[deathcap]

proposed changing to Uint16Array (maximum voxel-mesher/ao-mesher size) in #18 but agreed passing in arrayType from voxel-engine would be preferable

[deathcap]

0.5.0 is now using Uint16Array but we may still want to pass in game.arrayType. The array type is only used in generate(), which does have a (currently unused) game parameter.