Announcement

Collapse
No announcement yet.

UE-35852 AI Move To Location zeros velocity each call NOT FIXED!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • replied
    Originally posted by ShadowGames-Dev View Post
    I am still getting this bug now in 4.15.1!
    Hi ShadowGames-Dev.

    The two tickets that we previously have both been tested and closed as resolved in the 4.13.1 and 4.14 releases.

    For the issue you are experiencing in 4.15.1, please follow the link in my signature to file a bug report for it.

    Thanks

    Leave a comment:


  • replied
    I am still getting this bug now in 4.15.1!

    Leave a comment:


  • replied
    still getting this bug in 4.14.2

    Leave a comment:


  • replied
    Del.

    UPD: After some testing everything works fine.
    Last edited by Barnacle-Rus; 11-11-2016, 07:39 AM.

    Leave a comment:


  • replied
    Hey R00dy,

    Could you please create a new thread for this in the Bug Reports section of the Answerhub?

    Thanks

    Leave a comment:


  • replied
    still getting this bug in 4.14 preview 3

    Leave a comment:


  • replied
    Originally posted by ostava View Post
    Thanks for the clarification Kyle. By "the next release" you probably mean 4.14, correct? It's just that I haven't really seen any new CLs in 4.13 branch since the 4.13.1 patch so it looks like there are no plans to release a new hotfix (hopefully I'm wrong with this as well).
    So the bug is still valid internally and is going back to the engineer. I cannot verify which engine version it will be in. I can only say that my best guess would probably be 4.14.

    Leave a comment:


  • replied
    Originally posted by Kyle Langley View Post
    Hey ostava,

    The internal version (which is what the engineers are using when they say they cannot reproduce) is not the same version you or others have. It's marked that way because the fix might of already been put in before the bug was written, which means the engineer responsible for fixing it doesn't see the issue. This is good news as there is a very good possibility the fix will be in the next engine release.
    Thanks for the clarification Kyle. By "the next release" you probably mean 4.14, correct? It's just that I haven't really seen any new CLs in 4.13 branch since the 4.13.1 patch so it looks like there are no plans to release a new hotfix (hopefully I'm wrong with this as well).

    Leave a comment:


  • replied
    Hey ostava,

    The internal version (which is what the engineers are using when they say they cannot reproduce) is not the same version you or others have. It's marked that way because the fix might of already been put in before the bug was written, which means the engineer responsible for fixing it doesn't see the issue. This is good news as there is a very good possibility the fix will be in the next engine release.
    Last edited by ImVawx; 10-10-2016, 12:11 PM.

    Leave a comment:


  • replied
    Originally posted by Kyle Langley View Post
    By the way, the issue has been marked as "Cannot Reproduce". I haven't had a chance to try it in 4.13.1 myself but if others still have an issue with this it would be good to let folks from Epic know.
    Last edited by ImVawx; 10-10-2016, 11:41 AM.

    Leave a comment:


  • replied
    The joys of having similar function names ;D Will look into using Move To Location

    Leave a comment:


  • replied
    Hello everybody,

    First, thank you for the feedback. Secondly, sorry for the confusion as what was fixed was for "Move to Location" Blueprint node and not the "AI MoveTo" node. However, I have submitted a new issue ticket for the AI MoveTo Blueprint node. You can view it here:

    https://issues.unrealengine.com/issue/UE-36812

    For now, the Move To Location Blueprint node should have the functionality to move to a position without the freeze.

    Leave a comment:


  • replied
    Thank you very much! Gonna try and write it in a C++ function since I have lots of calls to AI Move To; and if I remember correctly I was only able to call AI Move To in the main event graph (not BP functions) so I won't be able to wrap this in a BP function :/

    Really can't understand how this isn't fixed as it's such a key function

    Leave a comment:


  • replied
    Originally posted by AlexDiru View Post
    Cheers for the workaround, any chance you could screenshot your Blueprint of how you fix it?
    Click image for larger version

Name:	bp_setup_moveto_dirtyfix.png
Views:	1
Size:	215.1 KB
ID:	1116176


    The delay is just there to ensure we are not setting 0 all the time.
    Last edited by Burnz; 10-03-2016, 06:34 PM.

    Leave a comment:


  • replied
    Cheers for the workaround, any chance you could screenshot your Blueprint of how you fix it?

    Leave a comment:

Working...
X