If the Pathway Offset feature is enabled for the path from the Docking Station, Yarbo can no longer calculate a path to Recharge and presents the WP5 error. I didn’t see any notes about using this feature on this pathway. Am I doing something wrong?
Does anyone else feel Yarbo really dropped the ball on the last updates with no info how to use new features? Very odd, as before they at least sent a email about new features.
Have you tried limiting the distances? I feel like this is one of those corner cases they didn’t account for. I understand why you’d want this (on the pathway entrance) but I could see why this would fail on the exit. The path line would have to stay within that green square to work (my assumption). Even then you’d likely end up with it driving off the side of the dock. I’m sure the “fix” AKA workaround will be it won’t work for docking station pathways.
I haven’t tried the changing the distance yet. I had modified a bunch of things when recharging broke. It took me a couple hours of backtracking to figure it out.
I can also see how this feature could cause issues at the dock. I disagree that this is edge case though. I was expecting it would shift the end point which is one of the major turf wear point complaints.
It shifts the whole path is the issue. Like it moved the entire pathway X amount of feet to the left or right depending on the offset you chose and the start and end.
Yep. I figured that’s what was happening as well, shifts it out of the docking path hence the error.
Yeah (I think) start and end is the left and right where it will start and end the shift. It’s not start of the pathway to the end of the pathway as someone might think. In my limited playing with it, at least that is how it seems to work.
I was busy enabling it all my pathways and moving a couple so they had room for the shift. Then I couldn’t recharge. Frustrating. It would have been simple to disable the feature for that particular Pathway.
I love the change, they got 90% of the way there and fell apart on the final 10%. That’s a organizational issue they need to get fixed, and quickly.