Creating an HLOD with a FallbackMesh that has a section with triangles=0 will incorrectly set the UVs of the StaticMesh

The UVs in HLOD's StaticMesh appear to be broken when there are sections with zero triangles in the fallback mesh. This is most likely the case for sections containing only small parts.

Workaround:

void FMeshMergeHelpers::ExtractSections(const UStaticMeshComponent* Component, int32 LODIndex, TArray<FSectionInfo>& OutSections)
{
	

// ...

	for (const FStaticMeshSection& MeshSection : StaticMesh->GetRenderData()->LODResources[LODIndex].Sections)
	{
		// Skip empty sections
		if (MeshSection.NumTriangles == 0)
		{
//			continue; // remove this continue
		}

1. Download the repro project (HLODTest) from addtional URL
2. Open the editor
3. Delete HLODs
4. Build HLODs

Result:

UVs of StaticMesh are incorrectly set (attached NG_HLOD0, NG_HLOD1)

Expected:

UVs of StaticMesh are set correctly (attached OK_HLOD0, OK_HLOD1)

Why does the REMOVE method of map container remove elements have memory leaks?

How does TextureRenderTarget2D get TArray<uint8> type data?

How do I set a material as a post-processing material?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

UMG RichText not appear image when packaged

How to delete some elements correctly when deleting an array loop?

What is the difference between Camera and CineCamera?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.