FlightGear wiki - User contributions [en]

Howto:Make full spherical panorama

2015-02-22T13:59:52Z

Cri: add link to forum thread about full spherical panorama

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. To see many examples of spherical panorama, take a look at this forum thread: http://forum.flightgear.org/viewtopic.php?f=19&t=7713. The semi-automated process is useful for everyone that wants to contribute to the flightgear wiki by adding one of this panorama to each aircraft's page in order to display the cockpit. Here is an example of what can be achieved:

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|A full spherical panorama of the 3d cessna c172p cockpit]]

=== The tools ===
In order to take panorama in flightgear you need:
* of course [[Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

=== The automatic process ===
To make the process easier I've created a [[Nasal scripting language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
To get rid of the popup window telling you that the screenshots was saved, you can follow this guidance: http://forum.flightgear.org/viewtopic.php?f=17&t=13810#p140388

==== Taking the required screenshots ====
The easier way is to bind the following nasal script to a keyboard key (The {{key press|F3}} key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<syntaxhighlight lang="xml">
<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>
</syntaxhighlight>

Now substitute the [[Nasal scripting language|nasal]] code between the <script> tags with this:

<syntaxhighlight lang="nasal">
var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();
</syntaxhighlight>

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the {{key press|F3}} key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

==== Stitching the panorama with Hugin ====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

[[Category:Howto|Make full spherical panorama]]

Howto:Make full spherical panorama

2015-02-22T09:18:47Z

Cri: add tip to remove popup from screenshots

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that wants to contribute to the flightgear wiki by adding one of this panorama to each aircraft's page in order to display the cockpit. Here is an example of what can be achieved:

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|A full spherical panorama of the 3d cessna c172p cockpit]]

=== The tools ===
In order to take panorama in flightgear you need:
* of course [[Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

=== The automatic process ===
To make the process easier I've created a [[Nasal scripting language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
To get rid of the popup window telling you that the screenshots was saved, you can follow this guidance: http://forum.flightgear.org/viewtopic.php?f=17&t=13810#p140388

==== Taking the required screenshots ====
The easier way is to bind the following nasal script to a keyboard key (The {{key press|F3}} key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<syntaxhighlight lang="xml">
<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>
</syntaxhighlight>

Now substitute the [[Nasal scripting language|nasal]] code between the <script> tags with this:

<syntaxhighlight lang="nasal">
var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();
</syntaxhighlight>

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the {{key press|F3}} key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

==== Stitching the panorama with Hugin ====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

[[Category:Howto|Make full spherical panorama]]

Beechcraft B1900D

2014-08-18T16:56:31Z

Cri: Add template note and link

{{infobox Aircraft
|image = Beechcraft B1900D.png
|name = Beechcraft B1900D
|type = Airliner
|livery = Air New Zealand, Central Mountain Air, Northern Thunderbird Air
|liverydbid = 21
|authors = Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm = YASim
|status-fdm =
|status-systems =
|status-cockpit =
|status-model =
|fgname = b1900d
|download =
}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
[[File:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the AC BUSs above the generator switches
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
<ref>{{cite web |url=http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf |title=Beechcraft B1900D Aircraft Operating Manuals |publisher=SimPilots }}</ref>

== [[GPS]] ==
The B1900D is equipped with a functioning [[Avionics_and_instruments#Further_instruments|Bendix/King KLN 908]] [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== Liveries ==
Apart from the two liveries (SWISS AIR FORCE and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].
To create your own livery, a vector template (in svg format) is available in the [http://liveries.flightgear.org/download/paintkits/27.zip livery database].

== Notes ==
* The glas panel instruments (artificial horizon and horizontal situation indicator) don't show up with Rembrandt rendering
{{Appendix}}

{{Beechcraft}}

[[Category:Airliners]]
[[Category:Twin-engined aircraft]]
[[fr:Beechcraft B1900D]]
[[Category:Aircraft with Route Manager support]]

FlightGear Newsletter August 2014

2014-08-13T20:04:33Z

Cri:

{{Newsletter-header|August 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|3.2 Released}}<br/><br/>
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-item|FGCamera 1.0 Released}}<br />
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
{{Newsletter-cover-item|Yongphulla Domestic Airport - VQ10}}<br/>
{{Newsletter-cover-header|Other}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}}<br/>
{{Newsletter-cover-item|Beechcraft B1900d template}}<br/>
{{Newsletter-cover-header|Multiplayer events}}<br/>
|}
</div>
==3.2 Released==
The FlightGear development team is delighted to announce that the long awaited v3.2 release of FlightGear, the free, open-source flight simulator has been released on  INSERT FINAL RELEASE DATE HERE. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include ...

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v3.2 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!
''Read more at: [[Next Changelog|Version 3.2 Changelog]]''

==Development news==
===FGCamera 1.0 Released===
{{#ev:youtube|DMZB7QXpR9I|250|right|FGCamera v1.0 in action}}
FGCamera v1.0 is available to download. Features of current version:
* 4 camera types:
** Virtual cockpit,
** Aircraft (look-at),
** Aircraft (look-from),
** World (look-from);
* Arbitrary number of preset views;
* Smooth/discrete transition between the views of the same camera type.

v1.0 has graphical user interface to create and manage camera views:

<gallery widths=200px heights=200px>
Fgcamera main dialog.jpg|Main dialog with cameras management tools.
Fgcamera new camera dialog.jpg|Dialog used to create new cameras. Four camera types are available
Fgcamera camera settings dialog.jpg|Settings for currently selected camera
</gallery>
Read more at updated [http://wiki.flightgear.org/FGCamera FGCamera wiki article].

==Scenery corner==
===Yongphulla Domestic Airport - VQ10===
High mountains, deep valleys, strong winds and sometimes the rain may appear as something like snow. You are at the bhutanese '''[[Yongphulla Airport|Yongphula Domestic Airport]]''' (VQ10) at a height of 2573 metres. After [[Paro Airport|Paro]], also this airport has been improved. Besides the Terminal and Apron, shared models and other little things have now been added. [[TerraSync]] has it all! Have a nice flight in the Kingdom of Bhutan.
<gallery mode=packed heights=240px>
VQ10 Yongphula Airport.jpg|Yonghula Airport
VQ10 Yongphula Apron.jpg|Tower and Terminal of Yongphula
</gallery>

==Scenery corner==
===Beechcraft B1900d template===
A new template for the [http://wiki.flightgear.org/Beechcraft_B1900D B1900d] is available in the [http://liveries.flightgear.org/paintkits.php Paintkits] section of the [http://liveries.flightgear.org/ flightgear liveries database website]. The template comes in svg format (best used with [http://www.inkscape.org inkscape]) features:
* full rivets, panel lines and stencils details in vector format
* ambient occlusion layer
* dirt layer
Many B1900d liveries made with this template are available to download in the [http://liveries.flightgear.org/aircraft.php?limit=25&display=2&page=0&id=21 flightgear liveries database website]
<gallery mode=packed heights=240px>
B1900d_template.jpg|B1900d template painted/unpainted
</gallery>

FlightGear Newsletter August 2014

2014-08-13T19:56:22Z

Cri: Add b1900d template image

{{Newsletter-header|August 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|3.2 Released}}<br/><br/>
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-item|FGCamera 1.0 Released}}<br />
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
{{Newsletter-cover-item|Yongphulla Domestic Airport - VQ10}}<br/>
{{Newsletter-cover-header|Other}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}}<br/>
{{Newsletter-cover-item|Beechcraft B1900d template}}<br/>
{{Newsletter-cover-header|Multiplayer events}}<br/>
|}
</div>
==3.2 Released==
The FlightGear development team is delighted to announce that the long awaited v3.2 release of FlightGear, the free, open-source flight simulator has been released on  INSERT FINAL RELEASE DATE HERE. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include ...

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v3.2 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!
''Read more at: [[Next Changelog|Version 3.2 Changelog]]''

==Development news==
===FGCamera 1.0 Released===
{{#ev:youtube|DMZB7QXpR9I|250|right|FGCamera v1.0 in action}}
FGCamera v1.0 is available to download. Features of current version:
* 4 camera types:
** Virtual cockpit,
** Aircraft (look-at),
** Aircraft (look-from),
** World (look-from);
* Arbitrary number of preset views;
* Smooth/discrete transition between the views of the same camera type.

v1.0 has graphical user interface to create and manage camera views:

<gallery widths=200px heights=200px>
Fgcamera main dialog.jpg|Main dialog with cameras management tools.
Fgcamera new camera dialog.jpg|Dialog used to create new cameras. Four camera types are available
Fgcamera camera settings dialog.jpg|Settings for currently selected camera
</gallery>
Read more at updated [http://wiki.flightgear.org/FGCamera FGCamera wiki article].

==Scenery corner==
===Yongphulla Domestic Airport - VQ10===
High mountains, deep valleys, strong winds and sometimes the rain may appear as something like snow. You are at the bhutanese '''[[Yongphulla Airport|Yongphula Domestic Airport]]''' (VQ10) at a height of 2573 metres. After [[Paro Airport|Paro]], also this airport has been improved. Besides the Terminal and Apron, shared models and other little things have now been added. [[TerraSync]] has it all! Have a nice flight in the Kingdom of Bhutan.
<gallery mode=packed heights=240px>
VQ10 Yongphula Airport.jpg|Yonghula Airport
VQ10 Yongphula Apron.jpg|Tower and Terminal of Yongphula
</gallery>

==Scenery corner==
===Beechcraft B1900d template===
A new template for the [http://wiki.flightgear.org/Beechcraft_B1900D B1900d] is available in the [http://liveries.flightgear.org/paintkits.php Paintkits] section of the [http://liveries.flightgear.org/ flightgear liveries database website]. The template comes in svg format (best used with [http://www.inkscape.org inkscape]) features:
* full rivets, panel lines and stencils details in vector format
* ambient occlusion layer
* dirt layer
Some B1900d liveries made with this template are available to download in the [http://liveries.flightgear.org/aircraft.php?limit=25&display=2&page=0&id=21 flightgear liveries database website]
<gallery mode=packed heights=240px>
B1900d_template.jpg|B1900d template painted/unpainted
</gallery>

File:B1900d template.jpg

2014-08-13T19:53:49Z

Cri: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Template for B1900d}}
|date=2014-08-13 21:52:52
|source={{own}}
|author=[[User:Cri|Cristian Marchi]]
|permission=
|other_versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-3.0}}

[[Category:Template, paintkits]]

FlightGear Newsletter August 2014

2014-08-13T19:51:00Z

Cri: Add news about the new b1900d template

{{Newsletter-header|August 2014}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-item|3.2 Released}}<br/><br/>
{{Newsletter-cover-header|Development news}}<br/>
{{Newsletter-cover-item|FGCamera 1.0 Released}}<br />
| valign="top" width="33%" |
{{Newsletter-cover-header|Scenery corner}}<br/>
{{Newsletter-cover-item|Yongphulla Domestic Airport - VQ10}}<br/>
{{Newsletter-cover-header|Other}}<br/>
| valign="top" width="33%" |
{{Newsletter-cover-header|In the hangar}}<br/>
{{Newsletter-cover-item|Beechcraft B1900d template}}<br/>
{{Newsletter-cover-header|Multiplayer events}}<br/>
|}
</div>
==3.2 Released==
The FlightGear development team is delighted to announce that the long awaited v3.2 release of FlightGear, the free, open-source flight simulator has been released on  INSERT FINAL RELEASE DATE HERE. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include ...

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v3.2 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!
''Read more at: [[Next Changelog|Version 3.2 Changelog]]''

==Development news==
===FGCamera 1.0 Released===
{{#ev:youtube|DMZB7QXpR9I|250|right|FGCamera v1.0 in action}}
FGCamera v1.0 is available to download. Features of current version:
* 4 camera types:
** Virtual cockpit,
** Aircraft (look-at),
** Aircraft (look-from),
** World (look-from);
* Arbitrary number of preset views;
* Smooth/discrete transition between the views of the same camera type.

v1.0 has graphical user interface to create and manage camera views:

<gallery widths=200px heights=200px>
Fgcamera main dialog.jpg|Main dialog with cameras management tools.
Fgcamera new camera dialog.jpg|Dialog used to create new cameras. Four camera types are available
Fgcamera camera settings dialog.jpg|Settings for currently selected camera
</gallery>
Read more at updated [http://wiki.flightgear.org/FGCamera FGCamera wiki article].

==Scenery corner==
===Yongphulla Domestic Airport - VQ10===
High mountains, deep valleys, strong winds and sometimes the rain may appear as something like snow. You are at the bhutanese '''[[Yongphulla Airport|Yongphula Domestic Airport]]''' (VQ10) at a height of 2573 metres. After [[Paro Airport|Paro]], also this airport has been improved. Besides the Terminal and Apron, shared models and other little things have now been added. [[TerraSync]] has it all! Have a nice flight in the Kingdom of Bhutan.
<gallery mode=packed heights=240px>
VQ10 Yongphula Airport.jpg|Yonghula Airport
VQ10 Yongphula Apron.jpg|Tower and Terminal of Yongphula
</gallery>

==Scenery corner==
===Beechcraft B1900d template===
A new template for the [http://wiki.flightgear.org/Beechcraft_B1900D B1900d] is available in the [http://liveries.flightgear.org/paintkits.php Paintkits] section of the [http://liveries.flightgear.org/ flightgear liveries database website]. The template comes in svg format (best used with [http://www.inkscape.org inkscape]) features:
* full rivets, panel lines and stencils details in vector format
* ambient occlusion layer
* dirt layer
Some B1900d liveries made with this template are available to download in the [http://liveries.flightgear.org/aircraft.php?limit=25&display=2&page=0&id=21 flightgear liveries database website]

FlightGear Newsletter November 2013

2013-11-28T07:50:02Z

Cri: typo in ALS section

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter. Core developers are encouraged to add news about their latest work to the newsletter's development section and [[Next Changelog|the changelog of the upcoming release]]. At the end of each month, it's generally a good idea to get in touch with other contributors to ask them to add news about their contributions to the newsletter.''

Available in: '''English'''
Please help us translate in other languages!

== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].

=== Atmospheric Light Scattering ===

The Atmospheric Light Scattering rendering framework adopts a technique that has recently been introduced for the default and the Rembrandt rendering framework which allows to utilize a global map of Ocean water depth. This allows to render the shallow waters around islands in a compelling way. Combined with the ability of ALS to change the basic water color based on location and weather conditions/sky appearance, many combination of shallows, mud content and weather conditions can now be addressed by the highest detail water shader effect.

[[File:Depth01.jpg|400px|Water depth mapping in ALS]]

=== Initial OsgEarth integration ===

Thanks to recent work by forum user '''poweroftwo''' we now have initial osgEarth integration featuring a runtime selectable option for the terrain scene in FlightGear. Once enabled, osgEarth renders the terrain scene by building the textured geometry at runtime from raw source imagery and elevation data. Load times for an unvisited location are surprisingly fast given a respectable Internet download rate. For locations previously visited, an optimized file cache data is saved for rapid loading.

Input data can come from a variety of sources including web mapping services or local source data (e.g. geotiff) stored on disk. Once rendering is enabled, the entire FlightGear terrain scene graph is replaced along as well as the scene elevation queries. However, the native terrain implementation remains fully intact and can be restored by disabling osgEarth from its configuration dialog.

The benefits gained from this initial osgEarth integration include geo-specific imagery rendered in real-time from a variety of sources that are available worldwide; tiled terrain on demand; and high altitude views from anywhere above the earth. However, this implementation with FlightGear includes some notable limitations listed in the compromises section.

{{#ev:youtube|0aUZTvpdLFU}} {{#ev:youtube|dZ5JuQ9ZDEQ}}

Learn more at http://forum.flightgear.org/viewtopic.php?f=6&t=21351

=== Getting started with CppBind ===

FlightGear's built-in [[Nasal]] scripting language comes with a set of standard libraries, and can be extended using FlightGear specific APIs.

Until FlightGear 2.8, the [[Nasal]] scripting engine only provided a C API to expose such hooks/bindings to scripting space or to expose scripting space data structures back to C/C++.

Exposing simulator internals to scripting space is a fairly common and useful thing, because it enables base package developers to access these internals without having to build FlightGear from source, so the barrier to entry is significantly lower and we've seen an increasing number of novel features purely implemented in scripting space, due to powerful APIs being available to aircraft developers and other base package developers.

Unlike the core Nasal engine itself (which is C), FlightGear however is mostly written and being developed in C++. For quite a while, that meant that the Nasal APIs were a bit low-level, and sometimes also awkward to use when making functions, data structures or objects accessible between C++ and Nasal.

Thanks to Tom's [[Canvas]] system, there's now a new bindings framework to be found in simgear/nasal/cppbind. This is fully object oriented and supports modern C++ features.

You will find that most of the "old" code in $FG_SRC/Scripting still uses those old C-APIs for interacting with the Nasal engine. Only the new code, #include'ing <simgear/nasal/cppbind>, uses boost templates to hide low level details.

Most of the code in the Nasal subsystem itself (FGNasalSys) also still uses the legacy C APIs - this is just to explain the two approaches, to avoid unnecessary confusion. You will find the old, low-level APIs explained at [[Howto:Extend Nasal]].

The cppbind framework is much more generic and high level than the bare C APIs, cppbind includes unit testing support and makes use of modern C++ features like templates and STL support, including SimGear specific types like SGPath/SGGeod etc, its overhead is fairly small (not just performance, but also LoC to create new bindings). The cppbind framework is already extensively used by the Canvas system and the NasalPositioned_cppbind bindings, both of which are a good place to look for code examples.

Continue reading at [[Nasal/CppBind]]...

=== FGRun repository changes ===
The [http://gitorious.org/fg/fgrun FGRun Git repository] now uses the same branch concept as FlightGear and SimGear. Current development takes place in the <code>next</code> branch, while <code>release/X.X</code> branches are created for each release. In addition to that the FGRun version number is now in sync with FlightGear/SimGear, to make it easier to see whether your FGRun and FlightGear builds match.

=== The Walker ===
The Walker is currently made portable to be easily incorporated in arbitrary Aircraft. Additionally, an animatable Pilot Model for Cockpit Placement is in development. Walker and Crew will be supporting different Hand Poses, such as pointing, a Fist, thumbsup or a Victory Sign.

[[File:Walker Waldo.png|400px|The male Walker]]
[[File:Walker Amelie.png|400px|The female Walker]]
[[File:Walker pilot model.png|400px|A Pilot Model, Co-Pilot and Crew are to come.]]
[[File:Walker hand poses.png|400px|Hand Poses that will be selectable within the Animation Dialog]]

=== Random Buildings ===

=== Canvas System ===

=== High Level Architecture ===

=== Usability Improvements ===

=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done. Fundamentally we need more core devs.

If you are interested in contributing as a core developer, please see [[Howto:Start core development]].

== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Nasal Internals for hackers: Intern'ing symbols ==
''Contributed by Philosopher''

As some of you experienced Nasal/C-code hackers should recall, or even those familiar with scripting languages internals, namespaces are just hashes, with keys representing symbols - right? Well yes, mostly, but each of those symbols are unique in a way from all of the other strings out there: they're interned. (Interning is a process that takes strings and a dictionary and returns a matching string, adding one if needed. That means equal strings are substituted so they have the same pointer, i.e. one string represents all instances of "io", stored in a pool/hash of all used symbols.) Though these interned strings appear at runtime in the keys in namespaces, they get created during code generation (codegen), where the symbols (TOK_SYMBOL) get converted to Nasal strings, are interned to get the correct string (using the globals->symbols hash), and are stored in the naCode's constants' block. From there, the symbol-strings are used to set and get various lvalues (both local/global symbols and objects' members) in an optimized way (that's the whole point of the exercise). Looking at hash.c, there are some specialized functions that make use of the potential optimizations:

* naiHash_sym (looks up an interned symbol)
* naiHash_newsym (adds a symbol in the first empty slot for the hashcode)

(There's another that looks similar, naiHash_tryset, but it does not deal with interned symbols: it uses the findkey() method, which in turn uses the equals() method that checks for more general key equality instead of simple pointer equality.)

The first, naiHash_sym, is pretty neat and the prime example of the optimization: it runs through a hashcode's potential slots, checking only pointer equality (note that interned symbols' hashcodes are computed during interning, so that's another step that doesn't have to be done are runtime). naiHash_newsym is another nice optimization but a little problematic, due to its assumption that the key doesn't exist already. It's basically used for adding another argument as a local key, but it doesn't care about if it exists already, it just sees an occupied slot and keeps going. Consider the following example that illustrates calling with an argument into a hash that already has the argument's key in it:

<syntaxhighlight lang="nasal">
var f_creates_arg = func(arg...) {
foreach (var k; keys(caller(0)[0]))
print(k);
debug.dump(arg);
}
call(f_creates_arg, nil, nil, {arg:nil}); # call into namespace: arg=nil; with arguments of: arg=[]
</syntaxhighlight>

This should print:
<pre>
arg
arg
nil
</pre>

This shows that the key is being set twice (which violates a normal precondition of hashes): once as an argument and once to create an existing key in the namespace. The one set first is the one being picked up (e.g. the arg in {arg:nil} versus the arg... that equals []). And this behavior persists even through resizing: hashset() (which is used to reinitialize a hash after reallocation) only keeps appending keys in empty slots, so the number of keys doesn't change (even if there are multiple of the same keys).

For this reason, I would suggest amending naiHash_newsym to check keys' pointer equality before continuing; that way symbols aren't "trodden" over like this. (Please note that if "arg" exists in the hash as non-interned, then it will be trodden over anyways; having to look for non-interned symbols would mainly violate the point of the optimization at this step, and doesn't actually matter in the long run.) I would argue that finding an existing key (a few simple pointer comparisons!) would be more efficient generally, because the hash would never need to be resized if an existing one is found, whereas the old version would append regardless. (I think I once counted well over a hundred "arg" symbols in the __js0 namespace from the continual firing of bindings, which obviously isn't good.)

Continue reading at [http://forum.flightgear.org/viewtopic.php?f=30&t=21308&p=193935#p193935].

== New software tools and projects ==

== FlightGear addons and mods ==
====New textures and lightmaps for random buildings====

New textures and lightmaps for the random buildings areas.
[[File:Lightmap terrain at noon.png|thumb|220px|Lightmap terrain at noon]]
[[File:Lightmap terrain at night.png|thumb|220px|Lightmap terrain at night]]
The urban lightmap works using a modified urban shader + modified urban effect, the modified files need to be improve to make work the original urban shader when the random building function is off and enable new shader when the random building function is on.

Installation:

1- unzip the file

2- copy, paste and replace
a) urban.eff at $FG ROOT/Effects/
b) urban.frag , urban-gbuffer.frag and urban-lightfield.frag at $FG ROOT/Shaders/
c) buildings.png and buildings-lightmap at $FG ROOT/Textures/

3- i suggest to change the random building density to the middle of your computer default settings, you can make this by edit at autosave.xml or autosave_2_12.xml (depend your version), at the line "<building-density type="double">1</building-density>"

4- FAQ

Where is $FG ROOT? please click [[$FG ROOT|here]]

Where is autosave.xml or autosave_2_12.xml? please click [[FlightGear configuration via XML|here]]

If you want to go back to the default effects, please download this package and follow the installation instructions again

Download from [https://www.dropbox.com/s/r3o06xtxn9gp27m/New_Urban_effects.zip here]

Download default textures and effects from [https://www.dropbox.com/s/75jodt5psqc5yzl/Default_eff.zip here]

<gallery>
File:Lightmap terrain at dusk.png
File:Large building lights.png
File:City at night.png
File:Reflection map at dusk.png
File:Reflection map at night.png
</gallery>
== In the hangar ==
==== Tupolev Tu-134 ====

[[File:Tu134_aeroflot.png|thumb|270px|The "whistle" taking speed for take-off.]]

[[File:Tu-134 liveries nose.gif|thumb|270px|You can choose one of the 3 noses.]]

The [[Tupolev Tu-134]] dev team proudly announce a new soviet airliner for FlightGear! Some have already read a topic about it at the Forum. The release of version 1.0 is underway and will arrive soon. This YAsim aircraft has a very good FDM, great exterior and a basic cockpit. To contribute (read improve cockpit for example) contact us at the [http://forum.flightgear.org/viewtopic.php?f=4&t=15908 forum]

'''Promo movie'''

{{#ev:youtube|IbUMgRvEih0}}

Many Thanks to Helijah, Buckaroo, Cossack90.
=== New aircraft ===
The Oasis of the Seas has been released to the public and getting updates, it's sister ships and ferries are coming in from the ACJZA Hangar as well! If you have any skill with coding, it'll be thankful if you could help me. http://forum.flightgear.org/viewtopic.php?f=4&t=21277
=== Updated aircraft ===
'''EC130-B4 Ecostar'''
[[File:EC130 MedFlight N130NE.jpg|thumb|The EMS variant of EC130-B4, used by MedFlight, Ohio, USA]]
[[File:EC130 Grand Canyon Helicopters.jpg|thumb|New Livery of Grand Canyon Helicopters]]
The EC130 helicopter is on short final for a new major upgrade.
The existing model, which already had been of very high quality, has been refined in various aspects with lots of effort. The outside model has been enriched to a degree which should justify a '''5*''' rating.

The '''Rotorhead''' has been brought to a new level of detail, a full detailed '''Fenestron''' was added and animations were introduced to all moving parts.
[[File:EC130 Mainrotor front.png|thumb|closeup of EC130 Mainrotor, fully animated in all details]]
[[File:EC130 Config.jpg|thumb|EC130 fully integrated configuration dialog]]
[[File:EC130 Help.jpg|thumb|EC130 Help screen with all shortcuts and additional info]]

'''Cockpit''' was enriched for Pilot/Copilot controls, seats are textured now and a variable cabin configuration allows to set up an '''Emergency Medical Services (EMS) variant''', which comes preconfigured with a new Livery of '''N130NE MedFlight''' (Ohio).

Fans of '''Grand Canyon Helicopters''' now find a livery of the N155GC and the colorful painting in red/gold.

A lot of '''equipment''' (most of which was there already but hidden) can now be used, including a full blown '''SX16-Nightsun searchlight'''.

All of this has been brought together in a fully integrated configuration dialog which allows to set-up livery, fuel, extra views, weights, cabin setup and equipment.

Extra gimmics include a fully animated pilot, glass reflection on windows and front shield and variable rotor wakes depending on the strength of the downwash.

'''If you can't wait''' for the next release '''[https://gitorious.org/ec130/ec130/source/7fec576b77e7ff573a4c71907262f5aff06de086: check it out from the Git-Hangar]'''

<gallery>
File:EC130 Fenestron.jpg|A closeup of the full detailed fenestron
File:EC130 snowshoes hook.jpg|EC130 fitted with Snowshoes and Hook
File:EC130 stretcher.png|EC130 cabin configuration (EMS) with Stretcher
File:EC130-B4 MedFlight using SX-16 Nightsun.jpg|EC130 Helicopter using the SX-16 Nightsun searchlight
</gallery>

'''Some of the most interesting changes:'''

* '''Mainrotor''' fully animated and adapted to original
* '''Fenestron''' fully designed and animated, incl. control rod
* '''Cockpit Controls''' added: Stick, Collective, Pedals, Co-Pilot Controls (optional)
* '''Doors''' movable
* '''Searchlight'''
* '''Snowshoes'''
* '''Hoist/Hook'''
* '''Checklists''' implemented with conditional display
* '''Pilot''': ''fully animated''
* '''Autostart/Autoshutdown''' enabled after 15 flights
* '''Rotor-Wakes''' off-low-medium-high cyclable
* '''Sound improved''' (doors moving, low/high rotor rpm, overspeed)

'''Things on stack for FG 3.0 include:'''
* Rembrandt support
* BUG fixing

=== Liveries ===

== Scenery corner ==
=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

== Wiki updates ==
=== Translators required ===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}

== Community news ==
=== FlightGear on YouTube ===

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

To learn more about how the project works, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971 this short essay] written by Thorsten, for a more detailed article see [[How the FlightGear project works]].

=== Call for volunteers ===
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support

=== Did you know ===

[[Category:FlightGear Newsletter|2013 11]]
[[Category:Changes after 2.12]]

FlightGear Newsletter February 2012

2012-02-25T09:16:04Z

Cri: formatting

{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}
{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear 2.6.0 released ==
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.

== Development news ==

=== Heads up: Project Rembrandt ===
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].

{|
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]
|}

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== A new instrument: Vertical Situation Display ===
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).

This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD.

To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].

=== Glider winch launching ropes ===
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch.

[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:

* '''Strop''' (3 m) attached to the glider with a ring.
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.
* '''Trace''' (17 m)
* '''Parachute''' so the cable doesn't drop too quickly after releasing.
* '''Launch cable''' the longest part; all the way to the winch.

=== New aircraft ===
==== Hawker Siddeley Harrier GR.1 ====
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]].

It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control.

The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.

==== Boeing-Sikorsky RAH-66 Commanche ====
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj who later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]), help in development would be welcome.

It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. Automatic Flight Control System includes Stability Augmentation System, Control Augmentation System and Auto Hover.

=== Updated aircraft ===
==== Boeing 787-8 Dreamliner ====
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0.
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.

The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.

You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.

==== Cessna 337G Skymaster ====
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update.

The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.

New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.

=== Liveries ===

== Scenery corner ==
=== 3D-Model contributors: please read ===
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.
So, here they are: http://scenemodels.flightgear.org/contribute.php .
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .

=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers -this is now also true for FlightGear.
21 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.
{|
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]
|}

=== New textures for container ship and freighter AI models ===
[[File:Ships-comparison.png|200px|thumb|right|Comparison between untextured and textured AI ships (by Cristian Marchi)]]
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

[[File: Lightfield-1.1-14.jpg | 800px]]

A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).

== Suggested flights ==
===Copacabana to San Rafael over Lake Titicaca===
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.

*More places you can visit can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. Please note when uploading images that it's important to give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.

A good example comes from Michat who has designed new small logos for [[IAR80|Aircraft of the Month]], [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircrafts, allowing you to see at a glance which aircraft has some of those interesting features.

[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]
[[File:Aircraftofthemonth.png|IAR80]].

===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on YouTube ===
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?
Usually, an animation looks like this
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<property>foo/bar</property>
[..]more elements[..]
</animation>
</syntaxhighlight>
You can add a scaling factor or an offset to it, but that's basically all you can do that way.
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions.
Here is an example for a translate animation depending on two properties and the cosine function
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.

[[Category:FlightGear Newsletter|2012 02]]

FlightGear Newsletter February 2012

2012-02-25T09:14:50Z

Cri: layout

{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}
{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear 2.6.0 released ==
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.

== Development news ==

=== Heads up: Project Rembrandt ===
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].

{|
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]
|}

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== A new instrument: Vertical Situation Display ===
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).

This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD.

To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].

=== Glider winch launching ropes ===
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch.

[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:

* '''Strop''' (3 m) attached to the glider with a ring.
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.
* '''Trace''' (17 m)
* '''Parachute''' so the cable doesn't drop too quickly after releasing.
* '''Launch cable''' the longest part; all the way to the winch.

=== New aircraft ===
==== Hawker Siddeley Harrier GR.1 ====
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]].

It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control.

The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.

==== Boeing-Sikorsky RAH-66 Commanche ====
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj who later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]), help in development would be welcome.

It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. Automatic Flight Control System includes Stability Augmentation System, Control Augmentation System and Auto Hover.

=== Updated aircraft ===
==== Boeing 787-8 Dreamliner ====
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0.
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.

The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.

You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.

==== Cessna 337G Skymaster ====
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update.

The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.

New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.

=== Liveries ===

== Scenery corner ==
=== 3D-Model contributors: please read ===
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.
So, here they are: http://scenemodels.flightgear.org/contribute.php .
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .

=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers -this is now also true for FlightGear.
21 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.
{|
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]
|}

=== New textures for container ship and freighter AI models ===
[[File:Ships-comparison.png|250px|thumb|right|Comparison between untextured and textured AI ships (by Cristian Marchi)]]
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

[[File: Lightfield-1.1-14.jpg | 800px]]

A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).

== Suggested flights ==
===Copacabana to San Rafael over Lake Titicaca===
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.

*More places you can visit can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. Please note when uploading images that it's important to give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.

A good example comes from Michat who has designed new small logos for [[IAR80|Aircraft of the Month]], [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircrafts, allowing you to see at a glance which aircraft has some of those interesting features.

[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]
[[File:Aircraftofthemonth.png|IAR80]].

===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on YouTube ===
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?
Usually, an animation looks like this
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<property>foo/bar</property>
[..]more elements[..]
</animation>
</syntaxhighlight>
You can add a scaling factor or an offset to it, but that's basically all you can do that way.
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions.
Here is an example for a translate animation depending on two properties and the cosine function
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.

[[Category:FlightGear Newsletter|2012 02]]

FlightGear Newsletter February 2012

2012-02-25T09:11:18Z

Cri: Document the new textures for freighter and container ships

{{draft|newsletter|Feel free to contribute! Or [[FlightGear Newsletter January 2012|read the latest edition]].}}
{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== FlightGear 2.6.0 released ==
Following our [[release plan]], version 2.6.0 of our simulator has been released. Please check the [[changelog 2.6.0]] for what has changed since our last release 6 months ago.

== Development news ==

=== Heads up: Project Rembrandt ===
As many of you may have heard already, Fred is currently making huge progress on adding shadows to FlightGear in [[Project Rembrandt]]. Now, F-JJTH ported the P92 to use the new system and posted a youtube video demonstrating [[Project Rembrandt]] at work. To provide feedback, please check out the the [http://flightgear.org/forums/viewtopic.php?f=47&t=14883 forum thread].

{|
|{{#ev:youtube|v02phoOqWHE|400|Project Rembrandt at work}}
|[[File:Project-rembrandt-cockpit-lighting.png|600px|Cockpit lighting in Project Rembrandt at work (by F-JJTH)]]
|}

== Interview with a contributor (NAME) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* How long have you been involved in FlightGear?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?

More questions are being collected here: [[Interview questions]].

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== A new instrument: Vertical Situation Display ===
[[File:Omega95-vsd-instrument.jpeg|200px|thumb|Omega95's VSD instrument]]
Omega95 has created an entirely new instrument type for FlightGear, a so called Vertical Situation Display (VSD).

This was done entirely in scripting space using Nasal and XML animations. He's basically proven everbody wrong who ever claimed that complex instruments couldn't yet be created in scripting space. Apparently, he managed to create this instrument in less than 24 hrs. His first question related to this was about accessing trigonometric functions from Nasal, shortly thereafter he posted screen shots depicting his VSD.

To read up on the whole discussion, please see [http://flightgear.org/forums/viewtopic.php?f=30&t=15200 the forum topic]. There's work ongoing to turn his project into a new tutorial for the wiki on creating complex instruments in scripting space: [[Howto: Implement a Vertical Situation Display in Nasal]].

=== Glider winch launching ropes ===
[[File:DG-101G_winch_launch_with_rope.png|thumb|200px|A DG-101G during a winch launch.]]
Before now, FlightGear never showed ropes during winch launching. However, now, you will no longer have to fly gliders while being pulled by some invisible connection between you and the winch.

[[User:Gijs|Gijs]] started working on an animated 3D rope, attached to the glider and winch. The cable exist of the following parts:

* '''Strop''' (3 m) attached to the glider with a ring.
* '''Weak link assembly''' designed to break apart before the cable or any other equipment fails.
* '''Trace''' (17 m)
* '''Parachute''' so the cable doesn't drop too quickly after releasing.
* '''Launch cable''' the longest part; all the way to the winch.

=== New aircraft ===
==== Hawker Siddeley Harrier GR.1 ====
[[File:Harrier-GR1 Splash.png|thumb|200px|Harrier GR.1 splash screen]]
[[Hawker Siddeley Harrier GR1]] is a private project by pjedvaj, it was not intended to replace or update the existing [[British Aerospace Harrier]].

It has a detailed 3D model complete with a cockpit, animations and RAF livery. Instruments and HUD are also fairly authentic. The aircraft has working ADEN guns and basic fuel and weight control.

The FDM is adapted from the original BAe Harrier, but internal and external fuel tank capacities are modified to match the GR.1 version.

==== Boeing-Sikorsky RAH-66 Commanche ====
[[File:RAH-66 splash.png|thumb|200px|RAH-66 splash screen]]
[[Boeing-Sikorsky RAH-66 Commanche]] was started as a [[Bounty/RAH-66 Comanche|bounty]] by sgofferj and developed by pjedvaj who later withdraw from the bounty. This was my first helicopter project and FDM development is curently in stub (RAH-66 is using adapted FDM from Tatsuhiro Nishioka's [[Kawasaki OH-1]]), help in development would be welcome.

It has a detailed 3D model, animations and two liveries used to present different variants of RAH-66. Helicopter has a working XM301 cannon controled by joystick and basic weight control for armament in internal bays. Automatic Flight Control System includes Stability Augmentation System, Control Augmentation System and Auto Hover.

=== Updated aircraft ===
==== Boeing 787-8 Dreamliner ====
[[File:boeing-787-8-splash.png|thumb|200px|The Boeing 787-8 Splash Screen]]
The Boeing 787-8 Dreamliner has already been there in FlightGear for a very long time -it has been in the FG official hangar since version 1.0.
However, it was created while the 787 was still a prototype aircraft; it did not correctly show many of the 787's actual features like a realistic glass cockpit and accurate instruments.

The new/updated Boeing 787-8 is a community project that features new JSBSim flight dynamics, Vertical Navigation, a realistic 787 glass cockpit, new CDUs, Electronic Flight Bags, TCAS, advanced Nav Displays, [[Howto:_Implement_a_Vertical_Situation_Display_in_Nasal|Vertical Situation Display]], [[Howto:_Implement_a_Fly-By-Wire_System_for_Airliners|Fly-by-wire]] and a lot of other neat features. It has not exactly been completed and the project is still running.

You can find out more about the Boeing 787-8 Project HERE or wait for a while till a wiki page is created for it. One of the really good points of this project is how most of our findings and resources have been converted into Wiki HowTos for other aircraft developers to use for their projects.

==== Cessna 337G Skymaster ====
[[File:Cessna337-cockpit.png|thumb|200px|General view of the new Cessna 337G Skymaster cockpit]]
The [[Cessna 337G Skymaster]] from the Spain-Latinamerica "Vive FlightGear" factory have received a major update.

The new cockpit is now totally modelled, almost buttons and knobs are functional, animated, and properly labeled for easy identification.

New custom sounds, lights, controls, a Bendix/King avionics pack capable of full IFR and night navigation, 2 new HQ liveries and the first FlightGear's working [[ELT]] (Emergency Locator Transmitter) are part of this great improvement on a FlightGear aircraft.

=== Liveries ===

== Scenery corner ==
=== 3D-Model contributors: please read ===
A (long) time ago, specific instructions were given on how to contribute with 3D-models designing withing FG. That is: I want to create nice 3D models for my airport, submit them to the central database, and have them shipped back through Terrasync.
However, it appears that quite a lot of users are still not aware of those guidelines, and sometimes learn about their existence after having created their models.
So please, take some time to (re)read them, and inform the people around you who would like to contribute about the existence of those guidelines. This will save you extra time (and your models will be quickly inserted within the database) and this will also save the (precious) times of the poor guy(s) validating all the models at the other end.
So, here they are: http://scenemodels.flightgear.org/contribute.php .
We also remind you that, to add, edit or delete shared model positions (apart from mass import (that is if you have more than let's say 10 lines to add), you should use our webtools at http://scenemodels.flightgear.org/submission/ .

=== Shanghai Skylines: FG's New (not-so-)Hidden Gem ===
Shanghai is one of the biggest city in China and is among the cities with the most number of skyscrapers -this is now also true for FlightGear.
21 models were created over the past few months by JVC, who also modeled the Akashi-Kaikyo Bridge in Japan and the United Nations building in New York.
{|
|[[File:SH fgfs-screen-001.png|250px|thumb|A view of the Shanghai skyline]]
|[[File:Shanghai003.png|250px|thumb|Another view of Shanghai]]
|[[File:Shanghai007.png|250px|thumb|A closer view from near the Shanghai Stock Exchange]]
|}

=== New textures for container ship and freighter AI models ===
Starting from a hi-res panorama that he made, user Cristian Marchi (aka penta) provided new skins for the two AI ships that populates seas in flightgear. More info on the [http://www.flightgear.org/forums/viewtopic.php?f=23&t=14856 forum thread].
{|
|[[File:Ships-comparison.png|250px|thumb|right|Comparison between untextured and textured AI ships (by Cristian Marchi)]]
|}

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==

[[File: Lightfield-1.1-14.jpg | 800px]]

A P-51D flying at 20.000 ft over Juneau (Alaska) at dawn using lightfield shaders to render the sunrise (see [http://www.flightgear.org/forums/viewtopic.php?f=47&t=14755 here] for the shader package for download).

== Suggested flights ==
===Copacabana to San Rafael over Lake Titicaca===
Bolivia to Peru. This trip will lead you over one of the highest and deepest lakes in the world towards the highest airfield in the world. It a demonstration of a [[IFR]] flight towards a fix and a demonstration how accurate FlightGear simulates air density and the effects it has on aircraft.
[[File:Slcc-sprf.jpg|thumb|200px|left|Flight and fix SLCC to SPRF]]
Place your aircraft on the airfield [http://en.wikipedia.org/wiki/Copacabana,_Bolivia SLCC, Copacabana], with an [[elevation]] of 12,592 feet. FlightGear will show snow all around you but that is not very realistic so let's clean up. View=> Rendering Options=> Snow line=> Set to max. (5,000M).

We will fly towards and land at SPRF. If you would enter SLCC and SPRF in [[Kelpie]] planner you probably would not be able to find SPRF. To find SPRF I am adding an additional VOR-DME station and for a good fix give you another VOR-DME. Try Kelpie planner to plan this route and compare with this suggestion.

Equipment preparation. Set [[NAV1]] to [http://en.wikipedia.org/wiki/Juliaca Juliaca] VOR-DME on 155.55 with a radial of 311° (magnetic). Set [[NAV2]] to Arequipa VOR-DME on 113.7 with a radial of 212°. During our flight we will fly with [[true altitude]] as set with [[QNH]], keep QNH updated. Arm the autopilot with the [[heading bug]] at 311° and an initial altitude of 13,500 feet.

Take off and if you took the wrong RW pull up hard. Take a small tour over [http://en.wikipedia.org/wiki/Titicaca lake Titicaca], see the floating islands and try to find the lost golden treasure. Intercept the nearest radial on NAV1 towards Juliaca (about 311°).

Just before Juliaca is a hill so while on lake Titicaca increase altitude to 14,200 feet, the [[VFR]] part of this trip is over. After passing Juliaca set the radial of NAV1 to 352° and set the altitude to 17,422 feet. We will fly from NAV1 and slowly increase altitude.

At a distance of about 60 NM set the heading bug on the current course. Monitor the distance to NAV1, the radial of NAV2 and the distance to NAV2. At a distance of 74.5 NM to NAV1, a distance of 140.7 NM and at the '''radial''' intercept of NAV2 should be the runway. So, from 60 NM onwards, look outside the window, then at NAV1 and then NAV2 etc.

If you are at 80NM to NAV1 you have missed the airfield but you still won't hit any hills (unless you bank left). Bank right and set the heading bug to 172°. Fly back towards NAV1 and intercept the radial 352° at about 50NM again to repeat the search.

The runway SPRF, San Rafael, has a elevation of 14,422 feet and a heading of 297°/ 117°. Our initial altitude has been set 3,000NM above the RW elevation. That should give sufficient room for navigation.

After you have seen the airfield set the radial of NAV1 to 297°, the heading of the runway (not the course to the runway) as a visual aid. Land on RW 30 (and not on RW 12 unless you are a show-off). Oh, there is a small hill in front of RW 30, just so you know.

Decreasing speed at this altitude can be a bit tricky. The air is thin and does not give much resistance. Next to that, the difference between [[indicated airspeed]] and [[ground speed]] is very noticeable. The ground speed is much higher as the indicated airspeed.

After a successful landing, try to discover the [[Suggested_Flights#Origin_of_the_Amazon_River | origin of the Amazon river]] since we are now at the starting point of that trip.

*More places you can visit can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
[[User:Johan G|Johan G]] did a great job starting to categorise all images. The sub-categories are listed under [[:Category:Images]]. Please note when uploading images that it's important to give the file a descriptive name. That'll make it easier for others to find your file and use it in articles.

A good example comes from Michat who has designed new small logos for [[IAR80|Aircraft of the Month]], [[Dual Control]], [[Bombable]], [[Soaring]], [[Howto:_Do_aerotow_over_the_net|Aerotow]] and [[:Category:Aerospace|Aerospace]] aircrafts, allowing you to see at a glance which aircraft has some of those interesting features.

[[File:Dualcontrolready2.png|Dual_control]] [[File:BombableReady.png|Bombable]] [[File:Aerotowready.png|Doing aerotow over the net]] [[File:Thermalready.png|Soaring]] [[File:Spacetripready.png|Aerospace]]
[[File:Aircraftofthemonth.png|IAR80]].

===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on YouTube ===
* [http://youtu.be/hBEaOMzBq6E KSFO Thermal Demo] by MD-BFC Going on their way for Bocian certification
* [http://youtu.be/-yI5PzC5RE8 Sukhoi 37 'The russian dream'] by Águilas de FlightGear performing "Balalaika amok" master tune by Aleksei Arkhipovsky.

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can use expressions to create complex animations of objects in your 3d models or even drive them from multiple properties?
Usually, an animation looks like this
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<property>foo/bar</property>
[..]more elements[..]
</animation>
</syntaxhighlight>
You can add a scaling factor or an offset to it, but that's basically all you can do that way.
If you want to animate your object following a complex function, most people create complex Nasal scripts to compute the driving properties, probably not knowing that there is another way to achieve the goal: Expressions.
Here is an example for a translate animation depending on two properties and the cosine function
<syntaxhighlight lang="xml">
<animation>
<type>translate</type>
<expression>
<product>
<property>/my/factor-property</property>
<cos>
<deg2rad>
<property>/my/angular-property</property>
</deg2rad>
</cos>
</product>
</expression>
[..]more elements[..]
</animation>
</syntaxhighlight>
A rich set of predefined functions is available, including almost all those you have on your scientific pocket calculator.

[[Category:FlightGear Newsletter|2012 02]]

File:Ships-comparison.png

2012-02-25T09:05:53Z

Cri: Comparison between untextured and textured AI ships

Comparison between untextured and textured AI ships

FlightGear livery database

2012-02-02T18:49:34Z

Cri: typo

[[File:Livery database dhc-6 images.png|thumb|250px]]
[[File:Livery Database Stats.png|thumb|250px]]
The '''FlightGear livery database''' hosts [[Livery over MP|liveries]] and paintkits for [[FlightGear]] [[aircraft]], as [http://liveries.flightgear.org/contribute.php contributed] by users and developers.

Only liveries that flew, fly or are certain to fly in the near future are accepted, adding to the realism of the whole simulation. All liveries and paintkits are released under the GNU GPL license and are free to download.

== History ==
The database was started in February 2009 by [[User:Gijs|Gijs]], as a place to collect liveries. At that time there was no standard in how to name liveries, not much support in how to create liveries and no place to submit liveries and share them with other users. The initial database was hosted on a free domain, which had its obvious disadvantages. In December 2009, a paid domain was offered by [http://atiak.com Airborne Technologies]. This brought a whole lot of new possibilities, including a MySql and PHP driven database. Nowadays those are the languages used to run the database.

Over the past years, the database has been extended with many functions. Including personal pages - listing an author's liveries, thumbnails, and more recently an option to control various layout aspects has been added.

On January 20, 2012 all liveries that lacked a download were deleted from the server. Most of those got lost when the former server suddenly quit (all the way back in December 2009). As we were able to save the list of liveries, they ended up in the database eventough the files got lost. To save liveries from future server failures, backups are nowadays made on a regularly basis.

=== Milestones ===
* February 2009: database started
* December 22, 2009: moved to the current domain
* June 29, 2011: 500th livery
* October 8, 2011: 600th livery

== External link ==
* [http://liveries.flightgear.org FlightGear livery database]
* [http://www.flightgear.org/forums/viewforum.php?f=13 Subforum] dedicated to liveries

[[Category:Community]]
[[Category:FlightGear]]
[[Category:GPL]]

FlightGear livery database

2012-02-02T18:47:58Z

Cri: typo

[[File:Livery database dhc-6 images.png|thumb|250px]]
[[File:Livery Database Stats.png|thumb|250px]]
The '''FlightGear livery database''' hosts [[Livery over MP|liveries]] and paintkits for [[FlightGear]] [[aircraft]], as [http://liveries.flightgear.org/contribute.php contributed] by users and developers.

Only liveries that flew, fly or are certain to fly in the near future are accepted, adding to the realism of the whole simulation. All liveries and paintkits are released under the GNU GPL license and are free to download.

== History ==
The database was started in February 2009 by [[User:Gijs|Gijs]], as a place to collect liveries. At that time there was no standard in how to name liveries, not much support in how to create liveries and no place to submit liveries and share them with other users. The initial database was hosted on a free domain, which had its obvious disadvantages. In December 2009, a paid domain was offered by [http://atiak.com Airborne Technologies]. This brought a whole lot of new possibilities, including a MySql and PHP driven database. Nowadays those are the languages used to run the database.

Over the past years, the database has been extended with many functions. Including personal pages - listing an author's liveries, thumbnails, and more recently an option to control various layout aspects has been added.

On January 20, 2012 all liveries that lacked a download were deleted from the server. Most of those got lost when the former server suddenly quit (all the way back in December 2009). As we were able to save the list of liveries, they ended up in the database eventough the files got lost. To save liveries from future server failures, backups are nowadays made on a regularly basis.

=== Milestones ===
* Februari 2009: database started
* December 22, 2009: moved to the current domain
* June 29, 2011: 500th livery
* October 8, 2011: 600th livery

== External link ==
* [http://liveries.flightgear.org FlightGear livery database]
* [http://www.flightgear.org/forums/viewforum.php?f=13 Subforum] dedicated to liveries

[[Category:Community]]
[[Category:FlightGear]]
[[Category:GPL]]

Beechcraft B1900D

2011-12-24T08:23:33Z

Cri:

{{infobox Aircraft
|image = Beechcraft B1900D.png
|name = Beechcraft B1900D
|type = Airliner
|livery = Air New Zealand, Central Mountain Air, Northern Thunderbird Air
|authors = Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm = YASim
|status-fdm =
|status-systems =
|status-cockpit =
|status-model =
|fgname = b1900d
|download =
}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
[[File:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
Source: [http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf SimPilots]

== [[GPS]] ==
The B1900D is equipped with a functioning Bendix/King KLN 908 [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== Liveries ==
Apart from the two liveries (SWISS AIR FORCE and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].

== See also ==
* [[Table of models]]
* [[FlightGear 1.0 default aircraft]]

{{Beechcraft}}

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]
[[Category:Beechcraft]]

Beechcraft B1900D

2011-12-24T08:22:41Z

Cri:

{{infobox Aircraft
|image = Beechcraft B1900D.png
|name = Beechcraft B1900D
|type = Airliner
|livery = Air New Zealand, Central Mountain Air, Northern Thunderbird Air
|authors = Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm = YASim
|status-fdm =
|status-systems =
|status-cockpit =
|status-model =
|fgname = b1900d
|download =
}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
[[File:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
Source: [http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf SimPilots]

== [[GPS]] ==
The B1900D is equipped with a functioning Bendix/King KLN 908 [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== Liveries ==
Apart from the two liveries (SWISS ARMY and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].

== See also ==
* [[Table of models]]
* [[FlightGear 1.0 default aircraft]]

{{Beechcraft}}

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]
[[Category:Beechcraft]]

Beechcraft B1900D

2011-12-24T08:21:53Z

Cri: Add a paragraph about liveries

{{infobox Aircraft
|image = Beechcraft B1900D.png
|name = Beechcraft B1900D
|type = Airliner
|livery = Air New Zealand, Central Mountain Air, Northern Thunderbird Air
|authors = Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm = YASim
|status-fdm =
|status-systems =
|status-cockpit =
|status-model =
|fgname = b1900d
|download =
}}
[[File:b1900d-cockpit-pano.jpg|thumb|270px|[[Howto: Make full spherical panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

The '''Beechcraft 1900''' series [[aircraft]] is the most popular 19-passenger [[:Category:Airliners|airliner]] in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the [[Beechcraft|Beechcraft Division]] of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The Beechcraft B1900D is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
[[File:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

=== [[V Speeds]] ===
{| class="wikitable"
|-
|Stall speed, dirty (Vs0)||88 kts
|-
|Stall speed, clean (Vs1)||104 kts
|-
|Best angel of climb (Vx)||123 kts
|-
|Best rate of climb (Vy)||135 kts
|-
|Maneuvering speed (Va)||184 kts
|-
|Never exceed speed (Vne)||247 kts
|}
Source: [http://aerolinea.simpilots.es/descargas/Beechcraft_b1900d.pdf SimPilots]

== [[GPS]] ==
The B1900D is equipped with a functioning Bendix/King KLN 908 [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== [[Liveries]] ==
Apart from the two liveries (SWISS ARMY and AIR NEW ZEALAND) that comes with the b1900d aircraft, it is possible to download more on the [http://liveries.flightgear.org/aircraft.php?display=2&id=21 FlightGear Livery Database].

== See also ==
* [[Table of models]]
* [[FlightGear 1.0 default aircraft]]

{{Beechcraft}}

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]
[[Category:Beechcraft]]

Howto:Use the normal map effect in aircraft

2010-12-31T10:42:42Z

Cri: Further detail on file naming

FlightGear 2.0.0 introduces Effects, a powerful way to use Shaders within FG without having to write C code. As of March 2010, FlightGear Git has a Normal Map effect (Effects/bumpspec.eff), which provides both bump mapping and specular mapping. This Howto provides a tutorial on using this Effect for aircraft. Similar techniques can be used to use other Effects on aircraft.

If you don't know how a Normal Map works, have a look [http://en.wikipedia.org/wiki/Normal_mapping here].

The latest documentation on the FlightGear Effects system is to be found in [http://gitorious.org/fg/fgdata/blobs/master/Docs/README.effects $FG_ROOT/Docs/README.effects]

==Creating the Normal Map==

To create the Normal Map, there are two options.

We can use a plugin that can convert a 2D texture representing height to a set of normals. There is a good [http://registry.gimp.org/node/69 normalmap plugin] for GIMP available. Those on Ubuntu should be able to install it directly from the package manager.

On the other hand, we can create a high polygon density model of the object in a 3D editor, and generate the normal map from this model. You can find more informations on this approach , applied to blender, [http://wiki.blender.org/index.php/Doc:Manual/Textures/Maps/Bump_and_Normal_Maps here]

=== Lets see the 2D approach first: ===

Once you have the GIMP plugin installed, create the normal map as follows.

# Identify an object that you intend to apply the normal map to using Blender AC3D etc.
# Find the part of the texture (the texture coordinates) that apply to the object. Given that most aircraft textures are sensibly organized, this should be straightforward. The same texture coordinates will be used for the normal map.
# Open the texture in GIMP and create a new layer with black as the background color. We'll use the existing texture as a guide to creating the normalmap.
# Adjust the opacity of the new layer so you can see the texture underneath. This layer will be a height map, with black representing low points, and white representing very raised points. So, at the moment the entire height map is at sea level.
# Now use whatever painting technique you wish to draw the height. If you want well-defined edges, draw using a sharp-edged tool.

[[Image:normalmap1.png|thumb|Height Map with original texture]]

# Once you are satisfied with your height map, delete the background layer, increase the opacity back to 100% and save it as a new file.
# Now we need to convert the height map to a normal map. To do this, use Filters->Map->Normalmap. If this is not present, you haven't installed the normalmap plugin as described above.
# The default options will work fine, except that you should invert the Y axis (as OpenGL vectors origin is the bottom left rather than top left). However, the author of the plugin recommends the Prewitt 5x5 filter. Once you are happy with the options, press OK, and your image should turn generally blue, but with some strange colours around the areas that you coloured white. This is the normal map.
# Optionally, modify the transparency of the map to alter shininess. Fully opaque texture means maximum shininess. Fully transparent means no shininess, but often other channel are also erased, so to not loose the normal information, always keep a little bit of opacity. You can alter the texture with the eraser tool or use a layer mask. You may want to try to use a noise pattern in the layer mask to simulate dirt and wear on the airframe.
# Save off the normal map as a new png file in your aircraft directory, remembering the correct path.

=== Now lets see the 3D approach ===
( this method is independent of the above instruction, and can be done apart )

# In Blender, you created a low poly count model. This is the one that will be exported to FlightGear. Let's call it "low poly"
# Create a UV mapping for this object ( edit mode, select all, U ), then associate a new image to this UV mapping ( UV/image editor, new )
# Duplicate the "low poly" object, and call the new copy "High poly".
# Add details to the "high poly" model, where needed. ( don't MOVE the new copy ! This methods needs that both copies share the same center to work. You could use layers to clarify the viewport when working). You could use "multires", or subsurf modifiers, or you could even do the job by hand. The sculpture tools of blender can be handy too. The workflow depends only on your habits !

Once you are satisfied with the detail level of the "high poly" copy, it is time to create the normal map from this copy, and to transfer it to the "low poly" copy. Blender's powerful interface allows to do this in a single operation :

# In object mode, FIRST select the "high poly" object, THEN "SHIFT-select" the "low poly" object to add it to the selection.
# In the "scene" buttons ( F10 ) , click on the "bake" tab, and make sure you check the "selected to active" and "normals" options. In the menu under "dist" and "bias", choose 'tangent' as the normal space. You can leave 'quad split auto' at the bottom.
# It is wise to specify a bleeding margin in the "margin" option, to ensure the texture will cover the faces entirely. A dozen pixels is usually enough for FG.
# When everything is set, click the big "bake" button. If you followed the instructions carefully, you should see your normal map appear in the UV/image editor. Save it as a png file, and remember where you saved it.

Unfortunately, the space axes of blender and those of the FlightGear shader are different... You will need to invert the X and Y axes of your normal map, or the effect will look inverted. This is easy :

# Open your normal map in GIMP, and go to "Colors -> Components -> Decompose". Choose the RVB option, and "decompose as layers". Validate.
# In the new image that opens, invert the values in the RED and GREEN layers.
# Again, go to "Colors -> Components", but now, "Compose". Choose the RVB option.
# A new image opens, quite similar to the original, but with slight differences. Save this image.

While the main blue tone remains, if you look closely , you will notice that the red and green levels have been inverted. Your normal map is now ready to be used by the FlightGear shader.

Despite it is more complex, this method allows to generate complicated displacement effects, in a much more accurate way than using converted relief maps. This way it is possible to work on 3 axes, to simulate folds, concave zones, etc...etc, all this keeping total control on the desired effect amount, just be sculpting the high poly model accordingly. You can see an image tutorial of this technique [http://vi-wer.de.tl/Normalmap-Tutorial.htm here]

[[Image:normalmap2.png|thumb|Final normal map]]

==Creating the Normal Map Effect==

Now we have our normal map, we need to apply it to the aircraft. To do this, we need to create a new effect, based on the existing Effect/bumpspec.eff, and then apply it to the correct object in the model.

# Open Effect/bumpspec.eff. You'll find some instructions at the top of the file.
# Copy the first set of XML (between the <PropertyList> and </PropertyList> tags) into a new .eff file in your aircraft directory (e.g. if you want to apply the effect to wings, create the file bumpspec-wing.eff in aircraft-name/Models/Effects/)
# Edit the new file so that it has an appropriate <name> entry and an <image> entry that matches the normal map you created above. For example, in this case we've created the effect Aircraft/c172p/Models/Effects/bumpspec-wing, and are using the normal map Aircraft/c172p/Models/Liveries/wing-normal.png.

<code>
<PropertyList>
<name>Aircraft/c172p/Models/Effects/bumpspec-wing</name>
<inherits-from>Effects/bumpspec</inherits-from>
<parameters>
<texture n="2">
<image>Aircraft/c172p/Models/Liveries/wing-normal.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
</parameters>
</PropertyList>
</code>

Now we have a new effect, which is based on the original Effects/bumpspec.eff, but which uses our own normalmap.

==Applying the Effect to the model==

Finally, we need to apply the Effect to the model. This is very straightforward. Simply add a section to the model .xml file indicating the Effect you want to use and the object it should apply to.

For example:
<code>
<effect>
<inherits-from>Aircraft/c172p/Models/Effects/bumpspec-wing</inherits-from>
<object-name>wing_1</object-name>
</effect>
</code>

Now load your model and admire the Effect:

[[Image:normalmap3.png|thumb|Cessna with normal map]]

==Final Notes==

* The normal map uses the same texture coordinates as the original texture. However, the normal map does not need to be the same dimensions, so you can use a smaller or larger normal map if you need to.
* You'll need to define a different Effect for each normal map you use. Effectively this means that if you have two objects using different textures, they will need separate effects.
* The bumpspec.eff Effect uses the alpha (transparency) channel on the normal map to set specularity of the point (e.g. shininess). This can be used to make raised parts shiny.
* If you find that the effect is too pronounced, try varying the scaling in the normalmap filter. 0.1 seems to work well for "rivet" effects.
* Make sure all the faces of the object that you assign the effect to have a texture assigned to them, otherwise you will cause a crash in the OpenGL layer (below OSG), because the effect's tangent and binormal vectors are computed using object's texture mapping coordinates. If you try to feed an untextured object to the generator, it should abort with a null vector, and then passing this null vector to the driver leads to a segfault.

[[fr:Tutoriel: Usage de l'effet de Normal Maps]]

Howto:Use the normal map effect in aircraft

2010-12-31T10:06:04Z

Cri: typo

FlightGear 2.0.0 introduces Effects, a powerful way to use Shaders within FG without having to write C code. As of March 2010, FlightGear Git has a Normal Map effect (Effects/bumpspec.eff), which provides both bump mapping and specular mapping. This Howto provides a tutorial on using this Effect for aircraft. Similar techniques can be used to use other Effects on aircraft.

If you don't know how a Normal Map works, have a look [http://en.wikipedia.org/wiki/Normal_mapping here].

The latest documentation on the FlightGear Effects system is to be found in [http://gitorious.org/fg/fgdata/blobs/master/Docs/README.effects $FG_ROOT/Docs/README.effects]

==Creating the Normal Map==

To create the Normal Map, there are two options.

We can use a plugin that can convert a 2D texture representing height to a set of normals. There is a good [http://registry.gimp.org/node/69 normalmap plugin] for GIMP available. Those on Ubuntu should be able to install it directly from the package manager.

On the other hand, we can create a high polygon density model of the object in a 3D editor, and generate the normal map from this model. You can find more informations on this approach , applied to blender, [http://wiki.blender.org/index.php/Doc:Manual/Textures/Maps/Bump_and_Normal_Maps here]

=== Lets see the 2D approach first: ===

Once you have the GIMP plugin installed, create the normal map as follows.

# Identify an object that you intend to apply the normal map to using Blender AC3D etc.
# Find the part of the texture (the texture coordinates) that apply to the object. Given that most aircraft textures are sensibly organized, this should be straightforward. The same texture coordinates will be used for the normal map.
# Open the texture in GIMP and create a new layer with black as the background color. We'll use the existing texture as a guide to creating the normalmap.
# Adjust the opacity of the new layer so you can see the texture underneath. This layer will be a height map, with black representing low points, and white representing very raised points. So, at the moment the entire height map is at sea level.
# Now use whatever painting technique you wish to draw the height. If you want well-defined edges, draw using a sharp-edged tool.

[[Image:normalmap1.png|thumb|Height Map with original texture]]

# Once you are satisfied with your height map, delete the background layer, increase the opacity back to 100% and save it as a new file.
# Now we need to convert the height map to a normal map. To do this, use Filters->Map->Normalmap. If this is not present, you haven't installed the normalmap plugin as described above.
# The default options will work fine, except that you should invert the Y axis (as OpenGL vectors origin is the bottom left rather than top left). However, the author of the plugin recommends the Prewitt 5x5 filter. Once you are happy with the options, press OK, and your image should turn generally blue, but with some strange colours around the areas that you coloured white. This is the normal map.
# Optionally, modify the transparency of the map to alter shininess. Fully opaque texture means maximum shininess. Fully transparent means no shininess, but often other channel are also erased, so to not loose the normal information, always keep a little bit of opacity. You can alter the texture with the eraser tool or use a layer mask. You may want to try to use a noise pattern in the layer mask to simulate dirt and wear on the airframe.
# Save off the normal map as a new png file in your aircraft directory, remembering the correct path.

=== Now lets see the 3D approach ===
( this method is independent of the above instruction, and can be done apart )

# In Blender, you created a low poly count model. This is the one that will be exported to FlightGear. Let's call it "low poly"
# Create a UV mapping for this object ( edit mode, select all, U ), then associate a new image to this UV mapping ( UV/image editor, new )
# Duplicate the "low poly" object, and call the new copy "High poly".
# Add details to the "high poly" model, where needed. ( don't MOVE the new copy ! This methods needs that both copies share the same center to work. You could use layers to clarify the viewport when working). You could use "multires", or subsurf modifiers, or you could even do the job by hand. The sculpture tools of blender can be handy too. The workflow depends only on your habits !

Once you are satisfied with the detail level of the "high poly" copy, it is time to create the normal map from this copy, and to transfer it to the "low poly" copy. Blender's powerful interface allows to do this in a single operation :

# In object mode, FIRST select the "high poly" object, THEN "SHIFT-select" the "low poly" object to add it to the selection.
# In the "scene" buttons ( F10 ) , click on the "bake" tab, and make sure you check the "selected to active" and "normals" options. In the menu under "dist" and "bias", choose 'tangent' as the normal space. You can leave 'quad split auto' at the bottom.
# It is wise to specify a bleeding margin in the "margin" option, to ensure the texture will cover the faces entirely. A dozen pixels is usually enough for FG.
# When everything is set, click the big "bake" button. If you followed the instructions carefully, you should see your normal map appear in the UV/image editor. Save it as a png file, and remember where you saved it.

Unfortunately, the space axes of blender and those of the FlightGear shader are different... You will need to invert the X and Y axes of your normal map, or the effect will look inverted. This is easy :

# Open your normal map in GIMP, and go to "Colors -> Components -> Decompose". Choose the RVB option, and "decompose as layers". Validate.
# In the new image that opens, invert the values in the RED and GREEN layers.
# Again, go to "Colors -> Components", but now, "Compose". Choose the RVB option.
# A new image opens, quite similar to the original, but with slight differences. Save this image.

While the main blue tone remains, if you look closely , you will notice that the red and green levels have been inverted. Your normal map is now ready to be used by the FlightGear shader.

Despite it is more complex, this method allows to generate complicated displacement effects, in a much more accurate way than using converted relief maps. This way it is possible to work on 3 axes, to simulate folds, concave zones, etc...etc, all this keeping total control on the desired effect amount, just be sculpting the high poly model accordingly. You can see an image tutorial of this technique [http://vi-wer.de.tl/Normalmap-Tutorial.htm here]

[[Image:normalmap2.png|thumb|Final normal map]]

==Creating the Normal Map Effect==

Now we have our normal map, we need to apply it to the aircraft. To do this, we need to create a new effect, based on the existing Effect/bumpspec.eff, and then apply it to the correct object in the model.

# Open Effect/bumpspec.eff. You'll find some instructions at the top of the file.
# Copy the first set of XML (between the <PropertyList> and </PropertyList> tags into a new .eff file in your aircraft directory.
# Edit the new file so that it has an appropriate <name> entry and an <image> entry that matches the normal map you created above. For example, in this case we've created the effect Aircraft/c172p/Models/Effects/bumpspec, and are using the normal map Aircraft/c172p/Models/Liveries/wing-normal.png.

<code>
<PropertyList>
<name>Aircraft/c172p/Models/Effects/bumpspec</name>
<inherits-from>Effects/bumpspec</inherits-from>
<parameters>
<texture n="2">
<image>Aircraft/c172p/Models/Liveries/wing-normal.png</image>
<filter>linear-mipmap-linear</filter>
<wrap-s>repeat</wrap-s>
<wrap-t>repeat</wrap-t>
<internal-format>normalized</internal-format>
</texture>
</parameters>
</PropertyList>
</code>

Now we have a new effect, which is based on the original Effects/bumpspec.eff, but which uses our own normalmap.

==Applying the Effect to the model==

Finally, we need to apply the Effect to the model. This is very straightforward. Simply add a section to the model .xml file indicating the Effect you want to use and the object it should apply to.

For example:
<code>
<effect>
<inherits-from>Aircraft/c172p/Models/Effects/bumpspec</inherits-from>
<object-name>wing_1</object-name>
</effect>
</code>

Now load your model and admire the Effect:

[[Image:normalmap3.png|thumb|Cessna with normal map]]

==Final Notes==

* The normal map uses the same texture coordinates as the original texture. However, the normal map does not need to be the same dimensions, so you can use a smaller or larger normal map if you need to.
* You'll need to define a different Effect for each normal map you use. Effectively this means that if you have two objects using different textures, they will need separate effects.
* The bumpspec.eff Effect uses the alpha (transparency) channel on the normal map to set specularity of the point (e.g. shininess). This can be used to make raised parts shiny.
* If you find that the effect is too pronounced, try varying the scaling in the normalmap filter. 0.1 seems to work well for "rivet" effects.
* Make sure all the faces of the object that you assign the effect to have a texture assigned to them, otherwise you will cause a crash in the OpenGL layer (below OSG), because the effect's tangent and binormal vectors are computed using object's texture mapping coordinates. If you try to feed an untextured object to the generator, it should abort with a null vector, and then passing this null vector to the driver leads to a segfault.

[[fr:Tutoriel: Usage de l'effet de Normal Maps]]

Beechcraft B1900D

2010-12-01T19:38:15Z

Cri: Add cockpit panorama

{{infobox Aircraft
|image =BeechcraftB1900D.jpg
|name =Beechcraft B1900D
|type =Airliner
|livery=Air New Zealand, Central Mountain Air, Northern Thunderbird Air, [[Island Virtual Airways]], [[Air San Francisco]]
|authors =Syd Adams (3D model/FDM), Jean-Yves Lefort (MKVIII gpws)
|fdm =YASim
|status =Development
|fgname =b1900d
|download =http://www.flightgear.org/Downloads/aircraft/#b1900d
|ratingfdm =4
|ratingexterior =5
|ratingcockpit =4
|ratingsounds =4
}}

[[File:b1900d-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the 3d Beechcraft B1900d cockpit]]

== About the aircraft ==

The '''Beechcraft 1900''' series aircraft is the most popular 19-passenger airliner in history. It is a pressurized, twin-engine [[Powerplant#Turboprop|turboprop]] manufactured by the Beechcraft Division of the Raytheon Company (now Hawker Beechcraft). Designed primarily as an all weather regional airliner capable of landing on relatively short runways it has also been used by the United States military and other governments.

Beech announced the improved '''1900D''', simulated here, at the US Regional Airlines Association meeting in 1989. The main difference in the 1900D was the substantially deeper fuselage allowing stand up headroom in the cabin. It also had larger passenger and cargo doors and windows, twin ventral strakes and auxiliary horizontal fixed tails. To carry the extra weight Beech upgraded to two PT6A-67D engines, each rated at 1,279 shaft horsepower. Although rarely used a fully fueled Beechcraft 1900 has a range of 860 miles.

The [[Beechcraft B1900D]] is one of the default aircraft in [[FlightGear]] and has been available since [[FlightGear 0.9.8]].

== Procedures ==

=== Starting Procedure ===
In the menu bar at the top of the screen you may select B1900D and then Autostart. You may also choose to start-up manually. In the help menu you will find a start up tutorial this is a quick summary.

* Switch on the battery
* Switch on the left and right generators located on the lower left pilots panel. This should bring up the electrical systems and you should have instrumentation lights
* Switch on the avionics located just below the battery and generator switches.
* Look at the throttle panel in between the pilot and co-pilot. The two far right levers are labeled Condition. Move them fully forward by clicking at the top of the lever slots or by pressing “m”. You should now hear the engines starting up.
* Move the levers labeled Propeller forward by clicking at the top of the lever slots or by pressing “n”.
* Move the levers labeled Throttle to the idle position by clicking at the top of the lever slots or by pressing “9” or “PAGEUP”.
* Switch on Master Panel and any lights needed on the left side of the overhead console.
* Reset the Master Caution Warning in the middle top of the pilot panel that is probably flashing red now that all systems are powered up.
* The aircraft is now ready for take off.

=== Takeoff ===
* Decision at 105 KIAS
* Rotation at 110 KIAS
* Pitch 10-15 degrees
* Trim before engaging autopilot

=== Climb ===
* Airspeed 160 KIAS
* Climb Rate 1500 fpm

=== Cruise ===
* 220 –240 KIAS

=== Descent ===
* 180 KIAS
* Descent Rate –1500 fpm

=== Approach ===
* Establish 150 KIAS
* Set flaps to approach
* Establish 130 KIAS
* Landing gear down – set flaps full down
* Final glide slope 110 KIAS

=== Landing ===
* 100 KIAS
* Main wheels down first
* Lower nose gear

== [[GPS]] ==
The B1900D is equipped with a functioning Bendix/King KLN 908 [[GPS]] that can be slaved to the autopilot. In the help menu you will find a tutorial on [[GPS]] navigation.

== See also ==
* [[Table of models]]
* [[FlightGear 1.0 default aircraft]]

[[File:Beechcraft_B1900D.JPG|thumb|270px|Cockpit of the B1900D]]
{{Beechcraft}}

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]
[[Category:Beechcraft]]

File:B1900d-cockpit-pano.jpg

2010-12-01T19:36:42Z

Cri: An equirectangular 360x180 pano of the Beechcraft B1900D cockpit

An equirectangular 360x180 pano of the Beechcraft B1900D cockpit

IAR 80

2010-11-21T13:02:28Z

Cri: Add cockpit panorama

{{non-stable}}

{{infobox Aircraft
|image =Iar80-flight.jpg
|alt =IAR80 in the default Romanian livery.
|name =IAR 80
|type = Fighter aircraft
|livery =
|authors = Emilian Huminiuc
|status = beta
|fdm = YASim
|fgname = IAR80
|download = http://flightgear.org/forums/viewtopic.php?f=4&t=7225
}}[[Image:iar80-cockpit-dusk.jpg|thumb|270px|The IAR80 cockpit]][[Image:iar80-dusk.jpg|thumb|270px]][[Image:iar80-metal.jpg|thumb|270px]][[Image:iar80-ocean.jpg|thumb|270px]][[Image:iar80-angry.jpg|thumb|270px]]
The '''IAR 80''' was a Romanian World War II low-wing, monoplane, all-metal construction [[:Category:Military aircraft|fighter aircraft]]. When it first flew, in 1939, it was competitive with most contemporary designs like the German [[Messerschmitt Bf 109|Bf 109]]E, the British [[Hawker Hurricane]] and the [[Supermarine Spitfire]].

[[File:iar80-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the IAR 80 3d cockpit]]

==Aircraft Features==

===Livery System===
:Besides the default [[Livery_over_MP|livery]] there are two additional ones, a bare-metal one and another fictional one in the current Romanian Air Club scheme.
:Changing [[Livery_over_MP|livery]] also changes the reflectivity of the material, thus the default one is rather matte, while the two others have increased reflectivity.

===Shader Effects===
:The IAR-80 uses the reflect-bump-spec [[Shaders|shader]], giving it increased detail.
:Also for [[FlightGear_History#Version_2.0.0_.282010.29|Flightgear 2.0]] users, there's the initial version of the [[Shaders|shader]] provided, which can be activated by editing the iar80.xml file in the Models folder.

===Particle Effects===
*Engine smoke, changing colour and density with the thrust and mixture.
*When the engine experiences increased wear, there's also darker denser smoke.
*Particle [[Howto:_Add_contrails|contrails]].
*Wingtip vortices when near stall AOA.
*Propwash when on ground/at low altitude.

===View Effects===
:By use of [[Nasal_scripting_language|Nasal]], the internal view shakes when rolling on the runway, and to simulate the buffeting experienced when aproaching stall AOA.

===Controls Filter===
:Also via a [[Nasal_scripting_language|Nasal]] script, the control input is filtered resulting in decreased input to the control surfaces due to the airflow over them, also this was necessary as the elevator had dynamic compensator tabs.

===Submodel Bullets===
:No warbird is an warbird without it's ''claws''. Thus [[Gun_Effects|submodel bullets]] are implemented, with particle smoke and sounds too.

===Advanced Engine Startup and Management===
:The [[#Startup|startup]] procedure is rather 'realistic', from a dark and cold state. While flying you have to [[#Engine Management Precautions|take care]] of the engine (see the [[#Aircraft help|help]] section below).

===Engine Sputter===
*The engine sputters when overheated/worn due to incorrect management.
*The engine sputters when low on fuel.

==Aircraft help==

===Specific Key Bindings===
* '''ctrl+d''': open/close the canopy.
* '''r/shift+r''' : open/close the cowling flaps.
:''All other keybindings are the [[New_to_FlightGear#Using_the_Keyboard_and_Mouse|default]] ones.''

===Clickable Levers and Sliders===
:All the levers and sliders in the cockpit are clickable, and use LMB to increase value/position and MMB to decrease the value/position.<br />''Alternately you can use the scroll wheel to make finer adjustments.''

===Startup===
# Turn master switch on (the big hexagonal button over the pilot's right shoulder).
# Set mixture to rich (lever at forward position).
# Set some throttle.
# Prime 6-9 times.
# Set prop-pitch to middle position.
# Set magnetos to M1+2.
# Open the cowl-flaps ("r" key).
# Engage starter button and hope it will start.
:''If the engine doesn't start, just sputters, it usually means you have not primed enough. To check if that is the case, keep an eye on the fuel-pressure gauge (on the left pannel, the gauge with two needles on it, the right needle), it should increase when you engage the starter. Also, when priming, make shure the lever reaches the forward end of travel, otherwise that push doesn't register.''

===Warm-up===
# Set prop-pitch for minimum revs (towards the rear)
# Add some throttle until boost pressure reaches ~400 (engine rpm will stabilise at about 1250-1300)
# Wait until oil pressure gets over 1 and oil-temp reaches 60

===Taxi===
:For taxiing you have to use the differential brakes, as there was just a tail-skid.

===Takeoff===
# Close canopy if you have not done so yet.
# Set flaps to position 2 (30 degrees).
# Set prop-pitch so that the indicator forms a small "V" around 12 o'clock.
# Set full throttle.
# Release brakes and be prepared to correct the aircraft's tendency to yaw to the left (either by braking (at low speeds) or by using opposite rudder).
# Maintain a little forward pressure on the stick until the tail lifts off the ground.
# Maintain little back pressure (just enough to keep the plane level) until about 150-160 km/h when the plane should take off.
# Raise gear.
# Raise flaps at about 230km/h.

===Cruise===
# Set prop pitch so that the needles of the indicator form a V around the 11:05 position.
# Set mixture lever at about the apex of the bend in the lever guard. (~0.6 - 0.7 mixture).
# Cowl flaps at position 4/8.

===Landing===
# Reduce throttle.
# Open the cowl flaps.
# At about 300 km/h start extending full flaps.
# At about 250 km/h extend gear.
# Touchdown at ~170 km/h.

===Engine Management Precautions===
:The engine will exhibit increased wear signs and will eventualy stop if you do not follow these guidelines:
* Do not exceed (except ocasionally on take-off / in emergency) 950 boost.
* Keep below 1300 rpm until engine warm-up complete.
* Keep below 2500 rpm in normal flight (below 2800 on take-off/in emergency).
* Keep the oil temperature below 120 degrees C (except take-off/emergency).

[[Category:Aircraft]]
[[Category:Historical aircraft]]
[[Category:Military aircraft]]

File:Iar80-cockpit-pano.jpg

2010-11-21T13:01:16Z

Cri: An equirectangular 360x180 pano of the IAR 80 cockpit

An equirectangular 360x180 pano of the IAR 80 cockpit

Boeing 777-200

2010-11-21T12:54:26Z

Cri: Add cockpit panorama

''This includes the following models: '''777-200''', '''777-200ER'''''

{{infobox Aircraft
|image =777-200.jpg
|name =Boeing 777-200
|type =Airliner
|livery =Air Bagan, Air India, British Airways, Delta Air Lines, [[Island Virtual Airways]], Lufthansa, [[Air San Francisco]], [[Americair]]
|authors =Justin Smithies and Syd Adams
|fdm =YASim
|status =Development
|fgname =777-200, 777-200ER
}}
The '''777-200''' ('''772A''') was the initial A-market model of the [[Boeing 777]]. The first customer delivery was to United Airlines in May 1995. It is available with a maximum take-off weight (MTOW) from 505,000 to 545,000 pounds (229 to 247 tonnes) and range capability between 3,780 and 5,235 nautical miles (7,000 to 9,695 km).

The direct equivalent from Airbus is the [[Airbus A330-300]]. A total of 88 -200s have been delivered to ten different customers as of July 2008.

[[File:777-200er-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the Boeing 777-200ER 3d cockpit]]

==Liveries==
All FlightGear liveries are available at [http://liveries.flightgear.org FlightGear Liveries]. For the 777-200, as of March 2009 the following liveries are available:

* Air Austral
* Air Canada
* Air France
* American Airlines
* Asiana Airlines
* British Airways
* Continental Airlines
* Delta Airlines
** Old (2002-2007)
* EgyptAir
* Japan Airlines
* KLM Royal Dutch Airlines
* United Airlines

These liveries are also available at [http://www.unitedfreeworld.com United Free World]

==Aircraft help==
[[Image:Cockpit.jpg|thumb|270px|The 3D [[cockpit]] of a 777-200]]
You can see a guide on how to fly this plane on [[User:Vaeronic|Vaeron's wikipage]].
For version 2.0, an [[Boeing 777 Tutorial: Version 2.0|updated version]] is available.

===Start Procedure===
* Go to Equipment > Fuel and Payload and set your fuel amounts and make sure your tanks are selected
* Right-click twice to get into the move view mode and look at the overhead panel then click all the electrical buttons until they are all lit up
* Hold the 's' button for 10 seconds or until the engines are running at idle.

===Autopilot===
taken from [http://www.flightgear.org/forums/viewtopic.php?f=25&t=8338 forums].
[[Image:777-200_Autopilot.png|thumb|270px|777-200 Autopilot]]
Autopilot controls, from left to right, top to bottom:

*A/P - Autopilot engage/disengage button
*F/D - Flight director (the pink lines that show up on your attitude indicator)
*A/T ARM (L/R) - Arm/disarm autothrottle for left/right engines
*CLB CON - Continue climbing using the vertical speed the plane was at, when this setting was first engaged
*A/T - Autothrottle engage/disengage button- unlike the real 777, the autothrottle is not independent from the main autopilot, so you'll have to activate this switch AND the main autopilot to use the autothrottle
*IAS <> MACH - Switch between IAS speed mode and Mach number speed mode
*IAS window - Set your desired IAS speed or Mach speed here
*LNAV - Tells the autopilot to follow the Route Manager settings laterally (control the heading)- this has never worked for me, the autopilot just makes meaningless circles/goes north
*VNAV - Same as LNAV, except vertically (control the altitude)- never tried this setting before
*FLCH -
*A/P DISENGAGE - Dedicated autopilot disengage button- click twice
*HDG <> TRK - Switch between heading bug and course track
*HDG window - Set your desired heading or course track here
*Bank limits (AUTO/5/25) - Define banking limits for turning- i.e. 5 for gentle turns at cruising altitude, 25 for good maneuverability at lower speeds; auto will be fine in most cases
*HOLD - Engage/disengage heading or course hold mode
*V/S <> FPA - Switch between Vertical Speed and Flight Path Angle
*V/S window - Set your desired Vertical Speed or Flight Path Angle
*VS/FPA - Engage/disengage Vertical Speed/Flight Path Angle hold mode
*ALTITUDE window - Set your desired altitude here
*Altitude selection setting (AUTO/1000) - Switch between automatic incrementing (AUTO) and incrementing by the thousands (1000)- this setting only helps when selecting the altitude via the knobs, this won't apply if using the Autopilot Settings dialog
*HOLD - Engage/disengage altitude hold mode
*LOC - Track NAV1 VOR, flying by the heading given by the NAV1 radial
*APP - Track an ILS glideslope, laterally and vertically- can be overriden by LOC, HDG, and ALT (i.e. you want to maintain a certain altitude until you capture the glideslope)
*A/P - Engage/disengage autopilot
*F/D - Flight director

==Related content==
* [http://sourceforge.net/projects/xpc-777 Boeing 777 aircraft systems simulator ]
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Model with well-implemented cockpit]]

File:777-200er-cockpit-pano.jpg

2010-11-21T12:53:05Z

Cri: An equirectangular 360x180 pano of the Boeing 777-200er cockpit

An equirectangular 360x180 pano of the Boeing 777-200er cockpit

Lockheed SR-71 Blackbird

2010-11-21T12:43:15Z

Cri: Add cockpit panorama

''This includes the following models: SR-71A, SR-71B''<br/>
''This article is about the model in /data/Aircraft/SR71-BlackBird on CVS''

{{infobox Aircraft
|image =B-2.jpg
|name =Lockheed SR-71 Blackbird
|type =Strategic Reconnaissance
|fdm =JSBSim
|status =Development
|authors =Gerard Robin
|fgname =<tt>Blackbird, Blackbird-A, Blackbird-B</tt>
|download =http://www.flightgear.org/Downloads/aircraft/index.shtml#Lockheed-SR71
}}

The '''Lockheed SR-71''' is an advanced, long-range, Mach 3 strategic reconnaissance aircraft developed from the [[Lockheed A-12]] and [[Lockheed YF-12A|YF-12A]] aircraft by the Lockheed Skunk Works. The SR-71 was unofficially named the Blackbird, and called the Habu by its crews. Clarence "Kelly" Johnson was responsible for many of the design's advanced concepts. A defensive feature of the aircraft was its high speed and operating altitude, whereby, if a surface-to-air missile launch were detected, standard evasive action was simply to accelerate. The SR-71 line was in service from 1964 to 1998, with 12 of the 32 aircraft being destroyed in accidents, though none were lost to enemy action.

This article is about the model in /data/Aircraft/SR71-BlackBird on CVS and goes by fgname <tt> blackbird </tt>, but there is another one in the directory Aircraft/Lockheed-SR71/ and both can be downloaded from flightgear.org. The fgname for it is <tt> sr71-yasim </tt>, and it uses YASim.

[[File:sr71a-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the Lockheed SR-71 Blackbird 3d cockpit]]

==Aircraft help==
===Startup===
* Press <tt>}</tt> to toggle the master electric switch.
* Press space or <tt>s</tt> to activate the starter. The engine will spin up to a maximum of about 25% N2 (5.2% N1).
* After reaching 15% N1, press <tt>{</tt> to turn off the cutoff to let the engines start. Wait for the EP Ratio needle to come close to 1.1.
* Don't forget to press <tt>d</tt> to close the canopy.
* Release the parking brake, put the throttle to max and takeoff.

===Landing===
[[Image:B-2_refuel.jpg|thumb|270px|A SR-71 refueling behind a [[KC-135]] tanker]]

====Braking chute====
The braking chute will be automatically deployed if:

* Brake chute doors are opened (<tt>Ctrl-b</tt>).
* Airspeed is less than 200 kts.
* [[Above Ground Level|AGL]] is lees than 20 ft.
* Throttle positions are less than 0.1.

The braking chute will be released/untied if:

* Airspeed is less than 50 kts.

'''Remember:''' it can be used only once. If you want to use it again you have to reload (<tt>j</tt>).

== Flight Manual ==

There is an actual [http://www.netwrx1.com/skunk-works/sr71flt.pdf SR-71 Flight Manual] available online if you want to know the full operating procedures of the aircraft - not all operations are supported by the model though. Here is an abbreviated version geared to what is available and possible in Flightgear.

=== Pre-flight preparations ===

Select a destination and enter it into the route manager. The real SR-71 has an Astro-Inertial Navigation System (ANS) which is capable of navigating a preset series of waypoints just as the route manager. For a first flight, a distance to destination of about 1500 nm is suitable, the flight time is then about 1 hour with sufficient time to climb up to cruising altitude and spend some 15-20 minutes cruising. For better performance, reduce the fuel level accordingly. With full tanks, the Blackbird should have a range of 2900 nm, so 2/3 of normal fuel should be ample. Note that navigating by sight like following a coastline is quite impossible from 80.000 ft - it takes about 30.000 m visibility to see the ground directly beneath the aircraft, and at least 10 times this much to see anything from the cockpit. This is asking for really good weather in reality, and definitely not viable in the simulation - so the ANS is the only real option.

It also can't hurt to have some background knowledge about supersonic high-altitude flight - [[Understanding Supersonic Flight]] and [[Understanding airspeed measures]] provide some useful background to understand why the plane must be operated the way it is.

=== Takeoff ===

Start the electric system (<b>}</b>), start the engines (<b>s</b>), watch the engines spin up to 15% N1, then turn off the cutoff (<b>{</b>) and wait for the engines to become operational. Close the canopy (<b>d</b>), release parking brakes (<b>shift-b</b>) and taxi to the runway. Put the throttle to full afterburner power and rotate at about 200 KEAS (knots equivalent airspeed), retract gear (<b>g</b>) after liftoff. Climb out at about 250 KEAS.

=== Subsonic climb ===

The Blackbird is not exactly a nimble plane in the subsonic regime, but all in all handles well. After getting the okay from ATC, turn towards the destination (you may get the autopilot to lock on that heading) and start climbing while steadily accelerating towards Mach 1. Leave the throttle at full thrust (in fact, thrust will remain on full afterburner power all the way till the beginning of the descent). Climb below Mach 1 towards 25.000 ft. This is the usual air-air refueling altitude for the SR-71, so in a more complicated flightplan taking off with a small load of fuel, you would now find the tanker and fill the tanks. This is also a good opportunity for final changes of the heading - turning at Mach 3 costs a lot of time and fuel and should be avoided if possible.

=== Supersonic climb ===

[[Image:SR-71-Mach3.jpg|thumb|300px|Finally there - black morning sky and stars from 80.000 ft at Mach 3.2]]

While having a simulated autopilot fly a simulated plane is in general a bit odd, letting the autopilot handle the Blackbird in supersonic flight is worth considering, as it makes life <i>much</i> easier. The reason is that at high velocities, even a small-angle descent immediately leads to a very impressive sinkrate, so the plane needs to be controlled very precisely. But at the same time, the response of the plane at high altitude is increasingly sluggish, and overcorrecting happens easily. In addition, the plane rolls easily and it costs a lot of attention to control course. While small deviations from the optimal climb path just cost more fuel, larger deviations may mean that you have to descend and climb back again. The autopilot can handle the required maneuvering more efficient.

In any case, it is time to go supersonic. Dependent on conditions, the procedure is to either climb to 33.000 ft with Mach 0.99 and reach Mach 1.25 in a shallow descent to 30.000 ft, or to accelerate to Mach 1.25 in level flight at 25.000 ft. After reaching Mach 1.25, start climbing again.

The plane is now flown on a climbing trajectory of constant 450 KEAS. At higher altitude, this corresponds to increasingly higher Mach numbers. The climb is not particularly fast - just keep climbing slowly and steadily. At about 70.000 feet, allow reduction down to 400 KEAS when climbing to 80.000 ft, there level off - you should be able to reach Mach 3.2 or more, dependent on fuel load. When the fuel load is light, consider climbing to 85.000 ft for better efficiency. Cruise and watch the distance to destination melt away.

=== Descent ===

About 230 miles to destination, prepare for descent. Switch afterburner off and reduce thrust to military power. Keep the altitude until the plane decelerates to 350 KEAS, then start descending keeping this airspeed. The descent is again rather shallow, and it should take about 200 miles to get to 25.000 ft, at which point you can safely switch off the autopilot and fly the rest of the trip yourself.

[[Image:SR-71-Returning.jpg|thumb|300px|Descending from high altitude]]

=== Approach and landing ===

Fly the approach pattern of your choice to the destination runway. Reduce airspeed to about 220 KEAS below 10.000 ft, turn into final approach with about 200 KEAS. Watch the speed, especially when making tight turns in the approach pattern. The Blackbird is a supersonic aircraft with bad aerodynamics in subsonic flight - if you stall, there's little chance to recover. Arm the braking chute (<b>ctrl-b</b>), on final approach extend gear (<b>shift-g</b>) and prepare for landing.

Thanks to the magnificent view from the cockpit, you can't actually see straight ahead, i.e. you don't see the runway in a straight approach. There are three possible solutions: First, you could modify the viewpoint to simulate a pilot trying to put his head to the side. Second, you can approach at a shallow angle and only align with the runway when you are practically over it - in this way it can be seen better. Or you fix your eyes on a point next to the runway and fly an approach with this reference - if done correctly, that should get you on the runway. Touchdown with about 200 KEAS, put throttle to idle and watch the braking chute open and reduce speed quickly. Apply brakes (<b>b</b>) and use rudder to stay on the runway.

Then taxi to your parking position, apply parking brakes (<b>shift-b</b>), switch off the engines (<b>{</b>), the electrical system (<b>}</b>) and open the canopy (<b>d</b>).

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Lockheed}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

File:Sr71a-cockpit-pano.jpg

2010-11-21T12:41:13Z

Cri: An equirectangular 360x180 pano of the Lockheed SR-71 Blackbird (a) cockpit

An equirectangular 360x180 pano of the Lockheed SR-71 Blackbird (a) cockpit

Eurofighter Typhoon

2010-11-21T12:38:42Z

Cri: Add cockpit panorama

{{infobox Aircraft
|image =typhoon.jpg
|name = Eurofighter Typhoon
|type = Multirole fighter
|livery =
|fdm =YASim
|status =
|authors = Detlef Faber, Maverick Alex, Almursi, Algernon
|fgname = typhoon
|download = http://www.sol2500.net/flightgear/aircraft.html
}}
The '''Eurofighter Typhoon''' is a twin-engine canard-delta wing multirole [[aircraft]]. It is being designed and built by a partner consortium, Eurofighter GmbH, founded in 1986, made up of the major aerospace companies of the four Eurofighter partner nations: 21% [http://en.wikipedia.org/wiki/Alenia Alenia Aeronautica] (Italy), 33% [http://en.wikipedia.org/wiki/BAE_SYSTEMS BAE Systems] (UK), 13% [http://en.wikipedia.org/wiki/EADS_CASA EADS-CASA] (Spain) and 33% [http://en.wikipedia.org/wiki/DaimlerChrysler_Aerospace EADS-Deutschland] (Germany). Along with two other projects: Eurojet Turbo GmbH by Avio (Italy), ITP (Spain), MTU Aero Engines (Germany), and Rolls-Royce (UK), to develop the EJ200 engine for the new fighter aircraft; and Euroradar for Captor radar, comprised of EADS Defence Electronics (Germany), SELEX Galileo (UK and Italy) and INDRA (Spain). The project is managed by NETMA (NATO Eurofighter and Tornado Management Agency) which acts as the prime customer. The Eurofighter Typhoon entered service in 2003. <sup>[http://www.airforce-technology.com/projects/ef2000/]</sup>

'''Please note:''' some features do not work with FlightGear versions older than 1.9.

This aircraft is still under development, currently being undertaken by Almursi and Algernon. Both are contactable via the FlightGear Forums, where there is also a [http://www.flightgear.org/forums/viewtopic.php?f=4&t=1460|Eurofighter Typhoon thread]. Please contact them there if you have any contributions to make to the aircraft project.

[[File:Typhoon-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the Eurofighter Typhoon cockpit]]

==Flying the Eurofighter==
It should be noted that the current release of the Eurofighter Typhoon has an FDM which replicates the capabilities of the airframe to a realistic degree. What isn't yet included is the automated flight management system which computes the optimum surface positions based on pilot input and flies within safe limits for the aircraft, and more importantly, the pilot. The aircraft is capable of extremely high-G manoeuvres and pilots are advised to proceed with caution intitally (fortunately solved in the latest version of the FDM).

==Features Under Development==
The Eurofighter Typhoon is an advanced 4.5th generation multirole fighter, and as such will be fitted with state-of-the-art flight and warfare technology. Examples include: advanced (for FG) communication capabilities, several Radar modes, Electronic Countermeasures, an extended autopilot with Auto Climb (inc. Auto Take-off), Auto Attack and Auto Approach capabilities, and numerous others. In addition, the current release is an experimental naval variant equipped for carrier deployment and recovery - it is likely that at some stage, there will be two Typhoon variants - one land-based, one carrier-borne - bundled in the same aircraft folder.

==See Also==
*[[Eurofighter Typhoon: Flight Manual]] - a manual written especially for the FG Typhoon. A work in progress.

==External links==
* [http://www.eurofighter.com/ www.eurofighter.com] (Requires Adobe Flash)
* [http://www.airforce-technology.com/projects/ef2000/ Eurofighter Typhoon] (airforce-technology.com)

[[Category:Aircraft]]
[[Category:Military aircraft]]

File:Typhoon-cockpit-pano.jpg

2010-11-21T12:37:54Z

Cri: An equirectangular 360x180 pano of the Eurofighter Typhoon cockpit

An equirectangular 360x180 pano of the Eurofighter Typhoon cockpit

Howto:Make nice screenshots

2010-11-20T13:12:46Z

Cri: Add link to full spherical panorama wiki page

In this [[:Category:Howto|howto]] I will explain how to make nice screenshots in [[FlightGear]]. This is helpful for those who want to advertise FGFS on other sim-related forums or on booths around the world.

===Basics to know===
Good pictures:
* They appeal to us in some way, by telling a story, revealing something unexpected, or showing an interesting point of view.
* They encourage us to look at them for more than just a second, searching for more details. A good screen-shot can invite us to think about how it was made, maybe even inspire us to create images of our own.
* The best screen-shots are technically correct, the lighting and colors are right, and the composition is good.

The part of How to composite a picture is difficult to explain - so instead I suggest you to read tutorials and explanations given on many websites on the web like this one : [http://en.wikipedia.org/wiki/Composition_(visual_arts) Composition (visual arts)].

== Quality ==
A good virtual picture needs a good quality. That means:
* Use of AntiAliasing (AA)
* Appealing/true colors
* Size of the picture- not too small, not to big
* No Gui/Menu/FrameRateCounter etc. visible
* Full effects

This means you need a decent computer with middle - good specs. At least you should able to run FGFS with fluent fps with high AA-settings.
Some people don't have this, so there is another solution proposed by Melchior Franz : [http://www.opensubscriber.com/message/flightgear-devel@lists.sourceforge.net/8196594.html].

== How to get some unusual/ interesting views ==
To get some ideas, I suggest to look on the aircraft picture pages around the web like [http://www.airliners.net Airliners.net]. It will give you some ideas. In addition, it is always a good idea to think about what you actually want to show case. While a snapshot of an airliner in mid flight is -for instance- a nice way of showing it's latest features on the forum, it typically doesn't really last as an overall impressive screen shot. Placing the aircraft in a scene where some implied action is taking place will most of the time already make a huge difference. Capture the plane while it's banking, gear is retracting, etc etc, will imply some dynamic motion in your otherwise static image. In this respect, it may help to think of a little story, a scenario that you're reenacting. Trying to capture a few key scenes from that story may also help to make the difference between an average and an interesting screen shot.

===Air to Air===
* '''Helicopter View:''' This assumes that you are in a virtual, not visible helicopter besides the aircraft. You are always flying level. With the mouse you can choose the position of the "helicopter".
* '''Chase View:''' This assumes you are chasing the aircraft. It is very similar to the first one.
* '''Chase View with yaw:''' Also chasing the aircraft, but the virtual camera doesn't turn with the aircraft.
Try switching between them to see what you like more(I prefer Chase view). Playing around with position of the camera will help too. As an example if the aircraft is turning and banking, make a shot from the wing to the aircraft facing the ground. Or while approaching the runway, a shot from behind the aircraft would be good.

===Ground to Air===
[[Image:Wiki PlaceTower.jpg|thumb|270px|Setting the Tower on top of the mountain looking down to the airport with the [http://www.gidenstam.org/FlightGear/misc/place_tower.xml Place_Tower.xml]]]

For this we use the Tower view and Tower View look from. This assumes that the virtual camera is on the Airport Tower, ca. 30ft above the airport level. You can choose via the Menu which airport is used. That's nice, but limited.

Anders Gidenstam made a nice little helping nasal script, with you can choose the tower position on the ground via mouse-click.
You can grab it [http://www.gidenstam.org/FlightGear/misc/place_tower.xml here]. Copy the code between the <property-list>-tags and put in somewhere of your preferences.xml . Now by ''Ctrl + LMB-Click'' somewhere on the scenery you can set the Tower-view position. It is still ca. 30ft above the airport level- assuming you are virtual walking in the scenery, you can change the line

setprop(tower ~ "/altitude-ft", 30 + MtoFT * click_pos.alt());

to

setprop(tower ~ "/altitude-ft", 6.5 + MtoFT * click_pos.alt());

===Panorama===
[[Image:Fgfs-screen-560 stitch2.jpg|thumb|600px|180 degrees Panorama stitched with 20 images inside the C172P cockpit while flying above the Custom Scenery for South France]]

[http://en.wikipedia.org/wiki/Panorama Panorama] is a wide-angle view. With this, you can show large areas of sceneries or interiors like flightdecks.

For this use the Cockpit, Passenger-view or Tower-view, and position the virtual camera at the point you want. Pause the sim and now, while panning the virtual camera, save many screenshots so they all cover the pan.
Now use your favourite Panorama-Software and stitch it!
No software yet? Use Google, as there are several Freeware-programs outside. I can recommend [http://hugin.sourceforge.net/ Hugin], it is OpenSource, crossplatform and used by many professional photographers.

If you want to make full spherical panorama take a look at this [http://wiki.flightgear.org/index.php/Howto:_Make_full_spherical_panorama tutorial].

== Field of View (FoV) ==
[[Image:wiki_FoV.jpeg|thumb|270px|The difference of wide/Narrow angle. See how the background changes using a zoom!]]

You can change this by pressing X/x-key or using the Mouse-wheel in View-mode.
The FoV is per default set to 55 (degrees).

Increasing the field you get wide angle up to 120 degrees. That's interesting as it covers a whole part of the scenery but also seems to make objects appear far away. So use it for showing large parts of sceneries, or long aircraft etc... Another interesting feature of using a wide angle is that it exaggerates perspective. One effective use of this consists of using a wide angle lens combined with placing the camera near the object. This will make the object in question appear larger, more impressive than it really is. For an higher wide angle make a panorama.

Decreasing the field you get a narrow angle and a zoom-effect. This means you can take far away objects virtually close to you. An interesting effect is, that it also makes the background more "dense". Another interesting side effect is distance foreshortening, meaning that the distance between various object is becoming compressed, suggesting less space between objects than there really is.

== Lighting and Daytime ==
[[Image:Wiki low sun shaders.jpg|thumb|270px|Showing the effect of the low sun and the water shaders]]

The most appealing photos in real life are made in the morning or evening. The light has a warm color, the shadows and ambient colors are soft and long which gives fantastic impressions. The noon gives hard shadows and strong contrasts, which are hard to deal with.

This applies to FlightGear as well. So play a bit with the daytimes, especially Dawn/Morning/Afternoon and Dusk. Play with the seasons and locations as well. In the winter near the poles the sun is low, while near the equator the sun is standing high in the sky. As an example this gives nice effects with the shaders on the water.

== Weather ==
Our weather has improved much in CVS and upcoming releases. Much more realistic clouds, better sky and ambient colors and the possibility to set your own [[METAR]], clouds etc. makes it more easy to create a stunning weather background for your picture.

== Locations ==
The choice of the location depends a bit what you want to show. So what want you to show? Do you have already a theme for in mind?

As an example for showing an aircraft just for presentation, use an "empty" background like the sky, sea or desert. If you want to show the aircraft during operation you could choose some or our better airports like [[EHAM]], [[LFPG]] etc. as background, or some of the more detailed sceneries like our Custom Sceneries.

== Colors and whitebalance ==
As in real life, in FGFS the pictures often have to be corrected in colors and whitebalance. This can be done with almost any image editor. In [http://www.gimp.org GIMP] this can be done through <tt>Layers > Colors > Brightness and contrast</tt>.

== Conclusion ==
Combining all this, playing with all this you should be able to create some stunning pictures. Try and play with as much you can, look at real images to get hints or try to copy a real life image in FlightGear. All this will help you to make a good picture!

General Dynamics F-16 Fighting Falcon

2010-11-20T12:59:31Z

Cri: add cockpit pano

{{infobox Aircraft
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = Production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = f16
}}

[[File:F16-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the f-16 cockpit]]

==Keyboard Controls==
'''Flight Controls'''
{| class="prettytable"
|Ctrl-b
|: Toggles speed brake
|-
|Delete
|: Toggles FBW (Fly by Wire) override
|}
'''Miscellaneous'''
{| class="prettytable"
|Ctrl-f
|: Triggers flare release
|-
|Ctrl-h
|: Toggles arrester hook
|-
|C
|: Toggles canopy
|-
|e
|: Fires the cannon
|-
|}
'''Radar'''
{| class="prettytable"
|Ctrl-n
|: Toggles Radar RWS / TWS AUTO Modes
|-
|E
|: Decreases Radar Range
|-
|R
|: Increases Radar Range
|-
|q
|: Toggles Radar Standby Mode
|-
|}

== Development status/Issues/Todo ==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
**This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
**Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds: (Low priority)
* Establish a list of all sounds that can be produced by the F-16 and its driver:

Cockpit:
**switches
**knobs
**levers
**buttons
**wheels (ICP)
**rudder pedals
**ejection seat
**canopy **implemented**
**canopy lock **implemented**

Audio:
**"bitching betty"
***missile launch
***warning **implemented**
***chaff/flare
***jammer
**RWR
***radar signature identification sounds
****radar spike
****radar lock
**gear horn (currently implemented as alert?)

Pilot:
**breathing
**movement
**brevity comms

External-sounds:
**engine **implemented**
**landing gear
***up
***down
***broken
**ordnance
***jettison store(s)
***bomb drop
***missile launch
***20mm cannon **implemented**
**damage
***airframe overstress
***gun hit
***explosion
**Mid air refueling
***refueling door
****open
****close
***tank boom (tanker aircraft)
****connect
****disconnect

== Related content ==

* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the F-16, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft|F-16 Falcon]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

Cessna 172P

2010-11-20T12:58:13Z

Cri: moved cockpit pano

{{non-stable}}

{{infobox Aircraft
|image =Cessna 172P.jpg
|name =Cessna 172P
|type =Civilian aircraft
|fdm = JSBSim
|status =production
|authors =David Megginson
|ranking=5
|fgname = <tt>c172p</tt>, <tt>c172p-2dpanel</tt>, <tt>c172p-panel-only</tt>, <tt>c172r</tt>
}}

A C172 has been the default aircraft in FG since 2000, when it replaced the Navion. It has had a long development and includes a wide variety of simulation features for FG 1.0. See [[Understanding Propeller Torque and P-Factor]]

C172 has a simulation of the [[Bendix/King KAP140 Autopilot]].

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the 3d cessna c172p cockpit]]

==Variants==
The following four variants exist in the [[FlightGear CVS]] data repository:
* <tt>c172p</tt>
* <tt>c172p-2dpanel</tt>
* <tt>c172p-panel-only</tt>
* <tt>c172r</tt>

==Aircraft help==

===Engine Start===
* Mixture: Rich (Red all the way in)
* Throttle: Open 1/8 (Black almost all the way out)
* Parking Brake: Applied (Shift-B)
* Prop Area: Clear
* Magnetos: Both (}}} three times)
* Ignition: Start (s)

===Takeoff===
* no flaps
* full throttle
* rotate at 55 KIAS

===Climbout===
* no flaps
* full throttle
* 80 KIAS

===Cruise===
* throttle 65%
* mixture rich of peak

===Landing===
* full flaps
* 65 KIAS

===V Speeds===
Vso: 33 kts
Vx: 56 kts
Vy: 76 kts
Va: 99 kts
Vne: 158 kts

== Common Aircraft Keys==
{| border="1"
|-
! align="center"|Key !! Action
|-
| align="center"| Enter || Move Rudder Right
|-
| 0/Insert || Move Rudder Right
|-
| align="center"|[] || Flaps up/down
|-
| align="center"|{} || decrease/increase magneto on selected engine
|-
| align="center" | ~ || select all engines
|-
| align="center"|s || start selected engines
|-
| align="center"|h || toggle heads up display
|-
| align="center"|m/M || mixture richer/leaner
|-
| align="center"|n/N || propeller finer/coarser
|}
== Development status/Issues/Todo ==

'''Outside:'''
* textures/ mapping needs some correction

'''3D cockpit:'''
* cockpit is textured but textures need more polish
* no pilot or co pilot present
* the light switch labels are hard to read.

'''General:'''
* It is routine to observe 135 Kias at 2850 RPM in level flight at 1000 MSL, using only 13 gph. This is not the sort of performance seen in real-life Skyhawks.
** What is the expected performance according to your estimation?

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]

=== Related links ===
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]
[[Category:Model with well-implemented cockpit]]
[[Category:Interactive Tutorial Support]]
[[Category:Aircraft with Checklists]]
[[Category:Aircraft with Help]]

[[fr:Cessna 172]]

File:F16-cockpit-pano.jpg

2010-11-20T12:57:19Z

Cri: An equirectangular 360x180 pano of the F-16 cockpit

An equirectangular 360x180 pano of the F-16 cockpit

De Havilland Canada DHC-2 Beaver

2010-11-20T12:55:43Z

Cri:

{{infobox Aircraft
|image =DHC-2.jpg
|name = de Havilland Beaver
|type = STOL utility transport
|liveries = Military, Trans Provincial Airlines, [[Air San Francisco]]
|authors = Syd Adams
|fdm =YASim
|status =Finished
|fgname =dhc2F (floats) / dhc2W (wheels)
|download =http://flightgear.org/Downloads/aircraft/#dhc2
}}

The '''de Havilland Canada DHC-2 Beaver''' is a single engined, high wing, propeller-driven, STOL aircraft developed by de Havilland Canada, primarily known as a bush plane. It is used for cargo and passenger hauling, aerial application (crop dusting and aerial topdressing), and has been widely adopted by armed forces as a utility aircraft. The U.S. Army Air Corps purchased several hundred and nine DHC-2s are still in service with the US Air Force Auxiliary (Civil Air Patrol) for search and rescue. A Royal New Zealand Air Force Beaver supported Sir Edmund Hillary's expedition to the South Pole. Over 1,600 Beavers were produced until 1967 when the original line shut down, and today the aircraft is in such demand that there is a steady market for finding surplus examples in air museums and rebuilding them.

The Beaver is one of the most famous bush planes in the world, and the most-produced all-Canadian aircraft. Due to this success, the Royal Canadian Mint commemorated the Beaver on a special edition Canadian quarter in November 1999.

The DHC-2 with floats debuted in 2005, in [[FlightGear 0.9.8]].

[[File:Dhc2f-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the De Havilland Canada DHC-2 Beaver cockpit]]

==Aircraft help==
{| class="prettytable"
!Key
!Function
|-
|!
|Toggle battery switch
|-
|@
|Toggle alternator switch
|-
|#
|Toggle fuel pump
|-
|$
|Toggle pitot heat
|-
|%
|Toggle landing light
|-
|^
|Toggle nav lights
|-
|o
|Connect tow cable
|-
|O
|Disconnect tow cable
|}

===Startup===
# Set magnetos to both
# Set fuel tank to switch to rear tank
# Engage battery switch (up)
# Engage fuel pump switch (up)
# Engage starter switch (hold up till the propeller starts spinning)
# Once engine is running, engage alternator switch (up)

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]

{{de Havilland Canada}}

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Light Aircraft]]

File:Dhc2f-cockpit-pano.jpg

2010-11-20T12:54:28Z

Cri: An equirectangular 360x180 pano of the De Havilland Canada DHC-2 Beaver cockpit

An equirectangular 360x180 pano of the De Havilland Canada DHC-2 Beaver cockpit

Howto:Make full spherical panorama

2010-11-20T12:47:14Z

Cri:

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that wants to contribute to the flightgear wiki by adding one of this panorama to each aircraft's page in order to display the cockpit. Here is an example of what can be achieved:

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the 3d cessna c172p cockpit]]

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[Nasal_scripting_language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[Nasal_scripting_language|nasal]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T12:46:27Z

Cri: add image example

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit. Here is an example of what can be achieved:

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the 3d cessna c172p cockpit]]

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[Nasal_scripting_language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[Nasal_scripting_language|nasal]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

Cessna 172P

2010-11-20T10:42:49Z

Cri: Add full spherical panorama of the 3d cockpit

{{non-stable}}

{{infobox Aircraft
|image =Cessna 172P.jpg
|name =Cessna 172P
|type =Civilian aircraft
|fdm = JSBSim
|status =production
|authors =David Megginson
|ranking=5
|fgname = <tt>c172p</tt>, <tt>c172p-2dpanel</tt>, <tt>c172p-panel-only</tt>, <tt>c172r</tt>
}}

A C172 has been the default aircraft in FG since 2000, when it replaced the Navion. It has had a long development and includes a wide variety of simulation features for FG 1.0. See [[Understanding Propeller Torque and P-Factor]]

C172 has a simulation of the [[Bendix/King KAP140 Autopilot]].

==Variants==
The following four variants exist in the [[FlightGear CVS]] data repository:
* <tt>c172p</tt>
* <tt>c172p-2dpanel</tt>
* <tt>c172p-panel-only</tt>
* <tt>c172r</tt>

[[File:C172p-cockpit-pano.jpg|480px|thumb|center|[[Howto:_Make_full_spherical_panorama|A full spherical panorama]] of the 3d cessna c172p cockpit]]

==Aircraft help==

===Engine Start===
* Mixture: Rich (Red all the way in)
* Throttle: Open 1/8 (Black almost all the way out)
* Parking Brake: Applied (Shift-B)
* Prop Area: Clear
* Magnetos: Both (}}} three times)
* Ignition: Start (s)

===Takeoff===
* no flaps
* full throttle
* rotate at 55 KIAS

===Climbout===
* no flaps
* full throttle
* 80 KIAS

===Cruise===
* throttle 65%
* mixture rich of peak

===Landing===
* full flaps
* 65 KIAS

===V Speeds===
Vso: 33 kts
Vx: 56 kts
Vy: 76 kts
Va: 99 kts
Vne: 158 kts

== Common Aircraft Keys==
{| border="1"
|-
! align="center"|Key !! Action
|-
| align="center"| Enter || Move Rudder Right
|-
| 0/Insert || Move Rudder Right
|-
| align="center"|[] || Flaps up/down
|-
| align="center"|{} || decrease/increase magneto on selected engine
|-
| align="center" | ~ || select all engines
|-
| align="center"|s || start selected engines
|-
| align="center"|h || toggle heads up display
|-
| align="center"|m/M || mixture richer/leaner
|-
| align="center"|n/N || propeller finer/coarser
|}
== Development status/Issues/Todo ==

'''Outside:'''
* textures/ mapping needs some correction

'''3D cockpit:'''
* cockpit is textured but textures need more polish
* no pilot or co pilot present
* the light switch labels are hard to read.

'''General:'''
* It is routine to observe 135 Kias at 2850 RPM in level flight at 1000 MSL, using only 13 gph. This is not the sort of performance seen in real-life Skyhawks.
** What is the expected performance according to your estimation?

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]

=== Related links ===
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]
* [http://www.atlasaviation.com/checklists/cessna-172/cessna_172_checklist.htm Cessna 172 checklists at AtlasAviation.com]

{{Cessna}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Cessna]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]
[[Category:Model with well-implemented cockpit]]
[[Category:Interactive Tutorial Support]]
[[Category:Aircraft with Checklists]]
[[Category:Aircraft with Help]]

[[fr:Cessna 172]]

Howto:Make full spherical panorama

2010-11-20T10:38:49Z

Cri: /* The automatic process */

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit.

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[Nasal_scripting_language|nasal]] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[Nasal_scripting_language|nasal]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T10:35:18Z

Cri: /* Stitching the panorama with Hugin */

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit.

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[nasal|Nasal_scripting_language] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[nasal|Nasal_scripting_language]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you told Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T10:34:20Z

Cri: /* Stitching the panorama with Hugin */

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit.

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[nasal|Nasal_scripting_language] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[nasal|Nasal_scripting_language]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you tell Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T10:31:15Z

Cri: /* Taking the required screenshots */

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit.

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[nasal|Nasal_scripting_language] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[nasal|Nasal_scripting_language]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start Flightgear but in order to use efficiently this script and the provided Hugin file you need to set the video format to 4/3 (800x600, 1024x768, 1200x900, 1600x1200...). When in the game press the "F3" key and wait. You will see the camera changing heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow the next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you tell Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T10:27:49Z

Cri: /* Stitching the panorama with Hugin */

In this [[:Category:Howto|howto]] I will explain how to make full spherical panorama in [[FlightGear]]. The semi-automated process is useful for everyone that want to contreibute to the wiki by adding one of this panorama to each aircraft's page in order to display the cockpit.

===The tools===
In order to take panorama in flightgear you need:
* of course [[Flightgear|Flightgear]]
* a panorama stitching tool. I suggest to use [http://hugin.sourceforge.net Hugin]: it's free and very powerful.

===The automatic process===
To make the process easier I've created a [[nasal|Nasal_scripting_language] script that capture automagically the required screenshots. This script can be binded to a keyboard key. Also I've created a standard Hugin file to assemble this screenshots into a full spherical panorama.
====Taking the required screenshots====
The easier way is to bind the following nasal script to a keyboard key (The "F3" key that is used by default to take screenshots). To do this, open the file keyboard.xml that you can find in the fgdata folder with a text editor and look for the following section:

<key n="259">
<name>F3</name>
<desc>Capture screen</desc>
<binding>
<command>nasal</command>
<script>
var success = fgcommand("screen-capture");
var path = getprop("/sim/paths/screenshot-last");
if (success)
gui.popupTip("Screenshot written to '" ~ path ~ "'");
else
gui.popupTip("Error writing screenshot '" ~ path ~ "'");
</script>
</binding>
<mod-shift>
<desc>Load panel</desc>
<binding>
<command>panel-load</command>
</binding>
</mod-shift>
</key>

Now substitute the [[nasal|Nasal_scripting_language]] code between the <script> tags with this:

var timeint=3;
var runs=2;

menubarvalue=getprop("/sim/menubar/visibility");
znearvalue=("sim/rendering/camera-group/znear");
fovvalue=getprop("/sim/current-view/field-of-view");
freezemvalue=getprop("/sim/freeze/master");
freezecvalue=getprop("/sim/freeze/clock");
headingvalue=getprop("/sim/current-view/heading-offset-deg");
pitchvalue=getprop("/sim/current-view/pitch-offset-deg");

setprop("/sim/screenshots/runs", runs);
setprop("/sim/menubar/visibility", 'false');
setprop("/sim/rendering/camera-group/znear",0.03);
setprop("/sim/current-view/field-of-view", 120);
setprop("/sim/freeze/master",'true');
setprop("/sim/freeze/clock",'true');

var takescreen = func(n,k) {
var runs=getprop("/sim/screenshots/runs");
if ( n > 0 ) {
var panofov = getprop("/sim/current-view/field-of-view");
setprop("/sim/current-view/heading-offset-deg", n*90);
setprop("/sim/current-view/pitch-offset-deg", k);
settimer( func { var success = fgcommand("screen-capture");
if (success) {
print ("screen taken with heading= ",n*90 ," and pitch= ", k);
takescreen(n-1,k);
} else {
print("screen not taken");}
}, timeint, timeint );
}
}
var scr_runs = func {
var runs_left = getprop("/sim/screenshots/runs");
print("run: ", runs_left);
if (runs_left > 0) {
if(runs_left > 1){
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,-45);
}else{
setprop("/sim/screenshots/runs", runs_left-1);
print("runs_left-1 =",runs_left-1);
takescreen(4,45);
}
settimer(scr_runs, timeint*5, timeint*5);
}else{
setprop("/sim/menubar/visibility", menubarvalue);
setprop("/sim/current-view/field-of-view", fovvalue);
setprop("/sim/current-view/heading-offset-deg", headingvalue);
setprop("/sim/current-view/pitch-offset-deg", pitchvalue);
setprop("/sim/freeze/master", freezemvalue);
setprop("/sim/freeze/clock", freezecvalue);
}
}
scr_runs();

Now you are ready to start flightgear. When in the game press the "F3" key and wait. You will see the camera change heading and pitch automatically. When the required screenshots are taken, the original view is restored. Now exit flightgear, look for saved screenshots in png format and follow next step.

====Stitching the panorama with Hugin====
Copy all the eight screenshots in a new folder named as you want. Open this folder and create in it a new text file called panorama.pto. Open this file and copy the following lines in it:

# hugin project file
#hugin_ptoversion 2
p f2 w3000 h1500 v360 E0 R0 n"TIFF_m c:LZW r:CROP"
m g1 i0 f0 m2 p0.00784314

# image lines
#-hugin cropFactor=1
i w800 h600 f0 v120 Ra0 Rb0 Rc0 Rd0 Re0 Eev0 Er1 Eb1 r0 p-45 y0 TrX0 TrY0 TrZ0 j0 a0 b0 c0 d0 e0 g0 t0 Va1 Vb0 Vc0 Vd0 Vx0 Vy0 Vm5 u10 n"fgfs-screen-001.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-002.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-003.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p-45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-004.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y0 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-005.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y90 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-006.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y180 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-007.png"
#-hugin cropFactor=1
i w800 h600 f0 v=0 Ra=0 Rb=0 Rc=0 Rd=0 Re=0 Eev0 Er1 Eb1 r0 p45 y270 TrX0 TrY0 TrZ0 j0 a=0 b=0 c=0 d=0 e=0 g=0 t=0 Va=0 Vb=0 Vc=0 Vd=0 Vx=0 Vy=0 Vm5 u10 n"fgfs-screen-008.png"

# specify variables that should be optimized
v r1
v p1
v y1
v r2
v p2
v y2
v r3
v p3
v y3
v r4
v p4
v y4
v r5
v p5
v y5
v r6
v p6
v y6
v r7
v p7
v y7
v

# control points

#hugin_optimizeReferenceImage 0
#hugin_blender enblend
#hugin_remapper nona
#hugin_enblendOptions
#hugin_enfuseOptions
#hugin_hdrmergeOptions -m avg -c
#hugin_outputLDRBlended true
#hugin_outputLDRLayers false
#hugin_outputLDRExposureRemapped false
#hugin_outputLDRExposureLayers false
#hugin_outputLDRExposureBlended false
#hugin_outputLDRExposureLayersFused false
#hugin_outputHDRBlended false
#hugin_outputHDRLayers false
#hugin_outputHDRStacks false
#hugin_outputLayersCompression LZW
#hugin_outputImageType jpg
#hugin_outputImageTypeCompression LZW
#hugin_outputJPEGQuality 100
#hugin_outputImageTypeHDR exr
#hugin_outputImageTypeHDRCompression LZW

Save the file and open it with [http://hugin.sourceforge.net Hugin]. In Hugin go to the "stitching" tab and press the "Stitch Now" button. You will be asked where to save the resulting image. Select a path and press ok. When Hugin terminates the stitching process you are done. Browse to where you tell Hugin to save the panorama, and take a look at the image to check if something went wrong.

Howto:Make full spherical panorama

2010-11-20T10:20:00Z

Cri: Created page with 'In this howto I will explain how to make full spherical panorama in FlightGear. The semi-automated process is useful for everyone that want to contreibute…'

File:C172p-cockpit-pano.jpg

2010-11-20T09:38:07Z

Cri: An equirectangular 360x180 pano of the cessna c172p cockpit

An equirectangular 360x180 pano of the cessna c172p cockpit