Im playing around in top down sample, and i created a custom class “item” of an actor with a touchsphere and a static mesh. i left the collision of the static mesh on nocollision at all times.
now when i try to implement clickable events, i noticed that as long as “nocollision” on the touchsphere is active on the “item” blueprint, it does not register any click events.
as soon as i change that to “overlap pawn”, it does register clicks. so far so good. how comes ? is the mouseclick dependent upon the collision settings? i noticed that some tutorials recommended to put collision settings of a class that is to be clicked on “block all” so apparently there is some kind of dependency.
annoying thing: even though the mesh of the item as well as the touchsphere should ignore/overlap my character, as i have collision on overlappawn, for some reason the touchsphere now blocks the character ?!?! is this intended behavior, epic ?
i couldnt find any info on this !