neuronine / voxel

Voxel

First pass at Voxel Generation in Unity

Configuring the World

• All configuration options, including chunk size, view distance, and such are located in the VoxelData class as constants.

voxel's Issues

Use Object Pooling for Chunk Creation

Instead of creating a new Monobehavior for every chunk, and having to add components which is causing performance issues, we could instead move all the chunk data into its own object and then pool the game objects representing visible chunks. As new chunks are generated we would create a ChunkData object instead and they would be loaded into a pool of visible chunk game objects. This pool should be sized based on view distance, and be able to load and unload ChunkData as needed.

This will probably require a significant rewrite of the chunk loading code as nearly all of it depends on an array of chunk objects that grows over time.

Hitting Triangle/Vertice Limit in Mesh

It appears that there is a limit on the number of vertices or triangles that
can exist within a given mesh. This seems to only appear when a large enough
cave is generated within a chunk, causing extra vertices that need to be
drawn. Once the maximum value is reached, the rest of the mesh is not drawn
leaving blank spots at the top of the chunk.

Research needs to be done on if there is a way to either not draw caves that
the player cannot see, or if there is a way to expand the number of vertices
that can be placed within a given mesh. another option would be to use smaller
chunks and perhaps stack them on the y axis, though this would require a huge
rewrite.

Thread off chunk loading

Currently loading chunks in the background causes notable lag, this work is quite parallelizable and should be threaded off.

Some Options:

https://docs.microsoft.com/en-us/dotnet/api/system.componentmodel.backgroundworker?redirectedfrom=MSDN&view=netcore-3.1