Zezo forum:

Post by toxcct | 2017-12-17 | 19:50:40

When on the lobby, I launch the VR Dashboard.
So far, almost all good except that the race name doesn't appear. Instead, it shows "Race #333".

When I click on the VOR thumbnail to open the race, indeed, VR Dashboard doesn't seem to recognize the race anymore, as it throws an error popup which says : Unsupported race #333.

And now, it does not open the router page anymore, obviously...

31 Comments

Post by zezo | 2017-12-17 | 20:00:33

Ooops. I removed the RORC race and renamed Clipper to "Sydney Hobart" (race parameters are also updated. Timeshift, finish and waypoint)

But left a stray comma on the last line which broke the json syntax.

Thanks for the notice.

Post by toxcct | 2017-12-17 | 20:08:48

Yay, fixed ;)

Post by toxcct | 2017-12-18 | 00:01:31

you meant in this (http://zezo.org/races.json) file ?

Post by zezo | 2017-12-18 | 00:03:43

Yes. It said

{ "id" : 329, "name" : "Sydney Hobart", "url": "clipper" },

for a while.

Check races2.json . That will be the new format.

Post by toxcct | 2017-12-18 | 00:07:48

Uhh, what is this new Id format ?

Post by zezo | 2017-12-18 | 00:13:23

Race.leg. Sydney Hobart is declared as Clipper leg, and there should be a separate Clipper leg at the same time. Also the last leg opened before the previous one was closed.

Post by Inicio | 2017-12-17 | 20:12:25

Thanks!
Without Zezo we are like orphaned children lost in the dark forest!

Post by zezo | 2017-12-17 | 20:14:37

I'm on the development version myself so did not spot it (it uses different config file with slightly different syntax to accommodate separate races with same ID)

Spoiler: It also has Rank and DTL columns, but they are weird because VR rank calculations are not done at every iteration. Still have not collected enogh data points to tell for sure what exactly happens server-side.

Post by Inicio | 2017-12-17 | 20:30:59

Great!

Post by Ursus Maritimus | 2017-12-17 | 20:46:56

if it is just in the table when sent by the server and else empty cells, that would already be great !

Post by zezo | 2017-12-17 | 21:08:55

It's asynchronous, so is stored and displayed at the next position update.

That works fine, but the numbers jump up and down as you can already see in the built-in game ranking.

Post by Ursus Maritimus | 2017-12-17 | 21:16:19

doesn't matter, it's more fyi ..

in the game interface, if you update the general ranking, right after VR Dashboard received an update, you have your position including the latest two minutes of movement. just before it, you are 0,75 nm behind everyone (at these winds)

curious to see where we end up. I think we are pretty well positioned towards the finish !

Post by Ursus Maritimus | 2017-12-17 | 22:14:39

they update the ranking in the top-left corner of the client, just after VR Dashboard received a server update. so it should be in the messages somewhere

Post by zezo | 2017-12-17 | 22:27:51

It's not "just after" it's 1 minute later, or possibly "at some random point of time, between 0 and 2 minutes later"

It looks like the total ranking is recalculated at some odd interval like 40 or 50 minutes and the displayed rank is based on some relative calculation in the meantime.

Post by Ursus Maritimus | 2017-12-17 | 22:54:51

than just add a line with timestamp, classification and dtl ?

Post by zezo | 2017-12-17 | 23:14:13

No need for separate line - it won't improve accuracy, just reduce the latency by few seconds. Wait for a day or two and you'll see what I mean.

Post by Ursus Maritimus | 2017-12-17 | 23:20:42

okay, trying to be patient ;)

the poistion in the ranking reported is increasing during a position update cycle and than drops when your gps position is updated by the server (every two minutes). maybe just wait for that drop in position and record that, along with the dtl. Than at least zezo position and dtl are consistent with eachother. That is primarily what we want.

The exact position in the ranking and dtl are less interesting. With the increase / decrease you can see wheather you are gaining / loosing compared to the leader.

Post by zezo | 2017-12-17 | 23:26:12

Try to make sense of this. Rank and DTL are updated simultaneously:

Time Rank DTL
21:20:23 UTC 223 5.59
21:18:17 UTC 223 5.59
21:16:13 UTC 239 5.59
21:14:09 UTC 239 5.59
21:12:05 UTC 239 5.59
21:09:58 UTC 239 5.59
21:07:54 UTC 239 5.59
21:05:49 UTC 239 5.59
21:03:43 UTC 188 5.59
21:01:38 UTC 188 5.59
20:59:34 UTC 188 5.59
20:57:29 UTC 188 5.59
20:55:27 UTC 188 5.59
20:53:21 UTC 224 5.61
20:51:16 UTC 192 5.64
20:49:13 UTC 189 5.66
20:47:06 UTC 190 5.67
20:45:01 UTC 191 5.7
20:42:58 UTC 189 5.71
20:40:54 UTC 189 5.6

Post by Ursus Maritimus | 2017-12-17 | 23:40:01

dtl seems to be quite ok.

it can go up and down as:
- wind conditions and the leader change differently from your own
- leader and/or you may have changed direction
- leader may have changed to a new leader in a completely different wind area
- angle to mark changes for both, especially when one of you and the leader is sailing at a large angle with it

position is allways an indication, but indeed varies a lot

could you request your position to the server, just like the client does? or is that an infringement of the TOC (in french) ?

Post by CaptKAOS | 2017-12-17 | 23:29:18

I�m playing VR exclusively on my Ipad, does the dashboard also work on that?

Post by zezo | 2017-12-17 | 23:39:15

Game does not run in a browser on mobile platforms.

And even if it did, I'm not sure if mobile Chrome supports extensions now. My iPad is two VOR editions old, still running iOS7 and I'm a bit behind in that area.

Technically, it's possible to write an app (MITM proxy) that pretends to be a VPN service and captures and decodes the game traffic, I also has to install fake certificates because the traffic is SSL-based.

There are similar general-purpose Android apps. Tried one of them and it displayed the protocol data. It also supports plugins so it's probably possible to extend it to do something with the captured data.

Post by Ursus Maritimus | 2017-12-17 | 23:42:59

I'd prefer you dedicate your scarce resources to improving desktop in stead of supporting and maintaining multiple platforms

Post by CaptKAOS | 2017-12-18 | 00:01:17

Thanks Cvetan for the explanation, guess I have to get back to me ol PC.
Cheers!

Post by mcmgj | 2017-12-17 | 23:47:54

Hi Cvetan, you haven't see the screen capture that i send to you ?
The rank is fine on it ... updated each 2 minutes with a correct value, when you enter in game, the rank is no good, due to cycle to move all boat is not finish.

time . . . . . . . . . . . . . .rank. . twa. . .delta_t autosail_left
17/12/2017 � 20:17:33 UTC . . . 902. . 129.8. .126. . .11h50m
17/12/2017 � 20:15:27 UTC . . . 903. . 129.8. .124. . .11h52m
17/12/2017 � 20:13:23 UTC . . . 904. . 129.8. .124. . .11h54m
17/12/2017 � 20:11:19 UTC . . . 904. . 129.8. .124. . .11h56m
17/12/2017 � 20:09:15 UTC . . . 904. . 129.8. .124. . .11h58m
17/12/2017 � 20:07:11 UTC . . . 905. . 129.8. .128. . .12h00m
17/12/2017 � 20:05:03 UTC . . . 905. . 129.8. .124. . .12h02m
17/12/2017 � 20:02:59 UTC . . . 905. . 129.8. .126. . .12h05m
17/12/2017 � 20:00:53 UTC . . . 905. . 129.8. .127. . .12h07m
17/12/2017 � 19:58:46 UTC . . . 906. . 129.8. .126. . .12h09m
17/12/2017 � 19:56:39 UTC . . . 911. . 129.8. .128. . .12h11m
17/12/2017 � 19:54:31 UTC . . . 912. . 129.8. .124. . .12h13m
17/12/2017 � 19:52:26 UTC . . . 913. . 129.8. .124. . .12h15m
17/12/2017 � 19:50:22 UTC . . . 913. . 129.8. .126. . .12h17m
17/12/2017 � 19:48:16 UTC . . . 915. . 129.8. .126. . .12h19m
17/12/2017 � 19:46:11 UTC . . . 916. . 129.8. .125. . .12h21m
17/12/2017 � 19:44:06 UTC . . . 920. . 129.8. . .5. . .12h23m synchro ?
17/12/2017 � 19:44:01 UTC . . . 920. . 129.8. .124. . .12h23m
17/12/2017 � 19:41:57 UTC . . . 921. . 129.8. .128. . .12h26m
17/12/2017 � 19:39:50 UTC . . . 921. . 129.8. .126. . .12h28m
17/12/2017 � 19:37:44 UTC . . . 925. . 129.8. .126. . .12h30m

Post by zezo | 2017-12-17 | 23:50:55

It's fine for a while and then jumps back 50 places.

In my code the log rank column is a copy-paste of the rank column from the other table.

Hint: Try clicking the ranking in the upper left corner and see what happens, both with numbers on-screen and in the log.

Right now it was around 175. Clicked the ranking and it went to 217.

Post by zezo | 2017-12-17 | 23:55:17

Then 174 with the next automated rank message. Click on the ranking again ... 174 again. Click once more - 209.

Post by mcmgj | 2017-12-18 | 00:02:11

yes, when you click rank, or other action, you obtain the "instant rank" somewhere in cycle...
all 2 minues (at the end of move boats cycle) the rank is updated ...

Post by Ursus Maritimus | 2017-12-18 | 00:11:52

correct, that is also my observation. every rank request is proably running a query to the server for actual gps positions and ranking. the one that comes with the update at VR Dashboard is also show in the top left corner of the client (normal sailing view). when you click for instant ranking, your position is usually a bit higher because postions of other boats have been updated at the server in those few seconds. dtl stays usually correct for a while, unless the position of the leader is updated shortly after yours.

I would say put it in as is, Cvetan

it provides all of us with more information. now I keep that manually in Excel ...

have a good night!

Post by Ursus Maritimus | 2017-12-18 | 00:14:41

when you click for an 'instant position' in the client, the position in VR Dashboard is updated in the header. But also that one is never really correct. it is a two minute cycle of updates of the 120.000 boats (1000 boats / second)

Post by zezo | 2017-12-18 | 09:40:51

It's weird. Like your DTF is compared with other players position +/1 one game iteration. But sometimes the DTL jumps around, sometimes it stays the same but the ranking varies, and sometimes it's more than one step (got a DTL of 0.02 for a while yesterday. It was more like 2.xx in reality)

That can be explained partly by comparison to incomplete iteration (DTL may be the same because leader has not moved, but boats behind it have moved, so the ranking is affected, or vice versa)