I think it’s important to note that this blueprint was working just fine earlier today without any modifications. I’ve started over 3 times now and so far I’ve always come back to this error after some time passes as if the engine suddenly decided “nope, I don’t feel like running smoothly anymore,” but I digress.
Dear community, I’ve tried everything after searching this forum and it’s companion reddit community for a solution but no luck so far. Can you see anything in my blueprint that may be causing this error? Or have you encountered this before and solved it? How did you do it and what can I do to solve my own dilemma?
I’m beginning to think that this is a problem with the editor itself. I am on 4.22, I am going to try 4.21 and see if that solves the problem. But since I know software problems don’t fix themselves that easily I’m not holding my breath…
My problem is not within the blueprint. It had nothing to do with it. As I just discovered, UE4 does not like it when I place a player inside the realm of another object. For example, lets say I made a torus ring and increased its X,Y scale by 10000. It’s really big now. Then if I place my player in the center it will then throw this error. I don’t know why exactly. I guess UE4 doesn’t like it when a player is inside the boundaries of a blueprint. Removing this boundary fixed my issue but not after ripping my hair out trying to find out what was wrong with my code.
Umm…this is likely due to collisions and your player character being deleted. Check the world outliner and see if your player character even exists when you place it in the middle of a torus. My guess is, the “torus” isn’t actually “hollow” when you look at the collision properties and placing a character inside basically means it is “stuck” and bugs out gets deleted then when you try and rotate the player character the “get player character” node returns a null value. And if that isn’t it, then you actually have a “pawn” class for the player “character” and not an actual “character” class. So get player character returns none. If this is the case, the solution is simple, just use the node “get player pawn” instead of “get player character” and everything will be fine
