HLOD creator reports wrong SM in error

When generating proxy meshes, the HLOD fails in some cases (already reported elsewhere: seems to be when custom lightmaps or lightmaps in channel >1 are used).

the report looks like this:

LogStaticMesh: Building static mesh LOD_SM_Bookcase_London_C_H209…
LogMeshUtilities: Error: Raw mesh is corrupt for LOD0.
LogStaticMesh: Error: Failed to build static mesh. See previous line(s) for details.

The issue is that the reported mesh (SM_Bookcase. in this example) is not actually the one with the problem, it’s just the first one in the list. If there are many meshes in the HLOD, this can be quite a pain since you have to try one-by-one which mesh is the issue.

If more info is needed, let me know!


We’ve recently made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.