I am developing an FPS shooter game. Everything was working perfectly for past few days but now suddenly the forward movement of character is not working properly. Left Right and Backward movement are working fine but only the forward movement is being restricted.
Please help me, I’ve been working on this project for a while and now this issue will ruin everything. Please help.
#5-0EA
Hi. You’re not giving much information. How can we help if we have little to no information of what you are doing and what is happening exactly?
Please provide more info.
1 Like
I was following this tutorial series as reference (https://youtube.com/playlist?list=PLL0cLF8gjBprG6487lxqSq-aEo6ZXLDLg). Everything was working good.
And the most important thing is I’m using Third Person Template in which movement of player is already defined. Suddenly, the movement of character is acting abnormally.
To be more specific, when I try to move forward, the character moves in such a way that it is being collided with something but when I crouch and move forward, then everything works fine.
And same thing is happening with the AI Character as well. AI character movement also freezes when it tries to move forward.
I don’t have any ideas how and from where this issue came. I checked all the blueprints and everything is fine.
Try activating the display of collision boxes when you run the game. Maybe there’s some hidden collision box blocking the way?
Type “show collision” in the command textbox.
I tried “show collision” but there is no collision boxes which are blocking the way.
And one more thing which I noticed today, I created another Blueprint Character and it was running smoothly.
Then I compared each and every value of the new character and existing character and everything was same.
I just ran into this same issue randomly. I was following a coursera class and took a break for a few days. I cant move forward and its like im hitting invisible collision. however I dont have any assets in the way.
EDIT: had to set collision complexity to simple on multiple mesh assets and finally got around this issue.
Server Correction!
Use Console Command: p.NetShowCorrections 1
Whenever the server corrects a movement it’ll display a Red Capsule and a Green capsule.
Red is characters Bad Location.
Green is the Correction applied.
Most likely there’s a movement speed conflict between client and server. Server is Authoritative.
The best thing you can do is follow these courses all the way thru, there are time’s where there is a node that needs to be connected to something later on in which some tend to forget to mention until later on. If your still having issues then the absolute best thing to do is back track, even if it seems like a really bad idea, you had to have tweaked one or two settings without realizing it, I’ve done it many times without thinking only to find that tweaking that single setting or finding a work around for that setting fixes it. Good luck