[Bug] Custom mesh component bounds give inaccurate values

[4.16.1] Using “Get Component Bounds” on a Custom mesh component gives unusual numbers for the Box extent output.
In my example image provided below, a custom mesh component is used to create a floor mesh for the Steam VRChaperone bounds. The four vertices of the bounds are

  • X=100.000 Y=100.000 Z=0.000
  • X=100.000 Y=-100.000 Z=0.000
  • X=-100.000 Y=-100.000 Z=0.000
  • X=-100.000 Y=100.000 Z=0.000

But the Custom mesh component get component bounds’s box extent returns as:

  • X=1048576.000 Y=1048576.000 Z=1048576.000

The steps to reproduce are:

  1. Create new actor blueprint
  2. Add a CustomMesh Component to the actor.
  3. Use Set Custom Mesh triangles to add geometry to the custom mesh (number of tri’s appear irrelevant to issue)
  4. Use ‘get component bounds’ to see extent of custom mesh.

Current result: Custom mesh bounds are displayed as X=1048576.000 Y=1048576.000 Z=1048576.000

Desired result: Custom mesh bounds should be accurate to the triangles of the mesh. (in this case it should display X=100, Y=100, Z=0)

Image below can reproduce the bug without requiring extra unnecessary nodes.

Hi m500,

Thank you for the report. I was able to reproduce this behavior so I’ve created JIRA UE-46170. Our developers will be investigating further.

-TJ