Pawn rotating, Collisions not so much?

Hello there,

So, this took me almost a day to figure out and this is horrifying me.
But I really REALLY hope this is a mistake on my side.

It seems like rotating a pawn will not update it’s collision properly. In fact, it looks like the collision mesh will rotate using it’s own pivot point instead of rotating in relation to the static mesh
Though, the Show COLLISION command shows that everything is correct…

Weird huh? Just take a look at that

In this example I have a stick that has a long collision mesh. If I rotate the mesh upside down, i can avoid the blocks just fine. Because the collision’s pivot is at the same place as the static mesh.

But if I move the Collision to the end of the stick and rotate my Pawn so it avoids the obstacles, it will collide nonetheless.
Fun facts : This happen if I rotate the pawn in-game and also if I do it in the editor !

And the last test, rotating the pawn so it hits something. Well, it doesn’t !!

So, did I messed up editing my collision mesh ? Am I missing some kind of settings to tweaK? I’m not using any third party tool, only UE.

Hi ,

I haven’t been able to reproduce this on my end, what collision settings are you using on your static mesh and on the boxes you have it colliding with?

Which version of the editor are you currently using?

Hey ,

The box obstacle is the Shape_Cube from the starter pack, Collision Complexity is set to Default.

My pawn is using a StaticMesh that is also set to Default.
The pawn blueprint has no settings modified except for Collision presets set to BlockAll

4.6.1
I could upload the projet somewhere for you to check if you aren’t able to repro it on your side. But I don’t know much about file hosting websites.

Let’s recap my step to repro :

  1. Make a staticmesh from a BSP shape (pivot point in the center)

  2. Open the StaticMesh Editor

  3. Click on “Add Box Simplified Collision”

  4. Scale down a bit the newly created Collision box, then move it on the side of the StaticMesh

  5. Create a new Pawn Blueprint then add a StaticMesh component using the one created (Should be the Root)

  6. In the event graph add an Event Tick that fires an Add Actor World Offset (Delta Location : X:-2 Y:0 Z:0), so the pawn start moving when spawned. Check “Sweep” so the function detect collisions when moving

  7. Now place the BP in the world and make sure there is an obstacle in the trajectory of the Collision Box (the one created in step3) of the Pawn

  8. Test. It should collide as expected

  9. Now in the editor, rotate your pawn so the Collision Box would not collide with the Obstacles when moving.

  10. Notice that the Pawn still collide

Hi ,

If you could, upload it to a dedicated FTP server such as dropbox and put the link here I would be happy to take a look.

Hope this is working

To save space I didn’t include the StarterPack Content (600mo). You’ll need to copy it from another project :slight_smile:

Merry christmas !

Hi ,

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

Hi ,

We do not currently have a method for users to track bugs, this is something we are trying to find a proper way to implement in the future.

Hey ,

Alright then, glad to know it’s not only on my side.
Is there a chance to access your bug tracker so I can get an update of when it’s fixed?

@-
is there an update on this issue? i have a similar issue in my MovementComponent when i rotate it and don’t get collisions :frowning:

Hi,

This is currently under assessment by the development staff. Unfortunately I do not have a timeframe of when this will be fixed.

This does appear to be an engine bug, I have a fix for 4.8 that is being reviewed by some other engineers. Thanks for the test project, it helped track things down!

Sweet ! That will help my project :slight_smile:
Thanks

Fix has been submitted, CL 2505561.

Hi, I think I experience the bug mentioned here and now I’m not sure if it’s a new one or if the fix is just not in 4.9? It’s not a huge problem, if it’s fixed in 4.10 then everything is fine :slight_smile: So my question is just whether this should be fixed in 4.9.2 or not.

This fix was implemented back in 4.8. Is this still occurring for you? What steps are you taking to reproduce this on your end?

Hi everybody! we have the same bug in 4.22, we have a camera rotating around an object, we want the camera to clllide with object in order to not make it go through them, how could we solve this problem?

Hi,

I don’t think this is fixed in 4.22 and ever will to be honest.
The solution I applied, to workaround that technical limitation, was to calculate the destination location, operate a translation, detect if there are collision, then apply rotation.

I’ve to use this feature and would like to get an idea of what I’m about to encounter. Just checking to see if it is fixed as of 4.24/4.25?