I haven’t solved this problem yet either but it IS a solved problem somewhere.
One thing I noticed about the engine is that it will put your pawn to a dead stop if you have the Sweep checkbox enabled in your ActorSetLocation (or similar) node in blueprint, and the place it’s trying to set the pawn’s location to will cause it to overlap a blocking collision shape. When that happens and it uses Sweep,
then it does this:
- trace back to the farthest it can go toward the target location without overlapping the blocking shape,
- set the actor’s location to THAT instead,
- Kill all the actor’s velocity in every direction.
Super annoying.
In C++ of the Character actor class or maybe it’s the Character Movement component, there is a function named something like SlideAlongWall which sounds a lot like what you want, but I haven’t dived into the C++ stuff yet. Thing is, I believe that function already happens every tick of movement on the character to help resolve just what you’re talking about, but if you’re not using a Character Pawn, OR if you’re using SetLocation nodes with Sweep enabled, it can dead-stop the pawn.