Sail.x files

[Sharpy]

To Dom and others.
I have noticed that a saif.x file in VSF needs to have "dummy/empty" sails.x files
or VSF creates it's own version of them.
Odd thing but true on my machine.
So I just add two empty sailsl and sailsr .x files. And it works just fine.

Steve

EDIT: Moved from Vehicle Wish List

[Sailorjohn]

FWIW, some time back Ron mentioned Ilan had suggested use of a "string.x" instead of sail.x in VSF to have response to wind direction, without creating unwanted 'sail' side effects like flutter, chuter, AP function, autogeneration of sailf.x, etc. It was evidently created for gliders/sailplanes to animate the 'woolyworm' relative wind indicators...which we rag sailors also use. It supposedly has no effect on sounds or dynamics, and would work for flags, pennants, and other non-sailing uses. So far I have been unable to find 'string.x' in tutorials, or models. Anyone else see this, or know it's specific application rules?

[Sharpy]

Aloha SJ.
I have heard of the string also.

The ONLY thing I could find was
string - yaw string
It would be a named part inside the vehicle.x file.

Also I doubt that the string (If we could find it) would have a furled state which is of course one reason the sails are used for lights, launches (Sycara) etc. A non pivoting part.

That flutter and chutter is so annoying!

So much left to figure out with VSF.

[ron]

Hi, my question to Ilan was about the use of an instrument for the flag as 50 meters is the limit for instrument visibility?
Ilan suggested the use of a part such:
>>>>>>>>>>>>>
I have one part you can use, called "string" this part reacts with the wind much like a flag, can you use this part and see if it is ok ?
For example see this attached vehicle called "glider_old" the string is in front of the pilot.
<<<<<<<<<<<<<

Ron