I have created “Case # 00099009: MultiBoxTraceByChannel regression with custom trace channel”, however, since my recent experiences regarding the bug reporting policies were very negative, I’ll post it here for others to check. Basically, while trying to reproduce, I’ve found that custom collision traces are completely broken in 4.22 preview, I did not even come to the point to reproduce the trace “flickering” which I was talking about. These are the steps to reproduce:
- Create a blank BP project.
- In project settings, collision, create a custom trace channel (“TestChannel”) with default response “ignore”.
- Create a new BP class based on Actor. Add a sphere as root component. Add a box collision as child of this sphere.
- Configure the box collision aus follows:
collision presets - custom
Trace responses: Visibility - ignore, Camera - ignore, TestChannel - block - Place one of this BP Actor around Position 0,0,40
- Run frequent MultiBoxTraceByChannel, (e.g. in the attached project, it is in the level blueprint Tick), on this position, using TraceChannel “TestChannel”.
Print return value and/or enable debug drawing.
MultiBoxTraceByChannel does not return a blocking hit on 4.22
MultiBoxTraceByChannel returns a blocking hit on 4.21
Hopefully, some more QA will be done with regard to custom traces.