The problem with executing dead ends has returned… It doesn’t always follow the trajectory of the dead end as it was created, but starts by aiming for the perimeter wall… Can’t the programming for executing them, which was present in May, be restored? It was one of the few things that worked perfectly and didn’t need to be changed.
Hi there,
Could you please share a bit more detail about the behavior you’re seeing? This will help me better understand the issue and pass along clear feedback to our product team for review.
Same problem I reported a while ago, even opening a ticket… it basically starts by crashing into the perimeter wall instead of following the path I created for the dead end. The way it executes them has also changed since May. Before, it would position itself facing the dead end and then execute them… Now, first it stops diagonally to the dead end, then it rotates in the direction it needs to go, and when it starts, it swerves towards the perimeter wall and then tries to correct itself.
I suggest recording a short video that demonstrates the problem.
It’s a known problem that they haven’t fixed yet, or rather, they haven’t restored it to when it was working perfectly. There’s not much to understand. It does what it wants instead of simply following the path I created. If I tell it to go straight, it shouldn’t start by turning left and then straighten up again and go straight.