Sailonline.org - Online Sailing

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!

Tweets by @sailonline

Board » Technical Support » qtVlm thread

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

Posted by Zorba777 Posts 65 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 Posts 29 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 Posts 65 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 Posts 65 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 Posts 93 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 QTVLM_steps_for_SOLers_Dingo.doc (814.5 KB)
Posted by Dingo Posts 93 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 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 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 Posts 151 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 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 qtVlm_nmea_feed_window.png (302.9 KB) screenshot_qtVlm_nmae_main.png (969.5 KB)

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:

Susan Hood Trophy Race 2022

Lake Ontario Offshore Racing (LOOR) welcomes racers to the second virtual Susan Hood Trophy race. This is a 75nm weekender on western Lake Ontario starting and finishing at the Port Credit Yacht Club (PCYC) via Niagara and Burlington, and is one of two that will count towards special Sailonline's LOOR Series medals. As our Beneteau/First 36.7 managed the course so well last year, we shall race her again!
Race #1574
INFOby brainaid.de
First 36.7 PARTICULARS
NAM_AWIP WX Updates:
0245 / 0845 / 1445 / 2045
Ranking: SYC - LOOR
Race starts: Jun 03rd 23:45 Registration Open!

▶ Flash

GO TO RACE

Susac X2
Welcome to the beautiful calm waters of the Adriatic Sea for the virtual running of the Susac X2 race which is a real-life race organized by the JK Mornar Sailing Club based in Split, Croatia. Although we, unfortunately, aren’t running this magnificent race with the real fleet this year, we hope to make this possible in the coming editions. This amazing race is a total of 91 nautical miles which consists of rounding the beautiful island of Sušac. Our SOLers will be racing around these amazing waters in none other than our great Seascape 18s. Be sure to bring your binoculars for this one as with such beautiful surroundings you will definitely need them!
Race #1586
INFO by brainaid.de
Seascape 18 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
Race starts: May 27th 14:00 Registration Open!

▶ Flash

GO TO RACE

Vasco da Gama Ocean Race 2022

Point Yacht Club welcomes Sailonline to the 2022 running of the classic Vasco da Gama Ocean Race. This race is the oldest established international sailing event in South Africa and traditionally starts in the bay of Maputo, the old Portuguese colonial capital of Mozambique and finishes in Durban. Last year, and now again this year, the race was/will be from Durban to East London - circa 250nm in native Cape 31 speed machines.
Race #1573
INFO by brainaid.de
Cape 31 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
ARQ2 - ARCH - SUPSOL - SYC
RACE CLOSE: Sunday,
May 29 at 2300 UTC.
Race starts: May 22nd 08:00 Registration Closed

▶ Flash

GO TO RACE

San Francisco to New York 2022
Cornelius Vanderbilt, who made his money - that his descendants enjoyed to spend sailing and racing yachts - by recognizing that getting from the East Coast to the West Coast of the USA was best done by rail, would have been more than a little amused to see SOL organizing yacht races over the very route by water he made redundant. It's about 13,000 nautical miles, which compares with less than 3000 statute miles by train! Six years ago, the best SOLers managed to complete the passage from San Francisco to New York in around 36 days, sailing our much-used veteran ocean greyhound, the Super Maxi 100. Time to try again, this time on the VO70. If you aim for a SOG of 18kn, it'll only take you a month.
PRIZE: SMPF
Race #1567
INFO by brainaid.de
VO70_v4 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
OCQ2 - OCCH - SUPSOL - SYC
Race starts: May 01st 19:00 Registration Closed

▶ Flash

GO TO RACE

Go to race archive

SYC Ranking

View full list

Series

Mobile Client

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

The mobile client