180 degree bug and downwind track
Post by iconPost by Ormetkruper | 2020-12-19 | 11:59:38

Seems to be a 180-degree bug in the game when when using waypoints. It has happend to me twice now but I saw it soon before it made much damage. If you are sailing with waypoints and plan to add more later beware of the bug. If you are passing a waypoint when in the game when you plan more waypoints the first waypoint may not be erased when you pass it. So when the game updates it turns your boat 180 dergrees to that waypoint!

I do not know if it really do that but I did not wait and see. To much time to loose if so.

Not good if it did that. So to fix it you have to place the latest waypoint ahead of your track again or erase all and place them again.

Another thing if you follow your track is that after passing a waypoint it seems that it made the turn early and the track shows you have sailed true downwind for an hour or so. This maybe be a track rounding in the game but who knows. Not optimal to sail true downwind...

commenticon 10 Comments
Post by iconPost by tabasco2 | 2020-12-19 | 14:39:57
The same thing happened to me last night. The boat is pointing 180 degrees off course.
Post by iconPost by BooBill | 2020-12-19 | 15:33:18

Do not trust your eyes, trust your instruments.

Tips for waypoints.
1. Set them well in advance. 30 minutes or more. Same goes for adding or editing waypoints.
2. The visual representation of waypoints is generally pretty good.
3. Verify in Dashboard that the VR server has received your waypoints. The message you see in Dashboard is an intercepted message from the server back to your client that it has them.
4. Keep your hands off the controls and I know it's hard, but ignore what you see on the screen. Often the game client will get confused. Only intervene if it hasn't straighten out after a server refresh.
Post by iconPost by zezo | 2020-12-19 | 18:57:13
This happens when the boat passes a waypoint while you are fiddling with the waypoints in the client. The client does not know the waypoint is already passed and sends it back as a command to the server.

So avoid editing waypoints when the closest one is withint 10 or even 20 minutes. And as Bill says, there are another limitations (you can't place a waypoint within 15 minutes of current time), so better plan well in advance and better live with 1 minute error than mess the whole thing.
Post by iconPost by tabasco2 | 2020-12-19 | 20:30:26
Thank you Cvetan and BooBill.
Post by iconPost by MidnightFoiler | 2020-12-21 | 14:14:16
The limit is actually a distance - for some reason the number never sticks in my head but I think it is 2nm. So if it is very light winds in a slow boat it could be 45 mins - caught me out in one of those drifter races around the English Channel.

Easy to check the distance next time you set a wpt, put it just outside the circle that appears and then read the distance on the left.

Post by iconPost by carelbi | 2020-12-21 | 14:19:31
I am using an iPad. Zero is routing me back to cape of good hope rather than Cape Horn. How do I change it ?
Post by iconPost by turtle 1663 | 2020-12-22 | 08:58:14
Right click in the chart and select Cape Horn as destination, or a destination at your discretion
Post by iconPost by carelbi | 2020-12-22 | 14:15:03
Thanks for responding but I am using an iPad and a “right click” does not happen on an iPad. It is fine on a pc

Post by iconPost by Hardtack | 2020-12-22 | 15:14:33
If you're looking at the mobile version (m.zezo.org), bring the desired destination under the cross hairs, then select 'Set destination' from the menu.
Post by iconPost by MidnightFoiler | 2020-12-23 | 02:25:57
or on mobile version, select destination from the menu button - down the bottom of the menu under sail options etc.

I swear I posted that days ago but apparently I never submitted it.
Topics list
Copyright 2009 by ZEZO.ORG. All Rights Reserved.