Third Person Character upon swipe left or right ignores object mesh collision and teleports into the object instead of hitting the static mesh

Development World Creation
, , , , , ,
1

Hello everyone, Jenna here, I have been having this issue I have been working on for the past few weeks and can’t seem to find a fix for this. Searched everywhere for my specific issue with no results. So here’s my issue:

I have an endless runner game, I used the virtus tutorial on YouTube to create the swipe function. Character will run on a straight lets call it road, and you can swipe left to make the player go to the left, and right for the character to go right. There are three points on the tiled road that the character will swipe into. Below I included the logic behind the swipe controls in screenshot #3 “New.png”. In screenshot #2 “aa.png” you will see the blue print for the tiled road. There are 3 spawn point arrows that the character will move into upon swipe.

The Third Person Character upon swipe left or right ignores object mesh collision and teleports into the object instead of hitting the static mesh. My current collision configurations can be seen in screenshot #1 “a.png”. Character needs to be able to upon swiping left and hitting the train needs stop at the train and keep running. The character right now is ignoring the trains collision and teleporting into the train then forced up on top of the train. I have tried to add an additional collision box around the train and the same thing is happening. I have also tried using different collision configurations for the train itself and I still can’t get the character from teleporting into the train. Ideally id like if the character swiped into the lane where the train is on, just hit the trains wall and keep on going straight, but it is teleporting into the lane which the train is sitting on so the character gets inside of the train and then forced up on top of the train a second later. Any help or if someone could point me in the right direction I would greatly appreciate it.

Thanks alot everyone,
Jenna

338499-new.jpg
338499-new.jpg1658×1966 577 KB

2

tl;dr: tick Sweep on the Set Actor Location node

The long story:

When we’re talking about pawns (especially characters!), we’re dealing with a root component which is usually a collision capsule and a movement component that shifts things around while handling that collision.

Normally, movement for a pawn / character using a movement component is applied with Add Movement Input / Add Vector Input nodes which allows the aforementioned components to spit out a graceful sliding collision result and prevents most interpenetration errors.

Now, by using Set Actor Location instead, you discard all that collision processing and force the actor’s location. This is not always a bad option, though as you may want to push a Ghost character into a wall…

Do tell whether Sweep works well enough. Otherwise it might be necessary to rewrite the way movement is applied -instead of Setting Actor Location you’d add a pertinent movement vector.