 |
| Let's get out there |
 |
| Crisis-meeting at the Tradewinds lighthouse |
 |
| Qyv and me testing, no land in sight |
The air was thick with frustrations. Some blamed the Lindens, some blamed the boatbuilder. Some blamed the landmasses in the area, and yet some blamed the wind system. Now, I dunno about the landmasses. It seems boats sail smoother, when there are less details to render on the horizon. However, SL allows us to adjust viewing distance, thus releaving the servers from the burden of rendering land.
 |
| Qyv and me testing, land in sight |
Tradewinds YC does not seem to create massive lag, but sure enough... the minute the system has to render stuff on the horizon, the viewer slows down, and all those planes aren't helping. Not a big surprise really. The boat then. Is the boat causing these problems? Hardly. Usually the Q2m sails like a dream. Sometimes we see eleven boats racing just fine. Here's a video of eleven Q2ms at the starting line.
The Q2m use the wwc wind system. That system is also used by the Shelly Fizz, the Flying Fizz, the Bolero II and the Cotton Blossom II. Why? Because it has features for creating interesting races. Wind, windshifts, waves and currents are all part of an exciting race. SRYC run regular races with the Shelly, the Fizz and the Q2m. Usually they have more than 8 boats. No problems at all. We've seen numerous Flying Fizz races with 8+ boats elsewhere. Here's a Fizz race at Tradewinds.
 |
| Another wwc boat |
The latest invention, the Q2.4mR comes with wwc too. Simply because it makes racing fun. The image shown above is from a beautiful area in the North Sea, but the scenery definately causes lag. As soon as I reached open water, the sailing was smooth, so no... I don't see any substantial evidence that the wwc is the major cause of these problems.
Minutes after the cancellation I was out there in a Flying Fizz. No problems at all. Then I sailed the Q2m with Qyv. All was good. I also sailed the Baby Sloop out there. Again no probs. Finally I took a Demo Nemo (3) out there, and it kinda worked too, though the steering was slow and it sailed half submerged.
Minutes after the cancellation I was out there in a Flying Fizz. No problems at all. Then I sailed the Q2m with Qyv. All was good. I also sailed the Baby Sloop out there. Again no probs. Finally I took a Demo Nemo (3) out there, and it kinda worked too, though the steering was slow and it sailed half submerged.
There are lots of myths about lag and what causes lag. I think I'll start looking for facts.
Update1: One day later we saw great Flying Fizz races from BS-Travertine.
Update2: The WWC Windsetter does not continuously communicate with the boats.
Update2: The WWC Windsetter does not continuously communicate with the boats.
This is a very good article . I and many other skippers could not for the life us understand . The thinking behind the blaming of the boat . And the WWC setter.
ReplyDeleteThat morning I had arrived early and was testing a fizz engine on the course with no problems what soever .
There are some forty planes rezzed in Dex . This was completely discounted . What I did find amazing was how fast people posted it was WWc or Qs boat to blame as well as How ready availible and swiftly the bwind sloop offered up and was testing the course the minute the race was canceled.
Yet the QM2 that has the option of using the BWind was not.
Good for you Noodles for writing a Completely un bias report .
What we really need are better and more powerfull servers from the lindens.
ReplyDeleteBut that too is a catch 22.
Cause the moment they do we cram it full with more stuff.
Thanx... I too found it strange how the wwc windsystem was blamed. It's been working great for years now. Ronin, you can double the server power once a year. Bad coding will set you back way more than that.
ReplyDelete