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:

Fernando de Noronha to Faroe 2025

The RWW Series concludes with a spectacular journey from Fernando de Noronha to the Faroe Islands, a legendary destination in the wild North Atlantic. Panning 4,100 nautical miles, this leg will be a true test of endurance, strategy, and sheer determination. Also the penultimate leg of the 2025 Ocean Championship, it’s your chance to prove your mettle against the sea, the wind, and yourself. We’ll be racing aboard the Ragamuffin 100, a vessel built for speed and challenge — demanding planning, precision and grit from every sailor on deck. Do you have what it takes to master the Northern Atlantic?.
PRIZE: SMPF
Race #1960
INFO by brainaid.de
Ragamuffin 100 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RWW - OCQ4 - OCCH - SUPSOL - SYC
Race starts: Nov 03rd 11:00 Registration Open!
▶ Flash
GO TO RACE

Mistli's Birthday BBQ Race 2025


Welcome to one of Sailonline's great traditions - the ofttimes slightly untimely celebration of SOLer Mistli's birthday on November 1, by way of a tricky race through the Stockholm Archipelago. To match the day that’s in it, this year correctly, we are providing you with a fleet of sleek 11 metre 1-designs (get it?) to slice through these (at least) 61.5nm of SLI-infested waters, and give you a fair chance that there will still be some beer left by the time you moor up by the jetty at Trosa!
Race #1947
INFO by brainaid.de
11m OD PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
Race starts: Nov 01st 14:00 Registration Open!
▶ Flash
GO TO RACE

ORCV Melbourne to Devonport Race 2025

Welcome to the legendary Rudder Cup, Australia’s oldest and most storied yacht race—sailed for over 110 years across the challenging Bass Strait from Melbourne to Tasmania. Organized by the Ocean Racing Club of Victoria, this 195nm classic tests sailors’ skill, strategy, and endurance against the unpredictable Southern Ocean. This year, our SOLers will be racing the timeless Swan 36, Nautor’s very first production yacht—a Sparkman & Stephens masterpiece renowned for her elegance, balance, and seaworthy performance. Get ready for a true ocean racing adventure!
Race #1951
INFO by brainaid.de
Swan 36 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
Race starts: Oct 31st 03:30 Registration Open!
▶ Flash
GO TO RACE

Sinbad by Balloon 2025 - Carnarvon to Dondra


From here, our home in Bharatavarṣa is now north west of us – said Sinbad to his fellow balloonists. Perhaps we can ride the wind first further north, and then catch the winds that every year bring the rain, perhaps not. It’s 2600nm and we could be aloft awhile, so, Master el-Quarters, victuals only, no sandbags, provisioning the giant hamper. It will be not a picnic!
Race #1886
INFOby brainaid.de
SOL Balloon PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC - SBB
Race starts: Oct 15th 11:00 Registration Closed
▶ Flash
GO TO RACE

Go to race archive

SYC Ranking

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

View full list

Series

Mobile Client

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

The mobile client