Reply by marcelsterk | 2024-09-25 07:29:26
Images:
Reply by mighty_brute | 2024-09-25 07:35:03
<@454014247559495683> , here are some key points for you: a higher acceptance radius means the bot can accept a position outside of where it can actually stand. Additionally, you can adjust the character’s speed in the Floating Pawn Movement component.
Reply by marcelsterk | 2024-09-25 07:35:06
With some rational thinking, I concluded that our solution was better before. I don’t want to have the bot stand so close to it anyway. However, the bot continues to try to detect the location.
Reply by mighty_brute | 2024-09-25 07:36:29
For delayed responses, try changing the language to English and check if you are still experiencing the delay.
Reply by marcelsterk | 2024-09-25 07:37:14
We increased it to 500 before and get the same results. I can record another time for you to see
Reply by marcelsterk | 2024-09-25 07:37:30
https://www.dropbox.com/t/dgqU7f5LI92AqCql
Embedded Content:
Marcel Sterk sent you 1 item
Acceptence radius.mp4
Link: Transfer - Dropbox
Replying to mighty_brute’s Message
Reply by mighty_brute | 2024-09-25 07:36:29
For delayed responses, try changing the language to English and check if you are still experiencing the delay.
Reply by marcelsterk | 2024-09-25 07:37:55
That is incredibly interesting to hear. I never thought of it like that.
Replying to mighty_brute’s Message
Reply by mighty_brute | 2024-09-25 07:35:03
<@454014247559495683> , here are some key points for you: a higher acceptance radius means the bot can accept a position outside of where it can actually stand. Additionally, you can adjust the character’s speed in the Floating Pawn Movement component.
Reply by marcelsterk | 2024-09-25 07:39:04
So as you can see the acceptance radius was increased and the issue still remains.
Reply by marcelsterk | 2024-09-25 08:53:16
P.s. we also tried making an extra actor to function as the go to element. But then it does not recognize it.
Reply by marcelsterk | 2024-09-25 17:42:12
I solved the problem <@1216254232957685765>
Reply by marcelsterk | 2024-09-25 17:42:40
Wanted to let you know that by removing the move to action, the bot is no longer conflicted when we ask it to move somewhere.
Reply by k3kalinix | 2024-09-25 17:43:25
Thanks for sharing the details. <@454014247559495683>
FYI: <@&1163218672580575372>
Reply by marcelsterk | 2024-09-25 17:48:41
So a brief more clear summary:
We have set it up so that we ask the bot to go to a location instead of the object. This is because our machine’s component falls outside of the navmesh. In addition to sentences being cut off and strange bugs, as well as the bot constantly indicating that it couldn’t reach the object, I realized that the narrative design is essentially also communicating with the bot. So I thought if I remove the action, the bot won’t be prompted to respond to it either.
Reply by mighty_brute | 2024-09-27 13:09:07
<@454014247559495683> thanks for the info.
This conversation happened on the Convai Discord Server, so this post will be closed.