Facebook

Login

Support Sailonline

If you haven't already - join the SAILONLINE YACHT CLUB!

Please also consider making a donation - all amounts are greatly appreciated!

Board » Technical Discussion » When is my command executed?

warning: I'll explain how serverjumps, commands and the client refresh rate work, but it's complicated and I cannot tell you yet how to take advantage of this knowledge (when rounding a mark for example)

Most of you know about server jumps. For rounding a mark, it's important to turn as early as possible, but absolutely not too early. This is made difficult by the server jumps, and client refresh rate, you rarely see your boat where it actually is. What you see is running a couple of seconds behind, in rare cases it could reach up to about 45 seconds.

So what is exactly happening. It's more than just the server jumps and the client update rate, but let's start with them anyway:

The server continuously checks all boats. For every boat that has not been moved by the server for at least 10 seconds, the server updates its position. This means, your boat will move every 10-12 seconds (when it's busy, it may take 2 seconds before the server notices it hasn't moved your boat yet).

When you haven't issued a command in the last 15 minutes or so, the server may skip you once or twice, and then do one big jump to catch up. This unloads the server a bit from boats that aren't actively steered.

useful tip: send a command 5-10 minutes before rounding a mark (setting a delayed command for 5-10 minutes before the mark also works). It'll make sure the server jumps for your boat are short when you reach the mark.

For the rest of this post, let's assume server jumps of 11 seconds: your boat is moved by the server every 11 seconds. I'm also assuming you have a fast internet connection.

The client polls the server every 15 seconds (roughly). Let's see what can happen with an example:
12:00:00 (jump) server moves your boat
12:00:00 (poll) client polls boat position, you see your boat at its current position (barely any delay!)
12:00:11 (jump)
12:00:15 (poll) your boat moves from its 12:00:00 position to its 12:00:11 position (running 4 second behind)
12:00:22 (jump)
12:00:30 (poll) your boat moves from its 12:00:11 position (19 seconds behind) to its 12:00:22 position (8 seconds behind).
12:00:33 (jump)
12:00:44 (jump)
12:00:45 (poll) your boat moves from its 12:00:22 position (23 seconds behind) to its 12:00:44 position (1 second behind). Note: the 12:00:33 position is not shown, it looks like you made one large jump.

A better understanding of how this works may not easily transfer into being able to steer your boat better. One useful tip is: when you see your boat make a large jump, you know two server jumps happened in the last 15 seconds, meaning the last jump happened less then 4 seconds ago. If you see a short jump, you know only 1 server jump happened in the last 15 seconds, meaning the last jump happened between 4 and 11 seconds ago.

Commands are executed independently from serverjumps. What does this mean? You might have seen your command execute at the start of a new server jump, or at the end. Both can happen. A command will never execute in the middle of a serverjump. All commands due to be executed (of every boat, in every race) are executed in one go, with 4 or 5 seconds between each go. So your command will generally be executed within 5 seconds after the time you set the command for. BUT your boat may still be at a position from 11 seconds ago. This means, your command will have an effect 11 seconds earlier than it was set to execute.

So now there are three things with an interval: the client polls ever 15 seconds, the server moves boats every 11 seconds and turns boats every 4 or 5 seconds. This is complicated, I can't tell you yet how to take advantage of this knowledge.
Up to now I've done one of two things for markroundings:
- wait until the client shows me clear to round, then send the command.
- when I expect a double jump to happen until the next client refresh, and I only need one more jump, I count, to 10. But 11 is probably safer.

Now I've researched how commands work, I might come up with a method that results in better roundings, without the risk of missing the mark. That will be something I'll post on solfans
One advantage I take of your very informative explanation is: Don’t tack (gybe) too short for rounding a waypoint/buoy. To set a tack command in advance may have the effect to round too early. Seems to be better to wait for the visible pass by of the waypoint – then tack or gybe or set new course.
(Apologies for bad english).
This is why roundings are missed even though DC Checker shows the mark as clear. DC Checker assumes that the DC is going to fire exactly at that time with no uncertainty. That is not the case in reality.
Hi kroppyer

Thanks a lot for your explanation.

This post is quite ancient so, is it still true or had the situation changed ?

At the end, you speak about another post on solfans, I didn't find it.

Thanks
The server-side hasn't changed much in this regard as far as I know. But there's a whole new client by now, so that part of the story may have changed.

I have never written that post on solfans. I think partially because I didn't find easy and reliable ways to get a significant advantage from the knowledge.

By now, I think there is software that tries to sync up with the server jumps. I believe Kipper's AGL does this, and possibly even the HTML5 client. Which makes it easier, and more intuitive to work with the server jumps.

From what I recall, I had some thoughts that could help you navigate around a mark with the server jumps. If you are in sync with the server jumps, you basically have 10 seconds to decide when and how much you want to steer, and it should be fairly obvious when to turn and by how much. What matters a lot here is that you need to get luck with where you end up after each jump. For example: If you jump just short of the mark, you'll have to continue sailing in the same direction for another 11 second, even though you needed only 2 more seconds to reach the mark. Depending on the situation, you can reduce the effect of this by aiming a bit wider, so that when you're less than 10 second from the mark, you can already start part of your turn. Of course, beware of wind direction and performance loss. And finally, I recall that maybe I wanted to figure out and describe a somewhat reliable way to determine where you'd end up multiple jumps ahead so that you know whether you need to steer wider or not.

Please login to post a reply.

Races

Next Race: 00d 00h 00m


Current Races:

SSANZ Triple Series 2025 - Race 3

Welcome to the grand finale of this year's SSANZ Triple Series! The stage is set for the Lewmar 50, a thrilling 39nm challenge tracing the southern shores of the stunning Waiheke Island, pushing out to Tarahiki before the sprint back to Islington Bay. Expect fast legs, tactical battles, and no shortage of drama as our SOLers take on the waters in their Young 88s, lining up once again against the talented IRL members of the Young 88 Association. With the series on the line and everything still to fight for, it all comes down to this final race!
Race #1934
INFO by brainaid.de
Young 88 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
SSANZ - SYC
Race starts: Aug 29th 21:15 Registration will open soon
▶ Flash
GO TO RACE

Red Eye - Myth of Malham 2025

In 1947, Hugh McLean & Sons of Gourock, Scotland built a radical racing yacht for John Illingworth, soon-to-be Commodore of the RORC, to a design by Laurent Giles. With a masthead rig, giving her ‘free’ sail area per the rules of the time, and short overhangs reducing pitching, Myth of Malham went on to win The Fastnet that year and again in 1949, and to compete in numerous Admiral's Cups. In 1958, in honour of the yacht, the Myth of Malham race was conceived - a mini-Fastnet to the first lighthouse on a rock west of Cowes, Eddystone, rather than the second, to be held in non-Fastnet years. IRL this year it has been raced already, but this stops us not from “Red Eye” racing its online 230nm in Fareast 31Rs, leaving how to deal with the Isle of Wight open to your own discretion.
Race #1847
INFOby brainaid.de
Fareast 31R PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC - RED
Race starts: Aug 25th 12:00 Registration Open!
▶ Flash
GO TO RACE

Africa by Sea 2025 - Maputo to Mogadishu


The fifth leg of our exploration of Africa By Sea takes us north along the length of the Continent’s succulent sub-tropical and tropical Indian Ocean coast. Much fought over by traders and colonists both well-before and after a Portuguese expedition under the command of Vasco da Gama first sailed there from Europe back in the 16th century, it is yet to be properly explored as a yachting destination. With plenty of islands off- and inshore, small and very large, there is much to interrupt your 1900nm voyage and visit in your Swan 65, from Maputo to Mogadishu! Race #1858
INFOby brainaid.de
Swan 65 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC - ABS
Race starts: Aug 20th 17:00 Registration Closed
▶ Flash
GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member vida
  2. Sailonline Yacht Club Member WRmirekd
  3. Sailonline Yacht Club Member CriticalHippo
  4. Sailonline Yacht Club Member rafa
  5. Sailonline Yacht Club Member KaSToR
  6. Sailonline Yacht Club Member Kipper1258
  7. Sailonline Yacht Club Member Sax747
  8. Sailonline Yacht Club Member BRENTGRAY
  9. Sailonline Yacht Club Member FreyjaUSA
  10. Sailonline Yacht Club Member CollegeFund

View full list

Series

Mobile Client

SYC members have the benefit of access to our mobile/lightweight web client!

The mobile client