
Announcement
Collapse
No announcement yet.
There is something wrong with the MoveToLocation node in UE 4.13
Collapse
X
-
tatzel repliedHey guys, so I just upgraded to 13.1 which patch notes says it's fixed, but mine's still broken.
Leave a comment:
-
ImVawx repliedHey everybody,
Thanks for the feedback.
I was able to reproduce the issue on my end and have created a issue for it. You can follow it here:
https://issues.unrealengine.com/issue/UE-35852
Leave a comment:
-
Truong.Bui repliedThank you for your investigation, I'm not familiar with the engine source code so I think I will stay with version 4.12 till new updates come out.
Originally posted by iaanus View PostUnity 4.13 changed the functions MoveToActor and MoveToLocation by adding a call to UPathFollowingComponent::AbortMove in case the component is already moving.
Leave a comment:
-
iaanus repliedOriginally posted by Barnacle-Rus View PostSomeone should create a bug report on the AnswerHub...
Leave a comment:
-
Barnacle-Rus repliedSomeone should create a bug report on the AnswerHub...
Originally posted by iaanus View PostUnity 4.13
Leave a comment:
-
iaanus repliedSame problem here. From the C++ source code, Unity 4.13 changed the functions MoveToActor and MoveToLocation by adding a call to UPathFollowingComponent::AbortMove in case the component is already moving. Unfortunately, the change IMHO introduced a bug, since the call to AbortMove also resets the speed, a thing that didn't occur before. Since we are using a custom compiled version of the engine, we were able to fix the bug by telling AbortMove to keep the current speed. If you are not able to re-compile the engine, I guess you should wait for an hotfix.
Leave a comment:
-
Truong.Bui repliedOriginally posted by DrFrancky View PostSame here.
I use Move to location or Actor as a temp solution.
Leave a comment:
-
Truong.Bui repliedOriginally posted by andrzejBG View PostI have exactly same issue after upgrading to 4.13. Right now I couldn't solve it, so I stayed with 4.12 for a moment. I hope it's a bug, not a thing that got changed intentionally.
Leave a comment:
-
andrzejBG repliedI have exactly same issue after upgrading to 4.13. Right now I couldn't solve it, so I stayed with 4.12 for a moment. I hope it's a bug, not a thing that got changed intentionally.
Leave a comment:
-
There is something wrong with the MoveToLocation node in UE 4.13
Hi, I'm currently working on a Topdown game. I upgraded my project to 4.13 yesterday and found my character moved very weird.
This is my Character in version 4.12.5. It moves quite smoothly without any glitch
After upgraded to 4.13
As you can seen, It seem stopped moving when I clicked continuously. It is likely you use AIMoveTo task then call StopMovement node then AIMoveTo again. I think MoveToLocation in 4.13 changes Max Walk Speed value of CharacterMovement component but don't know how to fix that. Does anyone has the same problem?
This is my moving event in BP
Tags: None
Leave a comment: