Line Trace for custom Object Type always false
If I do a line trace for a custom object type, the result is always false, even though it should have hit. As soon as I change back object type and the line trace object type to pawn, the result is true.
Expected: custom object types should also return true if the trace hits, just like the trace reacts to default object types.
Repro: Go to project settings, add a new collision object type (for this example: player) Add a pawn to the scene, change capsule component -> collision -> object type to "player" Do a line trace from the camera to that object, with object type array added "player" See that the result is false Now change pawn object type back to "pawn" Set line trace object type array also to "pawn" and do the line trace again See that the line trace returns true.
asked Aug 06 '15 at 06:01 AM in Bug Reports
I haven't heard back from you yet, so I'm resolving this for now. If you get the opportunity to build a small test project in which this same problem occurs, please upload it somewhere and get me a download link to check out. Thanks!
answered Aug 10 '15 at 08:49 PM
I had this same issue with a sphere trace. Rebooting the client fixed it. I think something wasn't saving with the project settings or something, not too sure. Fixed though...
answered Sep 24 '15 at 02:56 AM
I just wasted an hour of my time with this exact issue. Rebooting the client fixed it as well. Amazing. Thank you Cory.
For epic - The bug seems to happen when you:
Add a CapsuleTraceForObjects (example) to your BP, but you don't have a custom channel type yet. Go to project settings and add a new channel object type Go back to BP you can't select your new channel type yet. So Compile. Now select the custom object type.
Restarting the client fixes it.
answered Aug 13 '18 at 02:30 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here