Spawn even if colliding flag

Development Programming & Scripting Blueprint
, , , , ,
1

Here is my original investigation
At the end of the thread I posted the files and line number to start tracing, and explain in above post why this flag is useless and should default to on for spawnActor node.(as of today the source code seems to be the same these months later.

Now, if Epic can fix this and make it more intuitive, when this flag is off, if there are any collision(with the exception like spectator pawn special case.), people would expect to have nothing spawned. To make it even better, there should be a boolean return to reflect there is a collision or not.

Thanks!

2

Hi PenguinTD,

This is an issue that we are already tracking internally (UE-3772). Unfortunately, we do not have it corrected yet. I have added some information to the ticket to reflect this post as well as the forum thread that you linked.

3

Any word on this 4 years later?