Incorrect box collision on negatively scaled mesh

If you have a mesh with a rotated box in its simple collision primitives, that box won't be in the correct position if you scale the mesh by -1.

This issue was reported in 4.20 (CL-4212847) and reproduced in 4.19.2 (CL-4033788) and Main 4.21 (CL-4221482)

1. Download and open the attached project
2. Press Play or Simulate
3. Open up the console and type the command "pxvis collision"

Results: 'CollisionTestShape_ShapeB2's box primitives are in the wrong position - it's in the right location, but at the wrong rotation.

Expected: 'CollisionTestShape_ShapeB2's box primitives are in the right position

How does TextureRenderTarget2D get TArray<uint8> type data?

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

UMG RichText not appear image when packaged

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

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

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

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

What is the difference between Camera and CineCamera?

为什么我的电脑无法安装ue，错误代码一直是IS-IN-BV05,该如何解决

Why does UV setting float2(1,1) display incorrectly in the material's custom node?