Capsule Collision doesn't transform correctly with scaled Splinemeshes

On the left I use a box collision object on the mesh being used as spline mesh, on the right I use a capsule - which scales but doesn’t move when the underlying splinemesh is being scaled.

91869-wonkycapsule.gif

1 Like

Hi bzxo,

  • Does this occur in a clean, blank project with no additional content or is it limited to one project?
  • What steps can I take to reproduce this error on my end?
  • Are you scaling the entire capsule or are you targeting a specific scale such as Half Height?
  • Is this limited to capsules?

Hey ,
I made a clean repro case which you can DL here; https://we.tl/FEHEH5ZgEw

Open the SplineMesh_CapsuleCol\splinemesh map, select the Blueprint with the cylinder splinemesh, and adjust the [x] value of the Vector2D scale variable under Default (remember to show collisions).

Boxes move and scale correctly, but all other types of collision objects (I’ve tested sphere, capsule and 26DOP) have issues.

Unfortunately, our firewall prevents me from opening that file. Do you have a trusted FTP service such as dropbox or google drive you can upload it to?

Sure; https://dl.dropboxusercontent.com/u/18110562/answerhub01.

I checked with the project you sent but I’m not seeing anything specifically wrong. What is the expected result and what specific error are you seeing that does not match the expected results?

Hi , I expect the collision objects to scale and move with the spline mesh (when adjusting the spline mesh scale using the variable I set up - not the blueprint object scale), but currently only the box does that. The rest of the objects scale, but don’t move.

92121-collisionslip.gif

In this gif I’m scaling between 0.5 and 2.0 in X (yellow box on the right), and I’ve put all the collision objects in the mesh so they’re flush with the side of the cylinder. But, only the box stays attached to the cylinder when it scales - the other object don’t. I’d expect all of them to follow along like the box does.

Here’s the BP, for reference;

I was able to reproduce this on my end and have entered a bug report, UE-31361, to be assessed by the development staff.