dang it. So I was building my 3rd person game from scratch. Followed everything to the T. What happend when I went to test it?
Well AWSD all acted like the same function. After about an hour checking and double checking I said fudge it. Closed it down opened the pre made 3rd person Blueprint and everything is the the same. I can't find a single difference. I actually believe this is the blue print he builds in the videos. And I know this because he set some stupid high jump and it is still present in the 3rd person blueprint. Anyway, I'll just go off the pre made like I had planned all a long. I really wish I could figure it out though. It's just not worth the frustration, because I'm sure later down the road I'll want to Hulk smash my PC.
I did learn some, so it wasn't all lost.
I already got the Speed and jump and stuff set the way I think I want it for now. Took All of 10 mins.
Welcome to the world of unskilled debugging!
I hate it when I get two identical looking things yet one is broken. I always end up removing feature after feature until it starts working again. Remove the fluff and hopefully find the bug, you know. What is really frustrating is when you get down to a SINGLE line of code left, which is 100% equal to the working version, and yet it still doesn't work. That's when you find out you've really screwed things up.
Web dev is more like that then game dev though. With this forum I have zero debugging tools and can't even print debug info easily.
With Unity and I imagine blueprint, you have tons of tools at your disposal to quickly narrow in on the problem. I'd highly recommend finding a tutorial on how to use them. It'll save you tons of time.