I updated one of my projects to 4.14 and realized that now player can’t stand on a landscape normally and glides on it. Player also can’t change walking direction instantly. Instead of this, it collides with something like an invisible wall and slowly increases its speed after some time. I didn’t use any physics material in a landscape but looks like it’s a problem with a friction(maybe something wrong with a physics). I don’t know how to reproduce this situation (on the other projects landscape works well), so at least maybe something can tell me a workaround for this bug?
So in order to effectively assist you, we are going to need a way to reproduce this is a new blank project using minimal content. I would check to make sure your character blueprint is not using any sort of friction changes as well.
Let me know if you have further questions or need additional assistance.
Character blueprint are not using any sort of friction. Everything worked even in 4.14 preview, so I wonder why it happened.
I already tried to reproduce this error in a new project, but as I said, I don’t know what caused it. Maybe you can recommend me some kind a sort of debugging method to find the problem?
Hm… looks like it’s not only a landscape problem.
I have a pretty big level and I have such problem only on one part of the level(it has 2 big parts). Also the same bug exist even if character stands on a static mesh.
The more distance from origin is, the more visible this bug with physics. I started to change distance of player from origin and bug begins to be visible if I set X location to 3000000.0 cm. If I set it to 19000000.0 cm, I will get result like in example project from the link above. If I set it to 119000000.0 cm, then I can’t even move in certain directions at all and animations looks strange.
The size of the level you are mentioning is likely to give your floating point precision issues. You are expected to have similar issues even prior 4.14
Hmm… Looks like you’re right and this bug occurs only on specific hardware. I have a map with offset around 5600000 cm in my project since 4.11 and everything worked well even in 4.14 preview. Then I changed my PC and started to test my project in UE 4.14 release and I found this error. Now I tested my map in 4.12 on a new hardware and found the same bug. I wonder which component caused this error: GPU or CPU? This is really a bad bug and looks like I lost a lot of potential clients by sharing a demo with this error
