<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.silentwings.no/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ola</id>
	<title>Silent Wings Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.silentwings.no/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Ola"/>
	<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php/Special:Contributions/Ola"/>
	<updated>2026-06-03T22:54:47Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=UDP_Output&amp;diff=1859</id>
		<title>UDP Output</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=UDP_Output&amp;diff=1859"/>
		<updated>2011-07-16T11:12:38Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings 1.08. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Silent Wings can output various flight data to a configurable UDP socket. This can be useful for add-on developers and cockpit builders. Specifically, we support the Simmeters protocol for output of flight data to [http://www.simmeters.com Simmeters] instrument panels. In addition, we support the Condor format and our own binary format.&lt;br /&gt;
&lt;br /&gt;
The following options in the &amp;quot;options.dat&amp;quot; file control the UDP protocol settings.&lt;br /&gt;
&lt;br /&gt;
 use_output_udp      = true&lt;br /&gt;
 output_udp_protocol = simmeters&lt;br /&gt;
 output_udp_address  = localhost&lt;br /&gt;
 output_udp_port     = 6060&lt;br /&gt;
 output_udp_rate     = 30&lt;br /&gt;
&lt;br /&gt;
== Simmeters Protocol ==&lt;br /&gt;
&lt;br /&gt;
== Condor Protocol ==&lt;br /&gt;
&lt;br /&gt;
To enable it, use the option&lt;br /&gt;
&lt;br /&gt;
    output_udp_protocol = condor&lt;br /&gt;
&lt;br /&gt;
The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are (without the &amp;lt;&amp;gt; brackets):&lt;br /&gt;
&lt;br /&gt;
 time=&amp;lt;decimal hours&amp;gt;&lt;br /&gt;
 airspeed=&amp;lt;absolute airspeed&amp;gt;&lt;br /&gt;
 altitude=&amp;lt;altitude&amp;gt;&lt;br /&gt;
 vario=&amp;lt;variometer value [1]&amp;gt;&lt;br /&gt;
 evario=&amp;lt;variometer values [1]&amp;gt;&lt;br /&gt;
 nettovario=&amp;lt;netto vario&amp;gt;&lt;br /&gt;
 integrator=&amp;lt;integrated vario&amp;gt;&lt;br /&gt;
 compass=&amp;lt;compass heading&amp;gt;&lt;br /&gt;
 slipball=&amp;lt;ball angle (radians) [2]&amp;gt;&lt;br /&gt;
 turnrate=&amp;lt;rad/sec&amp;gt;&lt;br /&gt;
 yawstringangle=&amp;lt;radians&amp;gt;&lt;br /&gt;
 radiofrequency=&amp;lt;current comm frequency&amp;gt;&lt;br /&gt;
 yaw=&amp;lt;rotation about z axis, radians&amp;gt;&lt;br /&gt;
 pitch=&amp;lt;rotation about y axis, radians&amp;gt;&lt;br /&gt;
 bank=&amp;lt;rotation about x axis, radians&amp;gt;&lt;br /&gt;
 quaternionx=&amp;lt;quaternion representation of aircraft orientation, X component&amp;gt;&lt;br /&gt;
 quaterniony=&amp;lt;quaternion representation of aircraft orientation, Y component&amp;gt;&lt;br /&gt;
 quaternionz=&amp;lt;quaternion representation of aircraft orientation, Z component&amp;gt;&lt;br /&gt;
 quaternionw=&amp;lt;quaternion representation of aircraft orientation, W component&amp;gt;&lt;br /&gt;
 ax=&amp;lt;accelleration along X axis&amp;gt; &lt;br /&gt;
 ay=&amp;lt;accelleration along Y axis&amp;gt;&lt;br /&gt;
 az=&amp;lt;accelleration along Z axis&amp;gt;&lt;br /&gt;
 vx=&amp;lt;velocity along X axis (m/s)&amp;gt; &lt;br /&gt;
 vy=&amp;lt;velocity along Y axis (m/s)&amp;gt; &lt;br /&gt;
 vz=&amp;lt;velocity along Z axis (m/s)&amp;gt; &lt;br /&gt;
 rollrate=&amp;lt;radians/second around X axis&amp;gt;&lt;br /&gt;
 pitchrate=&amp;lt;radians/second around Y axis&amp;gt;&lt;br /&gt;
 yawrate=&amp;lt;radians/second around Z axis&amp;gt;&lt;br /&gt;
 gforce=&amp;lt;filtered g load&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note [1]: The first variometer value is filtered with a slow&lt;br /&gt;
filter to simulate a slower mechanical vario. The &amp;quot;evario&amp;quot; value&lt;br /&gt;
is the variometer value that is normally indicated in the&lt;br /&gt;
instrument panel.&lt;br /&gt;
&lt;br /&gt;
Note [2]: The slip ball  is calibrated to +/- 15 degrees in radians&lt;br /&gt;
&lt;br /&gt;
All coordinate values are given in aircraft body coordinates&lt;br /&gt;
which are defined as X forward, Y right and Z down.&lt;br /&gt;
&lt;br /&gt;
== Binary Protocol ==&lt;br /&gt;
&lt;br /&gt;
The binary protocol is the most compact, and gives the best precision, but can be harder to program and debug.&lt;br /&gt;
To enable it, use the option&lt;br /&gt;
&lt;br /&gt;
    output_udp_protocol = binary&lt;br /&gt;
&lt;br /&gt;
in the options.dat file.&lt;br /&gt;
&lt;br /&gt;
The binary protocol sends the following data:&lt;br /&gt;
&lt;br /&gt;
    unsigned int timestamp;          // Millisec  Timestamp&lt;br /&gt;
    double position_latitude;        // Degrees   Position latitude,&lt;br /&gt;
    double position_longitude;       // Degrees            longitude,&lt;br /&gt;
    float  altitude_msl;             // m         Altitude - relative to Sea-level&lt;br /&gt;
    float  altitude_ground;          // m         Altitude above gnd&lt;br /&gt;
    float  altitude_ground_45;       // m         gnd 45 degrees ahead (NOT IMPLEMENTED YET),&lt;br /&gt;
    float  altitude_ground_forward;  // m         gnd straight ahead (NOT IMPLEMENTED YET).&lt;br /&gt;
    float  roll;                     // Degrees&lt;br /&gt;
    float  pitch;                    // Degrees&lt;br /&gt;
    float  yaw;                      // Degrees&lt;br /&gt;
    float  d_roll                    // Deg/sec   Roll speed.&lt;br /&gt;
    float  d_pitch                   // Deg/sec   Pitch speed.&lt;br /&gt;
    float  d_yaw                     // Deg/sec   Yaw speed.&lt;br /&gt;
    float  vx                        // m/sec     Speed vector in body-axis&lt;br /&gt;
    float  vy &lt;br /&gt;
    float  vz                &lt;br /&gt;
    float  vx_wind                   // m/sec     Speed vector in body-axis, relative to wind&lt;br /&gt;
    float  vy_wind&lt;br /&gt;
    float  vz_wind &lt;br /&gt;
    float  v_eas                     // m/sec     Equivalent (indicated) air speed. &lt;br /&gt;
    float  ax                        // m/sec2    Acceleration vector in body axis&lt;br /&gt;
    float  ay&lt;br /&gt;
    float  az&lt;br /&gt;
    float  angle_of_attack;          // Degrees   Angle of attack&lt;br /&gt;
    float  angle_sideslip;           // Degrees   Sideslip angle&lt;br /&gt;
    float  vario                     // m/sec     TE-compensated variometer.&lt;br /&gt;
    float  heading                   // Degrees   Compass heading.&lt;br /&gt;
    float  rate_of_turn              // Deg/sec   Rate of turn.&lt;br /&gt;
    float  airpressure               // pascal    Local air pressure (at aircraft altitude).&lt;br /&gt;
    float  density                   // Air density at aircraft altitude.&lt;br /&gt;
    float  temperature               // Celcius   Air temperature at aircraft altitude.&lt;br /&gt;
&lt;br /&gt;
total size: 132 bytes&lt;br /&gt;
&lt;br /&gt;
[[Category:Interfaces]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1818</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1818"/>
		<updated>2009-09-15T10:39:12Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors that help financing such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.tif{/banner}&lt;br /&gt;
 {banner}silentwings.tif{/banner}&lt;br /&gt;
 {banner}youradhere.tif{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
The image format supported is currently TIFF (.tif, .tiff). Alpha channel (transparency) and LZW compression can be used. &lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between in the list of images, where you want the blank. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
* The banners do not contain web links. You cannot click them to open a web browser.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1814</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1814"/>
		<updated>2009-06-08T14:41:14Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors that help financing such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.jpg{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between in the list of images, where you want the blank. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
* The banners do not contain web links. You cannot click them to open a web browser.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1813</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1813"/>
		<updated>2009-06-08T14:40:15Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors that help financing such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.jpg{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between in the list of images, where you want the blank. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1812</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1812"/>
		<updated>2009-06-08T14:33:02Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors that help financing such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.jpg{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1811</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1811"/>
		<updated>2009-06-08T14:32:12Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.jpg{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1810</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1810"/>
		<updated>2009-06-08T14:31:23Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/image.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1809</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1809"/>
		<updated>2009-06-08T14:31:03Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. &lt;br /&gt;
&lt;br /&gt;
Several common image file formats are supported, including .jpg, .png and .gif. We recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background. You can also add some invisible border to the images if you want the banner to get some margin distance from the upper left screen edges.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1808</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1808"/>
		<updated>2009-06-08T14:29:32Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
* If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
* The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
* The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1807</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1807"/>
		<updated>2009-06-08T14:29:17Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
Hints:&lt;br /&gt;
- If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
- The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
- The banners are downloaded when a viewer starts up. So to re-load getbannerinfo.php, the viewer must be restarted.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1806</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1806"/>
		<updated>2009-06-08T14:28:07Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url (replace mytrackingserver.com with your own ;-) )&lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
&lt;br /&gt;
The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1805</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1805"/>
		<updated>2009-06-08T14:27:25Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url &lt;br /&gt;
 http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
&lt;br /&gt;
The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1804</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1804"/>
		<updated>2009-06-08T14:27:04Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. It must be reachable by any web browser with the url http://mytrackingserver.com/getbannerinfo.php&lt;br /&gt;
A simple example of what getbannerinfo.php should return in your web browser could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
The images must be placed so that they can be opened in any web browser, using the url &lt;br /&gt;
 http://mytrackingserver.com/image.png. &lt;br /&gt;
&lt;br /&gt;
You may also for example define a path in the banner tag, like this:&lt;br /&gt;
 {banner}banners/buynlarge.png{/banner}&lt;br /&gt;
where the url then becomes&lt;br /&gt;
 http://mytrackingserver.com/banners/image.png. &lt;br /&gt;
&lt;br /&gt;
If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
&lt;br /&gt;
The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1803</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1803"/>
		<updated>2009-06-08T14:22:58Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
If you are running a tracking event server, you have the possibility to show banner ads in the viewer. This has been implemented to help getting sponsors for such events. Currently, this only works with vPos-compatible servers.&lt;br /&gt;
&lt;br /&gt;
To set it up, you need to add an additional php query to your server, called&lt;br /&gt;
&lt;br /&gt;
 getbannerinfo.php&lt;br /&gt;
&lt;br /&gt;
It must return a list of banner ad files and a tag for how many seconds each ad should be shown. A simple example of getbannerinfo.php could look like this:&lt;br /&gt;
&lt;br /&gt;
 {banner}buynlarge.png{/banner}&lt;br /&gt;
 {banner}silentwings.png{/banner}&lt;br /&gt;
 {banner}youradhere.png{/banner}&lt;br /&gt;
 {time}10.5{/time}&lt;br /&gt;
&lt;br /&gt;
In this case, the viewer will show the banners in this order, in an ever-going loop. Each banner will be displayed for 10.5 seconds. Several common image file formats are supported, including .jpg, .png and .gif. We do recommend using .png files as these do not have any compression artifacts, and you can use the transparency function to make it blend with the background.&lt;br /&gt;
&lt;br /&gt;
If you want a pause without any banner, create a banner which is empty. It could be a one-pixel transparent .png file, for example. Put this empty image in between where you want it displayed. &lt;br /&gt;
&lt;br /&gt;
The banners are displayed in the upper left corner. If they are wider than 2/3 of the screen width, they will be scaled down to fit within the 2/3 screen width.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1802</id>
		<title>Tracking - Banner advertisements</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Tracking_-_Banner_advertisements&amp;diff=1802"/>
		<updated>2009-06-08T14:10:18Z</updated>

		<summary type="html">&lt;p&gt;Ola: New page: &amp;#039;&amp;#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&amp;#039;&amp;#039;      Category:Tracking&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;Note: This feature is implemented in Silent Wings Viewer 1.10. It will not work with earlier versions&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tracking]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Category:Tracking&amp;diff=1801</id>
		<title>Category:Tracking</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Category:Tracking&amp;diff=1801"/>
		<updated>2009-06-08T14:07:49Z</updated>

		<summary type="html">&lt;p&gt;Ola: New page: This category deals with on-line tracking using the Silent Wings Viewer&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This category deals with on-line tracking using the Silent Wings Viewer&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=1800</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=1800"/>
		<updated>2009-06-08T14:06:51Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;&#039;&#039;&#039;Silent Wings Wiki&#039;&#039;&#039;&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Welcome to the Silent Wings wiki pages! This is set up to be a resource for information on the&lt;br /&gt;
[http://www.silentwings.no Silent Wings] soaring simulator. &lt;br /&gt;
&lt;br /&gt;
Primarily the Wiki is intended for Add-on developers who want to create new content such as Aircraft and Scenery for Silent Wings, but any Silent Wings related content is acceptable.&lt;br /&gt;
&lt;br /&gt;
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Unfortunately, frequent spamming attacks has forced us to disable anonymous editing as well as open registration of new users. If you want to contribute to the Wiki, please send us an email to support at silentwings.no and we will create an account for you. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;August 2008:&#039;&#039;&#039; Wiki is back online after a switch to new server. We are aware that some images are missing. We&#039;ll try to fix it asap. Let us know if you notice anything else missing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;October 2008:&#039;&#039;&#039; Again, we have had vandals adding their various silly links to the wiki. Hopefully we&#039;ve removed it all now. &lt;br /&gt;
&lt;br /&gt;
== Categories ==&lt;br /&gt;
The following categories are currently available:&lt;br /&gt;
&lt;br /&gt;
* [[:Category:Scenery|Scenery]] Articles related to creating scenery for Silent Wings&lt;br /&gt;
* [[:Category:Aircraft|Aircraft]] Making add-on aircraft&lt;br /&gt;
* [[:Category:Server|Server]] Multiplayer server setup&lt;br /&gt;
* [[:Category:Hardware|Hardware]] Articles related to connecting various hardware to Silent Wings&lt;br /&gt;
* [[:Category:Interfaces|Interfaces]] Articles related to communicating with Silent Wings from other applications&lt;br /&gt;
* [[:Category:Tracking|Tracking]] Articles related to tracking using the Silent Wings Viewer&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Talk:Main_Page&amp;diff=1799</id>
		<title>Talk:Main Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Talk:Main_Page&amp;diff=1799"/>
		<updated>2009-01-16T09:15:45Z</updated>

		<summary type="html">&lt;p&gt;Ola: Protected &amp;quot;Talk:Main Page&amp;quot; [edit=sysop:move=sysop]&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=1707</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=1707"/>
		<updated>2008-10-13T09:52:48Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;&#039;&#039;&#039;Silent Wings Wiki&#039;&#039;&#039;&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Welcome to the Silent Wings wiki pages! This is set up to be a resource for information on the&lt;br /&gt;
[http://www.silentwings.no Silent Wings] soaring simulator. &lt;br /&gt;
&lt;br /&gt;
Primarily the Wiki is intended for Add-on developers who want to create new content such as Aircraft and Scenery for Silent Wings, but any Silent Wings related content is acceptable.&lt;br /&gt;
&lt;br /&gt;
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Unfortunately, frequent spamming attacks has forced us to disable anonymous editing as well as open registration of new users. If you want to contribute to the Wiki, please send us an email to support at silentwings.no and we will create an account for you. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;August 2008:&#039;&#039;&#039; Wiki is back online after a switch to new server. We are aware that some images are missing. We&#039;ll try to fix it asap. Let us know if you notice anything else missing.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;October 2008:&#039;&#039;&#039; Again, we have had vandals adding their various silly links to the wiki. Hopefully we&#039;ve removed it all now. &lt;br /&gt;
&lt;br /&gt;
== Categories ==&lt;br /&gt;
The following categories are currently available:&lt;br /&gt;
&lt;br /&gt;
* [[:Category:Scenery|Scenery]] Articles related to creating scenery for Silent Wings&lt;br /&gt;
* [[:Category:Aircraft|Aircraft]] Making add-on aircraft&lt;br /&gt;
* [[:Category:Server|Server]] Multiplayer server setup&lt;br /&gt;
* [[:Category:Hardware|Hardware]] Articles related to connecting various hardware to Silent Wings&lt;br /&gt;
* [[:Category:Interfaces|Interfaces]] Articles related to communicating with Silent Wings from other applications&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=261</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=261"/>
		<updated>2008-08-19T13:12:19Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** http://www.silentwings.no|Silent Wings home&lt;br /&gt;
** http://www.silentwings.no/phpbb2/|Silent Wings forum&lt;br /&gt;
** http://competition.silentwings.no|Silent Wings competition&lt;br /&gt;
** http://meta.wikimedia.org/wiki/Help:Contents|help&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=239</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=239"/>
		<updated>2007-09-05T11:40:54Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** http://www.silentwings.no|Silent Wings home&lt;br /&gt;
** http://www.silentwings.no/phpbb2/|Silent Wings forum&lt;br /&gt;
** http://addons.silentwings.no|Silent Wings addons&lt;br /&gt;
** http://competition.silentwings.no|Silent Wings competition&lt;br /&gt;
** http://meta.wikimedia.org/wiki/Help:Contents|help&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=238</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=238"/>
		<updated>2007-08-15T10:48:16Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. &lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 nmea_frequency = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The output frequency of the NMEA strings in Hz. It defaults to 1. Be aware that a high frequency requires a higher port speed (see below). &lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !w string ==&lt;br /&gt;
&lt;br /&gt;
The output in this string is equal to what is documented to be output by the Cambridge C302 flight computer. It is built up as follows:&lt;br /&gt;
&lt;br /&gt;
 !w,&amp;lt;1&amp;gt;,&amp;lt;2&amp;gt;,&amp;lt;3&amp;gt;,&amp;lt;4&amp;gt;,&amp;lt;5&amp;gt;,&amp;lt;6&amp;gt;,&amp;lt;7&amp;gt;,&amp;lt;8&amp;gt;,&amp;lt;9&amp;gt;,&amp;lt;10&amp;gt;,&amp;lt;11&amp;gt;,&amp;lt;12&amp;gt;,&amp;lt;13&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is represented with no decimals, also is unsigned, and is explained as follows&lt;br /&gt;
&lt;br /&gt;
 1  - Wind direction in degrees (no decimals)&lt;br /&gt;
 2  - Wind speed in tenths of meters per second&lt;br /&gt;
 3  - The time since the last wind calculation in seconds (always 1 in Silent Wings)&lt;br /&gt;
 4  - Component wind in 10ths of Meters per second + 500 (500=0, 495 = 0.5m/s tailwind)&lt;br /&gt;
 5  - True altitude in meters + 1000&lt;br /&gt;
 6  - Instrument QNH setting (normally 1013)&lt;br /&gt;
 7  - Airspeed in 100ths of meters per second&lt;br /&gt;
 8  - Vario in 10ths of knots + 200&lt;br /&gt;
 9  - Averager in 10ths of knots + 200&lt;br /&gt;
 10 - Relative vario (netto) in 10ths of knots + 200&lt;br /&gt;
 11 - Mcready-setting in 10ths of knots &lt;br /&gt;
 12 - Instrument ballast setting in capacity percents&lt;br /&gt;
 13 - Instrument bug setting in percent&lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
== COM Port redirection ==&lt;br /&gt;
&lt;br /&gt;
If you want to use the data sent on the com port on the same computer, you can redirect the com port, either in hardware or software. The Hardware way requires two com ports on the same computer connected with a null-modem cable. &lt;br /&gt;
&lt;br /&gt;
On windows you can use com0com to do this in software instead. It is a free software package found at http://com0com.sourceforge.net/ . On Linux there is a virtual serial port driver that can be found here: http://www.tibbo.com/vspdl.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=237</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=237"/>
		<updated>2007-08-15T10:47:32Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. The strings are written once a second (1 Hz) with this setting enabled.&lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 nmea_frequency = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The output frequency of the NMEA strings in Hz. It defaults to 1. Be aware that a high frequency requires a higher port speed (see below). &lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !w string ==&lt;br /&gt;
&lt;br /&gt;
The output in this string is equal to what is documented to be output by the Cambridge C302 flight computer. It is built up as follows:&lt;br /&gt;
&lt;br /&gt;
 !w,&amp;lt;1&amp;gt;,&amp;lt;2&amp;gt;,&amp;lt;3&amp;gt;,&amp;lt;4&amp;gt;,&amp;lt;5&amp;gt;,&amp;lt;6&amp;gt;,&amp;lt;7&amp;gt;,&amp;lt;8&amp;gt;,&amp;lt;9&amp;gt;,&amp;lt;10&amp;gt;,&amp;lt;11&amp;gt;,&amp;lt;12&amp;gt;,&amp;lt;13&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is represented with no decimals, also is unsigned, and is explained as follows&lt;br /&gt;
&lt;br /&gt;
 1  - Wind direction in degrees (no decimals)&lt;br /&gt;
 2  - Wind speed in tenths of meters per second&lt;br /&gt;
 3  - The time since the last wind calculation in seconds (always 1 in Silent Wings)&lt;br /&gt;
 4  - Component wind in 10ths of Meters per second + 500 (500=0, 495 = 0.5m/s tailwind)&lt;br /&gt;
 5  - True altitude in meters + 1000&lt;br /&gt;
 6  - Instrument QNH setting (normally 1013)&lt;br /&gt;
 7  - Airspeed in 100ths of meters per second&lt;br /&gt;
 8  - Vario in 10ths of knots + 200&lt;br /&gt;
 9  - Averager in 10ths of knots + 200&lt;br /&gt;
 10 - Relative vario (netto) in 10ths of knots + 200&lt;br /&gt;
 11 - Mcready-setting in 10ths of knots &lt;br /&gt;
 12 - Instrument ballast setting in capacity percents&lt;br /&gt;
 13 - Instrument bug setting in percent&lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
== COM Port redirection ==&lt;br /&gt;
&lt;br /&gt;
If you want to use the data sent on the com port on the same computer, you can redirect the com port, either in hardware or software. The Hardware way requires two com ports on the same computer connected with a null-modem cable. &lt;br /&gt;
&lt;br /&gt;
On windows you can use com0com to do this in software instead. It is a free software package found at http://com0com.sourceforge.net/ . On Linux there is a virtual serial port driver that can be found here: http://www.tibbo.com/vspdl.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=236</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=236"/>
		<updated>2007-08-15T10:25:38Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. The strings are written once a second (1 Hz) with this setting enabled.&lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 nmea_frequency = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The output frequency of the NMEA strings. It defaults to 1, and is not set by the GUI. If you need a diffrent frequency you can set this manually in the config file. Be aware that a high frequency requires a higher port speed (see below). &lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !w string ==&lt;br /&gt;
&lt;br /&gt;
The output in this string is equal to what is documented to be output by the Cambridge C302 flight computer. It is built up as follows:&lt;br /&gt;
&lt;br /&gt;
 !w,&amp;lt;1&amp;gt;,&amp;lt;2&amp;gt;,&amp;lt;3&amp;gt;,&amp;lt;4&amp;gt;,&amp;lt;5&amp;gt;,&amp;lt;6&amp;gt;,&amp;lt;7&amp;gt;,&amp;lt;8&amp;gt;,&amp;lt;9&amp;gt;,&amp;lt;10&amp;gt;,&amp;lt;11&amp;gt;,&amp;lt;12&amp;gt;,&amp;lt;13&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is represented with no decimals, also is unsigned, and is explained as follows&lt;br /&gt;
&lt;br /&gt;
 1  - Wind direction in degrees (no decimals)&lt;br /&gt;
 2  - Wind speed in tenths of meters per second&lt;br /&gt;
 3  - The time since the last wind calculation in seconds (always 1 in Silent Wings)&lt;br /&gt;
 4  - Component wind in 10ths of Meters per second + 500 (500=0, 495 = 0.5m/s tailwind)&lt;br /&gt;
 5  - True altitude in meters + 1000&lt;br /&gt;
 6  - Instrument QNH setting (normally 1013)&lt;br /&gt;
 7  - Airspeed in 100ths of meters per second&lt;br /&gt;
 8  - Vario in 10ths of knots + 200&lt;br /&gt;
 9  - Averager in 10ths of knots + 200&lt;br /&gt;
 10 - Relative vario (netto) in 10ths of knots + 200&lt;br /&gt;
 11 - Mcready-setting in 10ths of knots &lt;br /&gt;
 12 - Instrument ballast setting in capacity percents&lt;br /&gt;
 13 - Instrument bug setting in percent&lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
== COM Port redirection ==&lt;br /&gt;
&lt;br /&gt;
If you want to use the data sent on the com port on the same computer, you can redirect the com port, either in hardware or software. The Hardware way requires two com ports on the same computer connected with a null-modem cable. &lt;br /&gt;
&lt;br /&gt;
On windows you can use com0com to do this in software instead. It is a free software package found at http://com0com.sourceforge.net/ . On Linux there is a virtual serial port driver that can be found here: http://www.tibbo.com/vspdl.php&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=235</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=235"/>
		<updated>2007-08-15T10:13:25Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. The strings are written once a second (1 Hz) with this setting enabled.&lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 nmea_frequency = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The output frequency of the NMEA strings. It defaults to 1, and is not set by the GUI. If you need a diffrent frequency you can set this manually in the config file. Be aware that a high frequency requires a higher port speed (see below). &lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !w string ==&lt;br /&gt;
&lt;br /&gt;
The output in this string is equal to what is documented to be output by the Cambridge C302 flight computer. It is built up as follows:&lt;br /&gt;
&lt;br /&gt;
 !w,&amp;lt;1&amp;gt;,&amp;lt;2&amp;gt;,&amp;lt;3&amp;gt;,&amp;lt;4&amp;gt;,&amp;lt;5&amp;gt;,&amp;lt;6&amp;gt;,&amp;lt;7&amp;gt;,&amp;lt;8&amp;gt;,&amp;lt;9&amp;gt;,&amp;lt;10&amp;gt;,&amp;lt;11&amp;gt;,&amp;lt;12&amp;gt;,&amp;lt;13&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The data is represented with no decimals, also is unsigned, and is explained as follows&lt;br /&gt;
&lt;br /&gt;
 1  - Wind direction in degrees (no decimals)&lt;br /&gt;
 2  - Wind speed in tenths of meters per second&lt;br /&gt;
 3  - The time since the last wind calculation in seconds (always 1 in Silent Wings)&lt;br /&gt;
 4  - Component wind in 10ths of Meters per second + 500 (500=0, 495 = 0.5m/s tailwind)&lt;br /&gt;
 5  - True altitude in meters + 1000&lt;br /&gt;
 6  - Instrument QNH setting (normally 1013)&lt;br /&gt;
 7  - Airspeed in 100ths of meters per second&lt;br /&gt;
 8  - Vario in 10ths of knots + 200&lt;br /&gt;
 9  - Averager in 10ths of knots + 200&lt;br /&gt;
 10 - Relative vario (netto) in 10ths of knots + 200&lt;br /&gt;
 11 - Mcready-setting in 10ths of knots &lt;br /&gt;
 12 - Instrument ballast setting in capacity percents&lt;br /&gt;
 13 - Instrument bug setting in percent&lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=234</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=234"/>
		<updated>2007-08-15T10:06:37Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. The strings are written once a second (1 Hz) with this setting enabled.&lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 nmea_frequency = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The output frequency of the NMEA strings. It defaults to 1, and is not set by the GUI. If you need a diffrent frequency you can set this manually in the config file. Be aware that a high frequency requires a higher port speed (see below). &lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=MediaWiki:Nosuchuser&amp;diff=227</id>
		<title>MediaWiki:Nosuchuser</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=MediaWiki:Nosuchuser&amp;diff=227"/>
		<updated>2007-05-22T15:23:32Z</updated>

		<summary type="html">&lt;p&gt;Ola: New page: There is no user by the name &amp;quot;$1&amp;quot;. Check your spelling, or create a new account by sending an email request to support at silentwings.no.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There is no user by the name &amp;quot;$1&amp;quot;. Check your spelling, or create a new account by sending an email request to support at silentwings.no.&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=226</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=226"/>
		<updated>2007-05-22T15:20:04Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;&#039;&#039;&#039;Silent Wings Wiki&#039;&#039;&#039;&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Welcome to the Silent Wings wiki pages! This is set up to be a resource for information on the&lt;br /&gt;
[http://www.silentwings.no Silent Wings] soaring simulator. &lt;br /&gt;
&lt;br /&gt;
Primarily the Wiki is intended for Add-on developers who want to create new content such as Aircraft and Scenery for Silent Wings, but any Silent Wings related content is acceptable.&lt;br /&gt;
&lt;br /&gt;
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Unfortunately, frequent spamming attacks has forced us to disable anonymous editing as well as open registration of new users. If you want to contribute to the Wiki, please send us an email to support at silentwings.no and we will create an account for you. &lt;br /&gt;
&lt;br /&gt;
== Categories ==&lt;br /&gt;
The following categories are currently available:&lt;br /&gt;
&lt;br /&gt;
* [[:Category:Scenery|Scenery]] Articles related to creating scenery for Silent Wings&lt;br /&gt;
* [[:Category:Aircraft|Aircraft]] Making add-on aircraft&lt;br /&gt;
* [[:Category:Server|Server]] Multiplayer server setup&lt;br /&gt;
* [[:Category:Hardware|Hardware]] Articles related to connecting various hardware to Silent Wings&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=154</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=154"/>
		<updated>2007-03-21T11:07:55Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** http://www.silentwings.no|Silent Wings home&lt;br /&gt;
** http://www.silentwings.no/phpbb2/|Silent Wings forum&lt;br /&gt;
** http://addons.silentwings.no|Silent Wings addons&lt;br /&gt;
** http://meta.wikimedia.org/wiki/Help:Contents|help&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=153</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=MediaWiki:Sidebar&amp;diff=153"/>
		<updated>2007-03-21T11:07:21Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* navigation&lt;br /&gt;
** mainpage|mainpage&lt;br /&gt;
** http://www.silentwings.no|Silent Wings home&lt;br /&gt;
** http://www.silentwings.no/phpbb2/|User forum&lt;br /&gt;
** http://addons.silentwings.no|Silent Wings addons&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** http://meta.wikimedia.org/wiki/Help:Contents|help&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Xf2sw&amp;diff=152</id>
		<title>Xf2sw</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Xf2sw&amp;diff=152"/>
		<updated>2007-03-19T10:05:28Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;xf2sw is a small perl script that will convert your polars generated with X-Foil to a .polar file readable by Silent Wings.&lt;br /&gt;
&lt;br /&gt;
You can download it in the software section at the [http://addons.silentwings.no Silent Wings addons website].&lt;br /&gt;
&lt;br /&gt;
The tarball contains a sample set of x-foil generated polars to demonstrate how it is done.&lt;br /&gt;
&lt;br /&gt;
- Start X-Foil, load the airfoil geometry&lt;br /&gt;
- Set a Reynolds number suited for the speed you want to use the airfoil in, or maybe use a variable Reynolds number coupled with CL? (this might give you a more realistic aircraft l/d polar)&lt;br /&gt;
- Calculate a polar and output it to a file&lt;br /&gt;
- Modify the airfoil geometry to a new flap setting&lt;br /&gt;
- Calculate a polar to another file&lt;br /&gt;
- continue until you&#039;re done&lt;br /&gt;
&lt;br /&gt;
For a proper set of airfoils it&#039;s recommended to have at least 2 rudder deflections in both direction around zero deflections (that&#039;s 5 polars in total). &lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft Physics]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=119</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=119"/>
		<updated>2007-03-06T12:59:59Z</updated>

		<summary type="html">&lt;p&gt;Ola: Reverted edits by Ola (Talk); changed back to last version by 129.240.228.21&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=118</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=118"/>
		<updated>2007-03-06T12:47:29Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
  \S_N &amp;amp;= S\\&lt;br /&gt;
&amp;lt;/math&amp;gt;&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
  \S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=117</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=117"/>
		<updated>2007-03-06T12:47:13Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
  \S_N &amp;amp;= S\\&lt;br /&gt;
  \S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=116</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=116"/>
		<updated>2007-03-06T12:46:46Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=115</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=115"/>
		<updated>2007-03-06T12:46:15Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=114</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=114"/>
		<updated>2007-03-06T12:45:53Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=113</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=113"/>
		<updated>2007-03-06T12:38:57Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ola tester testen:&lt;br /&gt;
&amp;lt;math&amp;gt;\sqrt{1-e^2}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=112</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=112"/>
		<updated>2007-03-06T12:34:51Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=111</id>
		<title>Scenery:Terrain Model</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Scenery:Terrain_Model&amp;diff=111"/>
		<updated>2007-03-06T12:34:29Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section describes how a GeoGFX terrain model is built on the&lt;br /&gt;
earth surface. &lt;br /&gt;
&lt;br /&gt;
The earth model used for the 3D visualisation in GeoGFX is a sphere&lt;br /&gt;
with radius $R = 6378000$ m. For visualization purposes, the&lt;br /&gt;
elliptical shape of the earth can safely be ignored. However, all&lt;br /&gt;
geographic processing and reprojection of input data is done in the&lt;br /&gt;
WGS84 datum so all input data will be matched to the same earth model.&lt;br /&gt;
&lt;br /&gt;
A GeoGFX terrain model is divided into \emph{blocks}, each block is a&lt;br /&gt;
rectangular section of the earth surface measured in degrees of&lt;br /&gt;
latitude and longitude. Each block is further divided into a regular&lt;br /&gt;
grid of \emph{tiles}. The number of tiles in a block should normally&lt;br /&gt;
be a power of two, and it should also be the same in north- and&lt;br /&gt;
east-direction, i.e a block can be 8$\times$8, 16$\times$16 etc.&lt;br /&gt;
Neighboring blocks must have the same number of tiles. &lt;br /&gt;
&lt;br /&gt;
Since the GeoGFX terrain is built on a spherical earth model, the&lt;br /&gt;
tiles will get narrower the further north or south we go. If you&lt;br /&gt;
select one tile size in degrees at the equator, the same number of&lt;br /&gt;
longitude degress will cover only half the distance at 60 degrees&lt;br /&gt;
north or south. To keep our tiles more equal sided, we compensate for&lt;br /&gt;
this by dividing the east tile size by the cosine of the latitude, i.e&lt;br /&gt;
if $S$ is tile size and $\phi$ is the latitude of the tile, we get:&lt;br /&gt;
&lt;br /&gt;
\begin{eqnarray}&lt;br /&gt;
  S_N &amp;amp;= S\\&lt;br /&gt;
  S_E &amp;amp;= \frac{S}{\cos(\phi)}&lt;br /&gt;
\end{eqnarray}&lt;br /&gt;
&lt;br /&gt;
Usually we will select a reference latitude $\phi_R$ which is used for&lt;br /&gt;
all terrain blocks that should be connected. For example for a&lt;br /&gt;
european terrain model covering Germany and the Alps we could select&lt;br /&gt;
50\degrees~north as reference latitude for all the terrain blocks. For&lt;br /&gt;
a scandinavian terrain model we would select for example 62\degrees. &lt;br /&gt;
At this reference latitude a tile would be equal size in north and&lt;br /&gt;
east direction. &lt;br /&gt;
&lt;br /&gt;
If no reference latitude is given, the middle of the south border&lt;br /&gt;
latitude of the terrain block is used. (This block would then only be&lt;br /&gt;
able to connect with other blocks on the same latitude).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Ola tester testen:&lt;br /&gt;
&amp;lt;math&amp;gt;\sqrt{1-e^2}&amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=110</id>
		<title>Category:Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=110"/>
		<updated>2007-03-06T11:21:08Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are a few things you can do if you like to use special hardware with Silent Wings:&lt;br /&gt;
&lt;br /&gt;
* [[NMEA format|Connect your PDA]] to the serial port on your PC (or use a USB-to-serial adapter), and use PDA soaring software like in a real glider.&lt;br /&gt;
* Use the [[NMEA format|special serial data string format]] to get a high-speed output of the aircraft state, and use these data for your own projects, like driving instruments or driving a full-motion cockpit.&lt;br /&gt;
* Create your own simulator cockpit, and create your own controls based on USB joysticks. Cheap USB joysticks can be disassebled and the internals used for custom-built sticks, pedals and other controls.&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=108</id>
		<title>Category:Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=108"/>
		<updated>2007-03-06T11:20:30Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are a few things you can do if you like to use special hardware with Silent Wings:&lt;br /&gt;
&lt;br /&gt;
* [[NMEA Format|Connect your PDA]] to the serial port on your PC (or use a USB-to-serial adapter), and use PDA soaring software like in a real glider.&lt;br /&gt;
* Use the [[NMEA Format|special serial data string format]] to get a high-speed output of the aircraft state, and use these data for your own projects, like driving instruments or driving a full-motion cockpit.&lt;br /&gt;
* Create your own simulator cockpit, and create your own controls based on USB joysticks. Cheap USB joysticks can be disassebled and the internals used for custom-built sticks, pedals and other controls.&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=100</id>
		<title>Category:Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=100"/>
		<updated>2007-03-06T11:17:12Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are a few things you can do if you like to use special hardware with Silent Wings:&lt;br /&gt;
&lt;br /&gt;
* Connect your PDA to the serial port on your PC (or use a USB-to-serial adapter), and use PDA soaring software like in a real glider.&lt;br /&gt;
* Use the special serial data string format to get a high-speed output of the aircraft state, and use these data for your own projects, like driving instruments or driving a full-motion cockpit.&lt;br /&gt;
* Create your own simulator cockpit, and create your own controls based on USB joysticks. Cheap USB joysticks can be disassebled and the internals used for custom-built sticks, pedals and other controls.&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=99</id>
		<title>NMEA format</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=NMEA_format&amp;diff=99"/>
		<updated>2007-03-06T11:14:38Z</updated>

		<summary type="html">&lt;p&gt;Ola: New page: Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI.    == Port options ==   For more advanced users, additional parameters ca...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Silent Wings can write NMEA data to a serial port. To enable this, set the proper options in the Silent Wings GUI. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Port options ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
For more advanced users, additional parameters can be set in the options.dat file found in the Silent Wings/data directory. Here are the available options:&lt;br /&gt;
&lt;br /&gt;
 use_nmea = &amp;lt;bool&amp;gt;  &lt;br /&gt;
&lt;br /&gt;
Set to true if you want to enable the NMEA output. The strings are written once a second (1 Hz) with this setting enabled.&lt;br /&gt;
&lt;br /&gt;
 nmea_port = &amp;lt;string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set to the port you want to use. On Windows, this is normally COM1 or COM2. On Linux it would be /dev/ttyS0 or maybe /dev/ttyUSB0, if you&#039;re using USB. On Mac, I don&#039;t know. (TODO)&lt;br /&gt;
&lt;br /&gt;
 nmea_speed = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set the port speed. If not defined this defaults to the NMEA default of 4800. You can however use something else if you want. The valid entries here are 4800, 9600, 19200, 38400, 57600 and 115200. The port settings will be 8 databits, No parity and 1 Stopbit (8N1) and you cannot change that. There is no handshaking.&lt;br /&gt;
&lt;br /&gt;
 use_nmea_special = &amp;lt;int&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is will enable a special Silent Wings specific nmea string output at the frequency in Hz set by &amp;lt;int&amp;gt;. It defaults to 0 which means it&#039;s disabled. If you ONLY want this string output without the other NMEA strings running at the same time at 1 Hz, set use_nmea = false and set use_nmea_special to something &amp;gt; 0. &lt;br /&gt;
&lt;br /&gt;
If you want to use a frequency higher than 1 Hz it&#039;s highly recommended to use the highest port speed that seems possible for your cable and receiving hardware. Otherwise the bandwidth of the port is not high enough and writing one string will not be done before the next one starts.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== NMEA strings ==&lt;br /&gt;
&lt;br /&gt;
Silent Wings will output the following NMEA strings.&lt;br /&gt;
&lt;br /&gt;
* $GPRMC&lt;br /&gt;
* $GPGGA&lt;br /&gt;
* $PCAID&lt;br /&gt;
* !w (a custom string used by the Cambridge C302 flight computer)&lt;br /&gt;
* !s (a silent wings custom string, also used by use_nema_special)&lt;br /&gt;
&lt;br /&gt;
With this set of strings most PDA flight computers will be quite happy. &lt;br /&gt;
&lt;br /&gt;
== The !s string ==&lt;br /&gt;
&lt;br /&gt;
The format of the !s string is as follows:&lt;br /&gt;
&lt;br /&gt;
 !s,&amp;lt;pitch&amp;gt;,&amp;lt;roll&amp;gt;,&amp;lt;alpha&amp;gt;,&amp;lt;beta&amp;gt;,&amp;lt;vario&amp;gt;,&amp;lt;accel&amp;gt;,&amp;lt;nmea checksum&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The numbers are all written with two numbers after the decimal points. Angles are in degrees. The vario is in meter per second, and the accel is the cockpit g meter in meters per second squared. Negative numbers will be signed with a minus &amp;quot;-&amp;quot; in front.&lt;br /&gt;
&lt;br /&gt;
This string can and has been used to control a full motion simulator cockpit. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=93</id>
		<title>Category:Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Category:Hardware&amp;diff=93"/>
		<updated>2007-03-06T10:52:21Z</updated>

		<summary type="html">&lt;p&gt;Ola: New page: * Connect your PDA to the serial port on your PC (or use a USB-to-serial adapter), and use PDA soaring software like in a real glider * Use the special serial data string format to get a h...&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Connect your PDA to the serial port on your PC (or use a USB-to-serial adapter), and use PDA soaring software like in a real glider&lt;br /&gt;
* Use the special serial data string format to get a high-speed output of the aircraft state, and use these data for your own projects&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=92</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Main_Page&amp;diff=92"/>
		<updated>2007-03-06T10:48:13Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;big&amp;gt;&#039;&#039;&#039;Silent Wings Wiki&#039;&#039;&#039;&amp;lt;/big&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Welcome to the Silent Wings wiki pages! This is set up to be a resource for information on the&lt;br /&gt;
[http://www.silentwings.no Silent Wings] soaring simulator. &lt;br /&gt;
&lt;br /&gt;
Primarily the Wiki is intended for Add-on developers who want to create new content such as Aircraft and Scenery for Silent Wings, but any Silent Wings related content is acceptable.&lt;br /&gt;
&lt;br /&gt;
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&#039;s Guide] for information on using the wiki software.&lt;br /&gt;
&lt;br /&gt;
== Categories ==&lt;br /&gt;
The following categories are currently available:&lt;br /&gt;
&lt;br /&gt;
* [[:Category:Scenery|Scenery]] Articles related to creating scenery for Silent Wings&lt;br /&gt;
* [[:Category:Aircraft|Aircraft]] Making add-on aircraft&lt;br /&gt;
* [[:Category:Server|Server]] Multiplayer server setup&lt;br /&gt;
* [[:Category:Hardware|Hardware]] Articles related to connecting various hardware to Silent Wings&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=91</id>
		<title>Aero.dat</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=91"/>
		<updated>2007-03-06T10:33:20Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The aero.dat configuration file describes the aerodynamic properties of the flight model. Currently, Silent Wings has two different aerodynamic models to choose from: The &amp;quot;panel model&amp;quot; and the &amp;quot;linear&amp;quot; model. &lt;br /&gt;
&lt;br /&gt;
For all player-controlled aircraft the panel model is recommended. This way of modelling has become quite popular in flight simulators, and is also sometimes called &amp;quot;Blade Element Theory&amp;quot; which is a method commonly used to simulate propellers. Silent Wings uses an extended Blade Element Theory on the propeller model, whereas the Panel Model is modified even more to be suited for a fixed-wing aircraft, even with low aspect ratio wings.  &lt;br /&gt;
&lt;br /&gt;
The linear model is implemented for use on autopilot controlled aircraft such as the towplane, and will only behave realistic at a small speed range. See the end of this article for a brief description of the linear model file format.&lt;br /&gt;
&lt;br /&gt;
The Silent Wings panel model describes the geometrical design of the aircraft that is to be simulated. By manually dividing an aircraft into segments, or &amp;quot;panels&amp;quot;, the flight dynamics code can calculate the forces that act on the aircraft and let it fly. The panel model works with two different panels: wingpanels and fuselage panels. The Wing panels are used to describe the wings and fins on the aircraft. Every wing panel needs an airfoil to do the aerodynamic definition, so these airfoils need to be defined as well. &lt;br /&gt;
&lt;br /&gt;
The airfoils can be shared between panels of the same wing, and are therefor defined before the wing panels. You must define one airfoil for each wing (or fin), also when they all would use the same airfoil, because the airfoil is defined with 3-dimensional properties (aspect ratio of wing, etc). You may, however, use several airfoils for a single wing, if you like.&lt;br /&gt;
&lt;br /&gt;
== Example file ==&lt;br /&gt;
&lt;br /&gt;
This is an example aero.dat file, taken from the SG38 model. It shows how to quicly create a usable aero model. Below, all options are described. For a more advanced aero.dat example, take a look at the Antares 20E aero model.&lt;br /&gt;
&lt;br /&gt;
 # SG38 Panelmodel data file &lt;br /&gt;
 # Part of Silent Wings&lt;br /&gt;
 # Ola Røer Thorsen 25.10.2004&lt;br /&gt;
 &lt;br /&gt;
 # General things&lt;br /&gt;
 plane_name		= SG 38&lt;br /&gt;
 plane_description	= Schulgleiter&lt;br /&gt;
 &lt;br /&gt;
 # Airfoil data. Note: these are &amp;quot;finite wing airfoils&amp;quot;, not&lt;br /&gt;
 # 2-dimensional data.&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= mainwing&lt;br /&gt;
    profile	= goe533&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 6.5&lt;br /&gt;
    meanchord	= 1.5&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= elevator&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 3.1&lt;br /&gt;
    meanchord	= 1.0&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= rudder&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k           = 1.2&lt;br /&gt;
    aspectratio = 1.1&lt;br /&gt;
    meanchord   = 1.2&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 # The panels&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= 1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff   = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;left wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 #area		= 4.5&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= -1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff    = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;right wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= -3.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= elevator&lt;br /&gt;
 airfoil	= elevator&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.0&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha 		= -3.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 elevator_mix	= 1.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= rudder&lt;br /&gt;
 dep_panels     = [ elevator ]&lt;br /&gt;
 airfoil	= rudder&lt;br /&gt;
 area		= 1.5&lt;br /&gt;
 meanchord	= 1.2&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 90.0&lt;br /&gt;
 delta_max	= 30.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral  = 0.0&lt;br /&gt;
 rudder_mix	= 1.0&lt;br /&gt;
 broken_drag    = 0.3&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 fuselage {&lt;br /&gt;
 name		= fuselage&lt;br /&gt;
 position	= [ 0.0 0.0 0.0 ]&lt;br /&gt;
 ref_area	= 12.53&lt;br /&gt;
 ref_volume	= 1.0&lt;br /&gt;
 cd_front	= sg38&lt;br /&gt;
 cd_side	= 0.05&lt;br /&gt;
 cd_top	        = 0.05&lt;br /&gt;
 k_y		= 0.0&lt;br /&gt;
 k_z		= 0.0&lt;br /&gt;
 alpha_fuselage = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Airfoils ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
An airfoil is defined like this: &lt;br /&gt;
 &lt;br /&gt;
 airfoil &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    profile = xx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
The variables to be defined are: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The name of the airfoil. This can be called whatever you like, and is the name to be used in the wing panels. &lt;br /&gt;
 &lt;br /&gt;
 profile = &amp;lt;name&amp;gt; &lt;br /&gt;
&lt;br /&gt;
There are [[Polar file formats | two airfoil file formats]] available. The &amp;lt;name&amp;gt; specifies the file name &#039;&#039;&#039;without&#039;&#039;&#039; the extension (.polar or .cl/.cd/.cm). The polar files are to be put in the Silent Wings/data/airfoils directory.&lt;br /&gt;
 &lt;br /&gt;
 k = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The &amp;quot;k&amp;quot; factor defines the induced drag finesse of the wing. A setting of 1.0 gives the optimum, planar wing with elliptical lift distribution. So any other planar wing will have a value higher than 1.0. &lt;br /&gt;
 &lt;br /&gt;
Wings with winglets may get values lower than 1.0. The best wings currently available (Antares) have a k factor of 0.95. &lt;br /&gt;
 &lt;br /&gt;
 aspectratio = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The aspect ratio of the wing that will use this airfoil. &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing that will use this airfoil &lt;br /&gt;
 &lt;br /&gt;
 cl_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
This factor can be used to fine-tune the lift curve. The variable is multiplied with the lift from the lift polar. Leave this to 1.0 when you start up, and use it as a last resort when fine tuning your model. &lt;br /&gt;
 &lt;br /&gt;
 cd_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This factor can be used to fine-tune the drag curve. The variable is added to the drag polar. Use with caution. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Wing panel ==&lt;br /&gt;
 &lt;br /&gt;
A wingpanel is defined with &amp;quot;wingpanel&amp;quot; followed by brackets containing the wing panel variables, one variable per line. &lt;br /&gt;
 &lt;br /&gt;
 wingpanel &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    area = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
A wing can be defined with one or several panels. For elevator and rudder surfaces, one panel is mostly sufficient. A main wing should have at least 4 panels in total (two left, two right). When not defined, variables default to zero. That means, if certain things are not to be used on the wing panel (such as a spoiler), the variables do not have to be set. &lt;br /&gt;
 &lt;br /&gt;
Please see the example illustration of the Ventus aero model to get a picture of how the panels are defined. &lt;br /&gt;
  &lt;br /&gt;
&#039;&#039;&#039;General data:&#039;&#039;&#039; &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;text string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Wing panel name &lt;br /&gt;
 &lt;br /&gt;
 airfoil = &amp;lt;text string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The airfoil to use. The name to use is the same as defined in one of the airfoil sections. &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position coordinate. See the illustration on how to define this point. &lt;br /&gt;
 &lt;br /&gt;
 area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Wing panel area &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing panel (not the wing!) &lt;br /&gt;
 &lt;br /&gt;
 alpha = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s angle of incident. &lt;br /&gt;
 &lt;br /&gt;
 dihedral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s dihedral angle. &lt;br /&gt;
 &lt;br /&gt;
 sweep = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s sweep angle. &lt;br /&gt;
 &lt;br /&gt;
 propwash = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
If the panel is positioned behind a propeller, you can set this value higher than 0.0 to have a propwash effect on the panel. This will for example allow for rudder and elevator authority when standing still on the Antares model. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Control surface variables:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The control system of Silent Wings is quite flexible, and can handle more exotic designs like canards, v-tails and flying wings. You can add all the controllers to have an effect on every panel in different ways. If the panel has no controls, these entries need not be defined.&lt;br /&gt;
 &lt;br /&gt;
 delta_max = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s maximum (positive) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_min = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s minimum (negative) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_neutral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s position when the controls are centered &lt;br /&gt;
 &lt;br /&gt;
 aileron_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of aileron control that is to be applied to the flap. For the left wing, normally 1.0 is used, for the right wing -1.0. For less effect use smaller numbers. For no aileron control set to 0.0 or leave it out. &lt;br /&gt;
 &lt;br /&gt;
 aileron_delta = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The maximum difference in deflection between the left and right aileron. For example, if with fully deflected ailerons the left one is at +10 and the right one at -10, this value should be set to 20.0. &lt;br /&gt;
 &lt;br /&gt;
 aileron_diff = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Aileron differential. This factor will define how much more the up-going (negative) aileron will go up compared with the down-going one (positive). The value 1.0 (default) means equal  deflection in both directions. A setting of 2.0 means the up-going aileron will do twice as much deflection as the down-going aileron. This is common on sailplanes as it reduces the adverse yaw effect of the ailerons. &lt;br /&gt;
 &lt;br /&gt;
 flap_pos = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most positive flap setting in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 flap_neg = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most negative flap position in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 elevator_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of elevator control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 rudder_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of rudder control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 throttle_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of throttle control that is to be applied to the flap (this is rather uncommon, so it will mostly be left out. It can be used to compensate or emulate some throttle effects) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Spoiler/airbrake variables:&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
If the panel has no controls, these entries need not be defined.&lt;br /&gt;
 &lt;br /&gt;
 brake_on = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Set this variable to 1 to enable the spoiler/airbrake &lt;br /&gt;
 &lt;br /&gt;
 brake_surface = &amp;lt;float&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The surface frontal surface of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_liftdest = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The amount of lift coefficient reduction with a fully extended brake. This is normally around 1.0, but must be experimented with. &lt;br /&gt;
 &lt;br /&gt;
 brake_cd = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag coefficient of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_superp = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Setting this to 1 enables superpositional mode. With this a brake can be added upon a wing and will have an effect on the lift and drag from the other wing panels only when the brake controller is on. When set to zero the wing panel is just a normal wing panel, that also has an airbrake/spoiler attached. Which to use depends on how the panelling of the wing is chosen. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Fuselage panel ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
The fuselage panel is a model of an aircraft fuselage. Its largest effect is to add drag to the aero model. &lt;br /&gt;
 &lt;br /&gt;
It is defined as &lt;br /&gt;
 &lt;br /&gt;
 fuselage &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    position = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Variable description: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Panel name &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position. This is the position where the drag force is applied, and does influence flight mechanics of your model, especially in spins. Start out by positioning this near to your model&#039;s centre of gravity. &lt;br /&gt;
 &lt;br /&gt;
 ref_area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference frontal area of the fuselage &lt;br /&gt;
 &lt;br /&gt;
 ref_volume = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference volume of the fuselage. In most cases, this can be set to 1.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_front = frontal_drag_filenamename (but without the .cd extension) &lt;br /&gt;
&lt;br /&gt;
The frontal drag is defined in a name.cd file that is placed in the airfoils directory. Use this file to finetune your model&#039;s glide polar. &lt;br /&gt;
 &lt;br /&gt;
 cd_side = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Sidewards drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 cd_top = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Top/bottom drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 k_y = 0.0 to 1.0 &lt;br /&gt;
 k_z = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
These two factors set the magnitude of instability of the fuselage. Try something like 0.1 first. A larger value means more instability. &lt;br /&gt;
 &lt;br /&gt;
 alpha_fuselage = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The fuselage&#039;s angle of incidence. Normally 0.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_landinggear = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag of an extended landing gear.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Linear aero model ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here are a sample aero.dat file when the linear aero model is used:&lt;br /&gt;
&lt;br /&gt;
 #-----------&lt;br /&gt;
 # Main wing&lt;br /&gt;
 #-----------&lt;br /&gt;
 wing_area               = 17.0&lt;br /&gt;
 wing_span               = 12.0&lt;br /&gt;
 mean_chord              = 1.5&lt;br /&gt;
 k_factor                = 1.5&lt;br /&gt;
 &lt;br /&gt;
 #------------------&lt;br /&gt;
 # Control surfaces&lt;br /&gt;
 #------------------&lt;br /&gt;
 aileron_limits          = [ -23.0 20.0 ]&lt;br /&gt;
 elevator_limits         = [ -23.0 28.0 ]&lt;br /&gt;
 rudder_limits           = [ -16.0 16.0 ]&lt;br /&gt;
 &lt;br /&gt;
 flap_min                = 0.0&lt;br /&gt;
 flap_max                = 1.0&lt;br /&gt;
 flap_eff                = 0.2&lt;br /&gt;
 &lt;br /&gt;
 #--------------------------&lt;br /&gt;
 # Aerodynamic coefficients&lt;br /&gt;
 # --------------------------&lt;br /&gt;
 c_lift_0                = 0.410&lt;br /&gt;
 c_lift_a                = 5.143&lt;br /&gt;
 c_lift_elev             = 0.340&lt;br /&gt;
 c_drag_0                = 0.08&lt;br /&gt;
 c_drag_i                = 0.08&lt;br /&gt;
 c_side_beta             = -0.31&lt;br /&gt;
 c_side_rudder           = 0.25&lt;br /&gt;
 c_yaw_beta              = 0.165&lt;br /&gt;
 c _yaw_rudder            = -0.25&lt;br /&gt;
 c_yaw_aileron           = 0.0&lt;br /&gt;
 c_yaw_roll_rate         = 0.0&lt;br /&gt;
 yaw_damping             = -0.099&lt;br /&gt;
 c_pitch_0               = 0.02&lt;br /&gt;
 c_pitch_a               = -0.8&lt;br /&gt;
 c_pitch_elev            = -0.7&lt;br /&gt;
 c_pitch_dot_a           = 0&lt;br /&gt;
 pitch_damping           = -12.4&lt;br /&gt;
 c_roll                  = 0.178&lt;br /&gt;
 roll_damping            = -0.47&lt;br /&gt;
&lt;br /&gt;
Here, a conventional coefficient based model is used to simulate the aircraft. If you have experience with such models you might recongnise the parameters and what they do.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft Physics]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=90</id>
		<title>Aero.dat</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=90"/>
		<updated>2007-03-06T10:30:03Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The aero.dat configuration file describes the aerodynamic properties of the flight model. Currently, Silent Wings has two different aerodynamic models to choose from: The &amp;quot;panel model&amp;quot; and the &amp;quot;linear&amp;quot; model. &lt;br /&gt;
&lt;br /&gt;
For all player-controlled aircraft the panel model is recommended. This way of modelling has become quite popular in flight simulators, and is also sometimes called &amp;quot;Blade Element Theory&amp;quot; which is a method commonly used to simulate propellers. Silent Wings uses an extended Blade Element Theory on the propeller model, whereas the Panel Model is modified even more to be suited for a fixed-wing aircraft, even with low aspect ratio wings.  &lt;br /&gt;
&lt;br /&gt;
The linear model is implemented for use on autopilot controlled aircraft such as the towplane, and will only behave realistic at a small speed range. See the end of this article for a brief description of the linear model file format.&lt;br /&gt;
&lt;br /&gt;
The Silent Wings panel model describes the geometrical design of the aircraft that is to be simulated. By manually dividing an aircraft into segments, or &amp;quot;panels&amp;quot;, the flight dynamics code can calculate the forces that act on the aircraft and let it fly. The panel model works with two different panels: wingpanels and fuselage panels. The Wing panels are used to describe the wings and fins on the aircraft. Every wing panel needs an airfoil to do the aerodynamic definition, so these airfoils need to be defined as well. &lt;br /&gt;
&lt;br /&gt;
The airfoils can be shared between panels of the same wing, and are therefor defined before the wing panels. You must define one airfoil for each wing (or fin), also when they all would use the same airfoil, because the airfoil is defined with 3-dimensional properties (aspect ratio of wing, etc). You may, however, use several airfoils for a single wing, if you like.&lt;br /&gt;
&lt;br /&gt;
== Example file ==&lt;br /&gt;
&lt;br /&gt;
This is an example aero.dat file, taken from the SG38 model. It shows how to quicly create a usable aero model. Below, all options are described. For a more advanced aero.dat example, take a look at the Antares 20E aero model.&lt;br /&gt;
&lt;br /&gt;
 # SG38 Panelmodel data file &lt;br /&gt;
 # Part of Silent Wings&lt;br /&gt;
 # Ola Røer Thorsen 25.10.2004&lt;br /&gt;
 &lt;br /&gt;
 # General things&lt;br /&gt;
 plane_name		= SG 38&lt;br /&gt;
 plane_description	= Schulgleiter&lt;br /&gt;
 &lt;br /&gt;
 # Airfoil data. Note: these are &amp;quot;finite wing airfoils&amp;quot;, not&lt;br /&gt;
 # 2-dimensional data.&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= mainwing&lt;br /&gt;
    profile	= goe533&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 6.5&lt;br /&gt;
    meanchord	= 1.5&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= elevator&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 3.1&lt;br /&gt;
    meanchord	= 1.0&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= rudder&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k           = 1.2&lt;br /&gt;
    aspectratio = 1.1&lt;br /&gt;
    meanchord   = 1.2&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 # The panels&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= 1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff   = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;left wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 #area		= 4.5&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= -1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff    = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;right wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= -3.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= elevator&lt;br /&gt;
 airfoil	= elevator&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.0&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha 		= -3.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 elevator_mix	= 1.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= rudder&lt;br /&gt;
 dep_panels     = [ elevator ]&lt;br /&gt;
 airfoil	= rudder&lt;br /&gt;
 area		= 1.5&lt;br /&gt;
 meanchord	= 1.2&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 90.0&lt;br /&gt;
 delta_max	= 30.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral  = 0.0&lt;br /&gt;
 rudder_mix	= 1.0&lt;br /&gt;
 broken_drag    = 0.3&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 fuselage {&lt;br /&gt;
 name		= fuselage&lt;br /&gt;
 position	= [ 0.0 0.0 0.0 ]&lt;br /&gt;
 ref_area	= 12.53&lt;br /&gt;
 ref_volume	= 1.0&lt;br /&gt;
 cd_front	= sg38&lt;br /&gt;
 cd_side	= 0.05&lt;br /&gt;
 cd_top	        = 0.05&lt;br /&gt;
 k_y		= 0.0&lt;br /&gt;
 k_z		= 0.0&lt;br /&gt;
 alpha_fuselage = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Airfoils ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
An airfoil is defined like this: &lt;br /&gt;
 &lt;br /&gt;
 airfoil &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    profile = xx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
The variables to be defined are: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The name of the airfoil. This can be called whatever you like, and is the name to be used in the wing panels. &lt;br /&gt;
 &lt;br /&gt;
 profile = &amp;lt;name&amp;gt; &lt;br /&gt;
&lt;br /&gt;
There are [[Polar file formats | two airfoil file formats]] available. The &amp;lt;name&amp;gt; specifies the file name &#039;&#039;&#039;without&#039;&#039;&#039; the extension (.polar or .cl/.cd/.cm). The polar files are to be put in the Silent Wings/data/airfoils directory.&lt;br /&gt;
 &lt;br /&gt;
 k = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The &amp;quot;k&amp;quot; factor defines the induced drag finesse of the wing. A setting of 1.0 gives the optimum, planar wing with elliptical lift distribution. So any other planar wing will have a value higher than 1.0. &lt;br /&gt;
 &lt;br /&gt;
Wings with winglets may get values lower than 1.0. The best wings currently available (Antares) have a k factor of 0.95. &lt;br /&gt;
 &lt;br /&gt;
 aspectratio = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The aspect ratio of the wing that will use this airfoil. &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing that will use this airfoil &lt;br /&gt;
 &lt;br /&gt;
 cl_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
This factor can be used to fine-tune the lift curve. The variable is multiplied with the lift from the lift polar. Leave this to 1.0 when you start up, and use it as a last resort when fine tuning your model. &lt;br /&gt;
 &lt;br /&gt;
 cd_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This factor can be used to fine-tune the drag curve. The variable is added to the drag polar. Use with caution. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Wing panel ==&lt;br /&gt;
 &lt;br /&gt;
A wingpanel is defined with &amp;quot;wingpanel&amp;quot; followed by brackets containing the wing panel variables, one variable per line. &lt;br /&gt;
 &lt;br /&gt;
 wingpanel &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    area = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
A wing can be defined with one or several panels. For elevator and rudder surfaces, one panel is mostly sufficient. A main wing should have at least 4 panels in total (two left, two right). &lt;br /&gt;
 &lt;br /&gt;
When not defined, variables default to zero. That means, if certain things are not to be used on the wing panel (such as a spoiler), the variables do not have to be set. &lt;br /&gt;
 &lt;br /&gt;
Please see the example illustration of the Ventus aero model to get a picture of how the panels are defined. &lt;br /&gt;
 &lt;br /&gt;
Variable descriptions: &lt;br /&gt;
 &lt;br /&gt;
General data: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;text string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Wing panel name &lt;br /&gt;
 &lt;br /&gt;
 airfoil = &amp;lt;text string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The airfoil to use. The name to use is the same as defined in one of the airfoil sections. &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position coordinate. See the illustration on how to define this point. &lt;br /&gt;
 &lt;br /&gt;
 area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Wing panel area &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing panel (not the wing!) &lt;br /&gt;
 &lt;br /&gt;
 alpha = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s angle of incident. &lt;br /&gt;
 &lt;br /&gt;
 dihedral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s dihedral angle. &lt;br /&gt;
 &lt;br /&gt;
 sweep = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s sweep angle. &lt;br /&gt;
 &lt;br /&gt;
 propwash = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
If the panel is positioned behind a propeller, you can set this value higher than 0.0 to have a propwash effect on the panel. This will for example allow for rudder and elevator authority when standing still on the Antares model. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Control surface variables:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The control system of Silent Wings is quite flexible, and can handle more exotic designs like canards, v-tails and flying wings. You can add all the controllers to have an effect on every panel in different ways. If the panel has no controls, these entries need not be defined.&lt;br /&gt;
 &lt;br /&gt;
 delta_max = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s maximum (positive) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_min = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s minimum (negative) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_neutral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s position when the controls are centered &lt;br /&gt;
 &lt;br /&gt;
 aileron_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of aileron control that is to be applied to the flap. For the left wing, normally 1.0 is used, for the right wing -1.0. For less effect use smaller numbers. For no aileron control set to 0.0 or leave it out. &lt;br /&gt;
 &lt;br /&gt;
 aileron_delta = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The maximum difference in deflection between the left and right aileron. For example, if with fully deflected ailerons the left one is at +10 and the right one at -10, this value should be set to 20.0. &lt;br /&gt;
 &lt;br /&gt;
 aileron_diff = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Aileron differential. This factor will define how much more the up-going (negative) aileron will go up compared with the down-going one (positive). The value 1.0 (default) means equal  deflection in both directions. A setting of 2.0 means the up-going aileron will do twice as much deflection as the down-going aileron. This is common on sailplanes as it reduces the adverse yaw effect of the ailerons. &lt;br /&gt;
 &lt;br /&gt;
 flap_pos = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most positive flap setting in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 flap_neg = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most negative flap position in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 elevator_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of elevator control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 rudder_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of rudder control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 throttle_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of throttle control that is to be applied to the flap (this is rather uncommon, so it will mostly be left out. It can be used to compensate or emulate some throttle effects) &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Spoiler/airbrake variables:&#039;&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
If the panel has no controls, these entries need not be defined.&lt;br /&gt;
 &lt;br /&gt;
 brake_on = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Set this variable to 1 to enable the spoiler/airbrake &lt;br /&gt;
 &lt;br /&gt;
 brake_surface = &amp;lt;float&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The surface frontal surface of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_liftdest = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The amount of lift coefficient reduction with a fully extended brake. This is normally around 1.0, but must be experimented with. &lt;br /&gt;
 &lt;br /&gt;
 brake_cd = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag coefficient of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_superp = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Setting this to 1 enables superpositional mode. With this a brake can be added upon a wing and will have an effect on the lift and drag from the other wing panels only when the brake controller is on. When set to zero the wing panel is just a normal wing panel, that also has an airbrake/spoiler attached. Which to use depends on how the panelling of the wing is chosen. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Fuselage panel ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
The fuselage panel is a model of an aircraft fuselage. Its largest effect is to add drag to the aero model. &lt;br /&gt;
 &lt;br /&gt;
It is defined as &lt;br /&gt;
 &lt;br /&gt;
 fuselage &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    position = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Variable description: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Panel name &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position. This is the position where the drag force is applied, and does influence flight mechanics of your model, especially in spins. Start out by positioning this near to your model&#039;s centre of gravity. &lt;br /&gt;
 &lt;br /&gt;
 ref_area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference frontal area of the fuselage &lt;br /&gt;
 &lt;br /&gt;
 ref_volume = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference volume of the fuselage. In most cases, this can be set to 1.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_front = frontal_drag_filenamename (but without the .cd extension) &lt;br /&gt;
&lt;br /&gt;
The frontal drag is defined in a name.cd file that is placed in the airfoils directory. Use this file to finetune your model&#039;s glide polar. &lt;br /&gt;
 &lt;br /&gt;
 cd_side = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Sidewards drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 cd_top = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Top/bottom drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 k_y = 0.0 to 1.0 &lt;br /&gt;
 k_z = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
These two factors set the magnitude of instability of the fuselage. Try something like 0.1 first. A larger value means more instability. &lt;br /&gt;
 &lt;br /&gt;
 alpha_fuselage = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The fuselage&#039;s angle of incidence. Normally 0.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_landinggear = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag of an extended landing gear.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Linear aero model ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here are a sample aero.dat file when the linear aero model is used:&lt;br /&gt;
&lt;br /&gt;
 #-----------&lt;br /&gt;
 # Main wing&lt;br /&gt;
 #-----------&lt;br /&gt;
 wing_area               = 17.0&lt;br /&gt;
 wing_span               = 12.0&lt;br /&gt;
 mean_chord              = 1.5&lt;br /&gt;
 k_factor                = 1.5&lt;br /&gt;
 &lt;br /&gt;
 #------------------&lt;br /&gt;
 # Control surfaces&lt;br /&gt;
 #------------------&lt;br /&gt;
 aileron_limits          = [ -23.0 20.0 ]&lt;br /&gt;
 elevator_limits         = [ -23.0 28.0 ]&lt;br /&gt;
 rudder_limits           = [ -16.0 16.0 ]&lt;br /&gt;
 &lt;br /&gt;
 flap_min                = 0.0&lt;br /&gt;
 flap_max                = 1.0&lt;br /&gt;
 flap_eff                = 0.2&lt;br /&gt;
 &lt;br /&gt;
 #--------------------------&lt;br /&gt;
 # Aerodynamic coefficients&lt;br /&gt;
 # --------------------------&lt;br /&gt;
 c_lift_0                = 0.410&lt;br /&gt;
 c_lift_a                = 5.143&lt;br /&gt;
 c_lift_elev             = 0.340&lt;br /&gt;
 c_drag_0                = 0.08&lt;br /&gt;
 c_drag_i                = 0.08&lt;br /&gt;
 c_side_beta             = -0.31&lt;br /&gt;
 c_side_rudder           = 0.25&lt;br /&gt;
 c_yaw_beta              = 0.165&lt;br /&gt;
 c _yaw_rudder            = -0.25&lt;br /&gt;
 c_yaw_aileron           = 0.0&lt;br /&gt;
 c_yaw_roll_rate         = 0.0&lt;br /&gt;
 yaw_damping             = -0.099&lt;br /&gt;
 c_pitch_0               = 0.02&lt;br /&gt;
 c_pitch_a               = -0.8&lt;br /&gt;
 c_pitch_elev            = -0.7&lt;br /&gt;
 c_pitch_dot_a           = 0&lt;br /&gt;
 pitch_damping           = -12.4&lt;br /&gt;
 c_roll                  = 0.178&lt;br /&gt;
 roll_damping            = -0.47&lt;br /&gt;
&lt;br /&gt;
Here, a conventional coefficient based model is used to simulate the aircraft. If you have experience with such models you might recongnise the parameters and what they do.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft Physics]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=89</id>
		<title>Aero.dat</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=89"/>
		<updated>2007-03-06T10:28:36Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The aero.dat configuration file describes the aerodynamic properties of the flight model. Currently, Silent Wings has two different aerodynamic models to choose from: The &amp;quot;panel model&amp;quot; and the &amp;quot;linear&amp;quot; model. &lt;br /&gt;
&lt;br /&gt;
For all player-controlled aircraft the panel model is recommended. This way of modelling has become quite popular in flight simulators, and is also sometimes called &amp;quot;Blade Element Theory&amp;quot; which is a method commonly used to simulate propellers. Silent Wings uses an extended Blade Element Theory on the propeller model, whereas the Panel Model is modified even more to be suited for a fixed-wing aircraft, even with low aspect ratio wings.  &lt;br /&gt;
&lt;br /&gt;
The linear model is implemented for use on autopilot controlled aircraft such as the towplane, and will only behave realistic at a small speed range. See the end of this article for a brief description of the linear model file format.&lt;br /&gt;
&lt;br /&gt;
The Silent Wings panel model describes the geometrical design of the aircraft that is to be simulated. By manually dividing an aircraft into segments, or &amp;quot;panels&amp;quot;, the flight dynamics code can calculate the forces that act on the aircraft and let it fly. The panel model works with two different panels: wingpanels and fuselage panels. The Wing panels are used to describe the wings and fins on the aircraft. Every wing panel needs an airfoil to do the aerodynamic definition, so these airfoils need to be defined as well. &lt;br /&gt;
&lt;br /&gt;
The airfoils can be shared between panels of the same wing, and are therefor defined before the wing panels. You must define one airfoil for each wing (or fin), also when they all would use the same airfoil, because the airfoil is defined with 3-dimensional properties (aspect ratio of wing, etc). You may, however, use several airfoils for a single wing, if you like.&lt;br /&gt;
&lt;br /&gt;
== Example file ==&lt;br /&gt;
&lt;br /&gt;
This is an example aero.dat file, taken from the SG38 model. It shows how to quicly create a usable aero model. Below, all options are described. For a more advanced aero.dat example, take a look at the Antares 20E aero model.&lt;br /&gt;
&lt;br /&gt;
 # SG38 Panelmodel data file &lt;br /&gt;
 # Part of Silent Wings&lt;br /&gt;
 # Ola Røer Thorsen 25.10.2004&lt;br /&gt;
 &lt;br /&gt;
 # General things&lt;br /&gt;
 plane_name		= SG 38&lt;br /&gt;
 plane_description	= Schulgleiter&lt;br /&gt;
 &lt;br /&gt;
 # Airfoil data. Note: these are &amp;quot;finite wing airfoils&amp;quot;, not&lt;br /&gt;
 # 2-dimensional data.&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= mainwing&lt;br /&gt;
    profile	= goe533&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 6.5&lt;br /&gt;
    meanchord	= 1.5&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= elevator&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 3.1&lt;br /&gt;
    meanchord	= 1.0&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= rudder&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k           = 1.2&lt;br /&gt;
    aspectratio = 1.1&lt;br /&gt;
    meanchord   = 1.2&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 # The panels&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= 1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff   = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;left wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 #area		= 4.5&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= -1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff    = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;right wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= -3.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= elevator&lt;br /&gt;
 airfoil	= elevator&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.0&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha 		= -3.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 elevator_mix	= 1.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= rudder&lt;br /&gt;
 dep_panels     = [ elevator ]&lt;br /&gt;
 airfoil	= rudder&lt;br /&gt;
 area		= 1.5&lt;br /&gt;
 meanchord	= 1.2&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 90.0&lt;br /&gt;
 delta_max	= 30.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral  = 0.0&lt;br /&gt;
 rudder_mix	= 1.0&lt;br /&gt;
 broken_drag    = 0.3&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 fuselage {&lt;br /&gt;
 name		= fuselage&lt;br /&gt;
 position	= [ 0.0 0.0 0.0 ]&lt;br /&gt;
 ref_area	= 12.53&lt;br /&gt;
 ref_volume	= 1.0&lt;br /&gt;
 cd_front	= sg38&lt;br /&gt;
 cd_side	= 0.05&lt;br /&gt;
 cd_top	        = 0.05&lt;br /&gt;
 k_y		= 0.0&lt;br /&gt;
 k_z		= 0.0&lt;br /&gt;
 alpha_fuselage = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Airfoils ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
An airfoil is defined like this: &lt;br /&gt;
 &lt;br /&gt;
 airfoil &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    profile = xx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
The variables to be defined are: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The name of the airfoil. This can be called whatever you like, and is the name to be used in the wing panels. &lt;br /&gt;
 &lt;br /&gt;
 profile = &amp;lt;name&amp;gt; &lt;br /&gt;
&lt;br /&gt;
There are [[Polar file formats | two airfoil file formats]] available. The &amp;lt;name&amp;gt; specifies the file name &#039;&#039;&#039;without&#039;&#039;&#039; the extension (.polar or .cl/.cd/.cm). The polar files are to be put in the Silent Wings/data/airfoils directory.&lt;br /&gt;
 &lt;br /&gt;
 k = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The &amp;quot;k&amp;quot; factor defines the induced drag finesse of the wing. A setting of 1.0 gives the optimum, planar wing with elliptical lift distribution. So any other planar wing will have a value higher than 1.0. &lt;br /&gt;
 &lt;br /&gt;
Wings with winglets may get values lower than 1.0. The best wings currently available (Antares) have a k factor of 0.95. &lt;br /&gt;
 &lt;br /&gt;
 aspectratio = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The aspect ratio of the wing that will use this airfoil. &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing that will use this airfoil &lt;br /&gt;
 &lt;br /&gt;
 cl_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
This factor can be used to fine-tune the lift curve. The variable is multiplied with the lift from the lift polar. Leave this to 1.0 when you start up, and use it as a last resort when fine tuning your model. &lt;br /&gt;
 &lt;br /&gt;
 cd_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This factor can be used to fine-tune the drag curve. The variable is added to the drag polar. Use with caution. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Wing panel ==&lt;br /&gt;
 &lt;br /&gt;
A wingpanel is defined with &amp;quot;wingpanel&amp;quot; followed by brackets containing the wing panel variables, one variable per line. &lt;br /&gt;
 &lt;br /&gt;
 wingpanel &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    area = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
A wing can be defined with one or several panels. For elevator and rudder surfaces, one panel is mostly sufficient. A main wing should have at least 4 panels in total (two left, two right). &lt;br /&gt;
 &lt;br /&gt;
When not defined, variables default to zero. That means, if certain things are not to be used on the wing panel (such as a spoiler), the variables do not have to be set. &lt;br /&gt;
 &lt;br /&gt;
Please see the example illustration of the Ventus aero model to get a picture of how the panels are defined. &lt;br /&gt;
 &lt;br /&gt;
Variable descriptions: &lt;br /&gt;
 &lt;br /&gt;
General data: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;text string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Wing panel name &lt;br /&gt;
 &lt;br /&gt;
 airfoil = &amp;lt;text string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The airfoil to use. The name to use is the same as defined in one of the airfoil sections. &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position coordinate. See the illustration on how to define this point. &lt;br /&gt;
 &lt;br /&gt;
 area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Wing panel area &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing panel (not the wing!) &lt;br /&gt;
 &lt;br /&gt;
 alpha = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s angle of incident. &lt;br /&gt;
 &lt;br /&gt;
 dihedral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s dihedral angle. &lt;br /&gt;
 &lt;br /&gt;
 sweep = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s sweep angle. &lt;br /&gt;
 &lt;br /&gt;
 propwash = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
If the panel is positioned behind a propeller, you can set this value higher than 0.0 to have a propwash effect on the panel. This will for example allow for rudder and elevator authority when standing still on the Antares model. &lt;br /&gt;
 &lt;br /&gt;
&#039;&#039;&#039;Control surface variables:&#039;&#039;&#039; (can be left out if the panel has no controls) &lt;br /&gt;
&lt;br /&gt;
The control system of Silent Wings is quite flexible, and can handle more exotic designs like canards, v-tails and flying wings. You can add all the controllers to have an effect on every panel in different ways. &lt;br /&gt;
 &lt;br /&gt;
 delta_max = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s maximum (positive) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_min = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s minimum (negative) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_neutral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s position when the controls are centered &lt;br /&gt;
 &lt;br /&gt;
 aileron_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of aileron control that is to be applied to the flap. For the left wing, normally 1.0 is used, for the right wing -1.0. For less effect use smaller numbers. For no aileron control set to 0.0 or leave it out. &lt;br /&gt;
 &lt;br /&gt;
 aileron_delta = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The maximum difference in deflection between the left and right aileron. For example, if with fully deflected ailerons the left one is at +10 and the right one at -10, this value should be set to 20.0. &lt;br /&gt;
 &lt;br /&gt;
 aileron_diff = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Aileron differential. This factor will define how much more the up-going (negative) aileron will go up compared with the down-going one (positive). The value 1.0 (default) means equal  deflection in both directions. A setting of 2.0 means the up-going aileron will do twice as much deflection as the down-going aileron. This is common on sailplanes as it reduces the adverse yaw effect of the ailerons. &lt;br /&gt;
 &lt;br /&gt;
 flap_pos = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most positive flap setting in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 flap_neg = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most negative flap position in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 elevator_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of elevator control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 rudder_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of rudder control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 throttle_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of throttle control that is to be applied to the flap (this is rather uncommon, so it will mostly be left out. It can be used to compensate or emulate some throttle effects) &lt;br /&gt;
&lt;br /&gt;
Spoiler/airbrake variables: (can be left out if the panel has no airbrake or spoiler) &lt;br /&gt;
 &lt;br /&gt;
 brake_on = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Set this variable to 1 to enable the spoiler/airbrake &lt;br /&gt;
 &lt;br /&gt;
 brake_surface = &amp;lt;float&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The surface frontal surface of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_liftdest = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The amount of lift coefficient reduction with a fully extended brake. This is normally around 1.0, but must be experimented with. &lt;br /&gt;
 &lt;br /&gt;
 brake_cd = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag coefficient of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_superp = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Setting this to 1 enables superpositional mode. With this a brake can be added upon a wing and will have an effect on the lift and drag from the other wing panels only when the brake controller is on. When set to zero the wing panel is just a normal wing panel, that also has an airbrake/spoiler attached. Which to use depends on how the panelling of the wing is chosen. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Fuselage panel ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
The fuselage panel is a model of an aircraft fuselage. Its largest effect is to add drag to the aero model. &lt;br /&gt;
 &lt;br /&gt;
It is defined as &lt;br /&gt;
 &lt;br /&gt;
 fuselage &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    position = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Variable description: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Panel name &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position. This is the position where the drag force is applied, and does influence flight mechanics of your model, especially in spins. Start out by positioning this near to your model&#039;s centre of gravity. &lt;br /&gt;
 &lt;br /&gt;
 ref_area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference frontal area of the fuselage &lt;br /&gt;
 &lt;br /&gt;
 ref_volume = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference volume of the fuselage. In most cases, this can be set to 1.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_front = frontal_drag_filenamename (but without the .cd extension) &lt;br /&gt;
&lt;br /&gt;
The frontal drag is defined in a name.cd file that is placed in the airfoils directory. Use this file to finetune your model&#039;s glide polar. &lt;br /&gt;
 &lt;br /&gt;
 cd_side = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Sidewards drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 cd_top = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Top/bottom drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 k_y = 0.0 to 1.0 &lt;br /&gt;
 k_z = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
These two factors set the magnitude of instability of the fuselage. Try something like 0.1 first. A larger value means more instability. &lt;br /&gt;
 &lt;br /&gt;
 alpha_fuselage = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The fuselage&#039;s angle of incidence. Normally 0.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_landinggear = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag of an extended landing gear.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Linear aero model ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here are a sample aero.dat file when the linear aero model is used:&lt;br /&gt;
&lt;br /&gt;
 #-----------&lt;br /&gt;
 # Main wing&lt;br /&gt;
 #-----------&lt;br /&gt;
 wing_area               = 17.0&lt;br /&gt;
 wing_span               = 12.0&lt;br /&gt;
 mean_chord              = 1.5&lt;br /&gt;
 k_factor                = 1.5&lt;br /&gt;
 &lt;br /&gt;
 #------------------&lt;br /&gt;
 # Control surfaces&lt;br /&gt;
 #------------------&lt;br /&gt;
 aileron_limits          = [ -23.0 20.0 ]&lt;br /&gt;
 elevator_limits         = [ -23.0 28.0 ]&lt;br /&gt;
 rudder_limits           = [ -16.0 16.0 ]&lt;br /&gt;
 &lt;br /&gt;
 flap_min                = 0.0&lt;br /&gt;
 flap_max                = 1.0&lt;br /&gt;
 flap_eff                = 0.2&lt;br /&gt;
 &lt;br /&gt;
 #--------------------------&lt;br /&gt;
 # Aerodynamic coefficients&lt;br /&gt;
 # --------------------------&lt;br /&gt;
 c_lift_0                = 0.410&lt;br /&gt;
 c_lift_a                = 5.143&lt;br /&gt;
 c_lift_elev             = 0.340&lt;br /&gt;
 c_drag_0                = 0.08&lt;br /&gt;
 c_drag_i                = 0.08&lt;br /&gt;
 c_side_beta             = -0.31&lt;br /&gt;
 c_side_rudder           = 0.25&lt;br /&gt;
 c_yaw_beta              = 0.165&lt;br /&gt;
 c _yaw_rudder            = -0.25&lt;br /&gt;
 c_yaw_aileron           = 0.0&lt;br /&gt;
 c_yaw_roll_rate         = 0.0&lt;br /&gt;
 yaw_damping             = -0.099&lt;br /&gt;
 c_pitch_0               = 0.02&lt;br /&gt;
 c_pitch_a               = -0.8&lt;br /&gt;
 c_pitch_elev            = -0.7&lt;br /&gt;
 c_pitch_dot_a           = 0&lt;br /&gt;
 pitch_damping           = -12.4&lt;br /&gt;
 c_roll                  = 0.178&lt;br /&gt;
 roll_damping            = -0.47&lt;br /&gt;
&lt;br /&gt;
Here, a conventional coefficient based model is used to simulate the aircraft. If you have experience with such models you might recongnise the parameters and what they do.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft Physics]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
	<entry>
		<id>http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=88</id>
		<title>Aero.dat</title>
		<link rel="alternate" type="text/html" href="http://wiki.silentwings.no/index.php?title=Aero.dat&amp;diff=88"/>
		<updated>2007-03-06T10:27:35Z</updated>

		<summary type="html">&lt;p&gt;Ola: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The aero.dat configuration file describes the aerodynamic properties of the flight model. Currently, Silent Wings has two different aerodynamic models to choose from: The &amp;quot;panel model&amp;quot; and the &amp;quot;linear&amp;quot; model. &lt;br /&gt;
&lt;br /&gt;
For all player-controlled aircraft the panel model is recommended. This way of modelling has become quite popular in flight simulators, and is also sometimes called &amp;quot;Blade Element Theory&amp;quot; which is a method commonly used to simulate propellers. Silent Wings uses an extended Blade Element Theory on the propeller model, whereas the Panel Model is modified even more to be suited for a fixed-wing aircraft, even with low aspect ratio wings.  &lt;br /&gt;
&lt;br /&gt;
The linear model is implemented for use on autopilot controlled aircraft such as the towplane, and will only behave realistic at a small speed range. See the end of this article for a brief description of the linear model file format.&lt;br /&gt;
&lt;br /&gt;
The Silent Wings panel model describes the geometrical design of the aircraft that is to be simulated. By manually dividing an aircraft into segments, or &amp;quot;panels&amp;quot;, the flight dynamics code can calculate the forces that act on the aircraft and let it fly. The panel model works with two different panels: wingpanels and fuselage panels. The Wing panels are used to describe the wings and fins on the aircraft. Every wing panel needs an airfoil to do the aerodynamic definition, so these airfoils need to be defined as well. &lt;br /&gt;
&lt;br /&gt;
The airfoils can be shared between panels of the same wing, and are therefor defined before the wing panels. You must define one airfoil for each wing (or fin), also when they all would use the same airfoil, because the airfoil is defined with 3-dimensional properties (aspect ratio of wing, etc). You may, however, use several airfoils for a single wing, if you like.&lt;br /&gt;
&lt;br /&gt;
== Example file ==&lt;br /&gt;
&lt;br /&gt;
This is an example aero.dat file, taken from the SG38 model. It shows how to quicly create a usable aero model. Below, all options are described. For a more advanced aero.dat example, take a look at the Antares 20E aero model.&lt;br /&gt;
&lt;br /&gt;
 # SG38 Panelmodel data file &lt;br /&gt;
 # Part of Silent Wings&lt;br /&gt;
 # Ola Røer Thorsen 25.10.2004&lt;br /&gt;
 &lt;br /&gt;
 # General things&lt;br /&gt;
 plane_name		= SG 38&lt;br /&gt;
 plane_description	= Schulgleiter&lt;br /&gt;
 &lt;br /&gt;
 # Airfoil data. Note: these are &amp;quot;finite wing airfoils&amp;quot;, not&lt;br /&gt;
 # 2-dimensional data.&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= mainwing&lt;br /&gt;
    profile	= goe533&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 6.5&lt;br /&gt;
    meanchord	= 1.5&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= elevator&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k		= 1.2&lt;br /&gt;
    aspectratio	= 3.1&lt;br /&gt;
    meanchord	= 1.0&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 airfoil {&lt;br /&gt;
    name	= rudder&lt;br /&gt;
    profile	= naca0012f60&lt;br /&gt;
    k           = 1.2&lt;br /&gt;
    aspectratio = 1.1&lt;br /&gt;
    meanchord   = 1.2&lt;br /&gt;
    cd_adjust   = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 # The panels&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= 1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff   = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= left wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;left wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 #area		= 4.5&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 -1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing tip&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 4.15 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 aileron_mix	= -1.0&lt;br /&gt;
 aileron_delta	= 30.0&lt;br /&gt;
 aileron_diff    = 1.5&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= right wing root&lt;br /&gt;
 dep_panels	= [ &amp;quot;right wing tip&amp;quot; ]&lt;br /&gt;
 airfoil	= mainwing&lt;br /&gt;
 area		= 5.0&lt;br /&gt;
 meanchord	= 1.5&lt;br /&gt;
 position	= [ 0.0 1.5 -0.5 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= -3.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= elevator&lt;br /&gt;
 airfoil	= elevator&lt;br /&gt;
 area		= 3.1&lt;br /&gt;
 meanchord	= 1.0&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha 		= -3.0&lt;br /&gt;
 dihedral	= 0.0&lt;br /&gt;
 delta_max	= 25.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral	= 0.0&lt;br /&gt;
 elevator_mix	= 1.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 wingpanel {&lt;br /&gt;
 name		= rudder&lt;br /&gt;
 dep_panels     = [ elevator ]&lt;br /&gt;
 airfoil	= rudder&lt;br /&gt;
 area		= 1.5&lt;br /&gt;
 meanchord	= 1.2&lt;br /&gt;
 position	= [ -3.5 0.0 -0.6 ]&lt;br /&gt;
 alpha		= 0.0&lt;br /&gt;
 dihedral	= 90.0&lt;br /&gt;
 delta_max	= 30.0&lt;br /&gt;
 delta_min	= -25.0&lt;br /&gt;
 delta_neutral  = 0.0&lt;br /&gt;
 rudder_mix	= 1.0&lt;br /&gt;
 broken_drag    = 0.3&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
 fuselage {&lt;br /&gt;
 name		= fuselage&lt;br /&gt;
 position	= [ 0.0 0.0 0.0 ]&lt;br /&gt;
 ref_area	= 12.53&lt;br /&gt;
 ref_volume	= 1.0&lt;br /&gt;
 cd_front	= sg38&lt;br /&gt;
 cd_side	= 0.05&lt;br /&gt;
 cd_top	        = 0.05&lt;br /&gt;
 k_y		= 0.0&lt;br /&gt;
 k_z		= 0.0&lt;br /&gt;
 alpha_fuselage = 0.0&lt;br /&gt;
 }&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Airfoils ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
An airfoil is defined like this: &lt;br /&gt;
 &lt;br /&gt;
 airfoil &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    profile = xx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
The variables to be defined are: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The name of the airfoil. This can be called whatever you like, and is the name to be used in the wing panels. &lt;br /&gt;
 &lt;br /&gt;
 profile = &amp;lt;name&amp;gt; &lt;br /&gt;
&lt;br /&gt;
There are [[Polar file formats | two airfoil file formats]] available. The &amp;lt;name&amp;gt; specifies the file name &#039;&#039;&#039;without&#039;&#039;&#039; the extension (.polar or .cl/.cd/.cm). The polar files are to be put in the Silent Wings/data/airfoils directory.&lt;br /&gt;
 &lt;br /&gt;
 k = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The &amp;quot;k&amp;quot; factor defines the induced drag finesse of the wing. A setting of 1.0 gives the optimum, planar wing with elliptical lift distribution. So any other planar wing will have a value higher than 1.0. &lt;br /&gt;
 &lt;br /&gt;
Wings with winglets may get values lower than 1.0. The best wings currently available (Antares) have a k factor of 0.95. &lt;br /&gt;
 &lt;br /&gt;
 aspectratio = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The aspect ratio of the wing that will use this airfoil. &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing that will use this airfoil &lt;br /&gt;
 &lt;br /&gt;
 cl_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
This factor can be used to fine-tune the lift curve. The variable is multiplied with the lift from the lift polar. Leave this to 1.0 when you start up, and use it as a last resort when fine tuning your model. &lt;br /&gt;
 &lt;br /&gt;
 cd_adjust = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
This factor can be used to fine-tune the drag curve. The variable is added to the drag polar. Use with caution. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Wing panel ==&lt;br /&gt;
 &lt;br /&gt;
A wingpanel is defined with &amp;quot;wingpanel&amp;quot; followed by brackets containing the wing panel variables, one variable per line. &lt;br /&gt;
 &lt;br /&gt;
 wingpanel &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    area = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 } &lt;br /&gt;
&lt;br /&gt;
A wing can be defined with one or several panels. For elevator and rudder surfaces, one panel is mostly sufficient. A main wing should have at least 4 panels in total (two left, two right). &lt;br /&gt;
 &lt;br /&gt;
When not defined, variables default to zero. That means, if certain things are not to be used on the wing panel (such as a spoiler), the variables do not have to be set. &lt;br /&gt;
 &lt;br /&gt;
Please see the example illustration of the Ventus aero model to get a picture of how the panels are defined. &lt;br /&gt;
 &lt;br /&gt;
Variable descriptions: &lt;br /&gt;
 &lt;br /&gt;
General data: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;text string&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Wing panel name &lt;br /&gt;
 &lt;br /&gt;
 airfoil = &amp;lt;text string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The airfoil to use. The name to use is the same as defined in one of the airfoil sections. &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position coordinate. See the illustration on how to define this point. &lt;br /&gt;
 &lt;br /&gt;
 area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Wing panel area &lt;br /&gt;
 &lt;br /&gt;
 meanchord = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The mean chord of the wing panel (not the wing!) &lt;br /&gt;
 &lt;br /&gt;
 alpha = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s angle of incident. &lt;br /&gt;
 &lt;br /&gt;
 dihedral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s dihedral angle. &lt;br /&gt;
 &lt;br /&gt;
 sweep = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The panel&#039;s sweep angle. &lt;br /&gt;
 &lt;br /&gt;
 propwash = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
If the panel is positioned behind a propeller, you can set this value higher than 0.0 to have a propwash effect on the panel. This will for example allow for rudder and elevator authority when standing still on the Antares model. &lt;br /&gt;
 &lt;br /&gt;
 Control surface variables: (can be left out if the panel has non controls) &lt;br /&gt;
&lt;br /&gt;
The control system of Silent Wings is quite flexible, and can handle more exotic designs like canards, v-tails and flying wings. You can add all the controllers to have an effect on every panel in different ways. &lt;br /&gt;
 &lt;br /&gt;
 delta_max = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s maximum (positive) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_min = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s minimum (negative) deflection angle, in degrees. &lt;br /&gt;
 &lt;br /&gt;
 delta_neutral = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The flap&#039;s position when the controls are centered &lt;br /&gt;
 &lt;br /&gt;
 aileron_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of aileron control that is to be applied to the flap. For the left wing, normally 1.0 is used, for the right wing -1.0. For less effect use smaller numbers. For no aileron control set to 0.0 or leave it out. &lt;br /&gt;
 &lt;br /&gt;
 aileron_delta = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The maximum difference in deflection between the left and right aileron. For example, if with fully deflected ailerons the left one is at +10 and the right one at -10, this value should be set to 20.0. &lt;br /&gt;
 &lt;br /&gt;
 aileron_diff = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Aileron differential. This factor will define how much more the up-going (negative) aileron will go up compared with the down-going one (positive). The value 1.0 (default) means equal  deflection in both directions. A setting of 2.0 means the up-going aileron will do twice as much deflection as the down-going aileron. This is common on sailplanes as it reduces the adverse yaw effect of the ailerons. &lt;br /&gt;
 &lt;br /&gt;
 flap_pos = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most positive flap setting in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 flap_neg = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
If the panel has flap control, set the most negative flap position in degrees here. &lt;br /&gt;
 &lt;br /&gt;
 elevator_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of elevator control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 rudder_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of rudder control that is to be applied to the flap. &lt;br /&gt;
 &lt;br /&gt;
 throttle_mix = -1.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
The amount of throttle control that is to be applied to the flap (this is rather uncommon, so it will mostly be left out. It can be used to compensate or emulate some throttle effects) &lt;br /&gt;
&lt;br /&gt;
Spoiler/airbrake variables: (can be left out if the panel has no airbrake or spoiler) &lt;br /&gt;
 &lt;br /&gt;
 brake_on = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Set this variable to 1 to enable the spoiler/airbrake &lt;br /&gt;
 &lt;br /&gt;
 brake_surface = &amp;lt;float&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The surface frontal surface of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_liftdest = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The amount of lift coefficient reduction with a fully extended brake. This is normally around 1.0, but must be experimented with. &lt;br /&gt;
 &lt;br /&gt;
 brake_cd = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag coefficient of the fully extended brake. &lt;br /&gt;
 &lt;br /&gt;
 brake_superp = 0 or 1 &lt;br /&gt;
&lt;br /&gt;
Setting this to 1 enables superpositional mode. With this a brake can be added upon a wing and will have an effect on the lift and drag from the other wing panels only when the brake controller is on. When set to zero the wing panel is just a normal wing panel, that also has an airbrake/spoiler attached. Which to use depends on how the panelling of the wing is chosen. &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Fuselage panel ==&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
The fuselage panel is a model of an aircraft fuselage. Its largest effect is to add drag to the aero model. &lt;br /&gt;
 &lt;br /&gt;
It is defined as &lt;br /&gt;
 &lt;br /&gt;
 fuselage &lt;br /&gt;
 { &lt;br /&gt;
    name = xxx &lt;br /&gt;
    position = xxx &lt;br /&gt;
    ... &lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
Variable description: &lt;br /&gt;
 &lt;br /&gt;
 name = &amp;lt;string&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Panel name &lt;br /&gt;
 &lt;br /&gt;
 position = [ x.x y.y z.z ] &lt;br /&gt;
&lt;br /&gt;
The panel position. This is the position where the drag force is applied, and does influence flight mechanics of your model, especially in spins. Start out by positioning this near to your model&#039;s centre of gravity. &lt;br /&gt;
 &lt;br /&gt;
 ref_area = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference frontal area of the fuselage &lt;br /&gt;
 &lt;br /&gt;
 ref_volume = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Reference volume of the fuselage. In most cases, this can be set to 1.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_front = frontal_drag_filenamename (but without the .cd extension) &lt;br /&gt;
&lt;br /&gt;
The frontal drag is defined in a name.cd file that is placed in the airfoils directory. Use this file to finetune your model&#039;s glide polar. &lt;br /&gt;
 &lt;br /&gt;
 cd_side = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Sidewards drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 cd_top = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
Top/bottom drag coefficient &lt;br /&gt;
 &lt;br /&gt;
 k_y = 0.0 to 1.0 &lt;br /&gt;
 k_z = 0.0 to 1.0 &lt;br /&gt;
&lt;br /&gt;
These two factors set the magnitude of instability of the fuselage. Try something like 0.1 first. A larger value means more instability. &lt;br /&gt;
 &lt;br /&gt;
 alpha_fuselage = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The fuselage&#039;s angle of incidence. Normally 0.0. &lt;br /&gt;
 &lt;br /&gt;
 cd_landinggear = &amp;lt;float&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The drag of an extended landing gear.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Linear aero model ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Here are a sample aero.dat file when the linear aero model is used:&lt;br /&gt;
&lt;br /&gt;
 #-----------&lt;br /&gt;
 # Main wing&lt;br /&gt;
 #-----------&lt;br /&gt;
 wing_area               = 17.0&lt;br /&gt;
 wing_span               = 12.0&lt;br /&gt;
 mean_chord              = 1.5&lt;br /&gt;
 k_factor                = 1.5&lt;br /&gt;
 &lt;br /&gt;
 #------------------&lt;br /&gt;
 # Control surfaces&lt;br /&gt;
 #------------------&lt;br /&gt;
 aileron_limits          = [ -23.0 20.0 ]&lt;br /&gt;
 elevator_limits         = [ -23.0 28.0 ]&lt;br /&gt;
 rudder_limits           = [ -16.0 16.0 ]&lt;br /&gt;
 &lt;br /&gt;
 flap_min                = 0.0&lt;br /&gt;
 flap_max                = 1.0&lt;br /&gt;
 flap_eff                = 0.2&lt;br /&gt;
 &lt;br /&gt;
 #--------------------------&lt;br /&gt;
 # Aerodynamic coefficients&lt;br /&gt;
 # --------------------------&lt;br /&gt;
 c_lift_0                = 0.410&lt;br /&gt;
 c_lift_a                = 5.143&lt;br /&gt;
 c_lift_elev             = 0.340&lt;br /&gt;
 c_drag_0                = 0.08&lt;br /&gt;
 c_drag_i                = 0.08&lt;br /&gt;
 c_side_beta             = -0.31&lt;br /&gt;
 c_side_rudder           = 0.25&lt;br /&gt;
 c_yaw_beta              = 0.165&lt;br /&gt;
 c _yaw_rudder            = -0.25&lt;br /&gt;
 c_yaw_aileron           = 0.0&lt;br /&gt;
 c_yaw_roll_rate         = 0.0&lt;br /&gt;
 yaw_damping             = -0.099&lt;br /&gt;
 c_pitch_0               = 0.02&lt;br /&gt;
 c_pitch_a               = -0.8&lt;br /&gt;
 c_pitch_elev            = -0.7&lt;br /&gt;
 c_pitch_dot_a           = 0&lt;br /&gt;
 pitch_damping           = -12.4&lt;br /&gt;
 c_roll                  = 0.178&lt;br /&gt;
 roll_damping            = -0.47&lt;br /&gt;
&lt;br /&gt;
Here, a conventional coefficient based model is used to simulate the aircraft. If you have experience with such models you might recongnise the parameters and what they do.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Aircraft Physics]]&lt;/div&gt;</summary>
		<author><name>Ola</name></author>
	</entry>
</feed>