Can't enter Box Collision with OverlapAllDynamic preset in UE4.8

After updating to 4.8, I can’t enter my Box Collision and because of that it won’t generate Overlap Events. The collision settings are set to OverlapAllDynamic. Before updating to 4.8 it worked just fine.

These are my Collision settings for the Box Collision:

Hi,

I think this is the same problem as I have. (Inconsistent collision responses from capsules - World Creation - Unreal Engine Forums)

I don’t have a solution to this but I found out that the same objects work in some levels. Very strange.

I hope this gets fixed soon, I want to pickup my weapons again and don’t want them to roll away from me :wink:

Regards, Joey

I have a similar issue as well, only in my case it neither collides nor generates an overlap event. It’s a relatively simple spherecomponent with overlap events that used to work fine in 4.7

Hi denneboomyo,

Does this only occur to the player character or are any other object able to trigger the overlap event? Additionally have you tried other collision configurations? As dj_joey stated, he has a similar error which I reported as UE-17121, however I’m not certain these two are directly related or if they are simply similar.

Try to uncheck “Auto weld” box in Physics of attached collision shape. In other case shape will have same behaviour as parent.

Hey,

thanks alot. This and setting “Can Character Step Up On” to “ECB Yes” in the collision settings for the parent (Car Static Mesh for me) made it work again.

Thank you!

EDIT:

Still some problems with this workaround. I guess you aren’t supposed to use Box Collision as a Trigger anymore in UE4.8 .

Hi denneboomyo,

As I stated previously, I think this is the same as dj_joey’s bug listed above, which I have reported as UE-17121. If you could, please take a look at his thread to see if it sounds similar to what you are experiencing.

Hey,

Yes, it’s exactly the same problem I have. Sorry for late answer, missed your first comment somehow.

Hi denneboomyo,

Not a problem at all. This is already in our system as UE-17121 and will be assessed by the development staff. Unfortunately, I don’t have a timeframe of when this will be addressed.