Material slot assignment incorrect after mesh reduction completely removes all triangles from a section

When mesh reduction results in a section becoming empty, the material slots are incorrectly assigned. e.g. if section 0 gets removed due to it having no triangles after reduction, then its material can get erroneously assigned to section 1 (the "new" first section).

In 5.0, we had a similar issue with Nanite, which was solved by permitting sections with zero triangles, and fixing up all the places in the rendering code which used to enforce that a section had a non-zero triangle count. It may be that this already works in 5.0, or a small tweak is all that's required in the mesh build process to allow zero-sized sections.

How does TextureRenderTarget2D get TArray<uint8> type data?

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

UMG RichText not appear image when packaged

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

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

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.

How to implement springarm components to scale according to mouse position in spawn?

How to assign a value to a member of UMG's UMaterialInterface pointer type in C++?

Why RevisionControl connect failed in Unreal5.4 but Unreal5.3 success