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 Support » qtVlm thread

Page: First Previous 27 28 29 30 31 32 33 Next

Posted by
Zorba777


Users avatar

Posts
67
Registered at
2020-06-06 08:22:54
2020-10-02 08:55:45 - Re: qtVlm thread
Hi Satori. I liked your Rum Run report. Figuring out how to squeeze a little bit more out of QtVlm routing is part of the fun for some of us. I think you are on the right track with your experiments. I am still learning too, but some of the things I try are:
1) Using barriers is a good way to force the routing to go around a buoy, or to close off possible paths that lead nowhere (like dead end fjords) and thus made the routing faster.
2) Another way to optimize/simplify faster is by using the "Selection" tool (blue square icon) and only optimize/simplify on that selected part. Much faster, especially on multi-day routings.
3) Watching the isochrones unfold during a routing is important to spot tactical alternatives. I mark them with waypoints and then do separate routings from boat to those waypoints to see how much they differ in time and to see which routes are improving (or getting worse) on subsequent WX updates.
4) As you pointed out in your report, with tallship polars QtVlm can sometimes struggle with the polar hops. You can then see the isochrones behave strangely and may even fall apart completely. Then you have a very unreliable routing. In that case try to route again with longer steps.
5) Varying the step can also give you routes that optimize better. 30 minutes or even 1 hour steps will sometimes give you quicker routes that a routing with 5 minute steps didn't find. Experiment.
6) It's also important to verify. Your boat position after 4 or 5 hours should be very close to where your used routing indicates it should be. If not you may be on wrong polar or be using an out of date grib. Both have happened many times to me. Checking where my boat is helps me to spot those problems.
7) When the routing tackes/gybes a lot it is often useful to adjust the route manually, before simply/optimize. Reduce the number of tacks/gybes can give you a faster ETA.

Good luck.
Posted by
dtayls


Users avatar

Posts
30
Registered at
2014-06-23 03:34:16
2020-10-03 04:41:53 - Re: qtVlm thread
Interesting. I wasn't aware of the 'selection tool'. I'll have to give it a go.
Posted by
Zorba777


Users avatar

Posts
67
Registered at
2020-06-06 08:22:54
2020-10-26 15:07:51 - Re: qtVlm thread
@Satori Another great race report for the recent Hatteras Sprint. I have had a busy week, so here are my belated comments to some of the points you raise about Qt routing.

It's important to experiment with some settings and find what works for you. This may vary depending on the boat polar and on the type of race.
I always set my crank duration to 1 minute for max accuracy. Simplify/optimize the route will reduce the number of DCs anyway.

In the boat settings for "tacks and gybes" is where many SOLers probably use very different values. This is the part where Qt is the least accurate because the PL loss formula in SOL differs from what Qt does. I prefer to set both tacks and gybes to 97% of polar speed for only 1 crank. In reality, depending on the wind speeds, my PL penalty will be more than that. But I will take that into account when I clean up my route. With those settings I know it will tack and gybe more often than needed. I manually improve my route when it has lots of tacks, as was the case in first part of the race here.
I just tacked manually going on max VMG, and I didn't use the intermediate tack to try to limit PL. In this case the boat speed was mostly around 7 kts. My PL always recovered to 100% within 1 or 2 server updates. Then I don't believe you can gain much by going on a lower speed for 10-20 seconds. That's like giving yourself a 30% performance penalty for 1 or 2 server updates. That doesn't pay off.
At boat speeds of >12kts it becomes another matter.

Where the router was very helpful (and will usually beat sotp navigation) is in the curved passages we had just before and after Hatteras inlet. I believe that's where I gained some time on most of the other boats. This are the type of passages where you can let the wind steer your boat without getting any PL. That's what I did here. I kept switching between COG and TWA to turn my boat to the wanted COG directions.
At Cape Hatteras turn it was of course straightforward, no router needed. Being only 0.01 NM behind I knew there was a chance to win by taking a bit more risk.
What I do there is set a DC that will turn about 10-12 seconds after the Cape. But at the same time I am ready to turn my boat a little bit earlier with a direct command. In this case I probably pushed the command about 8 seconds before the DC would have fired, when I eyeballed my boat to be right at the corner. That put me on inside with a slightly better angle.

It is really small differences that decide this kind of races. You have to squeeze out every inch you can, because many others are doing the same.

For short races like this one I route with 5 minute step. In longer ocean races I usually do 15 or even 30 minute steps. But it is important to test and compare with other step sizes. In some case you get better results with longer steps. Testing = knowing.




Posted by
Zorba777


Users avatar

Posts
67
Registered at
2020-06-06 08:22:54
2020-10-28 10:01:56 - Re: qtVlm thread
@Satori On the topic of NMEA failing to connect. I have had it a few times, but not nearly as often as you report.
Up to know I have always fixed it by closing both AGL and qtVLM. Then first restart AGL and wait until it has properly connected. You can see when it has connected to server. Can take as much as 30 seconds.

Then I restart qtVLM and it always connects to NMEA very quickly.

One thing you may want to check. Click on the boat in top-right in qtVLM to open a bunch of tabs. There is a tab for NMEA and there you can change the "update interval". Mine is set to 3 seconds. You may test and see if other values solve your problems. May too often can cause a bottleneck. Or too infrequent may cause connection loss. Just try.
Posted by
Dingo


Users avatar

Posts
94
Registered at
2013-03-09 04:23:58
2020-12-10 09:59:40 - A QtVlm beginners tutorial
Attached is the gist of the email I sent to Satori who has indicated he will tidy it up and post it somewhere when he has the chance. Meanwhile, this might help get a few more SOLers into QtVlm and routing in a fairly simple way with instructions which follow the normal sequence of routing using QtVlm for SOLing.

I'll monitor for queries and suggestions and try to incorporate what I can into the tutorial as time permits.

Attachments
Posted by
Dingo


Users avatar

Posts
94
Registered at
2013-03-09 04:23:58
2020-12-10 11:08:45 - Re: qtVlm thread
One configuration setting which is useful to adjust is under the advanced tab. There you can adjust the amount of detail shown in coastlines. For more detailed routes near land it could be useful to raise the level of detail.
Posted by
RainbowChaser


Users avatar

Posts
2656
Registered at
2009-06-14 09:44:50
2020-12-18 17:56:44 - Re: qtVlm thread
Dingo - would you be happy for me to include that as a QtVLM Quick Guide under the Links tab?
Posted by
Henrys


Users avatar

Posts
4
Registered at
2010-03-07 13:33:35
2020-12-21 11:39:24 - Re: qtVlm thread
Hi Dingo or anyone for that matter. Question...How do you copy a Location from qt to enter into aGages Optimum Angles Tool to work out the best VMC?
Posted by
Jawz


Users avatar

Posts
154
Registered at
2009-07-21 09:51:19
2021-01-02 13:48:06 - Re: qtVlm thread
I have worked it out. The coords must be decimal and without the degrees symbols. Set this up in settings. Otherwise its the same almost. Alt and click then there is a box that opens up. Copy the coords into Agages tool and remove the symbols and off you go!
Posted by
Silvarius


Users avatar

Posts
3
Registered at
2020-05-09 13:50:09
2021-01-25 21:24:01 - Re: qtVlm thread
Hello,

I'm new to SOL and I am trying to connect the game to qtVlm ... with some difficulties :-)

I am using the brainaid proxy server to export NMEA data to qtVlm. The server is properly running and qtVlm receives now a NMEA feed (NMEA raw data window shows it).

The brainaid server receives data from a boat that is sailing in the "Shetland race 2021".

The problem is that nothing happens on the screen. The race WP are not shown, my boat is not positioned and all instrument are inactive.

Once qtVlm receives properly the NMEA feed, is there any other setting that is to be activated so that the feed can be processed concretly? Or maybe the feed itself doesn't contain the proper data?

Has anyone of you already had this kind of problem in the past?
Attachments

Page: First Previous 27 28 29 30 31 32 33 Next

Please login to post a reply.

Races

Next Race: 00d 00h 00m

Current Races:

Easter Island to Tristan da Cunha 2026

Welcome to the second leg of our RNW series, rounding Cape Horn. This middle-most leg Round the New World, from Easter Island to Tristan da Cunha, is also part of our Ocean Championship, and as such the second race of OCQ3 2026. This race, like the previous race in the RNW series, will be sailed in our revised 'version 2' Imoca 60 Foil. Race #2050
INFO by brainaid.de
Imoca 60 Foil v2 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ3 - RNW - OCCH - SYC
Race starts: Aug 03rd 11:00 Registration Open!
▶ Flash
GO TO RACE

Magical Mediterranean 2026 - Benghazi to Korcula

We return to Antiquity’s Middle Sea for a seventh celebration of all things Mediterranean - fickle winds, history and olive oil. This time we will sail from ancient Benghazi, whence once grain shipped continuously to feed Rome’s urban masses, to the medieval Venetian thalassocracy’s port of Korcula, birthplace of Marco Polo; 700nm in classy Club Swan 50s!
Race #1978
INFO by brainaid.de
Club Swan 50 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: MED - SYC
RACE CLOSE: Friday,
August 7 at 2300 UTC.
Race starts: Jul 27th 15:00 Registration Open!

▶ Flash
GO TO RACE

Red Eye 2026 - Georgian Bay

Welcome to the sensational scenic Georgian Bay of northern Lake Huron, the first area of the Great Lakes to be visited by Europeans in 1615, so former SOLer A2R informed us when he designed this geometrically tortuous course of 317nm criss-cross through its island maze. Originally known as Lake Manitoulin, in 1822 the bay was renamed after King George IV after his succession to the throne. This time we’ll take the very flashy Fareast 31R, which hopefully should keep you wide awake!
Race #2051
INFOby brainaid.de
Fareast 31R PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RED - SYC
RACE CLOSE: Monday,
August 3 at 2300 UTC.
Race starts: Jul 26th 08:00 Registration Open!
▶ Flash
GO TO RACE

Tall Ships 2026 - Stavanger to Aalborg


Welcome to the fourth of four virtual Tall Ships Races in European waters which are concurrently being organized in-real-life by Sail Training International . This fourth race is from Stavanger in Norway into the Skaggerak to a finish off Denmark’s Aalborg and perhaps an Aquavit to toast the adventure afterwards – a final circa 250nm in Sailonline’s classic Clipper 240.
NOTE: Starts and Finishes in tall ships racing are always offshore to avoid conflict with shipping and shipping lanes; online and real-life may not match exactly.
Race #1995
INFO by brainaid.de
Clipper 240 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: TSI - SUPBUD - SYC
Race starts: Jul 25th 16:00 Registration Closed
▶ Flash
GO TO RACE

Chinook Salmon - Canada to Andreanovs


A year after spawning in the upper reaches of the rivers of British Columbia, Chinook Salmon develop the age-old urge, so familiar to SOLers, to go to sea, heading for different parts of the northern Pacific Ocean. This race catches up with a particular school with an instinctive memory for the Andreanov Islands far west on the Aleutian Islands chain, as they depart the Salian Sea between Vancouver Island and the San Juans. It’s 2200nm and we’re taking the 60ft Trimaran, in the hope we can keep up!
Race #2048
INFOby brainaid.de
60ft Trimaran PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: MIG - SYC
Race starts: Jul 21st 11:00 Registration Closed
▶ Flash
GO TO RACE

Juventud TIMED Race 2026

Welcome to Isla de la Juventud (Isle of Youth), Cuba’s second largest island after mainland Cuba. Known as a haven for pirates, the island was the inspiration for novels “Treasure Island” and “Peter Pan”. The circa 120nm course runs clockwise around the island.
This is a TIMEDrace so you may RE-REGISTER HEREto try again after finishing a run. You will have two weeks to test your skill and decision making after the race opens.
Race #2049
INFOby brainaid.de
The boat for this race is the sporty Mini 6.5p Foil PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
TRQ3 - TRCH - SYC
RACE CLOSE: Saturday,
1 August at 23:00 UTC
Race starts: Jul 19th 12:00 Registration Open!
▶ Flash
GO TO RACE

Alaska to Easter Island 2026

Welcome to yet another all-new series. The initial leg of the RNW (Round the New World), Alaska to Easter Island, also part of our Ocean Championship. The first race of OCQ3 2026. This race will be sailed in our revised 'version 2' Imoca 60 Foil. Race #2042
INFO by brainaid.de
Imoca 60 Foil v2 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ3 - RNW - OCCH - SYC
RACE CLOSE: Saturday,
August 1 at 2300 UTC.
Race starts: Jul 06th 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 WRmirekd
  3. Sailonline Yacht Club Member CriticalHippo
  4. Sailonline Yacht Club Member cdhinman
  5. Sailonline Yacht Club Member Panpyc
  6. Sailonline Yacht Club Member rafa
  7. Sailonline Yacht Club Member rthinman
  8. Sailonline Yacht Club Member ms0689
  9. Sailonline Yacht Club Member Sax747
  10. Sailonline Yacht Club Member ita10267

View full list

Series

Mobile Client

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

The mobile client