Miguel Lemos

Sure. How about this: Right now, the game sends batches of vertices to the GPU. Those are of a known size. We could add a secondary vertex batch-sender, one that...

At the end of the day what I am saying is to send, along with the grid data, the objects seen by the player categorized by importance, distance, and complexity,...

About increasing the size of batches, you lose control. My solution adds tons of tweaking room.

But is can be done, what you say. I mean, using a single batch with different data in it would be cleaner. What you do with that extra data is...

So, yeah. Thinking it trough, one big batch, with a separate area for miscellaneous data.

Luckily it truly is not necessary for us mortals to know the insides of the engine. About the array, is it dynamic? I am going to go check right now.

This should be tested, but for now I have to say that even if TArray supports dynamic array size, the data structure used for the voxels, (Grid>Regions>FInt3 Array of Voxel...

Quick question to get you thinking: The faces for the bricks are hard-coded as 6. 5 is the top, 6 the bottom. 1,2,3,4 the sides. You see how you would...

Sounds great!

Hey finally finals season ended and now I am going to work on this for a while! I am looking at how minecraft implemented the solution for this problem. Have...