Sydney to Auckland
Post by iconPost by LaBaltique | 2021-01-22 | 18:16:57


Is the Sydney-Auckland race going to be added?

Thanks a lot!

commenticon 27 Comments
Post by iconPost by zezo | 2021-01-22 | 18:19:07
It's added already. Please reload the dashboard/home page if you don't see it.
Post by iconPost by LaBaltique | 2021-01-22 | 18:37:12
Indeed! Thx
Post by iconPost by Erik VDM | 2021-01-24 | 09:59:25
Hi, I try to prepare a polar for Squid and have a problem using "Generating your own files" for the Class40 for the VR Sydney - Auckland: there is some conversion going wrong.
I get the message : TypeError : Cannot read property 'en' of undefined
Do you know where this comes from ?

Post by iconPost by lukla49 | 2021-01-24 | 10:41:38
Hi. I've got the same probleme on opera brosser. But it's still working with chrome. I wait also the answer
Post by iconPost by Hardtack | 2021-01-24 | 12:13:18
@Toxcct sail names changed from CamelCase to UPCASE a while ago. You may have inherited this bug from me :-)

@Erik, lukla, using the Class40 polars from the list of predefined polars works fine for me (blue triangle in the top right corner of the polars input field).

Post by iconPost by lukla49 | 2021-01-30 | 18:05:13
I have still the same error on Opera Browser when I select "generate your own files" and the boat in the list (class40 or other). But with Chrome, it's working well. Same problem after the reset of the application.
Post by iconPost by toxcct | 2021-01-30 | 21:22:48
I don't know why the caching issue still goes on, because the raw polars are supposed to be retrieved with a HTTP GET parameter that makes sure to use fresh data served from the server.

The raw polars served should be exactly this (the sails names are no more UPPERCASE, just like VR provides them from their servers) :
Post by iconPost by Hardtack | 2021-01-30 | 22:16:54
It's not a caching issue. VR sends polars sometimes with uppercase and sometimes with mixed case sail names.
Post by iconPost by toxcct | 2021-01-30 | 22:35:20
It's a caching issue in my generator, because all the raw polars are stored with the same format on my side (I manually retrieve them from VR occasionally, then save them in a JSON file).
So for my concern, the generator handles files with the right format, always.

But the thing is, I recently switched the generator code to use uppercased Sail Ids to CamelCased Id, just like I had the impression VR was sending them by now.
I also updated the Ids on all my stored JSON.

The cache issue seems now that even though my server can serve the right files, and even though the Ajax Get is made with a "cache:false" argument, the gemerator seems to have some difficulties to get fresh polars sometimes...

Post by iconPost by Hardtack | 2021-01-31 | 00:44:11
Okay, but how do you deal with polars retrieved with Dashboard and pasted?

Post by iconPost by toxcct | 2021-02-01 | 08:08:37
That's a risk.
Indeed, if users paste an unsupported format, the generator will shout out.
But normally, all the polars are already provided on the side list.
Post by iconPost by YourMomSA | 2021-01-30 | 22:11:21
Just zoomed in on the invisible gates... It looks like the West end of gate 2.3 might be a bit offshore, according to the dashboard map. Anyone know if that's true in the VR map too? There's a decent chance boats might be trying to cut that corner tight...
Post by iconPost by Ultimate Victory | 2021-01-31 | 18:08:29
This is a gate and not a mark, does it matter ?
Post by iconPost by YourMomSA | 2021-01-31 | 19:02:12
I think so, but i'm not 100% certain. There was a race a few months ago with a similar situation, and a few boats sailed close enough to the shoreline to miss the invisible gate... Their rankings and distance-to-finish started getting worse instead of better. It was a mess. So now when doing coastal races, I always check for that kind of thing.

But... the Google Earth map in Dashboard doesn't always correspond exactly to VR's in-game map. So it's possible that the gate is ok in VR's in-game map. The best way to check is for someone who's currently using waypoints to set one waypoint to maintain their current course, and then a second waypoint on that gate's west end's coordinates, and look to see if it's on land or water in the game's screen. If it's on land, then no worries. If it's in water, then it'll be a problem. I'm currently running on programmation, so I haven't checked it yet.
Post by iconPost by James | 2021-02-01 | 00:39:50
So if the gates are invisible, how can they be applicable in the game?
Post by iconPost by YourMomSA | 2021-02-01 | 02:07:21
As far as I know, their purpose is for measurement of rankings. When implemented properly, they should be harmless, because it should be impossible to sail the course defined by the visible buoys without validating all of the invisible gates. And... Usually, that's exactly how it is. Usually, both ends of each invisible gate are on continental land, making it impossible to avoid the gates. But VR occasionally makes mistakes like the one I mentioned from a few months ago and the one I'm concerned might exist for gate 2.3 in this event.
Post by iconPost by James | 2021-02-01 | 03:04:14
Well it's definitely not touching land on the dashboard map. Good eye.
Post by iconPost by YourMomSA | 2021-02-01 | 03:46:47
Paranoia is an asset in this game.
Post by iconPost by YourMomSA | 2021-02-03 | 04:49:42
Some good news... I dropped a waypoint on the coordinates of the west end of invisible gate 2.3. In-game, those coordinates are on land. So I don't think it's possible to miss that gate.
Post by iconPost by gavitellogolos0 | 2021-02-03 | 21:10:18
YourMomSA how do you spot the invisible gates?
Post by iconPost by YourMomSA | 2021-02-03 | 21:51:38
Dashboard's map.
Post by iconPost by gavitellogolos0 | 2021-02-03 | 21:52:26
Got it, thank you
Post by iconPost by lemulot79 | 2021-02-04 | 11:39:30
hello, what about checkpoint 1,2?
We will go north of the red.
Post by iconPost by Hardtack | 2021-02-04 | 12:15:06
It's in a checkpoint group with gate 1.1 which extends to Alaska. You only need to pass one gate of a group.
Post by iconPost by lemulot79 | 2021-02-04 | 15:17:27
Thank you
Post by iconPost by Luiz | 2021-02-05 | 14:12:00
Placing a decent course with this VR engine has been a nightmare with a 2-3 knot rounding wind like now. 10 minutes refresh allied with a line that does not reflect sail changes makes it virtually impossible to see beyond a few hours ahead. Sometimes not even that ... I miss the time that the game was WYSIWYG. Seriously considering skipping the Caribbean 600 (a race I like it) where in 24 hours we have different islands passes, tacks and sails changes. I don't want get annoyed (once more)...
Does anyone knows if have a hope to fix these bugs?
From what I saw in another post, Cvetan said that they occur even in the VIP subscription. Check?
Post by iconPost by YourMomSA | 2021-02-05 | 15:06:53
I don't think they see it as a problem, so I don't think it'll be viewed as a bug to fix. The thing is... The issue isn't about this being a tight coastal situation (although that certainly makes the issue harder to deal with, and it makes the light and shifty stuff unavoidable). The issue is just that the wind is shifting rapidly and the user interface deviates from the server when that occurs. The deviations are temporary and usually not dramatic, but... In cases like we're seeing right now approaching Auckland, they can be enormous for a while. It requires a lot of attention, and even when being attentive, it can be impossible to get it right.

On the other hand... In some ways, that isn't unrealistic. Real world races get very difficult in light and shifty conditions, and require a lot of attention to manage.

So... When questioning whether or not you want to enter a race, such as C600, I'd say... look at the forecast and base the decision on that. If you're seeing stable winds of decent strength, it should be fun as normal. If you're seeing light and shifty stuff and you don't want to deal with that, then skip the race. Same in real life, I guess... Plenty of people skip races when the forecast is light and shifty, or will start but later retire when the wind dies. That's ok. There's no point if it isn't fun.

On the other hand, if these conditions occur at a time when you can be attentive, you can look at them as opportunities. (It hasn't worked that way for me in Auckland... I've made mistake after mistake, and have had to ignore it through some tough parts that occurred while I was sleeping, and have learned that coastal stuff is difficult without full pack or VIP because you only get two waypoints at a time... But C600 is one of the few races I'm willing to lose sleep to do well in).

Topics list
Copyright 2009 by ZEZO.ORG. All Rights Reserved.