This only occurs in the GreedyMesh chunk type. The applied material is rotated by 90 degrees on some faces. I have included a screenshot of both a Greedy Chunk and a Naive Chunk.

I haven't been able to locate the root cause of the issue but it appears that only a single chunk is able to have blocks added or removed from it, one coordinate from that chunk is: 24, 6, 24 for reference.

Every other chunk will simply appear to ignore any attempts at modifying the chunk data.

When switching the world generation type to 3D in my marching cubes world the outcome are multiple layers of a 2D-generated landscape (see attachment). What am I missing here?

Using Generate2DHeightMap instead of Generate3DHeightMap leads to strange terrain.

The Xpos/Ypos calculation should probably changed from:
const float Xpos = x * Position.X;
const float Ypos = y * Position.Y;
To:
const float Xpos = x + Position.X;
const float Ypos = y + Position.Y;

Hey @BLaZeKiLL Block removal and adding does not work with Naive chunks. Can you fix it?

The sln file is not here so pulling and testing it does not work since i cant open the solution? not sure if you did that on purpose or just forgot to upload that 2

Hi again,

Thank you for this repository. Can you do caves? The chunks are empty inside and only generates top area like hills, mountains.

Assets in the Content folder are not showing up in UE5.1.1

Here's an implementation I found working you can add to your tutorial:

• ChunkBase.h:
  
  (A blueprint-accessible array for materials, plus arrays for the material struct and vertices instead of single values)

• ChunkBase.cpp:
  
  (On clearing, empty the arrays then refresh using the total amount of materials, not blocks)

• NaiveChunk.cpp, in GenerateMesh():
  
  (Get the material for the current block's face, minus 2 to skip null and air enums, clamp as a safety, then pass it to CreateFace() )

• NaiveChunk.cpp, in CreateFace():
  
  (Switch all mesh structs and the vertex int to the new arrays)

• GreedyChunk.cpp, GenerateMesh():
  
  (Same as NaiveChunk, but using CurrentMask.Block for the face's material)

• ApplyMesh():
  
  (First clear all previous sections, then generate a new one for each material on the chunk)

Basically the same code as before, but generates one unique section for each different block material. Straightforward to scale-up (just add materials to the array) and supports both naive/greedy meshing. Maybe you had something in mind too of the like.

Using BP_MarchingBlocks and attempting to edit results in:
\UE5VoxelTutorial\Private\Voxel\Chunk\ChunkBase.h] [Line: 44] Pure virtual not implemented (AChunkBase::RemoveVoxelData)

Hello!
THANK YOU FOR YOUR TUTORIAL, it's really amazing.

I'm having an issue trying to implement the greedy meshing shown in your episode 4. I've copied completely identically the code shown in the video (not the one in the UE5 github), with the necessary modifications to use the noise plugin. There's no UE4 greedy example provided unfortunately!

It generates the chunk normally but crashes when the size is set beyond 16 or with multiple chunks being spawned, with an error "Array index out of bounds". It's always from ChunkGreedy.cpp, but the lines often changes (24, 36, 94, 143), usually corresponding to "if (Mask[N].Normal != 0) {" or "Mesh->CreateMeshSection". The array size also changes, ex. on the provided crash "4096 from an array of size 4096", sometimes 512, etc. Maybe related to how TArrays work in UE4 versus UE5?

Here's the crash and sources I'm using:
Crash.log
Private.zip
(Using UE 4.25 in a clean C++ project with nothing else)

It does greedy meshing exactly as expected otherwise.

I was setting up some UVs to do something other than terrain with the greedy mesh code and I noticed the Width and Height are reversed.
By changing Width -> Height and Height -> Width the UVs work as Expected.