Hello,
I understand VR is calculating every 5 minutes, but updates positions every ten minutes. So if i understand correctly:
At time T and position A, VR displays position A and will until T+10min
At time T+5min , VR calculate a new position Ab, based on wind at A for time T, and configuration of sails/hdg at T+5. But VR continues to display A
At time T+10min, VR calculates a new position B, based on wind at Ab for time T+5min, and configuration of sails/hdg at T+10. And VR now displays B after around 1min.
On VR dashboard, we see only A & B, and speed / position based on 10 min iterations, not 5.
What about Zezo? is it calculating for 10 min iterations (for the first hours at least), or 5 min ?
Thanks
Post by
lucarc | 2020-12-18 | 16:05:34
I don't really know about VR system, to me the position is calculated every minute by the game since every programmation can be done at any minute. It's true though that there are things that are not iterated every minute on the game though, as the sail or the wind speed, but to me it is every 10 minutes, not 5 minutes.
About zezo though, it's clear to me that it is iterated every 10 minutes. You can see it with the router when you have a turn to dmake which is near the ZEA. The router will try to give you a route with angles that do not match VMG so that you can turn at a round time (17:00 for example), while being the closest to ZEA as possible. However, the actual "best" road would be a TWA at the best VMG angle, and a turn at the minute you are the closest to the ZEA, which could actually be 17:03 rather than the 17:00 mentionned above.
I hope I'm correct, this post is only based on my experience of the game, I may actually be wrong on some points.
Post by
zezo | 2020-12-18 | 16:11:58
No. The game currently calculates the positions every 10 minutes. You can make a turn in the middle of the interval, and it will be accounted for.
I don't think the game engine accounts for wind changes within the 10 minute interval.
The router rounds down the time to the previous 10 minutes, so should correspond to the game reported position. And it's written in a way that the step always falls on 10 minutes.
The initial step is 10 minutes, then increases to 20-30-60 after 6/24/48 hours. That's the reason it can't give you precise gybe times/optimal angles. Let's say it wants to gybe exactly at the red line at TWA 150. 8 hours in the future the possible gybe point will be +/10 minutes of the optimum. So it will either gybe up to 20 minutes earlier, or sail at TWA 145 for a while to get closer to the line. Neither of those is optimal, that's where the human can do better.
4 Comments
User Login
