Compare Collision Object Type is broken

Development World Creation
, , , ,
1

I do a Equal Collision Object type check with a branch, sometimes the equal check makes no sense. I have also made a print with get collision object type and that says it is the correct object type while compare Equal Enum says it is false. When it is false it does the print and checks again, it stays broken forever.

The object type can get changed before the check. This logic is done with lots of objects and in ca 1 of 50 it does this bug. The collision type is a custom type I added.

2

Hello ,

Could you provide the code/blueprint that reproduces this issue that you’re seeing? I’ll need to confirm that it’s the correct workflow before considering this as a bug, as well as reproduce it locally.

3

We haven’t heard from you in a while, . Are you still experiencing this issue? If so, can you provide the information mentioned in my previous comment? In the meantime, I’ll be marking this issue as resolved for tracking purposes.