FlightGear wiki - User contributions [en]

FlightGear wiki:Village pump

2014-09-02T19:35:54Z

Alexis:

{{Archives|[[/Archive 2012|2012]], [[/Archive 2013|2013]]}}
Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

: Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

: Old discussion should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

----

== MediaWiki updated to 1.22.0 ==
I've updated MediaWiki to the latest stable, 1.22.0 today. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.22

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:00, 26 December 2013 (UTC)

=== Found bugs ===
* Clicking the category link at the bottom of some articles will give a fatal error. For clicking the [[:Category:FlightGear]] at [[FlightGear]] will give the error message: ''Fatal error: Class 'Services_JSON' not found in /home/wiki/wiki/extensions/CategoryTree/CategoryTreeFunctions.php on line 224''.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 03:44, 28 December 2013 (UTC)
:: The CategoryTree extension relies on a function that was removed as of 1.22.0, so the extensions needs some fixing. I've disabled it for now.
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)
::: Yay, CategoryTree is back. Thanks Gijs!
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 19:50, 6 May 2014 (UTC)

* Also, the mobile theme results in an error: ''Fatal error: Call to undefined method MobileFormatter::setHtmlMode() in /home/wiki/wiki/extensions/MobileFrontend/includes/MobileFormatter.php on line 62'' (works fine after selecting desktop mode).
: Thanks,
: [[User:Philosopher|—Philosopher]] ([[User talk:Philosopher|talk]]) 03:59, 28 December 2013 (UTC)
:: I forgot to update the mobile extension. Works again ;-)
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:01, 28 December 2013 (UTC)

* In the CategoryTree the FlightGear category [[:Category:Documentation|appears empty]]. The solution is reported at [[mw:Extension:CategoryTree#Member counts are wrong, gray arrows ► are shown instead of ►]]. It's a minor problem but the solution looks easy, for what I can tell.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 00:27, 11 May 2014 (UTC)

:: Unfortunately that doesn't seem to help...
:: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:11, 11 May 2014 (UTC)

== Got any ideas for a better name for this page? ==
As this is for this page in particular, see the [[FlightGear wiki talk:Village pump#Any ideas for a better name|talk page]].

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:44, 5 March 2014 (UTC)

== Template for announcement of changes and new features ==

From a forum PM from Hooray (posted here with his permission):

<div style="background: #fafaf0; padding: 1em;">
hi, whenever we announce a new feature, we typically need to do this in three places:

* newsletter
* changelog
* the docs (corresponding wiki articles)

so far, we have always copied & pasted things, I would prefer to have a single template for this instead, something like
{{tlx|Announce|version|description}}

This could add announcements to each release cycle (i.e. 3.2 currently), and we could maybe automatically add things to the newsletter and the release changelog.

Like I said, I would like to avoid redundant efforts, i.e. less copy & paste

Do you have any ideas on how to implement this using existing wiki means ?

Ideally, we would create a new announcement, like for example "canvas mouse button support", and could then use this announcement in all 3 places by calling the corresponding template.

Thanks
</div>
My take is that to use a separate template for each new feature is not a good idea, but if I understand him correctly his intention is to gather up each months new features in one template.

Any thoughts on this?

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:14, 5 March 2014 (UTC)

{{WIP}}

<pre style="white-space: pre-wrap; margin-left: 1.5em;">I am thinking of restructuring the way we're writing our newsletter by focusing on our "ugly stepchild", namely the "changelog" - as others like Torsten have pointed out, we should ideally be writing the changelog as early as possible - but the truth is, it's mostly forum people contributing to it, and it's not seen too many edits. The newsletter is working a bit better for us. So I was thinking of how to unify both worlds - especially keeping in mind that our changelog encompasses basically 6 months, i.e. 6 newsletter editions.

So I am considering to split up our newsletter into a handful of building blocks and use a few templates, so that additions are added through a few custom templates, that would automatically add things to the changelog.

The changelog would then be written by contributing to the newsletter and using the proper templates, such as e.g.:

{{changelog|version=3.2|category:aircraft|type=updated|announcement=The 747-400 and 777-200 have received extensive updates, and are now both using the new MapStructure-based NavDisplay framework|screenshots=|videos=}}

The changelog would then be procedurally assembled by processing all templates for the corresponding release cycle.

I would even consider locking the changelog itself, and making it just a template that references the stuff included via templates.

We may however benefit from a few additional mediawiki extensions. But otherwise, I am hoping that the changelog is going to be more comprehensive, while the wiki would become more "formal" - we could obviously still support additions without using changelog-templates, i.e. those would be excluded.

thoughts / ideas ?

(CC'ing Philosopher, because he's been doing some template stuff, too)</pre>

:Need to come up with a template that handles announcements, primarily for the changelog and the newsletter. There's a mutual relationship here, but the newsletter is much more popular, i.e. sees more contributions and more activity overall. Changelog writing is still a chore. But basically 6 months worth of newsletters are equivalent to a single changelog, we only need to establish some framework around this - and then the whole changelog could be mostly based on newsletter contributions. It would greatly help to request people to make announcements ALWAYS using 3rd person speech, so that things can be directly copied from the forum/devel list to the newsletter/changelog. That's kinda the idea here. It would reduce our workload quite significantly

:* Changelog
:* Newsletter
:* Devel List
:* Forum
:* Website

:{{unsigned|21:25, 24 April 2014‎|Hooray}}

::I will probably have to take a look at this now and again to think about if and how this could be done. I assume Hooray is aiming at having each newsletter and change log built up mostly from "instances" of a template like in the above comments.

::There are pros and cons with this approach, as with any. I think that one of the cons is that even the slightest overhead and/or complication might scare away a few contributors. But at the other hand I fully understand that reading through six months of newsletters + forum posts + devel list posts are not that fun either (though I would guess that is not how things are done ;-).

::''Slightly off topic'' is that I would like to see a section in the change log mentioning changes that will break backwards compatibility. I first saw such a section, "Breaking changes", in the [https://www.mediawiki.org/w/index.php?title=Release_notes/1.22&oldid=848518#MediaWiki_1.22.0 change log of MedeiaWiki 1.22] when the software of this wiki was updated, and figured it would be a good idea. This could be useful for things like for example figuring out whether FlightGear x.x can use World Scenery y.y.

::''Even more off topic'' I think that the wiki/newsletter/devel list/etc are rather blunt tools for keeping an up to date change log. My gut feeling is that there are tools for that around, and even if we do not use them we might borrow some ideas from them, hopefully without bringing a lot of red tape(!).

::—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 20:14, 27 April 2014 (UTC)

::: Interesting subject! I think going through just 6 newsletters by hand is more rewarding than coming up with complex templates that will increase the entry barrier of the newsletter and still require summarising/rewordings afterwards to fit the concise format of a changelog. Introducing a template on the wiki won't take away the forum/devel list scanning that's required as not everyone contributes to the wiki.
::: I do support the "breaking changes" idea though ;-)
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 19:18, 1 May 2014 (UTC)

== Very dispersed Boeing 777 articles! ==

Hi, I got interested in Flightgear and was taking a look at the Boeing 777 articles and noticed that it was incredibly spread out.

Each aircraft has it's own page with information to varying degrees of completeness. Having a look at the A330 articles, they are much more 'aligned' and it's a lot easier to find stuff. Maybe this could be something that could be done with the Boeing. Since both seem to be very similar, I'm thinking that there could be a common page on help and tutorials respectively, with the individual type pages catering to unique information. I started on some stuff but pretty quickly figured out it was a better idea to check here first :)

--[[User:Manfred|Manfred]] ([[User talk:Manfred|talk]]) 11:55, 25 March 2014 (UTC)

: Doing a simple search for pages containing "777" (see [http://wiki.flightgear.org/index.php?search=777&title=Special%3ASearch&fulltext=1 this link]) I quickly see what you mean.

: I assume that the different versions may have different authors and thus probably are slightly different from each other when it comes to handling and completeness. It might be a good idea to start by going through each of the help pages and tutorials (preferably while playing with the different aircraft at the same time), as well as having a look at help dialogues and any readmes in the aircraft packages.

: Making a common page, while highlighting differences between the different versions, could probably help other users a lot and may perhaps be a help for aircraft developers to use features from more complete versions to improve the other ones as well as help motivate harmonizing handling like for example key bindings.

: If I understand your intention I can not see why anyone would do anything but trying to give you helpful hints, after all this is a wiki. :-)

: One hint for starters is to begin working on a page as a subpage to your user page, like for example [[User:Manfred/Boeing 777 Autopilot]] (I just moved it) and then moving it to the article namespace when you feel it has reached the level where you are comfortable with it (though this is not by any means necessary, it's just that I like doing so myself).

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 28 March 2014 (UTC)

: I am interested to help, this page could be a model of what we could offer : [http://wiki.flightgear.org/Boeing_787-8_Dreamliner 777-8 Dreamliner]
: -- [[User:F-JYL|F-JYL]] 21 April 2014 09:32

== Bash and DOS syntax highlighting ==

[[User:Daemonburrito|Daemonburrito]] found that we can use syntax highlighting for Bash. I guess that means that we could use syntax highlighting for most Linux (and possibly also Mac) command lines. Looking at [[mediawikiwiki:Extension:SyntaxHighlight_GeSHi]] I find that we also also probably can use that for DOS prompts.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:24, 5 May 2014 (UTC)

: We've had that extension installed for a while now. Everything that's listed at [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi#Supported_languages Supported languages] is supported, plus Nasal.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:23, 5 May 2014 (UTC)

:: I'm aware of the list, but was not aware that syntax highlighting could be used for shell programming (and hence shell promts) and guessed I was not alone.
:: Basically added the topic to highlight (pun intended) the possibility to do so. I should probably also mention it in [[Help:Formatting#Syntax highlighting]].
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:53, 5 May 2014 (UTC)

== A plan for a reorganization of the wiki ==

There is an ongoing discussion on [[User:Bigstones/Essay:A plan for a reorganization of the wiki]]. Please comment on its talk page, to avoid scattering the discussion. This "section" is only intended to inform about it.
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:53, 7 May 2014 (UTC)

== The new progress bar icons ==

I just changed icons that {{tl|progressbar}} is using and would like some constructive feedback.

Some things I have noted myself is that while I used a blend of the colours used in the old icons and in some of [[Special:ListFiles/Johan_G|my other icons]], these icons have a much larger coloured area and thus might have a little high contrast.

In any way I am going to let this rest for a week or two and follow it up then.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 01:05, 10 May 2014 (UTC)

: After having made them a tiny pixel smaller (from 16 px to 15 px) and having done no other changes I seem to be liking them more and more, so I leave them in their current state.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:13, 24 May 2014 (UTC)

== Category:Support ==
As it seems that support organization is a priority, I created [[:Category:Support]]. I hope the name is generic enough to avoid misunderstandings... but I thought better to have a bad one, than nothing. I'll try to put there everything on support I find so that it can be better organized (merged/split and then cleaned up).
--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:06, 11 May 2014 (UTC)

:Hi,
:
:I didn't read through all of your ideas yet, but isn't "Support" a rather obscure term? Everything could fit under that branch, so we'll end up with yet another giant category; which you tried to prevent, right? Or maybe I'm just missing the bigger picture...

:[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:23, 11 May 2014 (UTC)

:: Hi, I figured out (''edit: led to figure out'') that support organization is a major problem. There's a lot of "support" related articles, 2-3 articles only on OpenGL. I hoped that this name could indeed be wide enough, and that in case it could just be renamed. Troubleshooting seemed to narrow to me on the other side, but if you think that would be better I can change it now (waiting for response before proceeding).--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 13:29, 11 May 2014 (UTC)

::: Take [[Settings for slower graphics cards]] for example. It's categorised under [[:Category:Performance tuning]]. I would expect that to be a sub of [[:Category:Support]]. Anyone looking for articles on how to improve performance can check that category then. I don't expect anyone to go through a very broad category with 100s of articles to find info on a rather specific subject.
::: Or maybe I should reword my comment into a question: What would be the use case of [[:Category:Support]]?
::: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:39, 11 May 2014 (UTC)
::: PS: I know we have a lot of bloated categories on this wiki, so I'm glad you've brought all this back on the agenda ;-)

:::: With the example: I confess I was probably deceived by the presence of some development related stuff in [[:Category:Performance tuning]]. I thought it would be better to separate development and usage. Framerate is either a user issue, or a developer's aim. I think the two can be separated. The problem is I moved out the most of it! I should consider the contrary. I'll undo. (I currently have like 20 open browser tabs so it might take me some time).
:::: The use case however is: gather support articles so that a maintainer can split/merge them to make them more organized. Once that's done, there won't probably be more than 10 articles, and if there are, still one can subcategorize. In the above case, I just took the longest path, but given the lack of tools I confess I just wanted to get started.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:00, 11 May 2014 (UTC)
:::: ... I must confess also that after undoing, I feel the urge to redo that again. The two non-support related articles, [[GIT Performance Tests]] and [[Howto:Use the system monitor]] (where btw, the "profiling" section might be directed to ''core'' developers?) would have no place if I move this category into support. That's also why I moved it into Development. Let me know what you think, also regarding the Support category name.
:::: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 14:24, 11 May 2014 (UTC)

== FlightGear screenshot categories ==

I have been thinking about this for quite a while. When I was categorising the images, I gave the categories with the FlightGear screenshots quite cumbersome and long names.

I guess the discussions with Bigstones, in particular [http://wiki.flightgear.org/index.php?title=User_talk:Bigstones/Essay:A_plan_for_a_reorganization_of_the_wiki&diff=70678&oldid=70675 my reply here] (see second paragraph under 2.) might have stirred up some old dust for me. :-)

The cumbersome and long names has a couple negative effects. Firstly they are way longer to type than should be necessary, secondly, and more important I think, the probability that they show up in the upload wizard probably is rather low as they all begin with "FlightGear..." (what was I thinking, like if someone would upload a bunch of X-Plane screenshots here). I ''guess'' that by beginning most if not all screenshot category names with "Screenshots of..." the chances they would be used will increase.

In addition to that some of those categories are way too large and need to be diffused (broken down into smaller categories).

I have noted that a lot of aircraft images have been added to the aircraft article categories. I would prefer if the screenshot categories associated with different kinds of aircraft (e.g. fighters or airliners) would be subcategories to the screenshot categories ''and'' that those screenshot categories would be a subcategory to the category for those kinds of aircraft. I have at some point started to try mimic the structure of [[:Category:Aircraft by type]] in Category:FlightGear screenshots of aircraft by type, but got distracted or forgot about it for a while. Someting similar might be needed for the cockpit screenshots.

The note about intended contents should also mention that these categories are intended only for in-sim screenshots from FlightGear.

In conclusion I suggest, and would like feedback on, the following:

{| class="wikitable"
! Current category !! Suggested new category !! Alternative new category !! Comment
|-
| [[:Category:FlightGear cockpit screenshots‎]] || [[:Category:Screenshots of cockpits]] || Cockpit screenshots ||
|-
| [[:Category:FlightGear cockpit close-up screenshots‎]] || [[:Category:Screenshots of cockpit details]] || Cockpit close-up screenshots ||
|-
| [[:Category:FlightGear dialogue screenshots‎]]
| <s>Category:Screenshots of ‎dialogues</s>

[[:Category:Screenshots of FlightGear dialogs‎]]
| <s>Dialogue</s> Dialog box screenshots ||
|-
| [[:Category:FlightGear exterior screenshots]]‎ || [[:Category:Screenshots of aircraft]] || Exterior screenshots ||
|-
| [[:Category:FlightGear interior screenshots]] || [[:Category:Screenshots of cabins]] || Cabin screenshots ||
|-
| [[:Category:FlightGear scenery screenshots]]‎ || [[:Category:Screenshots of scenery]] || Scenery screenshots ||
|-
| Category:FlightGear screenshots of aircraft by type || [[:Category:Screenshots of aircraft by type]] || — || Should only contain categories
|-
| Category:FlightGear screenshots of vehicles || [[:Category:Screenshots of vehicles]] || Vehicle screenshots ||
|-
| [[:Category:FlightGear weather screenshots]]‎ || [[:Category:Screenshots of weather]] || Weather screenshots ||
|}

In essence it is a huge bot job, except for the diffusion of the largest screenshot categories.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 15:57, 12 May 2014 (UTC)

: As I might have said already, I'm ok with it and in particular I agree that images would be easier to find if in their own branch. The only thing, I think it's not going to last if the upload wizard doesn't enforce the use of a subcat of "Files", or at least, suggests that area in some handy way (i.e. not a written notice). Maybe the CategoryTree could be included (like with templates) to help finding the right category? It's hard to figure out a good one by typing characters one by one.
: --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 21:49, 12 May 2014 (UTC)

:: Created the category pages as above, except for Category:Screenshots of ‎dialogues, which I found a bit ambiguous. I named that one Category:Screenshots of dialogues in FlightGear‎ instead.
:: I have also added a request at the [[User talk:BotFlightGear#FlightGear screenshot categories|bot talk page]] ([http://wiki.flightgear.org/index.php?title=User_talk:BotFlightGear&oldid=71130#FlightGear_screenshot_categories permalink])
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:59, 13 May 2014 (UTC)

::: Did the move to [[:Category:Screenshots of aircraft by type]] by hand. Was only a few files.
::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:46, 13 May 2014 (UTC)

::: I hope I'm not late, I noticed only now, but ''dialogue'' tends to be used more as in "discussion between two", while the GUI elements are usually spelled ''dialogs''. I guess that more than real confusion this distinction would cause just minor hilarity, but... you never know, you might find in there screenshots of radio chat with ATC. (being not a native english speaker, [http://english.stackexchange.com/questions/59640/what-is-the-difference-between-dialogue-and-dialog here's my ref.]) --[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 19:20, 13 May 2014 (UTC)

:::: Well spotted, good reference as well and most important not too late. Thank you! I was wondering a bit but guessed that dialog was more or less colloquial as dialogue seemed correct with both my browsers English and American English dictionaries. Swedish schools teaching (very!) British English probably have something to do with my spelling as well.
:::: Changed the request on the [[User talk:BotFlightGear#FlightGear screenshot categories|bot page]] from Category:Screenshots of dialogues in FlightGear‎ to [[:Category:Screenshots of FlightGear dialogs]].
:::: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:06, 14 May 2014 (UTC)

=== Having separate image categories or not? ===
One thing that keeps nagging me is that all Wikipedias I have been able to read and some I can hardly read (English, Swedish + German and French) have separate categories for files/images. There is probably a reason for that (I am guessing at mainly ease of finding images for articles and possibly also for bandwidth reasons).

The upload wizard is borrowed from Wikimedia Commons (but is it properly attributed?) where pretty much all categories are for files/images. While I am not aware of its technical details I see few if any efficient ways it could be modified to only or primarily suggest image categories. As I see it it would require a ''fresh and updated'' list of categories that in one way or another would require some manual intervention.

Two things I have done so far is to re-categorize images and that I have begun trying to link the nodes to the nodes in the branch with the article categories by putting the image categories in the article categories (this is done on a very small scale though).

Questions is though: What is in the best interest of the users? Should I keep on having them separate or should I just let it grow wild(er)? It could be an interesting experiment though it would require a lot of work if it turns out less favourable.

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 22:02, 10 July 2014 (UTC)

:I saw you implementing this at some of my airport screen-shots and immediately adopted it on other images. I think your idea of separating those categories would help us puting a link at the end of each article which says: "Media about :XY". Thats why I think all the other wikis provide separated categories. That's the only way to get linkable categories which only contain media.

:--[[User:August|August]] ([[User talk:August|talk]]) 22:18, 10 July 2014 (UTC)

== Conventions on discussion conclusions ==
Sometimes proposals don't get the attention the proposer might have hoped for. Of course, everyone's involved in their projects, and following discussions in "recent changes" isn't easy, so nothing personal, my question is ''very practical''.

Sometimes these proposals need help from others (like my [[User_talk:Bigstones/Essay:A plan for a reorganization of the wiki#Bot proposal .28request.3F.29|"remove redundant categories"]]) so it's pretty clear that one will have to wait and retry/insist for that. Some other times though (like my above "Category:Support" topic - with which btw I did some mess moving messages around) one could easily continue on his/her own. In such cases, I feel that lack/loss of attention means "Ok, I don't mind if you do that, in case, we'll discuss the results" (like for the FAQ update - btw, thanks to the reviewers of [http://wiki.flightgear.org/index.php?title=Frequently_asked_questions&oldid=71015 my cuts]). If this is correct, I'd like to add it to the [[Help:Maintenance]] page, because it could help getting more things done and avoid misunderstandings. Oh, and by what I said, if I don't get answers, I'll take it for granted :D

--[[User:Bigstones|Bigstones]] ([[User talk:Bigstones|talk]]) 12:43, 13 May 2014 (UTC)

: I have found the lack of feedback to be discouraging at times, but at other times I have just went ahead and done things the way I would like to have them done, like for example my reorganisation and extension of the help pages, as well as adding the "[[FlightGear wiki:Village pump|Discuss!]]" link to the left side menu.

: I would guess that you draw the right conclusion with the statement that "Ok, I don't mind if you do that, in case, we'll discuss the results". The very most of the times that is the way to go. The good thing with a wiki is that it is so easy to revert a change (i.e "View history" tab → Go to topmost edit → Click the "undo" link). If if things go really wrong most things can be salvaged from the page history (though it can be a lot of work at times). ;-)

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:03, 13 May 2014 (UTC)

== Editing JavaScript files ? ==

: ''Moved here from [[Talk:Portal:Wiki#Editing JavaScript files ?]] ([http://wiki.flightgear.org/index.php?title=Talk:Portal:Wiki&oldid=72290 permalink]) since this might affect all users.''

I think, at some point, I saw someone editing JavaScript files here (Johan_G or Gijs probably) - what is involved to do that ? Any links/pointers ? Okay, found something at [[MediaWiki:Common.js]] Is it also possible to create custom JS/plain text files without any wiki markup ? Are my privileges even sufficient ? --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 21:11, 2 June 2014 (UTC)

: Nope, was not me. Javascript files is as far as I know currently limited to [[MediaWiki:Common.js]]. It is apparently possible to change some settings so that one can add "user javascript pages" (as well as "user Cascading Style Sheets"), see the WikiMedia Wiki pages [http://www.mediawiki.org/wiki/Manual:$wgAllowUserJs Manual:$wgAllowUserJs] (and [http://www.mediawiki.org/wiki/Manual:$wgAllowUserCss Manual:$wgAllowUserCss]).

: Both can be useful for testing stuff before including them in the "common" (i.e. site wide) files, as well as for personalizing the look, feel and functionality. I do not know what issues they could cause or if we have the permissions to change it. Maybe Simon and Gijs are the ones who can do it.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 04:40, 3 June 2014 (UTC)

== MediaWiki updated to 1.23.0 ==

I've updated MediaWiki to the latest stable release (1.23.0) today. I'm now updating all extensions, so some things may be broken temporarily. Please report bugs if you find any. For a list of changes, see https://www.mediawiki.org/wiki/Release_notes/1.23

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:04, 8 June 2014 (UTC)

== readability and quality of articles - quoting statements from the forum useful? ==

In the last two weeks I'm trying to debug something so I wanted to find some needed information in the wiki. Instead I stumbled on articles full of quoting meaningless and partly false) statements from the forum. I don't see the meaning of this, as it influences the readability of the wiki more and more in a negative way. And I don't see why this is in any way important or helpful to users. I guess this known user wants simply highlight some certain facts, but the way he is doing this is far away from any quality standard known from wikipedia.org, educational books and similar stuff on the web. As I could see former discussions about this issue had been useless. I have two articles about helicopter flying and helicopter-fdm in the pipeline, but I fear that those articles will be also filled up with useless quotes from the forum. So what quality standards the wiki is using?
Wouldn't be a simple footer with a link to the statement better than inserting quotes?
--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 09:33, 17 August 2014 (UTC)

: Hi HHS, assuming that you are referring to my edits: those are primarily about coding issues, so it may not be obvious to you if/how those are useful, but there are a number of very concrete features that have materialized by "bootstrapping" things like this over the last years.

: Now, whenever you start an article, or add significantly to it, you are obviously free to take over maintenance and "veto" any changes that you disagree with.

: As you can easily verify, I am not at all involved in anything relating to helicopters, so be assured that I won't interfere with any of your contributions in that department - that is, unless there's relevant feature requests and discussions to be summarized - in which case, I would consider any relevant additions to be outside the scope of the two topics you mention.

: If in doubt, I'll hereby promise to get in touch with you upfront, should I desire to contribute to any of "your" articles. So there's no need to use any blackmailing tactics by making any of your potential contributions dependent on whether a certain contributor agrees with you or not.

: The discussions you are referring to were specifically about the newsletter, where it was primarily Gijs who stated that such quotes should be cleaned up, and I have stated that I won't interfere with any such quality standards, but -like you- I would simply prefer to have such quality standards established first.

: Like I said elsewhere, I do not even disagree with the arguments made, but obviously it takes much more time to rephrase and summarize discussions than copying relevant statements directly to the wiki. Still, some concrete features (in terms of code) were very much based on such summarized discussions.

: Besides, I am really not sure why some people are turning into drama queens, and even attention junkies when it comes to certain contributions - especially people who have no significant/visible track record of contributing to the wiki in any major way?
: Obviously, this doesn't apply to people like Gijs, Johan_G and Thorsten whose feedback is obviously valuable-but I find it hard to believe that someone who -allegedly- "wanted to find some needed information in the wiki" would be affected by contributions, or even discussions/flame wars, in completely unrelated wiki articles-if that's the case, I would suggest that you may need help to properly use the wiki-for which you can get in touch with any of the admins, including myself - we'll be glad to provide all the assistance that you may need, including help with editing/improving articles.

: As a fellow wiki contributor, I happen to find massive edit histories confusing, i.e. all the maintenance work done by Gijs and Johan_G is hard to keep track of-but otherwise, I don't usually participate in discussions that I am not affected by. So, I find it kinda fascinating how you are apparently affected by flamewars taking place on very much unrelated talk pages ?

: Thus, I am looking forward to your contributions and I am offering to walk you through the necessary steps to integrate your changes properly, without being affected by completely unrelated articles, and their discussions. If there are any helicopter related articles that contain "meaningless quotes" in your opinion, please do feel free to either remove those (you can add a note or HTML comments tag to easily hide huge sections), raise the issue on the article's talk page (using civil language preferably), or simply point out those articles here, so that I can take a look.

: Once again, like I previously said, flame wars and disagreements are always unfortunate, but they come with the territority, and usually it takes at least '''two''' - and certain language is more likely to elicit behavior that we as a community find destructive - but apparently, there's also quite a bit of behind-the-scenes networking going on, so that subjectivity gets lost quickly.

: As I previously said, on wikipedia (or even just the FlightGear forum), your language would have gotten your comments censored, and your account quite possibly banned temporarily - so whatever your intentions were, you were almost certainly contributing to the problem, not the solution.

: Now, I didn't take any actions, because I am obviously not objective, and because I don't normally get involved in moderating stuff - but whenever two parties (like i4dnf and myself) decide to escalate a discussion beyond a certain point, it is up to '''them''' to deal with the terms - you shouldn't just show up and get involved without also expecting to be treated accordingly, especially given your choice of language - no matter if your hobby/profession is psychology or not, the kind of name calling you started would have been absolutely inappropriate elsewhere, especially for someone who's trying to be authoritative about a discussion that he hasn't even be involved in at all.

: And exactly the same thing happened a couple of days ago on the P51d's talk page where you were trying to "moderate" things in a rather blunt fashion - in the meantime, I have been in touch with hvengel via PM and exchanged a number of PMs with concrete suggestions on potential '''Nasal''' related issues (that you seem to be entirely unaware of, but still feel qualified to comment on ...), so that I simply disregarded your edits and tone.

: Finally, if you're interested in becoming a moderator to help moderate the wiki or forum, I suggest to get in touch with Gijs or Curt to get you set up - help is always needed and appreciated (I never asked for any of those "privileges", I prefer unencumbered discussions personally) - and I am more than willing to hand over the corresponding duties to you if they agree - but would suggest that you try to follow your own advice about applying good quality standards, but also an appropriate tone - while resisting the temptation to get involved in debates that you don't fully understand.

: All this doesn't mean however that I wouldn't agree with your comments on having a quality standard established. Or that I wouldn't appreciate your contributions. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:23, 17 August 2014 (UTC)

:: I am a strong believer in that a text (including illustrations), and more so a large collection of text like for example this wiki, should be both descriptive, concise and well structured. As for articles being concise, I am not a big fan of all the quotes, though I can see ''some'' of them useful. There is a lot to say about lengths of articles, sections and paragraphs, and the sometimes unfortunately combined lack of both being not very concise and not very descriptive, that really, really does not help reading those articles. There is also a lot to say about structure in articles by the use of section and subsection headings and in particular between articles.

:: Many articles strongly related to each other leave a lot to be wished for. There is often a huge amount of overlap and in addition there is often a horrendous need for having to read through related articles that in turn would require reading through the first article and then some to be understandable. I consider it totally unacceptable. Together with the diffuse verbosity of some articles it makes it really hard to penetrate the subject in question.

:: As for my many small edits with rather large summaries, I have my preferences set up so that my edits by default is marked as minor. While it may not be obvious at first, those edits can quickly be hidden by clicking ''Hide minor edits'' at the top of a history page. Unless I forget to uncheck ''This is a minor edit'', only edits that will be visible, in particular in articles, will not be submitted as minor edits.

:: ''Finally, as for the a bit too heated debates about edits on this wiki (dare I say quibbles) that has little or nothing to do with the discussion pages they were posted on, I have actually considered putting an identical message on a few users discussion pages asking them to '''take a few steps back''', '''calm down''' and consider '''what''' they have posted, '''where''' they posted (i.e. will a post there be useful), and '''if''' that really had to be posted, '''as well as blocking each user for 24 hours''' (three users I will not name, you can figure out who you are, and I pretty much do not care who started).''

:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 17:09, 17 August 2014 (UTC)

::: As can be seen in the logs, Gijs has just begun drafting some kind of style guide - I guess some more feedback would be good. But no matter the outcome, I don't mind adjusting my behavior/contributions accordingly, or adapting the [[Instant-Cquotes]] according to the requirements laid out there.

::: However, overall, I'd suggest to keep a healthy balance here - some wiki maintainers have increasingly strict requirements, and are obviously trying to adopt wp's best practices. Then again, our main issue is not having good ideas and coming up with guidelines, it's having the manpower -and time- to actually apply/enforce those.

::: Which is something that also applies in the core/fgdata/scripting department: There's an increasing amount of contributions that wouldn't have passed a review a few years ago - but like I've mentioned a few days ago: some "immature" contributions have meanwhile allowed "unskilled" (=new) contributors to become domain experts.

::: The same thing could very well happen in the context of the wiki: Back when we discussed certain wiki changes (such as making you, Johan_G, a wiki admin) - the whole idea was about turning an avid contributor into an '''expert''' over time, by providing the time, expertise -but also a playground and "grace period"- to experiment with changes, even if those may be relatively immature in the beginning. Meanwhile, you have become an expert when it comes to wiki templates - and I'm always grateful for any advice/help in this area.
::: And this can be seen in many other FG areas. We've seen this particular debate come up a number of times on the forum, and generally end-users are not too happy about having stringent requirements.
::: And there'd be at least half a dozen features that wouldn't be in FG today if fgdata requirements were similarly elevated/enforced (including the PFD/ND, Avidyne code etc).
::: Likewise, censorship/banning is a questionable measure, too - it has rarely, if ever, served us really well when dealing with real end-users (i.e. not just bots). Besides, in that case, you may want to get in touch with Gijs/Simon to have my account status downgraded/revoked, because I am not sure if you can really ban a fellow admin (I think I am in the same group as you).
::: But regardless if I remain involved in wiki maintenance or not, if any admin considers to use banning on real users, banning guidelines would probably be appropriate, too - i.e. could be based on wp (verbatim). Which would help ensure that certain tactics/language remain off limits. And it should also help to move such discussions to the User: namespace, so that people don't stumble across them accidentally - even though I am not sure that this would have prevented the 3rd user from interfering like he did...
::: But even apart from the fact that I generally don't consider censorship/banning appropriate tools, I would have been in a bad position to make this judgement, given that I was the one responding to those attacks in an equally-heated tone.
::: Never mind, I'll check if I can ban myself right away :-) --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:37, 17 August 2014 (UTC)

:::: Hello Johan
:::: Thanks for your answer. I'm studying to get a vocational school teacher, the last 6 months I was working as a freelance lecturer at a nursing school. So I not only have to read a lot of books, text and writing informative handouts, also had to create a lot of educational text for my students. Not always easy. For both sides, the students and me, it is important to get the needed information in a short time. At my university text is considered as scientific when the language is: comprehendible using short easy-to-read sentences , objective and unemotional. Though this wiki of course does not have to be seen scientific, we probably want the same: spreading knowledge. So I think the same rules applies to this wiki.
::::So in my eyes text full of quotes from the forum doesn't help here. Sometimes (but only sometimes!) it is needed to highlight certain facts with statements, therefor a quote can be helpful. As you said. But articles like [[http://wiki.flightgear.org/Status_of_AI_in_FlightGear]] aren't very helpful, not for user or (future) developers, and wasting space.
::::So I'm totally against such articles and especially the useless use of quotes.
::::How to deal? Proposal: www.wikipedia.org has a nice feature, they sign good articles with a star. Maybe we should do the same, so it is an orientation for those writing an article here. I think it is better then setting up "rules", especially as readability is also subjective.
::::--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 19:13, 17 August 2014 (UTC)

:::: Oh, I just read through the whole Manual of Style. Everything is said there, especially about quotations and the use of it. Thanks!
:::: --[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 19:20, 17 August 2014 (UTC)

::::: Just as input from one fairly new FG user/developer, to answer the original question: I did find one of the articles with many quotations from the forum to be quite useful. The Status of AI page (http://wiki.flightgear.org/Status_of_AI_in_FlightGear) had a lot of bits of discussion pulled in from the forums that I probably never would have taken the time to find on my own, and it helped me quickly wrap my head around the different aspects and approaches to AI in FlightGear and what kinds of improvements have been talked about. I suppose this type of article could need to be either pruned or updated as time went on, though, as the content would become less and less relevant as the discussion moves on.

::::: --[[User:chriscalef|chriscalef]]

:: @chriscalef: Thanks for actually providing a developer's point of view - it's really appreciated. Like I said elsewhere, I do fully agree that the style of such "collections of quotes" is very poor-but, we have many articles and features that started out as "stubs" exactly like you say. And we cannot possibly expect newcomers, interested in doing development, to do this degree of "research" in the archives, at the very least, it would be very unfriendly to keep pointing potential contributors to the archives like this and probably raise the barrier to entry, too - especially, because search terms are pretty specific.
:: But we also cannot be expected to create proper write-ups for each frequently raised topic on the devel list/forum.
:: Which is why those pages with quotes were/are created, and are being updated as time goes on.
:: I have been in touch with a number of contributors and developers to see if we can find a solution that keeps all considerations in mind, while still keeping in mind the degree of involvement and stakes people, and especially developers (current ones, but also future ones), have.

:: Obviously, given the number of important areas in FlightGear, competence and expertise vary widely among all contributors. And core developers may not necessarily be in a good position to judge the quality of of FDM/helicopter or 3D modeling related articles - and it seems that aircraft developers may not necessarily be in a good position to judge the quality/degree of usefulness of core developer quotes kept here.
:: Indeed, there's postings to be found on the forum from around ~2010 when I said that a property-tree based 2D rendering API could not work fast enough, and when I suggested that native Nasal bindings should be used instead - equally, write-ups like the original Canvas proposal were critically discussed/dissected by other contributors-meanwhile, as we all know, [[User:TheTom]] has proven all of us wrong with his [[Canvas]] system.
:: So I guess, that goes to show that everybody can be wrong-and proven wrong, even by newcomers, including even people involved in the project for years.
:: For now, I'll opt to stay out of this to allow all parties to remain level-headed... If anybody would still like to get in touch, please use my talk page or send a forum PM. I am sure that we can find a way that addresses all concerns, without possibly harming the project by applying quality standards that might kill off discussions/features prematurely. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 14:36, 19 August 2014 (UTC)

::::::@chriscalef:
::::::Are you aware that some of the quotes describing the "Status" are completly outdated? So I doubt that it was really useful. As an example the very last statement by Detlef Faber. Ground vehicles are now supported since a whole while (2-3 years?), they don't bank. The date of the quotes doesn't name the year, just the month.
::::::Btw. most of the quotes are by "Hooray" himself. Instead of quoting himself, he could wrote a small summary of all this: much more informative and more easy to read.
::::::Nethertheless: There is a style guide, which pretty much say everything. So no need from me to discuss this further: massive quoting is not wished! Point. --[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 16:24, 19 August 2014 (UTC)

The issue is not as simple as you are trying to make it sound, we're still talking about various pros & cons here - regardless of the whole style guide, and regardless of the fact that I do agree with all stylistic concerns voiced so far. The reasons for quoting myself is that I am trying to summarize frequently-raised topics, and those quotes obviously help with that.
But the quote you are referring to is not mine but is based on a posting made by DFaber in April 2014 (as you could have easily verified by clicking the link next to it!):

{{FGCquote
| here's my wishlist part 1: 
 
 
Disable the banking when turning with Ground Vehicles. There are Ground vehicles in FG, but mainly Trains, which I haven't been able to utilize for Cars. Also Cars need to lookup Ground elevation which AI Aircraft don't do too. 
 
FG determines submodel hits on AI/MP Objects by square Boxes around the Aircrafts Origin. These are too wide to be useful with Ground Vehicles and small Aircraft. Some more Size opions would be useful. 
 
When a new Target Heading is selected AI Aircraft don't turn harder than 30 degrees. It would be good to be able to configure this per Aircraft. 
 
I'd like to specify Model specific Properties like Livery, Type in the AI Scenario file. Right now I need to create and set them within the nasal section. 
 
These are some from the top of my head. More to come ...
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=207095#p207095
|title=<nowiki>Re: AI support</nowiki>
|author=<nowiki>DFaber</nowiki>
|date=<big>'''<nowiki>Fri Apr 25 2014</nowiki></big>
}}
}}

And based on looking at the C++ code a while ago, I have to agree with DFaber (and flug for that matter) that there are still various problems when it comes to controlling AI models from scripting space that are not supposed to behave like airliners/aircraft. I don't know how familiar you are with C++ code and the AI system in particular, but I also don't quite see how those comments were conflicting with your intentions to contribute to helicopter related articles. I would really prefer this to remain constructive and not turn into another pi**ing contest. I am sure that you have good intentions, but it seems hard to bring those across properly. And maybe that's in part because you do not belong to the intended target audience of such quote collections?
Thanks in advance for trying to keep this discussion "civil" though. '''Semicolon'''.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:10, 19 August 2014 (UTC)

:::::::Again: http://wiki.flightgear.org/FlightGear_wiki:Manual_of_Style#Specific_recommendations.
:::::::Then: Please keep your thoughts about the AI system, my intention etc. out here. They do not belong into this discussion here.
:::::::The quotations don't show the complete date - even if at the end you still have to verify every source. That is what I wanted to show you. The fact is, Detlef is wrong here (ground vehicles don't bank), but people reading those quotes in this official wiki thinks it is true. The same Emilian already told you.
:::::::--[[User:HHS|HHS]] ([[User talk:HHS|talk]]) 21:09, 19 August 2014 (UTC)

== PAF Team wiki Page ==
I would like to know if creating a PAF team wiki page would be a good idea ? i don't know if this type of page will be appreciated, because some page who talk about virtual airlines were deleted and listed on one page. But I think my situation is different (we are not à virtual airlines, but we are a french community in the french community) . I just think that this page would inform people who see "PAF team" on aircraft authors or when PAF team is quoted on the wiki.

This page would be written like that :
* Introduction
* Activities
** Flight school
** Multiplayer flight
** Developpement

What do you think? you have specific suggestions or reservations
Thank you for your opinion
--[[User:Alexis|Alexis]] ([[User talk:Alexis|talk]]) 19:35, 2 September 2014 (UTC)

[[Category:FlightGear wiki]]

FlightGear wiki:Village pump

2014-09-02T19:29:00Z

Alexis:

Fr/Escalier Mobile

2014-07-24T18:26:44Z

Alexis:

{{infobox Aircraft
|image =Mobile_Stairs.jpg
|name =Mobile Stairs
|type =Véhicule
|fdm =YASim
|status =Development
|authors =Maverick
|fgname =mobilestairs
|download =http://www.sol2500.net/flightgear/mobilestairs.zip
}}
'''Les escaliers Mobiles''' permettent aux passagers d'entrer ou de sortir de l'[[fr/Avions|avion]] quand aucun terminal n'est disponible. Ils ont étés créés pour s'adapter au [[Boeing 787]] et sont à sa hauteur.

== Développement ==
'''Géneral:'''
* pas d'animations des roues, du levage abaissement des escaliers.
* pas de lumières
* pas complètement texturé

Soyez libres de modifier le modèle si vous avez la chance d'être assez talentueux pour le faire. Partagez-le ensuite avec nous tous.

== Aide du véhicule==
{|
|Gauche
|0
|-
|Droite
|Entrée
|-
|Freins
|, (virgule)
|-
|Accélérer
|. (point)
|}

== Related lists ==
[[Fr/Vehicules|Véhicules]]

[[Category:Vehicles]]
[[en:Mobile Stairs]]

Mobile stairs

2014-07-20T12:50:22Z

Alexis:

{{infobox Aircraft
|image =Mobile_Stairs.jpg
|name =Mobile Stairs
|type =Vehicle
|fdm =YASim
|status =Development
|authors =Maverick
|fgname =mobilestairs
|download =http://www.sol2500.net/flightgear/mobilestairs.zip
}}
'''Mobile Stairs''' are used to get passengers in and out the [[aircraft]] where the full terminal facilities aren't available. They were designed to fit the [[Boeing 787]] and are at that height.

== Development status/Issues/Todo ==
'''General:'''
* no animations of wheels, stairs (up/down) and steeringwheel
* no lighting
* not completely textured

Feel free to modificate the model if you are lucky to be tallented enough to do so. Then, share it with us all.

== Vehicle help ==
{|
|Left
|0
|-
|Right
|Enter
|-
|Brake
|, (comma)
|-
|Accellerate
|. (dot)
|}

== Related lists ==
[[Vehicle]]

[[Category:Vehicles]]
[[fr:Escalier Mobile]]

Fr/Escalier Mobile

2014-07-20T12:45:06Z

Alexis: Created page with "{{infobox Aircraft |image =Mobile_Stairs.jpg |name =Mobile Stairs |type =Véhicule |fdm =YASim |status =Development |authors =Maverick |fgname =mobilestairs |download =http://..."

{{infobox Aircraft
|image =Mobile_Stairs.jpg
|name =Mobile Stairs
|type =Véhicule
|fdm =YASim
|status =Development
|authors =Maverick
|fgname =mobilestairs
|download =http://www.sol2500.net/flightgear/mobilestairs.zip
}}
'''Les escaliers Mobiles''' permettent aux passagers d'entrer ou de sortir de l'[[fr/Avions|avion]] quand aucun terminal n'est disponible. Ils ont étés créés pour s'adapter au [[Boeing 787]] et sont à sa hauteur.

== Development status/Issues/Todo ==
'''Generale:'''
* pas d'animations des roues, du levage abaissement des escaliers.
* pas de lumières
* pas complètement texturé

Soyez libres de modifier le modèle si vous avez la chance d'être assez talentueux pour le faire. Ensuite, partagez le avec nous tous.

== Aide du véhicule==
{|
|Gauche
|0
|-
|Droite
|Entrée
|-
|Freins
|, (virgule)
|-
|Accélérer
|. (point)
|}

== Related lists ==
[[Fr/Vehicules|Véhicules]]

[[Category:Vehicles]]
[[en:Mobile Stairs]]

Fr/Piper Aerostar

2013-08-17T10:29:11Z

Alexis:

{{infobox Aircraft
|image =Aerostar_700.jpg
|alt =Aerostar Super 700
|name =Aerostar 700
|authors =Syd Adams
|type =Civilian aircraft
|fdm =YASim
|status =Development
|fgname =aerostar700
|download =http://flightgear.org/Downloads/aircraft/#Aerostar-700
|ratingfdm =5
|ratingexterior =5
|ratingcockpit =5
|ratingsounds =4
}}
Le '''Piper Aerostar''' ou '''Ted Smith Aerostar''' est un bimoteur à hélice amécicain. Cet avion de transport léger a été conçu par Ted R. Smith. Il a initialement été construit par la Ted Smith Aircraft Company, qui après 1987 devient une part de la Piper Aircraft Corporation.

== Variantes ==
Actuellement, une seule variante est modélisée dans FlightGear:
* '''700 Superstar:''' un prototype avec fuselage allongé et deux moteurs IO-540M

[[File:Aerostar_700_Cockpit.jpg|thumb|270px|Le [[cockpit]] d'un Aerostar 700]]

== Mini-HOWTO ==
Ce mini-howto est basé sur mon expérience de vol personnelle sur ce magnifique avion (malheureusement, seulement dans FlightGear, jamais dans la vraie vie ...).

S'il vous plaît, n'hésitez pas à ajouter du contenu ou corrigez ce qui vous semble erronée.

==== Démarrage ====
* Allumez l'interrupteur de batterie et les deux alternateurs. Les commutateurs sont les 3 premiers de la gauche du panneau.
* Démarrez les moteurs en tournant les interrupteurs sur la droite (faites ctrl-c pour voire les éléments cliquables), et maintenez-les enfoncés jusqu'à ce que le moteur démarre.

==== Décollage ====

En raison de la faible surface alaire de l'Aerostar, il n'est pas recommandé de décoller sans volets. L'avion vous donnera l'impression de rouler éternellement !

* Volets: 20° (2nd cran) ou 30° (3ème cran), dépend de la longueur de la piste.
* Gaz: plein gaz
* Hélice: haut régime (petit pas).
* Mixture: plein riche
* Rotation: 80-100 kts, celà dépends de la configuration de vos volets (2cran ou 3 cran).

Laissez l'avion accélérer et passer les 140 kts avant de rentrer les volets.

=== Montée ===

* Volets: rentrés
* Gaz: 32~35 ingh
* Hélice: 2500~2600 rpm
* Mixture: réduire jusqu'à un écoulement de carburant d'environ 32gph
* Taux de monté: 1500~1700 fpm @160~180 kts

Un taux de montée de plus de 2000 fpm peut être atteint en étant plein gaz et hélice plein petit pas.

=== Croisière ===

Stabilisez l'avion à l'altitude désirée et trimer l'avion. Vous deverez atteindre plus de 217 kts en peu de temps ;-)

=== Approche ===

À cause de la faible surface alaire et la grande vitesse de cet avion, une réduction de la vitesse est préférable.

Lentement, réduisez les gaz (quasiment)à la position ralenti et cabrez l'avion pour diminuer votre vitesse sans perte d'altitude. Autour de 190 kts, commencez à sortir les volets (ouvert jusqu'au 3ème cran).

Essayez de garder un taux de descente de 1500 ~ 2000 fpm et de vitesse autour de 150 kts.

=== Atterrissage ===

Un circuit d'atterrissage sur une piste courte:
* 140 kts en vent de dos, stabilisé, volets à 30° (3ème cran), mixture plein riche et hélice à plein régime.
* Sortez entièrement les volets, réduisez votre vitesse à 125kts avant de tourner en base.
* Réduire la puissance et cabrez l'avion pour arriver en final à 110 kts.
* Atterrissage à 90 ~ 100 kts.

Sur une plus longue piste pourriez faire une procédure analogue sans appliquer pleins volets (ex: à 30 °), atteignant en finale une vitesse de 130 kts, et atterrir à 120kts.

== Lien externesExternal Links ==
* [http://www.aerostaraircraft.com/Specs.html Caractéristiques de l'Aerostar]
* [http://www.pilotfriend.com/flight_reports/reports/aerostar.htm Test de vol comme pilote Aerostar]

{{Piper}}

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

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Twin Engine Piston]]

[[en:Piper Aerostar]]

Fr/$FG AIRCRAFT

2013-04-20T20:18:08Z

Alexis: Created page with "'''$FG_AIRCRAFT''' fait référence au répertoire des avions de FlightGear. Il est disponible depuis la version 2.4.0 de FlightGear. Il peut être défini ..."

'''$FG_AIRCRAFT''' fait référence au répertoire des avions de [[Fr/FlightGear|FlightGear]]. Il est disponible depuis la version 2.4.0 de FlightGear.

Il peut être défini sur la première page de [[Fr/FlightGear Launch Control|FGRun]] (Avant la page de sélection de l'avion).

[[Category:Special directories|AIRCRAFT]]
[[en:$FG AIRCRAFT]]

$FG AIRCRAFT

2013-04-20T20:18:04Z

Alexis:

'''$FG_AIRCRAFT''' is refered to as the aircraft directory or directories of [[FlightGear]]. It is available since FlightGear 2.4.0.

It can be set on the first page of [[FGRun]] (previous from aircraft selection).

[[Category:Special directories|AIRCRAFT]]
[[fr:$FG AIRCRAFT]]

Fr/Accueil

2013-01-05T23:11:35Z

Alexis:

{{Main page/Header
|title=Bienvenue sur le [[FlightGear wiki|wiki FlightGear]]
|subtitle=''Fly free!''
|rightbox={{Main page/Languages}}
|introduction=
[[Help:Your first article|Participez]] en créant, en améliorant ou en complétant des articles.

|rightcolumn1= [[File:Portal user.png|40px]] </div>
[[Fr/Portal:Utilisateur|Utilisation]] 
[[Fr/Nouveau sur flightgear|Nouveau sur flightgear]] 
[[Fr/Foire aux questions|Foire aux questions]] · [[Fr/Howto: Débarrassez-vous des erreurs les plus fréquentes|Messages d'erreur communs]] · [[Troubleshooting problems|Dépannage]] 
[[Fr/Avions|Les avions]] · [[Fr/Helicoptere|Les hélicoptères]] · [[Fr/Vehicules|Les véhicules]] 
[[Fr/Installer une scène|Installer une scène]] · [[Fr/Howto Installer un avion|Installer un avion]] 
[[Fr/Piloter l'hélicoptère|Piloter l'hélicoptère]]
|rightcolumn2= [[File:Portal developer.png|40px]] </div>
[[Fr/Portal:Développeur|Développement]] 

[[Portal:Developer/Aircraft|Avion]] · [[Portal:Developer/Scenery|Scene]] 
[[Fr/Placer des objets 3D avec UFO|Placer des objets]] · [[Fr/Howto: Utiliser QGIS et images satellites|Améliorer les terrains]] 
[[How the FlightGear project works|Comment le Projet FlightGear fonctionne]]
|rightcolumn3= [[File:Portal wiki.png|40px]] </div>
 [[Fr/Portal:Wiki|Wiki]] 

[[FlightGear Wiki|À propos du wiki]] · [[Fr/Aide:Contenu|Aide]] 
[[Help:Your first article|Votre premier article]] · [[Fr/Help:Traduire|Traduire]] 
[[Special:Categories|Catégories]]


|sections=
{{Main page/Leftbox|title=About FlightGear
|logo=FlightGear logo.png
|contents= '''[[Fr/FlightGear|FlightGear]] Flight Simulator''' est un simulateur de vol open-source sophistiqué et fonctionnel, créé et maintenu entièrement par des volontaires. Le code source complet est accessible par [[Git]], sous une licence libre [[GNU General Public License]].

Le projet [[Fr/FlightGear|FlightGear]] propose un environnement de développement de simulateur de vol sophistiqué, pour une utilisation académique ou à des fins de recherche; il permet le développement d'autres idées intéressantes en simulation de vol, tout en restant aussi accessible à l'utilisateur lambda. Toute personne intéressée peut [[Volunteer|contribuer]] à l'ajout de fonctionnalités ou à l'amélioration de FlightGear (avions, scènes). De plus, il existe de nombreux [[FlightGear related projects|projets connexes]] ([http://www.flightgear.org/links.html liens]).

FlightGear est doté d'une documentation illustrée, parmi laquelle "Le Manuel", disponible aux formats [http://mapserver.flightgear.org/getstart-fr.pdf PDF] et [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. Ce Wiki a été lancé en 2006 et couvre actuellement une bonne partie des sujets liés à FlightGear. La fonctionnalité multi-langues est plus récente (été 2009) et, pour le moment, seulement une petite partie est effectivement traduite.

=== Je suis à la recherche de ... ===
* [[Fr/Portal:User|Aide pour l'utilisation de FlightGear]]
* [[Portal:Developer|Comment contribuer à quelque chose pour FlightGear]]

}}
{{Main page/Leftbox|title=Nouvelles
|logo=Nuvola apps knewsticker.png
|contents={{News}} }}
{{Main page/Leftbox|title=Le saviez-vous...
|logo=Nuvola apps ktip.png
|contents={{Did you know}} }}

}}

{{Main page/Rightcolumn
|title= [[:Category:Picture of the week|Image de la semaine]]
|contents= <center style="padding-top:.9em;">{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}</center>
|padding-right=23px
}}

{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Es/Portal:Wiki

2013-01-05T23:06:36Z

Alexis:

{{Main page/Header
|title=Bienvenido al portal de los editores del wiki
|introduction=Este es el lugar para saber lo que está sucediendo en el wiki de FlightGear. Aprender qué tareas hay que hacer y qué grupos existen para unirse y compartir noticias sobre los últimos acontecimientos o actividades actuales que tienen lugar en el wiki.
|rightbox=

|rightcolumn1= </div>
Comprobar artículos 

Mira también: [[Special:NewPages|nuevos artículos]], [[Special:NewFiles|archivos nuevos]] y [[Special:RecentChanges|cambios recientes]].
|rightcolumn2= [[FIle:Portal lamp.png|40px]] </div>
Inspiración para nuevos artículos 

[[Special:WantedPages|Artículos más buscados]] 
[[es/Help:Translate|Traducir artículos]]
|rightcolumn3= [[File:Portal_radarwheel.png|40px]] </div>
Mejorar artículos 

[[:Category:Articles considered for deletion|Artículos considerados para borrarse]] – Páginas que necesitan mejoras. 
[[:Category:Stubs|Ampliar (articulos cortos)]] 
[[:Category:Accuracy disputes|Discusiones sobre exactitud]]
|rightcolumn4= [[File:Portal developer.png|40px]] </div>
Mantenimiento regular 

[[Portal:Wiki/Plugin Requests|Solicitud de Instalación de Plugin]] 
[[:Category:Picture of the week|Fotos de la semana]] 
[[Special:UncategorizedFiles|Archivos sin categorizar]] 
[[Special:UncategorizedPages|Páginas sin categorizar]] 
[[Special:LonelyPages|Páginas huérfanas]] – Paginas todavia sin enlaces hacia ellas. 
[[:Category:Undocumented templates|Plantillas no documentadas]] 
[[:Category:Articles to be merged|Artículos que deben ser fundidos]] 
[[:Category:Accuracy disputes|Discusiones sobre exactitud]] 
[[Special:Categories|Categorias]]


|sections=
{{Main page/Leftbox|title=¡Participa!
|contents=Al igual que FlightGear, la wiki puede ser considerada de código abierto. Todos están invitados a [[Special:UserLogin|registrar una cuenta]] y empezar a contribuir! Este portal proporciona enlaces a artículos útiles, que van desde cómo empezar hasta las técnicas de marcado extensas.

Hay un canal de IRC en irc://#wiki@irc.flightgear.org y un [[FlightGear wiki:Village pump|contenedor]] para las cuestiones relacionadas con el wiki.

}}

}}
{{Main page/Rightcolumn end|title=[[Special:Statistics|Estadísticas Wiki]]
|contents=
* {{NUMBEROFARTICLES}} articulos
* {{NUMBEROFFILES}} archivos
* {{NUMBEROFUSERS}} usuarios
}}
[[en:Portal:Wiki]]
[[fr:Portal:Wiki]]
[[Category:Portals]]

Portal:Wiki

2013-01-05T23:06:07Z

Alexis:

{{Main page/Header
|title=Welcome to the wiki editing portal
|introduction= This is the place to find out what is happening on the FlightGear wiki. Learn what tasks need to be done and what groups there are to join, and share news about recent events or current activities taking place on the wiki.
|rightbox=

|rightcolumn1= </div>
Checking articles 

Also check: [[Special:NewPages|new articles]], [[Special:NewFiles|new files]] and [[Special:RecentChanges|recent changes]].
|rightcolumn2= [[FIle:Portal lamp.png|40px]] </div>
Inspiration for new articles 

[[Special:WantedPages|Most wanted articles]] 
[[Help:Translate|Translating articles]]
|rightcolumn3= [[File:Portal_radarwheel.png|40px]] </div>
Improving articles 

[[:Category:Articles considered for deletion|Articles considered for deletion]] – Pages that may need improvement. 
[[:Category:Stubs|Extending stubs (short articles)]] 
[[:Category:Accuracy disputes|Accuracy disputes]]
|rightcolumn4= [[File:Portal developer.png|40px]] </div>
Regular maintenance 

[[Portal:Wiki/Plugin Requests|Plugin Installation Requests]] 
[[:Category:Picture of the week|Pictures of the week]] 
[[Special:UncategorizedFiles|Uncategorized files]] 
[[Special:UncategorizedPages|Uncategorized pages]] 
[[Special:LonelyPages|Orphaned pages]] – Pages with no links to them yet. 
[[:Category:Undocumented templates|Undocumented templates]] 
[[:Category:Articles to be merged|Articles to be merged]] 
[[:Category:Accuracy disputes|Accuracy disputes]] 
[[Special:Categories|Categories]]


|sections=
{{Main page/Leftbox|title=Get involved!
|contents=Just like FlightGear itself, the wiki can be considered open-source. Everyone is encouraged to [[Special:UserLogin|register an account]] and start contributing! This portal provides links to useful articles, ranging from how to get started to extensive markup techniques.

There's an IRC channel at irc://#wiki@irc.flightgear.org and a [[FlightGear wiki:Village pump|village pump]] for wiki related questions.
}}

}}
{{Main page/Rightcolumn end|title=[[Special:Statistics|Wiki statistics]]
|contents=
* {{NUMBEROFARTICLES}} articles
* {{NUMBEROFFILES}} files
* {{NUMBEROFUSERS}} users
}}

[[es:Portal:Wiki]]
[[fr:Portal:Wiki]]
[[Category:Portals]]

Fr/Portal:Wiki

2013-01-05T23:05:49Z

Alexis: Created page with "{{Main page/Header |title=Bienvenue sur le portail d'édition du wiki |introduction= C'est l'endroit idéal pour découvrir ce qui se passe sur le wiki FlightGear. Apprend..."

{{Main page/Header
|title=Bienvenue sur le portail d'édition du wiki
|introduction= C'est l'endroit idéal pour découvrir ce qui se passe sur le wiki FlightGear. Apprendre quelles tâches doivent être réalisées, à quels groupes vous pouvez adhérer, et partager les nouvelles des évènement récents ou des activités se déroulant actuellement sur le wiki.
|rightbox=

|rightcolumn1= </div>
Vérification des articles 

Vous pouvez vérifier les [[Special:NewPages|Nouveaux articles]], les [[Special:NewFiles|Nouveaux fichiers]] et les [[Special:RecentChanges|Changement récents]].
|rightcolumn2= [[FIle:Portal lamp.png|40px]] </div>
Inspiration pour de nouveaux articles 

[[Special:WantedPages|Articles les plus demandés]] 
[[Fr/Help:Traduire|Traduction d'articles]]
|rightcolumn3= [[File:Portal_radarwheel.png|40px]] </div>
Améliorer les articles 

[[:Category:Articles considered for deletion|Articles en considération pour suppression]] – Pages pouvant nécessiter des améliorations. 
[[:Category:Stubs|Extending stubs (articles courts)]] 
[[:Category:Accuracy disputes|Accuracy disputes]]
|rightcolumn4= [[File:Portal developer.png|40px]] </div>
maintenance régulière 

[[Portal:Wiki/Plugin Requests|Demandes d'installation de plugin]] 
[[:Category:Picture of the week|Image de la semaine]] 
[[Special:UncategorizedFiles|Fichiers non classés]] 
[[Special:UncategorizedPages|Pages non classés]] 
[[Special:LonelyPages|Orphaned pages]] – Pages n'ayant aucun lien renvoyant vers elle pour l'instant. 
[[:Category:Undocumented templates|Templates non documentée]] 
[[:Category:Articles to be merged|Articles à fusionner]] 
[[:Category:Accuracy disputes|Accuracy disputes]] 
[[Special:Categories|Catégories]]


|sections=
{{Main page/Leftbox|title=Participez !
|contents=Tout comme FlightGear, le wiki peut être considéré comme étant open-source. Tout le monde est encouragé à se [[Special:UserLogin|créer un compte]] et commencer à contribuer ! Ce portail contient des liens vers des articles utiles, allant de comment débuter, au langage de balisage extensible.

Pour les questions relatives au wiki, vous trouvez une assistance sur le canal IRC à l'adresse irc://#wiki@irc.flightgear.org et sur cette page : [[FlightGear wiki:Village pump|village pump]].
}}

}}
{{Main page/Rightcolumn end|title=[[Special:Statistics|Statistiques du Wiki]]
|contents=
* {{NUMBEROFARTICLES}} articles
* {{NUMBEROFFILES}} fichiers
* {{NUMBEROFUSERS}} utilisateurs
}}

[[es:Portal:Wiki]]
[[en:Portal:Wiki]]
[[Category:Portals]]

Portal:Developer

2013-01-05T21:29:29Z

Alexis:

{{Main page/Header
|title=Welcome to the developer portal
|introduction=Please visit [http://flightgear.org/forums our forum] if you cannot find what you're looking for.
|rightbox=

|rightcolumn1= </div>
{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Getting started 

[[How the FlightGear project works]] · 
[[Howto: Understand the FlightGear development process|The development process]] · [[Release plan]] 
[[Building FlightGear]] · [[FlightGear and Git|Git]] · [[FlightGear Build Server|Build server]] 
[[Property tree]] · [[File formats]] · [[Tools of the Trade]]
|rightcolumn2= </div>
General 

[[Long Term Goals|Long term goals]] · [[Google Summer of Code]] 
[[Project Infrastructure Enhancements|Project infrastructure enhancements]] · [[Source Code Management Issues|Source management issues]] 
[[Improving Glider Realism|Improving glider realism]] · [[Improving Helicopter Realism|Improving helicopter realism]] 
[[Howto:Set up a multiplayer server|Setting up a multiplayer server]] · [[FlightGear Expo Checklist|Expo checklist]]
|rightcolumn3= [[File:Nuvola apps kaboodle.png|40px]] </div>
Animations 

[[Howto: Animate models|Animate models]] · [[Howto: Illuminate faces|Illuminate objects]] 
[[Howto: Animate gear scissors|Gear scissors]]
|rightcolumn4= [[File:Portal aircraft.png|40px]] </div>
[[Portal:Developer/Aircraft|Aircraft]] 

[[Howto: Make an aircraft|Making an aircraft]] · [[Flight Dynamics Model|Flight dynamics model]] 
[[Howto: 3D Aircraft Models|3D aircraft models]] · [[Howto: Edit a livery|Liveries]] 
[[Creating instruments for FG|Creating instruments]] · [[Howto: Make a clickable panel|Clickable panels]] 
[[Howto: Design an autopilot|Designing an autopilot]] 
[[Category:Aircraft_Resources|Resources]]
|rightcolumn5= [[File:Portal_developer.png|40px]] </div>
Core 

[[Howto: Start core development|Getting started]] · [[Programming resources]] · [[Built-in Profiler]] 
[[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projects]] · [[Request for comments]] · [[Code cleanup]] 
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Creating subsystems]] 
[[OpenSceneGraph]] 
[[Initialization Sequence|Initialization sequence]]
|rightcolumn6= </div>
[[Portal:Developer/Nasal|FlightGear Scripting with Nasal]] 

[[Nasal FAQ|Frequently asked questions]] · [[Writing simple scripts in "nasal"|Writing simple scripts]]
|rightcolumn7= [[File:Portal scenery.png|40px]] </div>
[[Portal:Developer/Scenery|Scenery]] 

[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]] 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]] 
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]] 
[[Interactive traffic]]


|sections=
{{Main page/Leftbox|title=Get involved!
|contents=If you would like to help with FlightGear's development, it's a good idea to subscribe yourself to the FlightGear development [[mailing list]]. Use the list or the FlightGear [http://code.google.com/p/flightgear-bugs issue tracker] to get in touch with fellow FlightGear core developers.

Visit [[:Category:Core development projects]] to see a list of currently ongoing projects!
See [[:Category:Developer Plans]] to see a list of developer plans for the upcoming release.
See [[request for comments]] for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress.
}}

{{Main page/Leftbox|title=Coding Help Needed!
|contents=
* {{Pending}} [[Project Rembrandt#TODO List|Project Rembrandt (Todo List)]] (Shadows/Deferred Rendering: OpenGL/OSG, C++)
* {{Pending}} [[Canvas Properties#Planned Features|Canvas Project (Planned Features)]] (fully scriptable 2D rendering API)
* {{Pending}} [[Canvas Widgets#Missing_.2F_Todo|Canvas Widgets (Missing Features)]] (Canvas GUI layer for scriptable widgets)
* {{Pending}} [[A_local_weather_system#Feature_requests_on_the_C.2B.2B_side|Local weather system Improvements]] (Requested C++ Changes)
* {{Pending}} [[Airport data (apt.dat) update]] (switch to the newer 850 format)
* {{Pending}} [[How the Nasal GC works|Fixing the Garbage Collector]] (the GC in [[Nasal]] needs to be improved)
* {{Pending}} [[Howto:Use a Camera View in an Instrument#osgViewer::CompositeViewer|Switching to osgViewer::CompositeViewer]] (multiple scenery cameras and moving maps)
* {{Pending}} [[FlightGear Run Levels|Subsystem allocation and re-initialization via listeners]] (Making subsystems optional and more configurable)
}}

{{Main page/Leftbox|title=Wanted: interview candidates
|contents=Every month we try to include an interview with a contributor in the [[FlightGear Newsletter]]. Anyone contributing to FlightGear, in whatever way, is welcome to answer a bunch of questions and write his/her own interview.

More info at [[FlightGear Newsletter: Interview]].
}}
}}

[[Category:FlightGear wiki:Portals]]
[[fr:Portal:Développeur]]

Fr/Portal:Développeur

2013-01-05T21:28:44Z

Alexis: Created page with "{{Main page/Header |title=Bienvenue sur le portail des développeurs |introduction=Si vous ne trouvez pas ce que vous recherchez, vous pouvez visiter le [http://flightgear..."

{{Main page/Header
|title=Bienvenue sur le portail des développeurs
|introduction=Si vous ne trouvez pas ce que vous recherchez, vous pouvez visiter le [http://flightgear.org/forums forum anglophone] ou [http://fr.flightgear.tuxfamily.org/forum/index.php le forum francophone]
|rightbox=

|rightcolumn1= </div>
{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Statut de développement du dépot]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Pour commencer 

[[How the FlightGear project works|Comment le projet FlightGear fonctionne]] 
[[Howto: Understand the FlightGear development process|Le processus de développement]] · [[Release plan|Plan de parution]] 
[[Building FlightGear|Compiler FlightGear]] · [[Fr/FlightGear et Git|Git]] · [[FlightGear Build Server|Build server]] 
[[Property tree|Arbre des propriétés]] · [[File formats|Formats des fichiers]] · [[Tools of the Trade]]
|rightcolumn2= </div>
Général 

[[Long Term Goals|Objectifs à long terme]] · [[Google Summer of Code]] 
[[Project Infrastructure Enhancements|Project infrastructure enhancements]] · [[Source Code Management Issues|Source management issues]] 
[[Improving Glider Realism|Améliorer le réalisme des planneurs]] · [[Improving Helicopter Realism|Améliorer le réalisme des hélicoptères]] 
[[Howto:Set up a multiplayer server|Installer un serveur multijoueur]] · [[FlightGear Expo Checklist|Expo checklist]]
|rightcolumn3= [[File:Nuvola apps kaboodle.png|40px]] </div>
Animations 

[[Howto: Animate models|Animer des modèles]] · [[Howto: Illuminate faces|éclairer les objets]] 
[[Howto: Animate gear scissors|Gear scissors]]
|rightcolumn4= [[File:Portal aircraft.png|40px]] </div>
[[Portal:Developer/Aircraft|Avion]] 

[[Howto: Make an aircraft|Créer un avion]] · [[Flight Dynamics Model|Modèle de voll]] 
[[Howto: 3D Aircraft Models|Modèles d'avions en 3D]] · [[Howto: Edit a livery|Livrés]] 
[[Creating instruments for FG|Créer des instruments]] · [[Howto: Make a clickable panel|Tableau de bord cliquables]] 
[[Howto: Design an autopilot|Conception d'un pilote automatique]] 
[[Category:Aircraft_Resources|Ressources]]
|rightcolumn5= [[File:Portal_developer.png|40px]] </div>
cœur 

[[Howto: Start core development|Premiers pas]] · [[Programming resources|Ressources de programmation]] · [[Built-in Profiler]] 
[[:Category:Developer Plans|Developer Plans]] · [[:Category:Core development projects|Projets]] · [[Request for comments|demande de commentaires]] · [[Code cleanup|nettoyage du code]] 
[[Howto:Add new fgcommands to FlightGear|Adding fgcommands]] · [[Howto:Create new subsystems|Création de sous-systèmes]] 
[[OpenSceneGraph]] 
[[Initialization Sequence|Séquence d'initialisation]]
|rightcolumn6= </div>
[[Portal:Developer/Nasal|Scripts Nasal pour FlightGear]] 

[[Nasal FAQ|Foire aux questions]] · [[Writing simple scripts in "nasal"|Écrire des scripts simples]]
|rightcolumn7= [[File:Portal scenery.png|40px]] </div>
[[Portal:Developer/Scenery|Scènes]] 

[[Fr/Placer des objets 3D avec UFO|Placer des objets]] · [[Signs|Airport signs]] 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]] 
[[Howto: Make an airport|Créer un aéroport]] · [[Fr/Utiliser TerraGear|Utiliser TerraGear]] 
[[Interactive traffic|Trafic virtuel]]


|sections=
{{Main page/Leftbox|title=Impliquez-vous !
|contents=Si vous souhaitez aider au développement de FlightGear, il serait intéressant de vous abonner à la [[mailing list|liste de diffusion]] du développement de FlightGear. Utilisez la liste ou le [http://code.google.com/p/flightgear-bugs gestionnaire d'incidents] de FlightGear pour entrer en contact avec les autres développeurs du cœur de de FlightGear.

Vous pouvez voir la [[:Category:Core development projects|liste des projet en cours]]. Vous pouvez également voir la [[:Category:Developer Plans|liste des plans de développement]] pour la prochaine parution.

Voir la [[request for comments|demande de commentaires]] pour obtenir une liste des problèmes persistants et enjeux qui affectent l'évolution de FlightGear et le progrès global de développement.
}}

{{Main page/Leftbox|title=Aide de codage nécessaire!
|contents=
* {{Pending}} [[Fr/Projet Rembrandt|Projet Rembrandt (Todo List)]] (Shadows/Deferred Rendering: OpenGL/OSG, C++)
* {{Pending}} [[Canvas Properties#Planned Features|Canvas Project (Planned Features)]] (fully scriptable 2D rendering API)
* {{Pending}} [[Canvas Widgets#Missing_.2F_Todo|Canvas Widgets (Missing Features)]] (Canvas GUI layer for scriptable widgets)
* {{Pending}} [[A_local_weather_system#Feature_requests_on_the_C.2B.2B_side|Local weather system Improvements]] (Requested C++ Changes)
* {{Pending}} [[Airport data (apt.dat) update]] (switch to the newer 850 format)
* {{Pending}} [[How the Nasal GC works|Fixing the Garbage Collector]] (the GC in [[Nasal]] needs to be improved)
* {{Pending}} [[Howto:Use a Camera View in an Instrument#osgViewer::CompositeViewer|Switching to osgViewer::CompositeViewer]] (multiple scenery cameras and moving maps)
* {{Pending}} [[FlightGear Run Levels|Subsystem allocation and re-initialization via listeners]] (Making subsystems optional and more configurable)
}}

{{Main page/Leftbox|title=Recherche: Candidats pour interview
|contents=Chaque mois nous essayons d'inclure une interview d'un contributeur dans la [[FlightGear Newsletter|lettre d'information]] de FlightGear. Toute personne contribuant à de FlightGear, de quelque manière, est invité à répondre à un tas de questions et d'écrire son / sa propre interview.

Plus d'info ici : [[FlightGear Newsletter: Interview]].
}}
}}

[[Category:FlightGear wiki:Portals]]
[[en:Portal:Developer]]

Fr/Portal:Utilisateur

2013-01-05T18:44:15Z

Alexis:

{{Main page/Header
|title=Bienvenue sur le portail des utilisateurs
|subtitle=''Volez librement!''
|introduction= Si vous ne trouvez pas ce que vous recherchez, vous pouvez visiter le [http://flightgear.org/forums forum anglophone] ou [http://fr.flightgear.tuxfamily.org/forum/index.php le forum francophone]
|rightbox=

|rightcolumn1= </div>
Vous débutez? 

[[Fr/Nouveau_sur_flightgear|Nouveau sur Flightgear]] · [[Fr/FlightGear_Manual|Manuel de Flightgear]] 
[[Fr/Foire_aux_questions|Foire Aux Questions]] 
[[Fr/Volontaires|Participer]]
|rightcolumn2= [[File:Portal helpcenter.png|40px]] </div>
[[Troubleshooting_problems|Problème / amélioration]] 

[[Howto:Understand_console_output|Erreurs fréquentes]] 
[[Howto: Improve framerates|Augmenter le nombre d'images par seconde]] 
[[Fr/Anti-aliasing|Anti-aliasing]]
|rightcolumn3= [[File:Portal aircraft.png|40px]] </div>
Voler 

[[Fr/Avions|Les avions]] · [[Fr/Helicoptere|Les hélicoptères]] · [[Fr/Vehicules|Les véhicules]] 
[[Fr/Piloter_les_warbirds|Piloter les warbirds]] · [[Fr/Piloter l'hélicoptère|Piloter des hélicoptères]] 
[[Howto: Aerial refueling|Ravitaillement en vol]] · [[Howto: Carrier|Appontage sur porte-avion]] 
[[Soaring|Vol à voile]] · [[Howto: Be a controller|Devenir contrôleur aérien]] 
[[Fr/Howto:_Multijoueur|Mode multijoueur]]· [[Dual control|Multi-équipage]]· [[Weather|Météo]] 
[[Avionics and instruments|Avionique et instruments]] · [[Aircraft lighting|éclairages de l'avion]] 
[[Altitude]] · [[Aircraft speed|Vitesse]] · [[Understanding Propeller Torque and P-Factor|Comprendre l'effet de couple et le Facteur P]] 
[[Understanding Navigation|Navigation]] · [[Howto:Create a flightplan|Créer un plan de vol]] 
[[List of abbreviations|Liste des abréviations]]
|rightcolumn4= [[File:Portal hardware.png|40px]] </div>
Matériel 

[[Joystick|Joystick, manche et palonnier]] · [[Howto: Configure camera view windows|Affichage multiple]] 
[[Fr/Hardware_Recommendations|Matériel prérequis]]
|rightcolumn5= [[File:Portal star.png|40px]] </div>
Articles conseillés 

[[Suggested Aircraft|Avions suggérés]] · [[Suggested Airports/Scenery| Aéroports et scenes suggérés]] 
[[Suggested Flights|Vols suggérés]] · [[Challenging Airports]] 
[[Suggested Software|Software]] 
|rightcolumn6= [[File:Portal tools.png|40px]] </div>
Outils supplémentaires 

[[FGo!]] · [[Fr/FlightGear_Launch_Control|FGRun]] · [[KFreeFlight]] 
[[Fr/FGCom|FGCOM]] · [[Fr/TerraSync|TerraSync]] 
[[Fr/Atlas|Atlas]] · [[Airport Diagram Generator]]
|rightcolumn7= [[File:Portal promotion.png|40px]] </div>
Promotion 

[[Unique Features|Fonctionnalités uniques]] · [[FlightGear Reviews|Avis]] 
[[FlightGear Videos|Vidéos]] · [[FlightGear logos|Logos]] · [[Howto:Make nice screenshots|Faire de belles captures d'écran]] 
[[Presentation Recipe|Presentation recipe]] · [[FlightGear Expo Checklist|Expo checklist]]


|sections=
{{Main page/Leftbox|title=Installation
|logo=Nuvola apps download manager.png
|contents=
{{{!}}
{{!}} valign="top" {{!}}
* [[Fr/Howto_Installer_un_avion|Ajouter des avions]]
* [[Fr/Installer_une_scène|Ajouter des scènes(aéroports,etc..)]]
{{!}} valign="top" {{!}}
* [[FlightGear hangars]]
{{!}}}
}}
{{Main page/Leftbox|title=Liens externe
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://fr.flightgear.tuxfamily.org/forum/index.php Forum FlightGear France]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

}}
}}

[[Category:Portals]]

[[En:Portal:User]]
[[Es:Portal:User]]

Fr/Accueil

2013-01-05T18:24:41Z

Alexis:

{{Main page/Header
|title=Bienvenue sur le [[FlightGear wiki|wiki FlightGear]]
|subtitle=''Fly free!''
|rightbox={{Main page/Languages}}
|introduction=
[[Help:Your first article|Participez]] en créant, en améliorant ou en complétant des articles.

|rightcolumn1= [[File:Portal user.png|40px]] </div>
[[Fr/Portal:Utilisateur|Utilisateur]] 
[[Fr/Nouveau sur flightgear|Nouveau sur flightgear]] 
[[Fr/Foire aux questions|Foire aux questions]] · [[Fr/Howto: Débarrassez-vous des erreurs les plus fréquentes|Messages d'erreur communs]] · [[Troubleshooting problems|Dépannage]] 
[[Fr/Avions|Les avions]] · [[Fr/Helicoptere|Les hélicoptères]] · [[Fr/Vehicules|Les véhicules]] 
[[Fr/Installer une scène|Installer une scène]] · [[Fr/Howto Installer un avion|Installer un avion]] 
[[Fr/Piloter l'hélicoptère|Piloter l'hélicoptère]]
|rightcolumn2= [[File:Portal developer.png|40px]] </div>
[[Portal:Developer|Développement]] 

[[Portal:Developer/Aircraft|Avion]] · [[Portal:Developer/Scenery|Scene]] 
[[Fr/Placer des objets 3D avec UFO|Placer des objets]] · [[Fr/Howto: Utiliser QGIS et images satellites|Améliorer les terrains]] 
[[How the FlightGear project works|Comment le Projet FlightGear fonctionne]]
|rightcolumn3= [[File:Portal wiki.png|40px]] </div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|À propos du wiki]] · [[Fr/Aide:Contenu|Aide]] 
[[Help:Your first article|Votre premier article]] · [[Fr/Help:Traduire|Traduire]] 
[[Special:Categories|Catégories]]


|sections=
{{Main page/Leftbox|title=About FlightGear
|logo=FlightGear logo.png
|contents= '''[[Fr/FlightGear|FlightGear]] Flight Simulator''' est un simulateur de vol open-source sophistiqué et fonctionnel, créé et maintenu entièrement par des volontaires. Le code source complet est accessible par [[Git]], sous une licence libre [[GNU General Public License]].

Le projet [[Fr/FlightGear|FlightGear]] propose un environnement de développement de simulateur de vol sophistiqué, pour une utilisation académique ou à des fins de recherche; il permet le développement d'autres idées intéressantes en simulation de vol, tout en restant aussi accessible à l'utilisateur lambda. Toute personne intéressée peut [[Volunteer|contribuer]] à l'ajout de fonctionnalités ou à l'amélioration de FlightGear (avions, scènes). De plus, il existe de nombreux [[FlightGear related projects|projets connexes]] ([http://www.flightgear.org/links.html liens]).

FlightGear est doté d'une documentation illustrée, parmi laquelle "Le Manuel", disponible aux formats [http://mapserver.flightgear.org/getstart-fr.pdf PDF] et [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. Ce Wiki a été lancé en 2006 et couvre actuellement une bonne partie des sujets liés à FlightGear. La fonctionnalité multi-langues est plus récente (été 2009) et, pour le moment, seulement une petite partie est effectivement traduite.

=== Je suis à la recherche de ... ===
* [[Fr/Portal:User|Aide pour l'utilisation de FlightGear]]
* [[Portal:Developer|Comment contribuer à quelque chose pour FlightGear]]

}}
{{Main page/Leftbox|title=Nouvelles
|logo=Nuvola apps knewsticker.png
|contents={{News}} }}
{{Main page/Leftbox|title=Le saviez-vous...
|logo=Nuvola apps ktip.png
|contents={{Did you know}} }}

}}

{{Main page/Rightcolumn
|title= [[:Category:Picture of the week|Image de la semaine]]
|contents= <center style="padding-top:.9em;">{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}</center>
|padding-right=23px
}}

{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Fr/Portal:Utilisateur

2013-01-05T18:23:12Z

Alexis:

{{Main page/Header
|title=Bienvenue sur le portail des utilisateurs
|subtitle=''Volez librement!''
|introduction=Vous pouvez visiter [http://flightgear.org/forums notre forum] si vous ne trouvez pas ce que vous recherchez
|rightbox=

|rightcolumn1= </div>
Vous débutez? 

[[Fr/Nouveau_sur_flightgear|Nouveau sur Flightgear]] · [[Fr/FlightGear_Manual|Manuel de Flightgear]] 
[[Fr/Foire_aux_questions|Foire Aux Questions]] 
[[Fr/Volontaires|Participer]]
|rightcolumn2= [[File:Portal helpcenter.png|40px]] </div>
[[Troubleshooting_problems|Problème / amélioration]] 

[[Howto:Understand_console_output|Erreurs fréquentes]] 
[[Howto: Improve framerates|Augmenter le nombre d'images par seconde]] 
[[Fr/Anti-aliasing|Anti-aliasing]]
|rightcolumn3= [[File:Portal aircraft.png|40px]] </div>
Voler 

[[Fr/Avions|Les avions]] · [[Fr/Helicoptere|Les hélicoptères]] · [[Fr/Vehicules|Les véhicules]] 
[[Fr/Piloter_les_warbirds|Piloter les warbirds]] · [[Fr/Piloter l'hélicoptère|Piloter des hélicoptères]] 
[[Howto: Aerial refueling|Ravitaillement en vol]] · [[Howto: Carrier|Appontage sur porte-avion]] 
[[Soaring|Vol à voile]] · [[Howto: Be a controller|Devenir contrôleur aérien]] 
[[Fr/Howto:_Multijoueur|Mode multijoueur]]· [[Dual control|Multi-équipage]]· [[Weather|Météo]] 
[[Avionics and instruments|Avionique et instruments]] · [[Aircraft lighting|éclairages de l'avion]] 
[[Altitude]] · [[Aircraft speed|Vitesse]] · [[Understanding Propeller Torque and P-Factor|Comprendre l'effet de couple et le Facteur P]] 
[[Understanding Navigation|Navigation]] · [[Howto:Create a flightplan|Créer un plan de vol]] 
[[List of abbreviations|Liste des abréviations]]
|rightcolumn4= [[File:Portal hardware.png|40px]] </div>
Matériel 

[[Joystick|Joystick, manche et palonnier]] · [[Howto: Configure camera view windows|Affichage multiple]] 
[[Fr/Hardware_Recommendations|Matériel prérequis]]
|rightcolumn5= [[File:Portal star.png|40px]] </div>
Articles conseillés 

[[Suggested Aircraft|Avions suggérés]] · [[Suggested Airports/Scenery| Aéroports et scenes suggérés]] 
[[Suggested Flights|Vols suggérés]] · [[Challenging Airports]] 
[[Suggested Software|Software]] 
|rightcolumn6= [[File:Portal tools.png|40px]] </div>
Outils supplémentaires 

[[FGo!]] · [[Fr/FlightGear_Launch_Control|FGRun]] · [[KFreeFlight]] 
[[Fr/FGCom|FGCOM]] · [[Fr/TerraSync|TerraSync]] 
[[Fr/Atlas|Atlas]] · [[Airport Diagram Generator]]
|rightcolumn7= [[File:Portal promotion.png|40px]] </div>
Promotion 

[[Unique Features|Fonctionnalités uniques]] · [[FlightGear Reviews|Avis]] 
[[FlightGear Videos|Vidéos]] · [[FlightGear logos|Logos]] · [[Howto:Make nice screenshots|Faire de belles captures d'écran]] 
[[Presentation Recipe|Presentation recipe]] · [[FlightGear Expo Checklist|Expo checklist]]


|sections=
{{Main page/Leftbox|title=Installation
|logo=Nuvola apps download manager.png
|contents=
{{{!}}
{{!}} valign="top" {{!}}
* [[Fr/Howto_Installer_un_avion|Ajouter des avions]]
* [[Fr/Installer_une_scène|Ajouter des scènes(aéroports,etc..)]]
{{!}} valign="top" {{!}}
* [[FlightGear hangars]]
{{!}}}
}}
{{Main page/Leftbox|title=Liens externe
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://fr.flightgear.tuxfamily.org/forum/index.php Forum FlightGear France]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]

}}
}}

[[Category:Portals]]

[[En:Portal:User]]
[[Es:Portal:User]]

Portal:User

2013-01-05T18:22:29Z

Alexis:

{{Main page/Header
|title=Welcome to the user portal
|subtitle=''Fly free!''
|introduction=Please visit [http://flightgear.org/forums our forum] if you cannot find what you're looking for.
|rightbox=

|rightcolumn1= </div>
Getting started 

[[New to FlightGear]] · [[FlightGear Manual]] 
[[Frequently asked questions]]
|rightcolumn2= [[File:Portal helpcenter.png|40px]] </div>
[[Troubleshooting problems|Troubleshooting]] 

[[Howto: Understand console output|Common errors]] 
[[Howto: Improve framerates|Improving framerates]]
|rightcolumn3= [[File:Portal aircraft.png|40px]] </div>
Flying 

[[Howto: Aerial refueling|Aerial refueling]] · [[Howto: Carrier|Aircraft carrier operations]] 
[[Flying Warbirds|Flying warbirds]] · [[Howto: Fly a helicopter|Flying helicopters]] 
[[Howto: Multiplayer|Multiplayer]] · [[Howto: Be a controller|Be an air traffic controller]] · [[Dual control|Multi-crew]] 
[[Soaring]] · [[Weather]] 
[[Avionics and instruments]] · [[Aircraft lighting]] 
[[Altitude]] · [[Aircraft speed|Speed]] · [[Understanding Propeller Torque and P-Factor|Propeller torque and P-factor]] 
[[Understanding Navigation|Navigation]] · [[Creating a flightplan]] 
[[List of abbreviations]]
|rightcolumn4= [[File:Portal hardware.png|40px]] </div>
Hardware 

[[Joystick|Joystick, yoke and rudder]] · [[Howto: Configure camera view windows|Multiple displays]] 
[[Hardware Recommendations|Recommendations]]
|rightcolumn5= [[File:Portal star.png|40px]] </div>
Suggested 

[[Suggested Aircraft|Aircraft]] · [[Suggested Airports/Scenery|Airports/Scenery]] 
[[Suggested Flights|Flights]] · [[Challenging Airports]] 
[[Suggested Software|Software]] 
|rightcolumn6= [[File:Portal tools.png|40px]] </div>
Additional tools 

[[FGo!]] · [[FGRun]] · [[KFreeFlight]] 
[[FGCOM]] · [[TerraSync]] 
[[Atlas]] · [[Airport Diagram Generator]]
|rightcolumn7= [[File:Portal promotion.png|40px]] </div>
Promotion 

[[Unique Features]] · [[FlightGear Reviews|Reviews]] 
[[FlightGear Videos|Videos]] · [[Howto:Make nice screenshots|Making nice screenshots]] 
[[Presentation Recipe|Presentation recipe]] · [[FlightGear Expo Checklist|Expo checklist]]


|sections=
{{Main page/Leftbox|title=Installing
|logo=Nuvola apps download manager.png
|contents=
{{{!}}
{{!}} valign="top" {{!}}
* [[Howto: Install aircraft|Additional aircraft]]
* [[Howto: Install scenery|Additional scenery]]
{{!}} valign="top" {{!}}
* [[FlightGear hangars]]
{{!}}}
}}
{{Main page/Leftbox|title=External links
|contents=
* [http://freechecklists.net/ Checklists]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
* [http://www.gcmap.com/ Great Circle Mapper]
* [http://www.smartcockpit.com SmartCockpit.com]
* [http://www.worldaerodata.com/ World Aeronautical Database]
}}
}}

[[Category:Portals]]

[[fr:Portal:Utilisateur]]
[[es:Portal:User]]

Fr/Accueil

2013-01-05T15:25:54Z

Alexis:

{{Main page/Header
|title=Bienvenue sur le [[FlightGear wiki|wiki FlightGear]]
|subtitle=''Fly free!''
|rightbox={{Main page/Languages}}
|introduction=
[[Help:Your first article|Participez]] en créant, en améliorant ou en complétant des articles.

|rightcolumn1= [[File:Portal user.png|40px]] </div>
[[Fr/Portal:User|Utilisateur]] 
[[Fr/Nouveau sur flightgear|Nouveau sur flightgear]] 
[[Fr/Foire aux questions|Foire aux questions]] · [[Fr/Howto: Débarrassez-vous des erreurs les plus fréquentes|Messages d'erreur communs]] · [[Troubleshooting problems|Dépannage]] 
[[Fr/Avions|Les avions]] · [[Fr/Helicoptere|Les hélicoptères]] · [[Fr/Vehicules|Les véhicules]] 
[[Fr/Installer une scène|Installer une scène]] · [[Fr/Howto Installer un avion|Installer un avion]] 
[[Fr/Piloter l'hélicoptère|Piloter l'hélicoptère]]
|rightcolumn2= [[File:Portal developer.png|40px]] </div>
[[Portal:Developer|Développement]] 

[[Portal:Developer/Aircraft|Avion]] · [[Portal:Developer/Scenery|Scene]] 
[[Fr/Placer des objets 3D avec UFO|Placer des objets]] · [[Fr/Howto: Utiliser QGIS et images satellites|Améliorer les terrains]] 
[[How the FlightGear project works|Comment le Projet FlightGear fonctionne]]
|rightcolumn3= [[File:Portal wiki.png|40px]] </div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|À propos du wiki]] · [[Fr/Aide:Contenu|Aide]] 
[[Help:Your first article|Votre premier article]] · [[Fr/Help:Traduire|Traduire]] 
[[Special:Categories|Catégories]]


|sections=
{{Main page/Leftbox|title=About FlightGear
|logo=FlightGear logo.png
|contents= '''[[Fr/FlightGear|FlightGear]] Flight Simulator''' est un simulateur de vol open-source sophistiqué et fonctionnel, créé et maintenu entièrement par des volontaires. Le code source complet est accessible par [[Git]], sous une licence libre [[GNU General Public License]].

Le projet [[Fr/FlightGear|FlightGear]] propose un environnement de développement de simulateur de vol sophistiqué, pour une utilisation académique ou à des fins de recherche; il permet le développement d'autres idées intéressantes en simulation de vol, tout en restant aussi accessible à l'utilisateur lambda. Toute personne intéressée peut [[Volunteer|contribuer]] à l'ajout de fonctionnalités ou à l'amélioration de FlightGear (avions, scènes). De plus, il existe de nombreux [[FlightGear related projects|projets connexes]] ([http://www.flightgear.org/links.html liens]).

FlightGear est doté d'une documentation illustrée, parmi laquelle "Le Manuel", disponible aux formats [http://mapserver.flightgear.org/getstart.pdf PDF] et [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. Ce Wiki a été lancé en 2006 et couvre actuellement une bonne partie des sujets liés à FlightGear. La fonctionnalité multi-langues est plus récente (été 2009) et, pour le moment, seulement une petite partie est effectivement traduite.

=== Je suis à la recherche de ... ===
* [[Fr/Portal:User|Aide pour l'utilisation de FlightGear]]
* [[Portal:Developer|comment contribuer àquelque chose pour FlightGear]]

}}
{{Main page/Leftbox|title=Nouvelles
|logo=Nuvola apps knewsticker.png
|contents={{News}} }}
{{Main page/Leftbox|title=Le saviez-vous...
|logo=Nuvola apps ktip.png
|contents={{Did you know}} }}

}}

{{Main page/Rightcolumn
|title= [[:Category:Picture of the week|Image de la semaine]]
|contents= <center style="padding-top:.9em;">{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}</center>
|padding-right=23px
}}

{{Main page/Rightcolumn end
|title= [[FlightGear and Git|Development repository status]]
|contents= <center style="padding-top:.9em;">{{GitStatus}}</center>
|padding-right=23px
}}

Fr/Helicoptere

2013-01-05T14:45:18Z

Alexis:

Il s'agit d'une compilation de certains hélicoptères actuellement disponibles. La plupart des installations FG requières des avions supplémentaires à télécharger séparément ([http://www.flightgear.org/download ici]) et à installer manuellement (voir :[[Installing Aircraft]]). Regardez le [[:fr:Table des modèles|tableau des modèles]] pour avoir une liste plus complète, ou [[Aircraft|avion]] et [[Vehicle|véhicules]] pour avoir plus d'exemples. ''Lire [[:fr:Piloter l'hélicoptère|Piloter l'hélicoptère]] pour avoir un manuel, ou retournez sur le [[:fr:Portal:Utilisateur|Le portail des utilisateurs]]''

{{Model Gallery | section=helicopters}}

[[de:Helikopter]]
[[es:Helicóptero]]
[[en:Helicopter]]

Fr/Fokker Dr.I

2013-01-04T22:45:47Z

Alexis: Created page with "{{infobox Aircraft |image = Fokker_DrI.jpg |name = Fokker Dr.I |type = Chasseur |authors = Michael Selig (FDM) Erik Hofman (3D model) |fdm = UIUC |fgname = fk..."

{{infobox Aircraft
|image = Fokker_DrI.jpg
|name = Fokker Dr.I
|type = Chasseur
|authors = Michael Selig (FDM) Erik Hofman (3D model)
|fdm = UIUC
|fgname = fkdr1-v1-nl-uiuc
|status = production
|ready = bombable
}}
Le'''Fokker Dr I''' est un [[Fr/Avions|avion]] de chasse triplan allemand avec moteur à piston de la première guerre mondiale.

== Aircraft help ==
{|
! Key
! Description
|-
| <nowiki>} </nowiki>
| Magneto on
|-
| {
| Magneto off
|-
| s
| Démarreur
|}

=== Démarrage ===
# Appuyez sur''}'' pour allumer les magneto.
# Mettre plein gaz.
# Appuyez sur ''s'' jusqu'au démarrage du moteur, ce qui peut prendre plusieurs secondes.

=== Décollage ===
# Avant de démarrer, avec le zoom (''Shift-X''), placez la vue de manière à pouvoir voir la piste de part et d'autre du cockpit.
#Démarrer le moteur avec les instructions ci-dessus. Dès que le moteur démarre, l'avion commence à rouler sur la piste. Le Dr.I n'était pas équipé de freins.
# Dès que l'avion commence à se déplacer, tirer fermement sur le manche pour contrer la tendance de l'avion à capoter.
# Alors que l'avion prend de la vitesse, soyez prêt à combattre fermement la tendance de l'avion à partir vers la gauche. Countering this requires firm left rudder and right aileron, while continuing to apply firm up elevator to counter the tendency to nose over.
# Alors que l'avion commence à décoller, poucez doucement le manche vers l'avant afin d'éviter un taux de montée trop raide. Si vous maintenez le manche tiré vers l'arrière de l'appareil va monter trop rapidement et perdre la vitesse,aboutissant au décrochage et au crash.
# De même, être prêt à relâcher le gouvernail et l'aileron alors que l'avion prend de la vitesse.

=== Croisière===
Notez que le moteur de la Dr.I l 'était contrôlé par la combinaison gaz, mélange, et l'interrupteur "blip", ce qui déconnecte le magnéto et a été utilisée pour couper l'alimentation du moteur pour de brèves périodes.
Dans FlightGear, utilisez les touches ''{'' and ''}'' pour contrôler la puissance du moteur.

== Liens ecternes ==
* [http://en.wikipedia.org/wiki/Fokker_Dr.I Wikipedia]
* [http://www.theaerodrome.com/forum/aircraft/47802-fokker-dr-1-throttle.html More about DR 1 throttle and engine controls]

{{Fokker}}

[[Category:Fighter aircraft]]
[[Category:Propeller aircraft]]
[[Category:Single-engine aircraft]]
[[Category:Triplane aircraft]]
[[en:Fokker Dr.I]]

Fokker Dr.I

2013-01-04T22:45:06Z

Alexis:

{{infobox Aircraft
|image = Fokker_DrI.jpg
|name = Fokker Dr.I
|type = Fighter
|authors = Michael Selig (FDM) Erik Hofman (3D model)
|fdm = UIUC
|fgname = fkdr1-v1-nl-uiuc
|status = production
|ready = bombable
}}
The '''Fokker Dr I''' was a triplane single piston engine [[aircraft]].

== Aircraft help ==
{|
! Key
! Description
|-
| <nowiki>} </nowiki>
| Magneto on
|-
| {
| Magneto off
|-
| s
| Starter
|}

=== Start up ===
# Press ''}'' to turn the magneto on.
# Engage full throttle.
# Then press and hold ''s'' until the engine catches, which may take several seconds.

=== Take off ===
# Before starting, zoom display out as far as possible using the ''Shift-X'' key, so that you can see the runway out of both sides of the cockpit.
#Start the engine according to the instructions above. As soon as the engine starts, the aircraft will start to roll down the runway. The Dr.I was not equipped with brakes.
# As soon as the aircraft starts to move, pull back firmly on the stick to counter the aircraft's tendency to nose over.
# As the aircraft picks up speed, be prepared to firmly counter the aircraft's tendency to yaw right and roll left. Countering this requires firm left rudder and right aileron, while continuing to apply firm up elevator to counter the tendency to nose over.
# As the aircraft starts to lift off, gently ease the stick forward so as to avoid a too-steep rate of climb. If you keep the stick pulled back the aircraft will climb too rapidly and lose airspeed, leading to an invitible stall, roll, and crash.
# Similarly, be prepared to ease off the rudder and aileron as the aircraft picks up speed.

=== Cruise ===
Note that that the Dr.I's engine was controlled by a combination of throttle, mixture adjustment, and "blip" switch, which disconnected the magneto and was used to cut engine power for brief periods.

In FlightGear you can use a combination of throttle and "blip" (''{'' and ''}'' keys) to control engine power.

== External link ==
* [http://en.wikipedia.org/wiki/Fokker_Dr.I Wikipedia]
* [http://www.theaerodrome.com/forum/aircraft/47802-fokker-dr-1-throttle.html More about DR 1 throttle and engine controls]

{{Fokker}}

[[Category:Fighter aircraft]]
[[Category:Propeller aircraft]]
[[Category:Single-engine aircraft]]
[[Category:Triplane aircraft]]
[[fr:Fokker Dr.I]]

Fr/Cessna 172P

2013-01-04T22:22:54Z

Alexis:

{{infobox Aircraft
|image = Cessna 172P.jpg
|name = Cessna 172P
|type = Avion léger civil
|fdm = JSBSim
|status = production
|authors = David Megginson
|ranking = 5
|fgname = c172p</tt>, <tt>c172p-2dpanel</tt>, <tt>c172p-panel-only</tt>, <tt>c172r
}}
Le '''Cessna 172 Skyhawk''' est un [[Fr/Avions|avion]] quadriplace, monomoteur à aile haute. Il effectua son premier vol en 1955 et est toujours en production, plus de Cessna 172 ont été construits que tout autres avions.

Le C 172 est l'avion par défaut dans FlightGear depuis 2000, il a remplacé le Navion. Il a eu un long développement et il inclut une grande variété de fonctionnalités pour FlightGear. Voir [[Understanding Propeller Torque and P-Factor|comprendre les effets moteur]].

Le C172 possède une simulation du [[Bendix/King KAP140 Autopilot|pilote automatique Bendix/King KAP140]].

== Variantes ==
Les quatre variantes suivantes existent dans le [[FlightGear CVS|dépôt CVS de FlightGear]]:
* <tt>c172p</tt>
* <tt>c172p-2dpanel</tt>
* <tt>c172p-panel-only</tt>
* <tt>c172r</tt>

[[File:C172P_cockpit.jpg|thumb|270px|Le cockpit 3D du C172P.]]

== Aide de l'avion ==

=== Mise en route ===
* Mixture: Riche (manette rouge poussée à fond)
* Gaz: 1/8" (1/2 cm)
* Frein de parking: Serré (Shift-B)
* Zone autour de l'hélice: Dégagée
* Magnétos: Both (} trois fois)
* Démarreur (s)

=== Décollage ===
* Volets rentrés
* Plein gaz
* Rotation à 55 KIAS

=== Montée ===
* Volets rentrés
* Plein gaz
* 80 KIAS

=== Croisière ===
* gaz: 65%
* mixture: "rich of peak"

=== Atterrissage ===
* Volets: tout sorti
* 65 KIAS

=== Vitesses limites ===
* VSO: 33 kts
* VX: 56 kts
* VY: 76 kts
* VA: 99 kts
* VNE: 158 kts

== Touches communes à tous les avions ==
{| border="1"
|-
! align="center"|Key !! Action
|-
| align="center"| Entrée || bouger les palonniers à droite
|-
| 0/Insert || bouger les palonniers à gauche
|-
| align="center"|[] || rentrer/sortir les volets
|-
| align="center"|{} || augmenter/diminuer les magnétos sur le moteur sélectionné
|-
| align="center" | ~ || sélectionner tous les moteurs
|-
| align="center"|s || démarrer les moteurs sélectionnés
|-
| align="center"|h || afficher/masquer le HUD
|-
| align="center"|m/M || enrichir/appauvrir la mixture
|-
| align="center"|n/N || diminuer/augmenter le pas d'hélice
|}
== Développement: statut/problèmes/choses à faire ==

'''Extérieur:'''
* textures / le mapping a besoin de quelques corrections

'''Cockpit 3D:'''
* Le cockpit est texturé mais les textures peuvent être améliorées
* Il manque un pilote et un copilote
* Les étiquettes des interrupteurs pour les lumières sont difficiles à lire

'''Général:'''
* On atteint souvent des vitesses de 135 kt indiqués à 2850 tr/min en pallier à 1000 ft AMSL, en consommant seulement 13 gallons/heure. Ce n'est pas le genre de performances observées sur de vrais Skyhawk.
** Quelles sont les performances attendues d'après vos estimations?

== Voir aussi ==
=== Listes ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]

=== Liens ===
* [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:Civilian aircraft]]

[[en:Cessna 172P]]

Fr/Table des modèles

2013-01-04T21:50:16Z

Alexis:

La liste inclus les [[Fr/Avions|avions]] sous [[GNU General Public License|licence GPL]] et les [[Fr/Vehicules|Véhicules]] de [[FlightGear]].

Ne sont pas inclus de la liste : les avions non libres, ou sous licence Creative Commons, mais peuvent être trouvés dans les [[FlightGear hangars|hangars]] de leur propriétaires. La liste est mise à jours avec les avions qui fonctionnent avec les avions fonctionnant avec les différentes versions de [[FlightGear]]. Prenez conscience quand vous installez un avion, qu'il n'est peut-être pas compatible avec vôtre version de FG.

Les fonctionnalités des modèles, leur qualité et leur compatibilité varient de façon significative; leur développement dépend du/des volontaire(s) qui ont travaillés dessus, avec l'exception de quelques projets d'universités ou du gouvernement (des états-unis) quand bien même ceux-ci furent pour la plupart perdu de vue... la liste inclue quelques avions en développement, mais pas encore disponibles. UD signifie qu'il n'est pas encore disponible mais en développement, C D ou Git signifie disponible en développement sur GIT mais incomplet.

* '''A:''' ailes fixes ou avion
* '''AG:''' glisseur, hydravion
* '''AZ:''' ballon, plus léger que l'air,
* '''H:''' hélicoptère
* '''RC:''' contrôlé par manette
* '''V:''' vehicule
* '''F:''' fiction/fantaiste/drôle

{| class="wikitable sortable" border="1" cellspacing="0"
|-
! style="background:#efefef" |
! style="background:#efefef" | Model
! style="background:#efefef" | 
! style="background:#efefef" | 
! style="background:#efefef" | 
! style="background:#efefef" | 
! style="background:#efefef" | 
! style="background:#efefef" | 
! style="background:#efefef" | [[FDM]] / Note
|-
|A|| [[A-6 Intruder|A-6E Intruder]] (Grumman, Northrop Grumman) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Aero Vodochody L-39 Albatros]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Piper Aerostar|Aerostar Super 700]] (Piper) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Aeroprakt A24 Viking]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|H|| [[Aérospatiale Alouette II]] (SA 318C) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Aérospatiale Alouette III]] (SA 316) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H || [[Aérospatiale Super Frelon]] (SA 321) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|H || [[Aerospatiale AS-332 L1]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|H || [[Aerospatiale Dauphin]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A || [[Allegro 2000]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Aichi D3A]] ('Val') || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A || [[Airco D.H.2]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Airbus A300]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Airbus A310-300]] || || || || 2.4 || 2.6 || || [[YASim]]
|-
|A|| [[Airbus A320]] ([[Airbus A320 Family]]) || 1 || 1.9 || 2.0 ||2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[Airbus A321]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Airbus A330]] || || || || || U || || [[JSBSim]] (planned)
|-
|A|| [[Airbus A340]] || || || || || U || || [[JSBSim]]
|-
|A|| [[Airbus A340-600]] || || U || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Airbus A350]]-1000 || || || || || U || || [[JSBSim]]
|-
|A|| [[Airbus A380]] || || D || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|AG|| [[Airwave Xtreme 150]] (hang glider) || 1||1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[UIUC]]
|-
|A|| [[Anderson-Greenwood AG-14]] || || || || || 2.6 || 2.8 ||
|-
|A|| [[Antonov An-2]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Antonov AN-24RV|Antonov An-24RV]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Antonov An-225]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || || [[YASim]]
|-
|A|| [[Arado Ar 234‎]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Arsenal VG-33]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[ATR 72-500]] || || || || 2.4 || 2.6 || 2.8||
|-
|A || [[Arup S2]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A || [[Avro Arrow]] || || || || || || 2.8 || [[YASim]]
|-
|A || [[Avro Lancaster]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Avro Vulcan|Avro Vulcan B.2]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[B-1B|B-1B Lancer]] (Rockwell, later Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[B-2 Spirit]] (Northrop, Northrop Grumman) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Boeing B-17 Flying Fortress|B-17 Flying Fortress]] (Boeing) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[B-24 Liberator]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[B-25 Mitchell]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[B-26 Marauder]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[B-29 Superfortress]] (Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]], [[YASim]]
|-
|A|| [[Northrop XB-35]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Convair B-36D|B-36D Peacemaker]] (Convair) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Boeing B-52|B-52F Stratofortress]] (Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A || [[BAe 125]] || || || || || || 2.8 || [[YASim]]
|-
|A|| [[B&F FK9 Mark 2]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|H|| [[AH-1 Cobra|Bell AH-1 Cobra]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|H|| [[Bell UH-1]] ("Huey") || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Bell P-39 Airacobra]] (1938) || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|H|| [[Bell P-59 Airacomet]] (1942) || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Bell Boeing V22 Osprey|Bell/Boeing V-22 Osprey]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Bell/Boeing VMX22-Osprey]] || || || || || 2.6 || 2.8 ||
|-
|A|| [[BAC TSR-2 Prototype]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Beech 99|Beechcraft 99]] ||1||1.9|| 2.0 || 2.4 || 2.6 || 2.8 ||[[YASim]], [[UIUC]]
|-
|A|| [[Beechcraft 1900|Beechcraft B1900D]] ||1|| 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Beechcraft Starship|Beechcraft Starship I]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Bernard HV220]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|AG|| [[PZL Bielsko SZD-9 Bocian|Bielsko SZD-9 Bocian]] (Glider) || 1 || 1.9 || 2.0 ||2.4 || 2.6 || 2.8
|-
|A|| [[Blohm & Voss BV 141|Blohm & Voss Bv 141]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Blohm & Voss Bv 170]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Blackburn Buccaneer]] S2 || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Bleriot XI]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Breguet Br 761]] "Deux ponts" || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Boeing 247]] (1933) || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Boeing 314]]-A || 1 || 1.9 || 2.0 || 2.4 ||2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[Boeing 707]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[Boeing 727-230]] || || D || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Boeing 737-100]] |||| D || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A || [[Boeing 737-200]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Boeing 737NG600]] || || || || || 2.6 || 2.8 ||
|-
|A|| [[Boeing 737-300]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Boeing 747-100]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]], [[YASim]]
|-
|A|| [[Boeing 747-200]] || 1 || 1.9 || 2.0 || 2.4 ||2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Boeing 747-400]] || || U || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Boeing 767-300]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||[[JSBSim]]
|-
|A|| [[Boeing 777-200]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Boeing 777-300]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Boeing 787-8]] || 1 || 1.9 || 2.0 || 2.4 ||2.6 || 2.8|| [[YASim]]
|-
|H|| [[AH-64 Apache|Boeing AH-64 Apache]] (formerly McDonald Douglas, Hughes) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|H|| [[CH-47 Chinook|Boeing CH-47 Chinook]] ||1||1.9|| 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Boeing-Sikorsky RAH-66 Commanche]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|H|| [[Boeing-Vertol H21C|Boeing-Vertol H-21C]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Bombardier 415]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Bombardier CRJ-200]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Bombardier CRJ-200LR]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Bombardier CRJ700 series]] || || || || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Breguet 19]] (XIX) || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Bristol Beaufighter]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A || [[Bristol Brabazon]] || || || || || || 2.8 || [[YASim]]
|-
|A|| [[Bugatti 100|Bugatti 100P]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Caudron C.684]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna 150|Cessna 150L]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna C172|Cessna 172P Skyhawk]] (1981 model) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[Cessna 172R Skyhawk]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Cessna 182|Cessna 182 Skylane]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna 182RG]] (c. 1978) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Cessna 208 Caravan]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna 310]]R (1979 model) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna 310|Cessna U-3A]] (USN Cessna 310) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Cessna 421]] || || || || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Cessna 550 Citation II]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Cessna Citation|Cessna Citation Bravo]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Cessna Citation X]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Cessna T-37]] (Cessna) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Cirrus SR20]](fdm only) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|AG || [[Colditz Cock|Colditz Escape Glider]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Colomban Cricri|Cri-Cri]] (Colomban MC-15 Cri-Cri) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Comper Swift]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Convair F-106 Delta Dart]] || || C || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Convair XFY-1 Pogo]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Concorde]] (v2.5) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Couzinet 70]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Dassault Falcon 50]] || || || || 2.4 || 2.6 || 2.8||[[YASim]]
|-
|A|| [[Dassault Mirage III]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Dassault Mirage IV]] || || || 2.0 || 2.4 || 2.6 || 2.8
|-
|A|| [[Dassault Mirage 2000]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Dassault Mirage F.1]] || || || || 2.4 || 2.6 ||2.8 ||[[YASim]]
|-
|A|| [[Dassault Rafale B]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Dassault-Bréguet Super Etendard]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Dassault/Dornier Alpha Jet]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Deperdussin]] || || C || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|AG|| [[Der Kleine Uhu]] || || C || 2.0 || 2.4 || 2.6 ||2.8 || model glider
|-
|A|| [[Diamond DA20-A1 Katana]] || || D || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Diamond DA20-C1 Eclipse]] || || D || || || || || [[JSBSim]]
|-
|A|| [[Diamond DA42 Twin Star]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Douglas A-4|Douglas A-4 Skyhawk]] (Douglas, Mcdonald Douglas) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8|| [[YASim]], [[UIUC]]
|-
|A|| [[Douglas A-26 Invader]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Douglas DC-2]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Douglas DC-3-C47]] (Dual Control) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], aircraft=dc-3
|-
|A|| [[Douglas DC-3]] (1937) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], aircraft=dc3
|-
|A|| [[Douglas DC-6]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Douglas DC-8-73]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Douglas Dolphin]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Douglas X-3|Douglas X-3 Stiletto]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Dornier Do 26]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Dornier Do 335]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Dornier Do R]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Dornier Do X]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Dornier Superwal]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[de Havilland Canada DHC-1 Chipmunk]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[de Havilland Canada DHC-2 Beaver]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[de Havilland Canada DHC-3 Otter]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[de Havilland Canada DHC-4 Caribu]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[de Havilland Canada DHC-6 Twin Otter]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[de Havilland Canada DHC-8]] (9-300Q) || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[de Havilland DH.88 Comet]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[de Havilland DH.89 Dragon Rapide]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[de Havilland DH.91 Albatross]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[de Havilland Mosquito|de Havilland DH.98 Mosquito]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[de Havilland DH.110 Sea Vixen]] FAW 2 || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Dewoitine D.510]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|H|| [[Dewoitine D.520]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[E-3 Sentry|E-3B Sentry]] (Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[English Electric Canberra]] B(I)8 || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[English Electric Lightning]] F.1A || 1 || 1.9 || 2.0 ||2.4 || 2.6 || 2.8||
|-
|H|| [[Eurocopter EC 135]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|H|| [[Eurocopter EC 130]] || || || D || 2.4 || 2.6 ||2.8 ||
|-
|H|| [[Eurocopter EC 665]] (Tigre) || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Eurofighter Typhoon]] || ||1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Ercoupe 415-C]] || || 1.9|| 2.0 || 2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[F-8 Crusader]] (Vought) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Grumman F-14 Tomcat|F-14B Tomcat]] (Grumman) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[McDonnell Douglas F-15C Eagle|F-15C Eagle]] (McDonnell Douglas, later Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[General Dynamics F-16|F-16 Falcon]] (General Dynamics, Lockheed Martin) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[F/A-18 Hornet]] (McDonnell Douglas, later Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Northrop/McDonnell Douglas YF-23|YF-23]] (Northrop/McDonnell Douglas) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[F-117 Nighthawk]] (Lockheed, Lockheed Martin) || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[F4U Corsair]] (Chance Vought) || 1 || 1.9 || 2.0 ||2.4 || 2.6 || 2.8||
|-
|A|| [[A-10 Thunderbolt II|Fairchild Republic A-10 Thunderbolt II]] (also Boeing) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Fairchild C-119]] "Flying Boxcar" || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Fairchild Metroliner]] (Fairchild Swearingen) || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Farman IV]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Fieseler Fi 156|Fieseler Fi-156 Storch]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Focke-Wulf Fw 44|Focke-Wulf Fw 44 Stieglitz]] (1937) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Focke-Wulf Fw 61]] || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Focke-Wulf Fw 190|Focke-Wulf Fw-190 A8]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Focke-Wulf Fw 200|Focke-Wulf Fw 200 Condor]] (1937) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Fokker 50]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Fokker 70]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Fokker 100]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Fokker Dr.I|Fokker Dr.1]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[UIUC]]
|-
|A|| [[Fokker E.III]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Fokker S.11]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Ford Trimotor]] (4-AT) || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Fouga Magister]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A || [[GDT Hornet (autogyro)|GDT Hornet Autogyro]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A || [[Gee Bee]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A || [[Gloster Meteor]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A || [[Gloster Whittle]] || || || || || || 2.8||
|-
|AG || [[Grob G 102 Astir]] (glider) || || || || || 2.6 ||2.8 ||
|-
|A || [[Grob G 109]] (motor-glider) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Grob G 115]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8|| [[YASim]]
|-
|A|| [[Grumman Albatross]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Grumman C-2 Greyhound]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8||
|-
|A|| [[Grumman F6F Hellcat]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Grumman F7F Tigercat]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Grumman TBF Avenger]] (General Motors TBM) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Hamburger Flugzeugbau HFB 320 Hansa Jet‎]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Handley Page Halifax]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Handley Victor]] || || || || || || 2.8|| [[YASim]]
|-
|A|| [[Henschel Hs P.75]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[British Aerospace Harrier|(Harrier) British Aerospace Sea Harrier FA2]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Hawker Hurricane|Hawker Hurricane IIb]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Hawker Hunter]] GA11 || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||[[YASim]]
|-
|A|| [[Hawker Seahawk]] FGA6 || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Hawker Siddeley Harrier GR1]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Hawker Siddeley Nimrod]] (1967) || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Heinkel He 162]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Heinkel He 178]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[HM-14]] (Henry Mignet) || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[HondaJet|Honda HondaJet]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]], [[YASim]]
|-
|A|| [[Horten Ho IX]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Hughes H-1 Racer]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Hughes H-4 Hercules]] (HK-1) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], [[JSBSim]]
|-
|A|| [[Hughes XF-11]] || || 1.9|| 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[IAR 80]] || || || 2.0? || 2.4 || 2.6 ||2.8 ||[[YASim]]
|-
|A|| [[Ilyoushin Il-2]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| Issoire [[APM 20 Lionceau]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Junkers Ju 52|Junkers Ju 52/3m]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Junkers Ju 87 Stuka]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Junkers G.38ce]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Kalinin K7]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Kamov Ka-50]] ("Hokum") || || || 2.0 || 2.4 || 2.6 || || [[YASim]]
|-
|H|| [[Kawasaki OH-1]] || || 1.9 || 2.0 || || || ||
|-
|A|| [[Kawasaki T-4|Kawasaki T-4 "Blue Impulse"]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]], [[YASim]]
|-
|A|| [[KC-135|KC-135E Stratotanker]] (Boeing)|| 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[KM Ekranoplan]] "Caspian Sea Monster" || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Kyushu J7W]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Levavasseur Antoinette IV]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Latécoère 290]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Lancair 235]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Lavochkin La 5]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Lockheed C-130 Hercules]] (later Lockheed Martin) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Lockheed Constellation]] (Lockheed 1049) || 1 ||1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[F-80 Shooting Star|Lockheed F-80C Shooting Star]] (P-80) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Lockheed F-104 Starfighter]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Lockheed L-1011-250]] (Lockheed Tristar) || || UD || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Lockheed P-38 Lightning]] & F-5B || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| "P-38-Lightning" and "Lockheed-P38"
|-
|A|| [[Lockheed SR-71 Blackbird]] A & B || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], 1 of 2 SR71 GIT "SR71-BlackBird"
|-
|A|| Lockheed SR-71 Blackbird || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| 1 of 2 on GIT "Lockheed-SR71"
|-
|A|| [[Lockheed Martin F-35B Lightning II]] || ||1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Lockheed Vega]] (5B) || || || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[McDonnell Douglas MD-11]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Macchi M.C.72|Macchi Castoldi M.C. 72]] || || 1.9|| 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|AG|| [[Mainair Flash 2 Alpha]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Martin-Baker MB5]] || 1 || || || || || ||
|-
|A|| [[X24|Martin-Marietta X-24B]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|H|| [[MBB Bo 105]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Messerschmitt Bf 109|Messerschmitt Bf 109 G14]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8
|-
|A|| [[Messerschmitt Bf 110 || || || || || || 2.8
|-
|A|| [[Messerschmitt Me 209 V1]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Messerschmitt Me 262]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Messerschmitt Me 262 HG III]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Messerschmitt Me 323]] "Gigant" || || || || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Messerschmitt Libelle]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Messerschmitt P.1101]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[MiG-15]]bis || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|A|| [[MiG-21]]bis || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[MiG-29 Fulcrum]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Mil Mi 12]] || || || 2.0? || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Moyes Dragonfly]] (Bailey, LiteFlite) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[A6M Zero|Mitsubishi A6M Zero]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], [[JSBSim]]
|-
|A|| [[Mitsubishi MRJ90]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Nakajima B5N]] ('Kate') || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Nakajima Ki-84]] ''Hayate'' ("Gale")('Frank') || 1 || 1.9 || 2.0 ||2.4 || 2.6 || 2.8||
|-
|A|| [[Nieuport 11]] || || || 2.0 ||2.4 || 2.6 || 2.8||
|-
|A|| [[Nord Noratlas]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8||
|-
|A|| [[F-86 Sabre|North American F-86F Sabre]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[P-51D|North American P-51D Mustang]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[OV-10|North American OV-10 Bronco]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[North American X-15]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[UTIAS Ornithopter No.1|Ornithopter No.1]] (UTIAS) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || || [[UIUC]]
|-
|AG|| [[Paraglider]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || || [[JSBSim]]
|-
|A|| [[Payen Pa 100]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || || [[YASim]]
|-
|A|| [[PBY Catalina|Consolidated Aircraft PBY-6 Catalina]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Piaggio P180 Avanti|Piaggio P180 Avanti II]] (FDM only) || 1 ||1.9 || 2.0 || 2.4 || 2.6 ||2.8|| [[YASim]]
|-
|H|| [[Piasecki HUP-3|Piasecki HUP-3 Retriever]] (later Boeing-Vertol) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Pilatus PC-6 Porter]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Pilatus PC-7]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Pilatus PC-9M]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Pilatus PC-21]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Piper J3 Cub]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]] (remodelled Apr10)
|-
|A|| [[Piper PA-18 Super Cub]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Piper PA-22]] || || || || || || 2.8|| [[YASim]]
|-
|A|| [[Piper PA-24 Comanche|Piper PA-24 Comanche 250]] (1962 model) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Piper Cherokee|Piper PA-28 Cherokee Warrior II]] (1979 model) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Piper PA-32]] || || || 2.0? || 2.4 || 2.6 || 2.8||
|-
|A|| [[Piper PA-34 Seneca|Piper PA-34-200T Seneca II]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Pitts Special|Pitts S1C]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Polikarpov I16]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|A|| [[Potez 630]] || || || 2.0? || 2.4 || 2.6 || 2.8||
|-
|A|| [[PZL-Mielec M-18 Dromader]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Quest Aircraft Kodiak 100]] || || || || || || ||
|-
|A|| [[Rallye-MS893E]] || || || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|RC|| [[Rascal 110]] (R/C model plane) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]], [[JSBSim]]
|-
|A|| [[Robin DR400]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Robinson R22]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Robinson R44]] || || || || || || 2.8|| [[YASim]]
|-
|A|| [[Royal Aircraft Factory S.E.5]] || || || || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A || [[Ryan NYP]] (Spirit of St. Lois) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[JSBSim]], [[YASim]]
|-
|A || [[Ryan PT-22]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A || [[Ryan Navion]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Rutan Quickie 2]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Rutan Model 61 Long-EZ]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Rutan Pond Racer]] || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[14bis|Santos Dumont 14bis]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||[[YASim]]
|-
|A|| [[Santos Dumont N 21 Demoiselle]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||[[YASim]]
|-
|A|| [[Saab Draken|Saab J35Ö Draken]] (J35oe) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Saab JAS 39 Gripen]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || SEPECAT Jaguar (GR1/S) (Breguet (later Dassault)/BAC) | || || 2.0 ||2.4 || 2.6 || 2.8||
|-
|A|| [[Aermacchi S-211|Siai Marchetti S.211]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[UIUC]] (FDM only)
|-
|A|| [[Scaled Composites White Knight with SpaceShipOne]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|AG || [[Schweizer 2-33]] (TG-4) (Glider) || 1 || 1.9 || 2.0 || 2.4|| 2.6 ||2.8 ||
|-
|AG || [[ASW-20 sailplane|Schleicher ASW 20]] (Single Glider) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[UIUC]]
|-
|AG || [[Schleicher ASK 21]] (Glider) || 1 ||1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|AG || [[Schleicher ASK 21-MI]] (Glider) || || || 2.0 || 2.4 || 2.6 ||2.8
|-
|A|| [[Short Empire]] || || || || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A || [[Short SC.7 Skyvan]] || || C || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Short Stirling]] || || || || || || 2.8|| [[YASim]]
|-
|H || [[Sikorsky Aircrane]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Sikorsky S-38B]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|H|| [[Sikorsky S51|Sikorsky S-51]] (R-5) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|H|| [[Sikorsky S58|Sikorsky S-58]] (H-34) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Sikorsky UH60|Sikorsky UH-60 Blackhawk]] (S-70 family) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|H|| [[Sikorsky S76C|Sikorsky S-76C++]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|H|| [[Sikorsky CH-53E Super Stallion]] (S-80) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]] (FDM only)
|-
|A|| [[Best Off Skyranger|Skyranger]] (Best Off Skyranger) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]], [[YASim]]
|-
|A|| [[SPAD VII]] || || || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Space Shuttle]] (FDM only) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Sopwith Camel]] 1F.1 || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[UIUC]], [[YASim]]
|-
|A|| [[Soko J-22 Orao]] / IAR-93 || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Stampe SV.4]] || || 1.9 ||2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Stearman Model 75]] (Boeing Kaydet) || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|AZ|| [[Submarine Scout]] (Blimp) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Sud Aviation SE 210 Caravelle]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Supermarine S.6B]] || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8||
|-
|A|| [[Supermarine Seafire|Supermarine Seafire MkIIIc]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Supermarine Spitfire|Supermarine Spitfire IIa]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Supermarine Spitfire Mk IX]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Sukhoi Su-25]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Sukhoi Su-26]]M || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Sukhoi Su-37|Sukhoi Flanker-F]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Sukhoi T-50 PAK-FA]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|A|| [[Super Guppy]] || || || || || || 2.8|| [[YASim]]
|-
|A|| [[Northrop T-38|T-38 Talon]] (Northrop, Northrop Grumman) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A || [[Taylor Aerocar]] || || || 2.0? || 2.4 || 2.6 || 2.8||
|-
|A || [[Tecnam P92]] || || || 2.0? || 2.4 || 2.6 || 2.8||
|-
|A || [[Transall C-160]] || || || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|A|| [[Tupolev ANT-20]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[YASim]]
|-
|A|| [[Tupolev 114|Tupolev Tu-114]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Tupolev 154|Tupolev Tu-154]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||[[YASim]]
|-
|A|| [[Velocity XL]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Van's Aircraft RV-6]] || || || 2.0 || 2.4 || 2.6 ||2.8||
|-
|A|| [[Vickers Vimy]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|H|| [[Lynx WG13|Westland Lynx WG13]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[Westland-Hill Pterodactyl Mk V]] || || || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|A|| [[Wright Flyer|Wright Flyer 1903]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[UIUC]]
|-
|RC|| [[YardStik]] (R/C model plane) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|A|| [[Yokosuka K5Y]] (K5Y1/Type 93/'Willow') || || || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|A|| [[YS-11]] (NAMC (''Nihon Kōkūki Seizō'')) || || || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|AZ || [[Zeppelin LZ 121 Nordstern]] || || || || 2.4 || 2.6 ||2.8 || [[JSBSim]]
|-
|AZ || [[Zeppelin NT]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Zivko Edge 540]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|A|| [[Zlin Z-50|Zlin Z-50LX]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|AZ || [[ZF Navy free balloon]] || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[JSBSim]]
|-
|
|-
|V|| [[Snowplow]] (Truck, with AI) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|V|| [[Deux Chevaux Citroen]] (2CV) || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || [[YASim]]
|-
|V|| [[Jeep]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| [[YASim]]
|-
|V|| [[Pushback]] (for aircraft pushback) || 1 || 1.9 || 2.0 || 2.4|| 2.6 || 2.8||
|-
|V|| [[Follow me]] || 1|| 1.9 || 2.0 || 2.4 || 2.6 || 2.8||
|-
|V|| [[Mobile Stairs]] || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 ||
|-
|V || [[M113AS3]] (tracked vehicle) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 ||
|-
|F|| [[Bell 222X]] ("Airwolf", fictional Bell 222 version) || || 1.9 || 2.0 || 2.4 || 2.6 || 2.8|| From Airwolf TV show.
|-
|F|| [[Carreidas 160]] (fictional jet transport) || || 1.9 || 2.0 || 2.4 || 2.6 ||2.8 || From Tintin comic.
|-
|F || [[Bluebird]] (Fictional hovercraft) || 1 || 1.9 || 2.0 || 2.4 || 2.6 ||2.8||
|-
|F|| [[Ogel]] (fantasy plane) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[JSBSim]]
|-
|F|| [[Santa Claus]] Sleigh || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8
|-
|F|| [[UFO from the 'White Project' of the UNESCO|UFO]] (fantasy flying saucer) || 1 || 1.9 || 2.0 || 2.4 || 2.6 || 2.8 || [[Howto: Place 3D objects with the UFO|Place objects with UFO]]
|-
|}

== References ==
* http://en.wikipedia.org/wiki/Flightgear
* http://www.flightgear.org/

[[en:Table of models]]
[[es:Tabla de modelos]]

Fr/Vehicules

2013-01-04T21:46:55Z

Alexis:

Des exemples de quelques-uns des '''véhicules''' de [[FlightGear]], voir le [[Fr/Table des modèles| tableau des modèles]] pour une liste plus complète.


{{Model Gallery | section=vehicles}}

[[de:Fahrzeuge]]
[[es:Vehículo]]
[[en:Vehicle]]

Fr/Avions

2013-01-04T21:22:35Z

Alexis: /* Véhicule spatiaux */

Cette liste n'est pas mise à jour pour contenir tous les avions sous [[GNU General Public License|licence GPL]] de Flightgear, mais elle donne un bon aperçu des différents types d'avions disponibles. Vous pouvez regarder la [[Fr/Table_des_modèles|liste des modèles]] pour une vue concise.

Les modèles présentés ici viennent officiellement du projet FlightGear, et sont disponibles sur [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear.org]. L'installation consiste alors à décompresser l'archive et à l'installer dans le dossier "Aircraft" de FlightGear (si ils ne font pas déjà parti du pack de base).

Plus d'avions sont disponibles dans les [[FlightGear hangars|hangars non officiels de Flightgear]], voir aussi les [[Fr/Helicoptere|Hélicoptères]], ou les [[Fr/Vehicules|Véhicules]] pour plus d'exemples.

Les caractéristiques, la qualité et la compatibilité des avions sont variables, leur développement dépend des [[Fr/Volontaires|volontaires]] impliqués, à l'exception de quelques projets financés par des gouvernements ou des Universités.

Souvenez-vous que cette liste n'est qu'un échantillon des avions de FlightGear !

=== Avions civil légers ===
Le Cessna 172 est l'avion par défaut de FlightGear. Ces avions disposent de 1 ou 2 moteurs à pistons, ce sont des avions à hélices équipés d'une avionique destinée aux pilotes civils.
{{Model Gallery | section=light_civilian_aircraft}}

=== Avions de ligne ===
Ils ont de 2 à 4 turbo-réacteurs, et disposent de procédures de décollage et d'atterrissage plus complexes (comme des [[flaps|volets]] multiples). De plus, dans le réel, leur avionique demande des licences professionnelles ainsi que des certifications. Rassurez-vous, ils sont généralement plus faciles à démarrer dans FlightGear !

{{Model Gallery | section=modern_airliners_narrowbody_midsize}}
{{Model Gallery | section=modern_airliners_widebody_jumbo}}

=== Hélicoptères ===
{{Main article|Helicopter}}

Les hélicoptères possèdent des commandes différentes des avions à ailes fixe (cf: [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]]. les hélicoptères modernes sont équipés de une à deux turbines entrainant un rotor comprenant 2 à 6 pales.

{{Model Gallery | section=helicopters}}

=== Vol à voile, planeurs, ULM ===
Équipés de contrôles basiques, avec une avionique minimum, les planeurs et autres avions de vol à voile vous permettent d'utiliser les thermiques ou le vol de pente (cf: [[Soaring|vol à voile]]). Les ULM pour leur part sont parmi les plus simple de [[FlightGear]].

{{Model Gallery | section=ultra_light}}

=== Warbirds ===
FlightGear possède un large panel d'anciens avions militaires, dont la complexité et le réalisme dépend de leur niveau de développement.

{{Model Gallery | section=warbirds}}

=== chasseurs embarqués ===
Ces avions sont capables d'utiliser les brins d'arrêt et les catapultes des porte-avions.

{{Model Gallery | section=carrier_borne_aircraft}}

=== Avions de l'OTAN ===
FG propose une large diversité de jets modernes ou déclassés, permettant par exemple le ravitaillement en vol avec le vénérable KC135 et la possibilité de larguer des bombes avec le A-10.

{{Model Gallery | section=modern_military_aircraft}}

=== Avions historiques ===
quelques avions d'obscures à fameux sont disponible, en qualités diverses.
{{Model Gallery | section=historical_aircraft}}

=== Inclassables ===
Avions expérimentaux, bateaux volants, avions spéciaux.

{{Model Gallery | section=experimental}}

=== Plus légers que l'air (à partir de la version 1.9.0) ===

Ils utilisent un gaz pour flotter dans l'air, en plus des contrôles traditionnels, ils peuvent avoir des contrôles avancés du gaz (ballasts, pression, volume.

{{Model Gallery | section=lighter_than_air}}

=== Science Fiction ===
Quelques modèles classifiés, dont certains peuvent être utilisés pour créer les scènes.

{{Model Gallery | section=science_fiction}}

=== Véhicules spatiaux ===
Des choses qui montrent à quel point nôtre planète terre est petite !
{{Model Gallery| section=spacecraft}}

== Liens ==
* [http://scenemodels.flightgear.org/ FGFS Scenery Object Database]: les modèles pour [[Scenery|le scenery]]
* [[Howto: Multiplayer]], [[Installing Scenery|installer des scènes]], et [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]].
[[en:Aircraft]]
[[es:Avión]]
[[pt:Avião]]

[[Category:List]]

Fr/Avions

2013-01-04T21:21:36Z

Alexis: /* Spacecrafts */

Cette liste n'est pas mise à jour pour contenir tous les avions sous [[GNU General Public License|licence GPL]] de Flightgear, mais elle donne un bon aperçu des différents types d'avions disponibles. Vous pouvez regarder la [[Fr/Table_des_modèles|liste des modèles]] pour une vue concise.

Les modèles présentés ici viennent officiellement du projet FlightGear, et sont disponibles sur [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear.org]. L'installation consiste alors à décompresser l'archive et à l'installer dans le dossier "Aircraft" de FlightGear (si ils ne font pas déjà parti du pack de base).

Plus d'avions sont disponibles dans les [[FlightGear hangars|hangars non officiels de Flightgear]], voir aussi les [[Fr/Helicoptere|Hélicoptères]], ou les [[Fr/Vehicules|Véhicules]] pour plus d'exemples.

Les caractéristiques, la qualité et la compatibilité des avions sont variables, leur développement dépend des [[Fr/Volontaires|volontaires]] impliqués, à l'exception de quelques projets financés par des gouvernements ou des Universités.

Souvenez-vous que cette liste n'est qu'un échantillon des avions de FlightGear !

=== Avions civil légers ===
Le Cessna 172 est l'avion par défaut de FlightGear. Ces avions disposent de 1 ou 2 moteurs à pistons, ce sont des avions à hélices équipés d'une avionique destinée aux pilotes civils.
{{Model Gallery | section=light_civilian_aircraft}}

=== Avions de ligne ===
Ils ont de 2 à 4 turbo-réacteurs, et disposent de procédures de décollage et d'atterrissage plus complexes (comme des [[flaps|volets]] multiples). De plus, dans le réel, leur avionique demande des licences professionnelles ainsi que des certifications. Rassurez-vous, ils sont généralement plus faciles à démarrer dans FlightGear !

{{Model Gallery | section=modern_airliners_narrowbody_midsize}}
{{Model Gallery | section=modern_airliners_widebody_jumbo}}

=== Hélicoptères ===
{{Main article|Helicopter}}

Les hélicoptères possèdent des commandes différentes des avions à ailes fixe (cf: [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]]. les hélicoptères modernes sont équipés de une à deux turbines entrainant un rotor comprenant 2 à 6 pales.

{{Model Gallery | section=helicopters}}

=== Vol à voile, planeurs, ULM ===
Équipés de contrôles basiques, avec une avionique minimum, les planeurs et autres avions de vol à voile vous permettent d'utiliser les thermiques ou le vol de pente (cf: [[Soaring|vol à voile]]). Les ULM pour leur part sont parmi les plus simple de [[FlightGear]].

{{Model Gallery | section=ultra_light}}

=== Warbirds ===
FlightGear possède un large panel d'anciens avions militaires, dont la complexité et le réalisme dépend de leur niveau de développement.

{{Model Gallery | section=warbirds}}

=== chasseurs embarqués ===
Ces avions sont capables d'utiliser les brins d'arrêt et les catapultes des porte-avions.

{{Model Gallery | section=carrier_borne_aircraft}}

=== Avions de l'OTAN ===
FG propose une large diversité de jets modernes ou déclassés, permettant par exemple le ravitaillement en vol avec le vénérable KC135 et la possibilité de larguer des bombes avec le A-10.

{{Model Gallery | section=modern_military_aircraft}}

=== Avions historiques ===
quelques avions d'obscures à fameux sont disponible, en qualités diverses.
{{Model Gallery | section=historical_aircraft}}

=== Inclassables ===
Avions expérimentaux, bateaux volants, avions spéciaux.

{{Model Gallery | section=experimental}}

=== Plus légers que l'air (à partir de la version 1.9.0) ===

Ils utilisent un gaz pour flotter dans l'air, en plus des contrôles traditionnels, ils peuvent avoir des contrôles avancés du gaz (ballasts, pression, volume.

{{Model Gallery | section=lighter_than_air}}

=== Science Fiction ===
Quelques modèles classifiés, dont certains peuvent être utilisés pour créer les scènes.

{{Model Gallery | section=science_fiction}}

=== Véhicule spatiaux ===
Des choses qui montrent à quel point nôtre planète terre est petite
{{Model Gallery| section=spacecraft}}

== Liens ==
* [http://scenemodels.flightgear.org/ FGFS Scenery Object Database]: les modèles pour [[Scenery|le scenery]]
* [[Howto: Multiplayer]], [[Installing Scenery|installer des scènes]], et [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]].
[[en:Aircraft]]
[[es:Avión]]
[[pt:Avião]]

[[Category:List]]

Fr/Table des modèles

2013-01-04T21:18:40Z

Alexis:

Fr/Avions

2013-01-04T21:01:22Z

Alexis:

Cette liste n'est pas mise à jour pour contenir tous les avions sous [[GNU General Public License|licence GPL]] de Flightgear, mais elle donne un bon aperçu des différents types d'avions disponibles. Vous pouvez regarder la [[Fr/Table_des_modèles|liste des modèles]] pour une vue concise.

Les modèles présentés ici viennent officiellement du projet FlightGear, et sont disponibles sur [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear.org]. L'installation consiste alors à décompresser l'archive et à l'installer dans le dossier "Aircraft" de FlightGear (si ils ne font pas déjà parti du pack de base).

Plus d'avions sont disponibles dans les [[FlightGear hangars|hangars non officiels de Flightgear]], voir aussi les [[Fr/Helicoptere|Hélicoptères]], ou les [[Fr/Vehicules|Véhicules]] pour plus d'exemples.

Les caractéristiques, la qualité et la compatibilité des avions sont variables, leur développement dépend des [[Fr/Volontaires|volontaires]] impliqués, à l'exception de quelques projets financés par des gouvernements ou des Universités.

Souvenez-vous que cette liste n'est qu'un échantillon des avions de FlightGear !

=== Avions civil légers ===
Le Cessna 172 est l'avion par défaut de FlightGear. Ces avions disposent de 1 ou 2 moteurs à pistons, ce sont des avions à hélices équipés d'une avionique destinée aux pilotes civils.
{{Model Gallery | section=light_civilian_aircraft}}

=== Avions de ligne ===
Ils ont de 2 à 4 turbo-réacteurs, et disposent de procédures de décollage et d'atterrissage plus complexes (comme des [[flaps|volets]] multiples). De plus, dans le réel, leur avionique demande des licences professionnelles ainsi que des certifications. Rassurez-vous, ils sont généralement plus faciles à démarrer dans FlightGear !

{{Model Gallery | section=modern_airliners_narrowbody_midsize}}
{{Model Gallery | section=modern_airliners_widebody_jumbo}}

=== Hélicoptères ===
{{Main article|Helicopter}}

Les hélicoptères possèdent des commandes différentes des avions à ailes fixe (cf: [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]]. les hélicoptères modernes sont équipés de une à deux turbines entrainant un rotor comprenant 2 à 6 pales.

{{Model Gallery | section=helicopters}}

=== Vol à voile, planeurs, ULM ===
Équipés de contrôles basiques, avec une avionique minimum, les planeurs et autres avions de vol à voile vous permettent d'utiliser les thermiques ou le vol de pente (cf: [[Soaring|vol à voile]]). Les ULM pour leur part sont parmi les plus simple de [[FlightGear]].

{{Model Gallery | section=ultra_light}}

=== Warbirds ===
FlightGear possède un large panel d'anciens avions militaires, dont la complexité et le réalisme dépend de leur niveau de développement.

{{Model Gallery | section=warbirds}}

=== chasseurs embarqués ===
Ces avions sont capables d'utiliser les brins d'arrêt et les catapultes des porte-avions.

{{Model Gallery | section=carrier_borne_aircraft}}

=== Avions de l'OTAN ===
FG propose une large diversité de jets modernes ou déclassés, permettant par exemple le ravitaillement en vol avec le vénérable KC135 et la possibilité de larguer des bombes avec le A-10.

{{Model Gallery | section=modern_military_aircraft}}

=== Avions historiques ===
quelques avions d'obscures à fameux sont disponible, en qualités diverses.
{{Model Gallery | section=historical_aircraft}}

=== Inclassables ===
Avions expérimentaux, bateaux volants, avions spéciaux.

{{Model Gallery | section=experimental}}

=== Plus légers que l'air (à partir de la version 1.9.0) ===

Ils utilisent un gaz pour flotter dans l'air, en plus des contrôles traditionnels, ils peuvent avoir des contrôles avancés du gaz (ballasts, pression, volume.

{{Model Gallery | section=lighter_than_air}}

=== Science Fiction ===
Quelques modèles classifiés, dont certains peuvent être utilisés pour créer les scènes.

{{Model Gallery | section=science_fiction}}

=== Spacecrafts ===
Des choses qui montrent à quel point nôtre planète terre est petite
{{Model Gallery| section=spacecraft}}

== Liens ==
* [http://scenemodels.flightgear.org/ FGFS Scenery Object Database]: les modèles pour [[Scenery|le scenery]]
* [[Howto: Multiplayer]], [[Installing Scenery|installer des scènes]], et [[Fr/Piloter l'hélicoptère|Piloter un hélicoptère]].
[[en:Aircraft]]
[[es:Avión]]
[[pt:Avião]]

[[Category:List]]

Fr/Eurocopter EC135

2012-12-29T16:41:12Z

Alexis: Created page with "{{infobox Aircraft |image =Ec135.png |name =Eurocopter EC135 |type = Hélicoptère |livery= ADAC, ANWB, ÖAMTC, Prototype |fdm =YASim |status =v0.5 in 2.6.0 |authors =Heiko Sc..."

{{infobox Aircraft
|image =Ec135.png
|name =Eurocopter EC135
|type = Hélicoptère
|livery= ADAC, ANWB, ÖAMTC, Prototype
|fdm =YASim
|status =v0.5 in 2.6.0
|authors =Heiko Schulz, Maik Justus, Melchior Franz
|fgname =ec135
}}
L''''Eurocopter EC135''' est un [[Fr/Helicoptere|hélicoptère]] bimoteur léger et polyvalent.

L'EC 135 descend du MBB Bo 108. Le Bo 108 était un prototype de démonstration des commandes de vol électriques et descendait du célèbre Bo 105.
Le Bo 108 est sorti lorsque la société Eurocopter fut fondée. Eurocopter entrevoyait qu'il y avait un marché pour un tel hélicoptère et continua son développement. La partie française d'Eurocopter apporta de son côté le rotor anti-couple de type fenestron. Le fenestron permet de limiter les risques pour le personel au sol et réduit le niveau de bruit d'environ 50% par rapport aux autres hélicoptères. C'est pourquoi l'EC 135 est très utilisé par les urgences et les forces de police, essentiellement en Europe mais aussi aux USA, au Japon et dans d'autres pays.

[[File:EC135 Swedish Police.jpg||thumb|right|270px|EC135 - " Police Suédoise" réalisé par Sanni]]

[[File:EC135 DRF.jpg||thumb|right|270px|EC135 - "DRF" réalisé par Sanni]]

[[File:EC135 Adebar16.jpg||thumb|right|270px|EC135 - "Adebar 16"]]

[[File:EC135 Air Zermatt.jpg||thumb|right|270px|EC135 - "Air Zermatt" réalisé par Sanni]]

[[File:EC135NEW2.jpg|thumb|right|270px| - Voici la version "Offshore" de l'EC135]]

[[File:EC135NEWBP.jpg|thumb|right|270px|New EC135 - Voici la livrée "Bundespolizei"- réalisé par Sanni aka Tanja S.]]

[[File:EC135NEW1.jpg|thumb|right|270px|Voici la version "Sauvetage en montagne"]]

[[File:Ec135_LFLJ.jpg|thumb|right|270px|EC 135 "D-HECZ" (prototype) dans FGFS 1.9.1prend son envol au-dessus des nuages à Courchevel; voir [[Flying the helicopter]] ]]

== Liens externes ==
[http://www.eurocopter.de www.eurocopter.de]

{{Eurocopter}}

[[Category:Helicopters]]
[[en:Eurocopter EC135]]

Eurocopter EC135

2012-12-29T16:41:06Z

Alexis:

{{infobox Aircraft
|image =Ec135.png
|name =Eurocopter EC135
|type =Helicopter
|livery= ADAC, ANWB, ÖAMTC, Prototype
|fdm =YASim
|status =v0.5 in 2.6.0
|authors =Heiko Schulz, Maik Justus, Melchior Franz
|fgname =ec135
}}This is an model of the '''Eurocopter EC135''', a light twin-engine, multi-mission [[helicopter]].

The EC 135 descends from the MBB Bo 108. The Bo 108 was a demonstration prototype for fly-by-wire and has it's descent from the famous Bo 105.
When the Eurocopter company was founded, the Bo 108 came with. Eurocopter decided that there was a marketplace for such a helicopter and the development went on. From the French partners it got the fenestron, from MBB the hingeless rotor. The fenestron makes it very hard for dangerous situations in the range of the tail rotor and reduces the noise level about 50% to other helicopters. That's why the EC 135 is a highly recommended helicopter for EMS and the police, especially in Europe but also in the USA, Japan and other states.

== Development status/Issues/Todo ==
[[File:EC135 Swedish Police.jpg||thumb|right|270px|New EC135 - "Swedish Police" made by Sanni]]

[[File:EC135 DRF.jpg||thumb|right|270px|New EC135 - "DRF" made by Sanni]]

[[File:EC135 Adebar16.jpg||thumb|right|270px|New EC135 - "Adebar 16"]]

[[File:EC135 Air Zermatt.jpg||thumb|right|270px|New EC135 - "Air Zermatt" by Sanni]]

[[File:EC135NEW2.jpg|thumb|right|270px|New EC135 - here the "Offshore"variant]]

[[File:EC135NEWBP.jpg|thumb|right|270px|New EC135 - here the converted "Bundespolizei"-livery by Sanni aka Tanja S.]]

[[File:EC135NEW1.jpg|thumb|right|270px|New EC135 - here the "Mountain rescue" variant]]

[[File:Ec135_LFLJ.jpg|thumb|right|270px|EC 135 "D-HECZ" (prototype) in FGFS 1.9.1 takes off above the clouds at Courchevel; see [[Flying the helicopter]] ]]
===Next upcoming version v1.0 (probably FGFS 3.0.0 Release)===
Expected

* new 3d-model more accurate and detailed
* latest shader (bumpspec-reflection and glasshader)
* new, much more accurate fdm close to POH
* more different configurations possible- lowskid, midskid and highskid, different sandfilter, different radomes etc...
* one single texture file - old liveries can be converted
* finally a complete flightdeck with photorealistic panel
* and of course completely Rembrandt compatible!
* and more to come....

=== Actual version: v.0.6 (EC135-Repo on gitorious.org) ===

* fixes wrong rotorshaft tilt in fdm
* some bugfixes on fuselage
* sound fixed

very next To-Do:
* rotor model and animation
* bugfixing on windscreen
* instruments finishing

=== Actual version: v.0.5 (FGFS 2.6.0 release) ===

* photorealistic panel
* liveries improved
* better fps-perfomance while changing liveries

=== Actual version: v.0.4 (FGFS 1.9.1 release) ===

This is a complete rebuild of the ec135 with a much better exterior
model It is currently a work in progress, so a lots of things can be
broken now, but it should be not worser to fly than in the last version.

* complete new exterior with added antennas and other mounting parts(search lights, cameras)
* glas shader with fresnel effect
* variants changing over mp
* better texture mapping so it should be easy to make your own livery

Currently in Progress at this date:
* replacing the panels and adding the digital version with a nearly photorealistic one!
* adding the overhead
* making it all clickable and working from the cockpit
* better interior : EMS and VIP-version
* remade D-HECZ-Livery
* mapped ec135 with D-HECZ-Livery
* added ADAC Chr. 23-Livery made with photorealistic parts like Fenestron and Logos- still some things missing like lines
* added phtorealistic textures to exhaust and rails
* adding and finishing the missing liveries like the OEAMTC, G-SASA, Bavarian Police
* adding the high skid model

=== Actual version: v.0.2 ===

* fully new made 3D-model - matching real good to the real one
* improved interior with stick and pedals
* changed variants: ADAC Chr. 31 "Berlin", D-HECZ "second prototype", ÖAMTC Christopherus 1
* improved cockpit with half analog IFR-panel
* HSI is now working, working VOR
* GSDI selectable
* improved and more detailed main rotor with incidence animation
* Fenestron now with the correct configuration of the blades: 1-4-1-4
* dynamic flight model now with the correct position of the CG
* added frontlight, retractable landinglight, strobes with the correct frequency, beacon with the correct frequency
* rotor brake system now working

To-Do:
* adding antennas and other mounting parts (search lights, cameras)
* fully clickable [[cockpit]] (half-analog and digital)
* complete light function
* variants with radardome
* variants with high-skid
* much more (international)variants!
* realistic dynamic flight model
* mainrotors much more detailed
* animation of the fenestron blades (incidence)
* sound still could be improved
* adding pilots figures

=== Actual version: v.0.1 ===

* first 3d-model of an ec135
* first try of an ec135-flight dynamic model
* livery changing
* two version: ADAC and Bavarian Police
* first version of the half analog cockpit
* doors to open

To-Do:
* better quality of the 3d-model
* full mainrotor animation
* better Fenestron
* improve cockpit, implementing a working HSI
* clean up the xml-files
* improve soundsystem
* realistic dynamic flight model
* selectable GSDI
* implementing rotor brake system
* more variants

== External links ==
[http://www.eurocopter.de www.eurocopter.de]

{{Eurocopter}}

[[Category:Helicopters]]
[[fr:Eurocopter EC135]]

Es/Cessna Citation X

2012-09-08T23:19:57Z

Alexis:

{{infobox Aircraft
|image = CessnaCitationX.jpg
|name = Cessna Citation X
|type = Jet de negocios
|status-fdm = 3
|status-systems= 3
|status-cockpit = 3
|status-model = 3
|livery = Stripes
|authors = Syd Adams
|fdm = YASim
|status = En Desarrollo
|fgname = CitationX
}}
El '''Cessna Citation X''' (X por el numeral romano de 10, no la letra) es un avión de negocios de tamaño medio y largo alcance. El Citation X es a la fecha, la aeronave civil más veloz aún en producción, con una velocidad maxima de Mach 0.92 (unas 703 mph). Esto tambien hace del Citation X, el avión de negocios más veloz de la historia. Este es impulsado
por dos motores Rolls-Royce turbofan y es ensamblado por "The Cessna Aircraft Company" en Wichita, Kansas. La marca Citation jets de negocios abarca seis diferentes "familias" de aeronaves. Aunque se basa en el modelo anterior Citation III, VI y VII, es un avión muy diferente. Este utiliza un diseño nuevo del ala y los motores, y cuenta con una cabina de cristal liquido.

== Contenido relacionado ==
* [[FlightGear Newsletter April 2011#Aircraft reviews|Clic aqui]] para consultar un análisis del Cessna Citation X.

{{Cessna}}

[[Category:Avión de negocios]]
[[En:Cessna Citation X]]
[[fr:Cessna Citation X]]

Cessna Citation X

2012-09-08T23:19:48Z

Alexis:

{{infobox Aircraft
|image = CessnaCitationX.jpg
|name = Cessna Citation X
|type = Business Jet
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|livery = Stripes
|authors = Syd Adams
|fdm = YASim
|status = Development
|fgname = CitationX
}}
The '''Cessna Citation X''' (X as in the Roman numeral for ten, not the letter) is a long range medium business jet aircraft. The X is currently the fastest civilian jet in production with a top speed of Mach 0.92 (703 mph). This also makes it the fastest business jet in history. The Citation X is powered by two Rolls-Royce turbofan engines and is built by the [[Cessna Aircraft Company]] in Wichita, Kansas. The Citation brand of business jets encompasses six distinct "families" of aircraft. Although based on the earlier Citation III, VI and VII models the Citation X is a significantly different airplane. It utilizes a totally new wing design, engines, and features a glass cockpit.

== Related content ==
* [[FlightGear Newsletter April 2011#Aircraft reviews|Click here]] for a review of the Cessna Citation X.

{{Cessna}}

[[Category:Business aircraft]]

[[es:Cessna Citation X]]
[[fr:Cessna Citation X]]

Fr/Cessna Citation X

2012-09-08T23:18:48Z

Alexis: Created page with "{{infobox Aircraft |image = CessnaCitationX.jpg |name = Cessna Citation X |type = Jet privé |status-fdm = 3 |status-systems = 3 |status-cockpit =..."

{{infobox Aircraft
|image = CessnaCitationX.jpg
|name = Cessna Citation X
|type = Jet privé
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|livery = Stripes
|authors = Syd Adams
|fdm = YASim
|status = Développement
|fgname = CitationX
}}
Le '''Cessna Citation X''' (X pour le chiffre romain dix, et non pour la lettre) est un avion d'affaire à grand rayon d'action. Le X est actuellement le jet civil le plus rapide avec une vitesse maximale de Mach 0.92 (703 mph). Ce qui en fait le jet d'affaire le plus rapide de l'histoire. Le Citation X est propulsé par deux turboréacteur Rolls-Royce et est construit par la [[Cessna Aircraft Company]] à Wichita au Kansas. La catégorie de jet d'affaire comprend six différentes «familles» de l'avion. Bien que basé sur le modèle précédent Citation III, VI et VII, le Citation X est un avion très différent. Il utilise une conception totalement nouvelle des ailes, des moteurs et comprend Planche de bord tout écran.

== Contenu associé ==
* [[FlightGear Newsletter April 2011#Aircraft reviews|Cliquez ici]] pour une présentation du Cessna Citation X.
{{Cessna}}

[[Category:Business aircraft]]

[[es:Cessna Citation X]]
[[fr:Cessna Citation X]]

Fr/Portal:Utilisateur

2012-09-08T19:45:25Z

Alexis:

{{PortalMenu}}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Le portail des utilisateurs</h2>
|-
|style="color:#000;"|
Ce portail est destiné aux utilisateurs de FlightGear. Pour être sûrs que vous ayez les dernières nouvelles, c'est une bonne idée de vous inscrire sur la liste [http://lists.sourceforge.net/lists/listinfo/flightgear-users FlightGear users]. [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-users Des archives de cette liste] sont disponibles et devraient être vérifiées avant de poser une question qui aurait déjà été traitée. Il y a aussi un forum anglophone sur http://www.flightgear.org/forums. Le forum francophone se trouve sur http://fr.flightgear.tuxfamily.org/forum/.

|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"

! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Pour débuter</h2>
|-
|style="color:#000;"|
* [[New to FlightGear|Nouveau sur FlightGear]]
* [[Unique Features|Fonctionnalités uniques]]
* [[FlightGear Manual|Manuel de FlightGear]]
* [[FAQ]]
* [[FlightGear tutorials|Tutoriels]]
* [[Hardware Recommendations|Matériel recommandé]]
* [[Notebooks known to run FlightGear]]
* [[Recommended Software|Logiciels recommandés]]
* [[Troubleshooting Problems|Résoudre les problèmes]]
* [[Volunteer|Participer]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Configurer Flightgear</h2>
|-
|style="color:#000;"|
* [[Command Line Parameters|Paramètres en ligne de commande]]
* [[Downloading New Flightgear Scenery for Windows XP|Télécharger de nouvelles scènes sous Windows XP]]
* [[Installing Scenery|Installer des scènes]]
* [[Installing Aircraft|Installer des avions]]
* [[Improving Framerates|Augmenter le nombre d'images par seconde]]
* [[Joystick]]
* [[Linux software audio mixing with FlightGear|mixage logiciel du son sous Linux avec FlightGear]]
* [[fr/Howto: Multijoueur|Multijoueur]]
* [http://www.inkdrop.net/dave/multimon.pdf Utiliser plusieurs écrans avec FlightGear]
* [[Howto:Configure Camera View Windows]]
* [[Fr/Anti-aliasing | Configurer l'anticrénelage (anti-aliasing)]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utiliser Flightgear</h2>
|-
|style="color:#000;"|

* [[fr/Table des modèles|Table des modèles]]
* [[fr/Avions|Aéronefs]]
* [[fr/Piloter l'hélicoptère|Hélicoptères]]
* [[fr/Piloter les warbirds|Piloter les warbirds]]
* [[Vehicle|Véhicules]]
* [[Chat Menu]]
* [[Doing aerotow over the net|Remorquage de planeur en multijoueur]]
* [[Dual control|Double commande en multijoueur]]
* [[Flying the Helicopter|Piloter un hélicoptère]]
* [[Instant Replay]]
* [[Menubar|Barre de menu]]
* [[Preset Properties]]
* [[Realism|Réalisme]]
* [[Starting in the Air|Démarrer en l'air]]
* [[Table of models|Tableau des modèles]] Nouveau! 
* [[FlightGear related projects|projets liés à FlightGear]]
* [http://www.nanjika.co.uk/flightgear/FGShortRef.pdf FlightGear Short Reference] pdf, 80 kB
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Suggestions</h2>
|-
|style="color:#000;"|

* [[Suggested Aircraft|Suggestions d'avions]]
* [[Suggested Airports/Scenery|Suggestions de scènes/aérodromes]]
* [[Suggested Flights|Suggestions de vols]]
* [[Suggested Prerecorded Flights|Suggestions de vols pré-enregistrés]] Nouveau! 
* [[Challenging Airports]]
* [[Suggested Software|Suggestions de logiciels]]

|-
|}

|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Communauté/évènements de FlightGear</h2>
|-
|style="color:#000;"|
* [[FlightGear Airways]]
* [[FlightGear Race]]
* [[Pilots of the Caribbean]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Interactive Scenarios</h2>
|-
|style="color:#000;"|
* [[AI Systems|Systèmes IA]]
* [[Interactive Traffic|Traffic interactif]]
* [[Soaring|Planeur]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Howtos</h2>
|-
|style="color:#000;"|
* [[Howto: Air-Air Refueling|Ravitaillement en vol]]
* [[Howto: Be a controller|Devenir contrôleur]]
* [[Howto: Carrier|Porte-avions]]
* [[Howto: Get rid of common errors|Corriger les problèmes courants]]
* [[Howto: Multiplayer|Multijoueur]]
* [[Howto: Make nice screenshots|Prendre de belles captures d'écran]]
* [[Howto: 737-300|737-300]]
'''[[:Category:Howto|Plus...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Tutoriels</h2>
|-
|style="color:#000;"|
* [[ATC Tutorial|Tutoriel ATC]]
* [[Instrument Landing System Tutorial|Tutoriel d'atterrissage aux instruments]]
* [[Updating FlightGear on Windows|Mettre à jour FlightGear sous Windows]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utiliser des outils additionnels</h2>
|-
|style="color:#000;"|
* [[FGCOM]] - communications vocales en temps réel
* [[Atlas]] - comment l'installer
* [[Airport Diagram Generator]] - créer des cartes à partir des données de FlightGear
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Promouvoir FlightGear</h2>
|-
|style="color:#000;"|
* [[Unique Features|Fonctionnalités uniques]]
* [[FlightGear Reviews]]
* [[FlightGear Videos|Vidéos de FlightGear]]
* [[FlightGear 1.0 features showcase|Présentation des fonctionnalités de FlightGear 1.0]]
* [[Logos|Logos de FlightGear]]
* [[Presentation Recipe]]
|-
|}

|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Avions les mieux notés</h2>
|-
|style="color:#000;"|
<w4g_ratinglist numberofitems="5"/>

'''[[Ratings|Plus...]]'''
|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[de:Portal:Benutzer]]
[[es:Portal:Usuario]]
[[pl:Portal:Dla użytkowników]]
[[en:Portal:User]]
[[zh:Portal:用户]]

Fr/Airbus A340-600

2012-09-08T12:54:20Z

Alexis: migration d'une page de wiki française

{{infobox Aircraft
|ready = dualcontrol
|image = Airbus.png
|name = Airbus A340-600
|type = Airliner
|livery = Airbus, Virgin Atlantic, Lufthansa, Iberia
|liverydbid = 6
|authors = Liam Gathercole, Isaias V. Prestes, Simon, Skyop, Ampere
|fdm = JSBsim
|status = Development
|fgname = A340-600
|download = http://www.flightgear.org/forums/viewtopic.php?f=4&t=11894
}}[[File:Airbus1.png|thumb|270px|Airbus A340-600 in Airbus colours]]

'''L'Airbus A340-600''', fabriqué par [[:Category:Airbus|Airbus Industries]], est le plus long [[:Category:Civilian aircraft|avion civil]] au monde. Il a été a été ajouté à [[Fr/FlightGear|FlightGear]] par Liam, à partir de début Novembre 2009.

Vous pouvez suivre sa progression et télécharger la dernière version en développement [[http://www.flightgear.org/forums/viewtopic.php?f=4&t=11894|ici]]

Conçu comme une première génération de remplacement du [[Boeing 747|747]], l'A340-600 peut transporter jusqu'à 380 passagers dans un aménagement tri-cabine de la classe (ou 419 dans un aménagement à classe 2), avec un rayon d'action de plus de 7500 miles nautiques (13,900 km). Il présente une capacité en sièges similaire au 747 mais avec 25% plus de volume de cargaison, et à moindre frais de voyage et de sécurité. Le premier vol de l'A340-600 fut le 23 avril 2001. Virgin Atlantic a débuta services commerciaux en août 2002. L'A340-600 mesure 10 m de plus qu'un [[Airbus A340|-300]] basique, ce qui en fait le plus long avion actuellement en production, plus de quatre mètres plus long que le Boeing [[Boeing 747-400]] et 2,3 m de plus que l'A380. L'Airbus A340-600 continuera à détenir le record du monde pour être la plus long des avions commerciaux jusqu'à ce que le premier Boeing 747-8 Intercontinental entre en service.

== Related content ==
* [[Airbus A340]]

{{Airbus}}

[[Category:Airliners]]
[[en:Airbus A340-600]]

Airbus A340-600

2012-09-08T12:51:35Z

Alexis:

{{infobox Aircraft
|ready = dualcontrol
|image = Airbus.png
|name = Airbus A340-600
|type = Airliner
|livery = Airbus, Virgin Atlantic, Lufthansa, Iberia
|liverydbid = 6
|authors = Liam Gathercole, Isaias V. Prestes, Simon, Skyop, Ampere
|fdm = JSBsim
|status = Development
|fgname = A340-600
|download = http://www.flightgear.org/forums/viewtopic.php?f=4&t=11894
}}[[File:Airbus1.png|thumb|270px|Airbus A340-600 in Airbus colours]]
The '''Airbus A340-600''', made by [[:Category:Airbus|Airbus]] Industries, is the longest [[:Category:Civilian aircraft|civil]] [[:Category:Airliners|airliner]] in world, until the [[Boeing 747-8i]]. It was was added to [[FlightGear]] by Liam Gathercole, starting in early November 2009.

You can follow it's progress and download the latest development version here: http://www.flightgear.org/forums/viewtopic.php?f=4&t=11894

Designed as an early generation [[Boeing 747|747]] replacement, the A340-600 caries up to 380 passengers in a three-class cabin layout (or 419 in a 2-class layout), with a range of over 7,500 nautical miles (13,900 km). It provides similar passenger capacity to a 747 but with 25% more cargo volume, and at lower trip and seat costs. First flight of the A340-600 was made on 23 April 2001. Virgin Atlantic began commercial services in August 2002. The A340-600 is more than 10 m longer than a basic [[Airbus A340|-300]], making it the longest airliner currently in production; more than four metres longer than the [[Boeing 747-400]] and 2.3m longer than the [[Airbus A380|A380]]. The Airbus A340-600 will continue to hold the record for being the worlds longest commercial aircraft until the first Boeing 747-8 Intercontinental is in service.

== Development status/Issues/Todo ==
=== Key Features ===
* Multiple liveries
* Reflection shaders
* External equipment models
* Internal cabin sound effects
* Autostart feature
* Good lights system
* Wings Flex with turbulence/lift
* 3D Cockpit
* Autopilot
* Animations

=== To-do ===
* Some cockpit development

== Related content ==
* [[Airbus A340]]

{{Airbus}}

[[Category:Airliners]]
[[fr:Airbus A340-600]]

FlightGear hangars

2012-08-31T12:35:02Z

Alexis: /* Aircraft hangars */

{{cleanup}}

''See [[Links]] for an overall listing of FlightGear related external websites''

FlightGear has [[aircraft]] and other content available from 3rd-party hangars, some which are GPL compatible and also included in official distributions while others are independent. Aircraft versions range from requiring a developmental build, to being compatible with the latest primary release, to requiring an older version.

Be careful with external links!

== Official hangars ==
=== Aircraft ===
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (Legacy site)
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (Legacy site)
* [http://gitorious.org/fg/fgdata/trees/master/Aircraft Git Hangar] (for [[Git]] builds)

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Liveries]

== Unofficial sites ==
=== Aircraft hangars ===
* [http://www.gitorious.org/fg-airbus-a332 Airbus A330-200 Series Development Git] (A330-203, A330-223, A330-243 - FGAirbus/theOmegaHangar)
* [http://www.gitorious.org/fg-airbus-a333 Airbus A330-300 Series Development Git] (A330-303, A330-323, A330-343 - FGAirbus/theOmegaHangar)
* [https://www.gitorious.org/airbus-aircraft Airbus Aircraft Development Git] (A320, A330, A340-300, A380 - various authors)
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] with [http://gitorious.org/anders-hangar aircraft repositories at gitorious].
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (& a YASim intro)
* <s>[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]</s>{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)
* <s>[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]</s>{{dead link|2012-04}} (a few well made aircraft)
* <s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}} (Blog format)
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ aircraft and add-ons)
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (164+ original aircraft)
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspired aerospace vehicles)
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (Classic aircraft)
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
* [http://flightgear.bplaced.de/ longfly's hangar] (not only German!)
** [http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts] (under development)
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)
* <s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
* [http://theomegahangar.yolasite.com/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)
* [http://pjedvaj.eu5.org/ pjedvaj's Hangar] (Mikoyan-Gurevich MiG-21bis, Pilatus PC-9M, Pilatus PC-21, Hawker Siddeley Harrier GR.1, Boeing-Sikorsky RAH-66)
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)
* <s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models & liveries)
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
* <s>[http://sydhangar.daffodil.uk.com/ Syd's Hangar ]</s>{{dead link|2012-04}} (older 1.9 versions) [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ] (newer 2.0 versions)
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]
* [http://acjza-hangers.webs.com/ ACJZA's Hanger] (A310, BAe 146, C-Series)

=== Old Hangars ===
* [http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)

=== Livery hangars ===
* [http://berwickskins.yolasite.com/ Berwick-skins]
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]

=== Homepages, blogs, etc. ===
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]
* [http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]
* [http://www.grupofgbr.com.br/ Grupo FGBR Brazilian Portal]
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (Last post Dec. 2008)
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009] (non-english)
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]
* [http://www.flightgearcanada.ca/ FlightGear Canada] (The home of everything Canadian for FlightGear)
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials and more)
* [http://www.fguk.eu/ FlightGear United Kingdom]
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]
* <s>[http://tehwarlock.tk/ Tehwarlock Blog]</s>{{dead link|2012-04}}
* [http://www.vivefg.org/ Vive FlightGear!] Aircrafts, scenery, manuals and forum (non-english)
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle

=== Other FlightGear repositories/mirrors ===
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)
* [http://www.flightgearplanes.com Flightgear Planes Website]
* [http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/ Older versions of FlightGear aircraft]

== Related content ==
* [[Table of models]]
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]

[[Category:List]]

Fr/Foire aux questions

2012-08-31T12:24:52Z

Alexis: /* Quelle autre documentation importante devrais-je lire ? */

Consultez également : [[Aircraft]], [[Howto: Multiplayer|Multiplayer Help]], [[Installing Scenery]], and [[Flying the Helicopter]].

'''Cette FAQ n'a pas été mise à jour de manière significative depuis 2006.''' 

''' Vous êtes donc invité à faire des ajouts, des changement ou des corrections.'''

== La FAQ ==
=== Où puis-je obtenir la dernière version de cette FAQ? ===

http://www.flightgear.org/Docs/FlightGear-FAQ.html

=== Qui puis-je contacter si j'ai des commentaires sur cette FAQ ? ===

Ajoutez vos commentaires à la page de discussion de cette FAQ [[Talk:FAQ]].

=== De quand date ce document ? ===

Cliquez sur l'onglet "historique" en haut de cette page.

=== Quelle autre documentation importante devrais-je lire ? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[Fr/Nouveau sur flightgear|Nouveau sur flightgear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.
* Voir aussi l'autre [http://www.flightgear.org/Docs/FAQ.shtml FAQ]

== Distribution ==

=== Où puis-je télécharger FlightGear? ===

La page officielle de téléchargement est http://www.flightgear.org/Downloads/. Notre principale méthode de distribution est le code source, mais des binaires précompilés sont disponibles pour Windows et SGI IRIX.

FlightGear également disponible sous forme de paquets pour Linux par SuSE, Debian (sid) et Mandrake (Cooker) et peut être ainsi directement installé pour ces distributions.

=== Comment installer FlightGear Sur Ubuntu ? ===

FlightGear peut être installé directement à partir du gestionnaire de paquets Synaptic.
Ouvrez le gestionnaire de paquets Synaptic (Système -> Administration -> Gestionnaire de paquets Synaptic, cherchez FlightGear et suivez les instructions. Pour Ubuntu 7.10 vous pourrez installer FlightGear 9.10.

=== What if I want to install FlightGear 1.0 or later versions on Ubuntu? ===

First install WINE from Synaptic, then run the FGSetup installer by right clicking and selecting open in WINE. Just follow instructions. Everything seems to work OK and is quite fast except for the first startup screen where the aircraft list is not visible. For information on WINE see http://www.winehq.org/

=== Quel est le mot de passe pour le serveur FTP ? ===

Le serveur FTP utilise une procédure d'identification anonyme standard. Identifiez-vous avec l'identifiant "anonymous" et utilisez votre adresse de courriel comme mot de passe. La plupart des clients FTP et des navigateurs web le feront automatiquement pour vous.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Où puis-je trouver le dernier code source de développement ? ===

The latest development code is available for everyone through our CVS repository. See http://www.flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== Qu'est-ce que SimGear et pourquoi en ai-je besoin ? ===

[[SimGear]] is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/. Note: When compiling FlightGear it is very important to have the matching version of SimGear.

=== Où puis-je voler et où télécharger les scènes ? ===

Afin d'éviter un téléchargement trop lours, le paquetage de base ne contient que la zone de la baie de San Francisco. Cependant, vous pouvez voler n'importe où dans le monde. Rendez-vous à la section "Additional Scenery" de la page http://www.flightgear.org/Downloads/ pour plus d'informations ou rendez-vous directement à l'interface graphique de téléchargement à l'adresse http://www.flightgear.org/Downloads/world-scenery.html.

Visitez également la section "Places to Fly" sur le site http://www.flightgear.org/Places/ pour de l'aide complémentaire à la navigation vers endroits exceptionnels. (voir également [[Installing Scenery]])

=== Where can I get different 3D models for my plane? ===

Official FlightGear aircraft can be found at http://www.flightgear.org/Downloads/aircraft-2.0.0/ . Other aircraft in development can be found on [[CVS]], and some other aircraft can be found on 3rd party [FlightGear hangars]].

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the [[$FG ROOT]]/Navaids/ and [[$FG ROOT]]/Airports/ directories. If you have updates or corrections to the dataset, see http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is available under a separate project called [[Atlas]] (See http://atlas.sf.net/) Also, [[MPmap]] is an online map for multiplayer.

=== Why don't you charge money for this? ===

FlightGear can be downloaded for free from many locations including the FlightGear website, but can also be bought on a CD. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

Occasionally you may see FlightGear for sale on auction sites or commercial websites under some other name. This can be done quite legitimately as long as the terms of the license are upheld and might be worth the cost if some value-added features such as additional scenery, aircraft or after-sale support are included. Unfortunately, most cases seen to date appear to be just someone trying to make money selling something that is free and providing no real added value.

=== How can I get started with FlightGear ===

FlightGear [[FlightGear 1.0.0|version 1.0]] can be downloaded at [http://www.flightgear.org/Downloads/ Download Central], but most [[aircraft]] need to be separately downloaded [http://www.flightgear.org/Downloads/aircraft-2.0.0/ Here] and installed manually (see also [[FlightGear 1.0 default aircraft]]). Be aware of system requirements! Also, check out [[New to FlightGear]].

== Compiler ==
{{main article|Building Flightgear}}

=== Pourquoi est-ce que FlightGear ne compile pas ? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, [[SimGear]], plib, zlib. If any of the packages are out of sync with the others, compilation may fail. See also [[Building FlightGear]]

The FlightGear Downloads page (http://www.flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://www.flightgear.org/mail.html for help with this.

=== J'utilise RedHat 7 et... ? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configurer ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== Comment configurer mon joystick ? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution and the [[Joystick]]-page on the wiki.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of [[Command Line Parameters|command line options]] with one option per line. The file is not an XML file.

If you would rather use an [[XML]] configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in [[XML]] files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries ([[PLIB]]) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

On the menu select View, Rendering Options , then check the box
that says Show Frame Rate

=== How do I toggle panel settings? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).

=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were too valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

=== Why won't the latest versions of some aircraft work in FlightGear 9.10? ===

The latest FlightGear aircraft need to use some files such as new instrument files only released with [[FlightGear 1.0|version 1.0]]. If you are stuck with an older version of FlightGear you can try downloading an earlier version of the aircraft here : http://web.archive.org/web/20060204211745/www.flightgear.org/Downloads/aircraft/
or here:http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/

== Hacking ==

=== En quel langage informatique est écrit FlightGear ? ===

Mostly C++ with some supporting C code that's primarily contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM ([[JSBSIM]]), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at [[YASim]], an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== Comment importer des avions à partir de Microsoft Flight Simulator ? ===

You can import planes by using the 3D Convert utility which will convert
the MSFS 3d model to a format used by FlightGear. You have to add the
animations and parts.

Also, although you can import the 3D model and textures, the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== Comment importer des scènes BGL de Microsoft Flight Simulator ? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution.
----

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

With Flightgear 0.9.10 there is an easy way for [[Placing 3D Objects with the UFO]]

See also [[FlightGear Scenery Designer]] .

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of [[XML]] syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for in a 3D design program such as [[AC3D]] or [[PPE]], there may be coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good [[OpenGL]] book eventually. However, FlightGear uses a high-level library, [[PLIB]], that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the [[$FG ROOT]]/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== How do I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, [[TerraGear]]. For more details, see http://terragear.org/.

== Flying ==

=== Why won't my engine(s) start? ===

==== Starting engine in single-engine aircraft ====
Aircraft vary in their starting procedure. Some may have an auto-start sequence menu entry or instructions in the aircraft help menu (Press "?").

But in general to start the engine on a piston-engine type aircraft, you need:

# Fuel - You can run out of fuel, of course, but for certain aircraft, FlightGear may load it with no fuel, making it impossible to start the engines. Check this in the menu Equipment/Fuel and Payload.
# Correct mixture (generally "rich", ie red knob all the way in)
# Magnetos on (R, L, or both--generally select "both")
# Throttle (some engines start better with a little gas)
# Hold starter for sufficient time.

You may be able to do all these functions with the standard 2-D panel or your aircraft's built-in panel. However using the standard key bindings is more reliable:

# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set it somewhere besides full rich)
# Press "}}}" (three times) to set magneto to R, L, and finally "Both".
# Open throttle a little.
# Press "s" to run the starter. For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.

==== Starting engine in multi-engine aircraft ====
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine. Flightgear provides a convenient way to do this for all engines at once.

Note that the default 2-D panel is connected to ''only one engine''. So if you try to start the engines using the 2-D panel controls you will most likely start only one engine.

Instead, use the keyboard to start all engines at once:

# Press "~" (select all engines)
# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set the mixture somewhere besides full rich)
# Press "}}}" (three times) to set magnetos to R, L, and finally "Both".
# Open throttle a little (it now controls all engines).
# Press "s" to run the starter (it now runs the starter on all engines). For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.
# Rev the engines a little with your throttle and check your tachometers and/or visually to be sure all engines are running.

Si les moteurs ne démarrent pas, assurez-vous que vous avez du carburant. Certains avions disposent de commutateurs pour contrôler quel réservoir de carburant alimente l'avion, donc vérifiez-les.

Make sure each engine you want to start is connected to a tank that has fuel. Check fuel tanks in the menu Equipment/Fuel and Payload.

=== Où puis-je apprendre le vol et la navigation aux instruments ? ===

http://www.navfltsm.addr.com/ est un très bon site pour apprendre les techniques de navigation.

[http://www.av8n.com/how/ Voir comment ça vole] est un bon livre par, disponible gratuitement en ligne.

Veuillez consulter la section [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder in the very same book...

=== Peut-on voler en réseau ? ===

Oui, les deux versions Windows et *nix permettent le vol en réseau sur des serveurs FlightGear.

Wiki: [http://wiki.flightgear.org/flightgear_wiki/index.php?title=Multiplayer_Howto Multiplayer_Howto]

Une carte affichant en temps réel tous les avions volant en réseau est disponible :

[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map] (voir aussi [[MPmap]])

=== Où puis-je trouver sur Internet des informations sur les aéroports et des cartes aéronautiques ? ===

Aéroports :
* [http://www.airnav.com/airports/ AirNav.com]
* [http://www.sia.aviation-civile.gouv.fr/html/frameset_aip_fr.htm SIA (pour la France)]

Cartes :
* [http://skyvector.com/ SkyVector.com]
* [http://www.sia.aviation-civile.gouv.fr/html/frameset_aip_fr.htm SIA (pour la France)]

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who has done much development in these areas until recently. Now there are third-party bombing scenarios for the [[A-10]] and other aircraft with armament, like the [[North American OV-10A Bronco]], [[General Dynamics F-16]] and [[F-117 Nighthawk]].

[http://flightgear.org/forums/viewtopic.php?f=2&t=5742 A new add-on (9/2009)] adds support for dogfighting (including multiplayer dogfighting) and bombing scenarios.

== FlightGear v0.7.6 ==

=== Pourquoi ai-je une erreur dans le fichier viewer.cxx à propose d'une non-déclaration d'`exit' ? ===

Cette erreur est apparue après la mise à disposition de la version 0.7.6. Pour corriger le problème, ajoutez "#include <stdlib.h>" en haut du fichier viewer.cxx.

== FlightGear v1.0.0 ==

=== Comment puis-je devenir contrôleur aérien (ATC) ? ===

Il n'est pas encore possible de devenir [[ATC]] avec la version stable, il vous faudra donc télécharger la version CVS.

[[en:FAQ]]
[[es:Preguntas frecuentes]]

Fr/Projet Rembrandt

2012-08-30T21:53:11Z

Alexis:

{{WIP}}
== Pourquoi ce nom? ==
[http://en.wikipedia.org/wiki/Rembrandt Rembrandt] était un peintre hollandais du XVIIème siècle, maître incontesté du [http://en.wikipedia.org/wiki/Chiaroscuro "clair-obscur"].

Ce projet a pour but de changer la manière de rendre les éclairages et les [[Shadows|ombres]] qu'utilise [[FlightGear]], et d'essayer d'imiter le style de Rembrandt dans FG.

== De quoi s'agit-il ? ==
L'idée maîtresse du projet est d'implémenter le [http://en.wikipedia.org/wiki/Deferred_shading rendu différé] au sein de FlightGear.
Depuis le début, FlightGear utilise un moteur de rendu en avant qui affiche toutes les propriétés d'un objet en une fois (ombre, éclairage, brouillard, ...), ce qui rend difficile le rendu d'un ombrage plus sophistiqué (voir le [[FlightGear Newsletter December 2011#Shaders|'Uber-shader']]) du fait que tous les paramètres de [http://www.wired.com/magazine/2010/07/st_equation_3danimation/ l'équation lumineuse] doivent être traités en une seule fois.

[[Image:project_rembrandt_1.png|thumb|300px|Vue principale avec le contenu des buffers affichés dans les coins]]
Au contraire, le rendu différé cherche à séparer les opérations en étapes simplifiées et à collecter les résultats intermédiaires dans des buffers cachés, qui peuvent être utilisés par la prochain étape.

;Le premier stade est celui de la Géométrie:
: nous rendons la scène entière dans 4 textures, en utilisant le rendu multi-cibles pour les traiter en un seul passage: un pour le buffer de profondeur, un pour les normales (en bas à gauche de l'image), un pour les couleurs "diffuses" (en bas à gauche) et un pour les couleurs "spéculaires" (en haut à droite).

;Le stade suivant est celui de l'ombre :
: nous rendons encore la scène dans une texture profondeur concernant les éclairages. Il y aura une texture pour chaque lumière diffusant des ombres.

;Ensuite, c'est le stade de l'éclairage, avec plusieurs sous-stades :
:*Sky pass: Le ciel est dessiné d'abord selon la méthode classique.
:*Ambient pass: la mémoire-tampon "diffuse" est modulé avec la couleur ambiante de la scène, et est dessiné comme un quad texturé aligné sur l'écran
:*Sunlight pass: Un second quad aligné à l'écran est dessiné et un shader examine la position pour calculer sa couleur "diffuse" et "specular" en utilisant le "normal" stocké dans le premier stade. La couleur résultante et mélangée avec la passe précédente. Les ombres sont examinées ici par comparaison de la position du pixel avec la position du cache lumière stockée dans la carte shadows

:*stade de la lumière additionnelle: le scene graph sera traversé une autre fois pour afficher les volumes de lumière (cône ou tronc de cône pour les taches de lumière, sphère pour les lumières omni directionnelles), et leur shader ajoutera la lumière composée uniquement par les pixels éclairés.
:*stade brouillard: un nouveau quad aligné sur l'écran est dessiné, et la position du pixel est calculée pour évaluer la quantité de brouillard du pixel. La couleur du brouillard est mélangée avec le résultat du stade précédent.
:*Stade des objets transparents: les objets transparents (et les nuages) sont enfin rendus en utilisant la méthode classique.

:Tous les données de lumière sont accumulées dans une seule mémoire tampon, qui sera utilisée pour le dernier stade en addition au stade Géométrie.

;A la fin, le stade affichage, avec l'option effet post-traitement :
:Les résultats des précédents tampons sont poussés dans le tampon principal pour être affichés, optionnellement modifiés pour montrer Glow, Motion blur, HDR, redout ou blackout, occlusion ambiante de l'espace écran, anti-aliasing, etc...

Dans FG, on termine le pipeline du rendu par l'affichage du [[Menubar|GUI]] et du [[HUD]].

Tous ces phases sont plus précisément décrites dans [http://bat710.univ-lyon1.fr/~jciehl/Public/educ/GAMA/2007/Deferred_Shading_Tutorial_SBGAMES2005.pdf tutorial] c'est la base du code actuel, avec quelque addition ou modifications.

== Avertissements ==
Le rendu différé n'affiche pas la transparence. Pour le moment, les nuages doivent être éclairés et ombrés par eux-mêmes. Les surfaces transparentes sont alpha-testées et non mélangées. Elles doivent être amenées dans leur propre bin sur l'image composite.

La partition profondeur ne marche pas non plus, à cause de la mémoire tampon profondeur, qui doit être gardée pour retenir la position de zone de vue, et, pour le moment, z-fighting est tout à fait visible. La partition profondeur sans rangée de profondeur superposée pourrait être la solution, et devrait être essayée.

Le passage de la lumière peut rendre certains MFD illisibles (ce qui utilisent une couleur émissive) car flous. Ils devront être traités comme transparents.

== Mise en œuvre ==
=== Répertoires ===
Le code est la principale branche du [[FlightGear and Git|répertoire officiel]]. Aucune autre localisation n'existe.

=== Rendu des surfaces transparentes ===
[[Image:project_rembrandt_5.png|thumb|300px|Surfaces transparentes desssinées d'après des objets opaques]]
Les surfaces transparentes sont détectées par les plugins OSG loader qui captent la nuance de rendu TRANSPARENT_BIN
In the culling pass, the cull visitor orders transparent surfaces in transparent bin. In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection. In a cull callback attached to the Lighting camera, after the scenegraph traversal, the transparent bins saved at the previous stage, are added to the render stage of the Lighting camera with a high order num. That way, the transparent surface are drawn on top of the scene lighted from the Gbuffer.

=== Memory consumption ===
For each camera defined in the camera group, there is a separate shadow map, so the video memory usage is :
* G-buffer and Lighting buffer: 20 bytes per pixel. For an HD screen (1920x1080) memory requirement is 40 Mb
* Shadow map: 3 x shadow_map_size x shadow_map_size bytes (if size is 8192, whole map size is 192 Mb
Not counting textures, display list or vertex buffers for models and terrain

3 HD screens require 120 Mb of memory for the buffers (shadow excluded), you're asking 3x8192x8192x3 = 576 Mb (megabytes) of memory for the shadows alone.

If you are seeing error messages during startup or FlightGear doesn't start up properly, it's probably because you don't have enough free video memory. Reduce the size of the shadow map in preferences.xml by locating

<syntaxhighlight lang="xml">
<map-size type="int">8192</map-size>
</syntaxhighlight>

And put 4096 or 2048 instead.
You can also use a startup parameter: --prop:/sim/rendering/shadows/map-size=2048

=== Configurable pipeline ===

The Rembrandt renderer uses an XML file to setup its pipeline for each viewport described in the camera group. This file describes the way the intermediary buffers are setup and how the different rendering stages are sequenced. The general outline of a pipeline file is as follow :

<syntaxhighlight lang="xml">
<?xml version="1.0" encoding="utf-8"?>
<PropertyList>

<buffer>

</buffer>
<buffer>

</buffer>


<stage>

</stage>
<stage>

</stage>
</PropertyList>
</syntaxhighlight>

==== Buffers ====
A buffer is a texture used as a storage area in the GPU. It's size is usually a multiple of the screen size, but fixed size is supported (typical for shadow map). The description of a buffer is described below :

<syntaxhighlight lang="xml">
<buffer>
<name>buffer-name</name>
<internal-format>rgba8</internal-format> 
<source-format>rgba</source-format> 
<source-type>unsigned-byte</source-type> 
<width>screen</width> 
<height>screen</height> 
<scale-factor>1.0</scale-factor>
<wrap-mode>clamp-to-border</wrap-mode> 

<shadow-comparison>true</shadow-comparison>

<condition>

</condition>
</buffer>
</syntaxhighlight>

==== Stages ====
A stage is an unit of rendering to a group of buffer. Most stages are predefined and their type is not free. When a type is not specified, the name is used. Stage types are :
{| class="wikitable"
!align="left"| Stage type
!align="left"| Purpose
|-
|geometry
|The geometry stage initialize most of the buffers and works on the real objects and geometry. Transparent objects are set aside and will be used untouched in the lighting stage. Other opaque geometry is rendered with the standard effects that do the hard work to put sensible data in the buffers.
|-
|shadow
|In this stage, the geometry is rendered in the normal map from the perspective of the sun.
|-
|lighting
|This stage uses the buffers filled by the previous stages to light every pixel of the scene. The result is rendered in another buffer to allow post effects.
|-
|fullscreen
|Stages of this type are used to alter the whole scene or transform data from a particular buffer.
|-
|display
|Final rendering of the scene to the screen or the texture defined in the camera group.
|}

A stage description is outlined below :
<syntaxhighlight lang="xml">
<stage>
<name>stage-name</name>
<type>stage-type</type> 
<order-num>-1</order-num>
<effect>Effects/fullscreen-effect</effect> 
<needs-du-dv>true</needs-du-dv> 
<scale-factor>0.25</scale-factor> 


<condition>

</condition>

<attachment>

</attachment>
<attachment>

</attachment>


<pass>

</pass>
<pass>

</pass>
</stage>
</syntaxhighlight>
Stages render in buffers (except for the display stage). Attachments describe which buffers are affected by each stage.

===== Attachments =====
Attachment describe bindings between buffer and attachment point :
<syntaxhighlight lang="xml">
<attachment>
<component>color0</component> 
<buffer>buffer-name</buffer>

<condition>

</condition>
</attachment>
</syntaxhighlight>

===== Passes =====
Passes are only available in the <tt>lighting</tt> stage. Three kind of stage are allowed :

{| class="wikitable"
!align="left"| Pass type
!align="left"| Purpose
|-
|sky-clouds
|Renders the skydome, sun, moon, planet, stars and clouds
|-
|lights
|Renders additional spot and point lights
|-
|fullscreen
|Fullscreen pass analog to a fullscreen stage except that it renders in the buffers attached to the lighting stage
|}
A pass is defined like below :
<syntaxhighlight lang="xml">
<pass>
<name>pass-name</name>
<type>pass-type</type> 
<order-num>-1</order-num>
<effect>Effects/fullscreen-effect</effect> 


<condition>

</condition>
</pass>
</syntaxhighlight>

A typical lighting stage is a succession of 5 passes :
# <tt>sky-clouds</tt> pass
# <tt>fullscreen</tt> pass for ambient light
# <tt>fullscreen</tt> pass for sun light (and shadows)
# <tt>lights</tt> pass
# <tt>fullscreen</tt> pass for fog

Each effect attached to the fullscreen passes define the way blending is done between the pass and the previous accumulation of render.

== Running Flightgear with Rembrandt ==
[[File:Rembrandt dialog.png|thumb|270px|Rembrandt dialog]]
The Rembrandt renderer is now integrated in the main repository but needs to be enabled to run. There are two ways to enable it (only one is needed!):
* <code>--enable-rembrandt</code> (when using [[FGRun]], you may add this behind the <tt>FG_EXECUTABLE</tt> on the first page).
* <code>--prop:/sim/rendering/rembrandt/enabled=true</code> (with FGRun this can be added via <tt>Advanced > Properties</tt> on the last page).

The <tt>View > Rendering Options > Rembrandt Options</tt> dialog allows you to toggle and adjust the various features that Rembrandt offers.

Rembrandt is quite demanding in GPU resources and may fail to run with the default options. The more frequent symptom is an OSG message in the console :

RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6
Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support multiple color outputs.

Some card also exhibit messages like this :

glLinkProgram "" FAILED
Program "" infolog:
Fragment info
-------------
0(37) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(36) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(35) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable
0(34) : error C6013: Only arrays of texcoords may be indexed in this profile, and only with a loop index variable

There is a number of additional options that can help to avoid these problems :

{| class="wikitable"
|<tt>--prop:/sim/rendering/rembrandt/use-color-for-depth=true</tt>
|Some old NVidia cards, such as 7600GT, don't give enough resolution for depth and that result in "fog curtains" at few meters from the viewer. One trick is to encode depth in another texture and get the proper value afterward. This option enables that.
|-
|<tt>--prop:/sim/rendering/shadows/enabled=false</tt>
|Disable shadows altogether.
|-
|<tt>--prop:/sim/rendering/shadows/num-cascades=1</tt>
|Avoid the "error C6013" message on old cards at the cost of resolution in the cockpit. Set <tt>/sim/rendering/shadows/cascade-far-m[0]</tt> to change the shadow map range. The more the range, the less the resolution (default value is 5 meters)
|-
|<tt>--prop:/sim/rendering/shadows/map-size=<power-of-two></tt>
|Set the shadow map size. Useful values are 1024, 2048, 4096 or 8192. Few cards have the resources to support 16384.
|-
|<tt>--prop:/sim/rendering/shadows/num-cascades</tt>
|Set the shadow map cascade number. Less cascades means less time spent in shadow map generation, but also means lower shadow quality. Integer between 1 and 4.
|-
|<tt>--prop:/sim/rendering/shadows/cascade-far-m[i]</tt>
(1 <= i <= <tt>/sim/rendering/shadows/num-cascades</tt> <= 4)
|Set the shadow map cascade range for each cascade. Default values are 5m, 50m, 500m and 5000m for 4 cascades.
|-
|<tt>--prop:/sim/rendering/rembrandt/no-16bit-buffer=false</tt>
|By default, Rembrandt uses 8 bit buffers for normals (so the property is set to true by default). This may create banding artifacts on specular highlights. If it's unacceptable and the GPU supports it, set to false to have better precision for normals and effects relying on normal direction.
|}

== Guidelines for shader writers ==
=== Predefined uniforms ===
These glsl uniforms don't need to be declared in the effect file.
{| class="wikitable"
!Name
!Type
!Purpose
|-
|<tt>fg_ViewMatrix</tt>
|<tt>mat4</tt>
|In fullscreen pass only, view matrix used to transform the screen position to view direction
|-
|<tt>fg_ViewMatrixInverse</tt>
|<tt>mat4</tt>
|In fullscreen pass only, view matrix inverse used to transform the screen position to view direction
|-
|<tt>fg_ProjectionMatrixInverse</tt>
|<tt>mat4</tt>
|In fullscreen pass only, projection matrix inverse used to transform the screen position to view direction
|-
|<tt>fg_CameraPositionCart</tt>
|<tt>vec3</tt>
|Position of the camera in world space, expressed in cartesian coordinates
|-
|<tt>fg_CameraPositionGeod</tt>
|<tt>vec3</tt>
|Position of the camera in world space, expressed in geodesic coordinates (longitude in radians, latitude in radians, elevation in meters)
|-
|<tt>fg_SunAmbientColor</tt>
|<tt>vec4</tt>
|
|-
|<tt>fg_SunDiffuseColor</tt>
|<tt>vec4</tt>
|
|-
|<tt>fg_SunSpecularColor</tt>
|<tt>vec4</tt>
|
|-
|<tt>fg_SunDirection</tt>
|<tt>vec3</tt>
|
|-
|<tt>fg_FogColor</tt>
|<tt>vec4</tt>
|
|-
|<tt>fg_FogDensity</tt>
|<tt>float</tt>
|
|-
|<tt>fg_ShadowNumber</tt>
|<tt>int</tt>
|
|-
|<tt>fg_ShadowDistances</tt>
|<tt>vec4</tt>
|
|-
|<tt>fg_DepthInColor</tt>
|<tt>bool</tt>
|Tells if the depth is stored in a depth texture or a color texture
|-
|<tt>fg_Planes</tt>
|<tt>vec3</tt>
|Used to convert the value of the depth buffer to a depth that can be used to compute the eye space position of the fragment
|-
|<tt>fg_BufferSize</tt>
|<tt>vec2</tt>
|Dimensions of the buffer, used to convert gl_FragCoord into the range [0..1][0..1]
|-
|<tt>osg_ViewMatrix</tt>
|<tt>mat4</tt>
|Defined by OSG, used only when working on actual geometry
|-
|<tt>osg_ViewMatrixInverse</tt>
|<tt>mat4</tt>
|Defined by OSG, used only when working on actual geometry
|}
They still have to be declared in the fragment or the vertex shader to be used.

=== Utility functions ===

To ease the maintenance of shaders, several utility functions are available for the fragment shader. These functions are put together in two files : <tt>gbuffer-functions.frag</tt> and <tt>gbuffer-encode.frag</tt>.

==== gbuffer-encode.frag ====

;<tt>void encode_gbuffer(vec3 normal, vec3 color, int mId, float specular, float shininess, float emission, float depth)</tt>
:Used to encode all the values of the G-Buffer in material shaders

==== gbuffer-functions.frag ====

;<tt>vec2 normal_encode(vec3 n)</tt>
:Used to compress normals into the G-Buffer in material shaders. Normally called from <tt>encode_gbuffer()</tt>

;<tt>vec3 normal_decode(vec2 enc)</tt>
:Reconstruct normals from the G-Buffer. Used in fullscreen shaders and light shaders

;<tt>vec3 float_to_color(in float f)</tt>
:Encode float values in the range [0..1] in the 24 bits of a color. This function is used by <tt>encode_gbuffer()</tt> if the <tt>/sim/rendering/use-color-for_depth</tt> is true, for old cards that don't provide depth information with enough resolution inside fullscreen or light shaders.

;<tt>float color_to_float(vec3 color)</tt>
:Decode float values in the range [0..1] from the 24 bits of a color. This function is used by <tt>position()</tt> if the <tt>/sim/rendering/use-color-for_depth</tt> is true, for old cards that don't provide depth information with enough resolution inside fullscreen or light shaders.

;<tt>vec3 position( vec3 viewDir, float depth )</tt>
:Reconstruct eye space position from the view direction and the depth read from the depth buffer

;<tt>vec3 position( vec3 viewDir, vec3 depthColor )</tt>
:Reconstruct eye space position from the view direction and the depth encoded in a color read from the depth buffer

;<tt>vec3 position( vec3 viewDir, vec2 coords, sampler2D depth_tex )</tt>
:Reconstruct eye space position from the view direction and the depth buffer (real depth or color, according to the value of <tt>/sim/rendering/use-color-for_depth</tt>) at a given fragment on screen, given by <tt>coords</tt>

==== Usage ====

For material shaders, it is necessary to provide both <tt>gbuffer-functions.frag</tt> and <tt>gbuffer-encode.frag</tt> in the effect file, like this :

<syntaxhighlight lang="xml">
<program>
<vertex-shader>Shaders/ubershader.vert</vertex-shader>
<fragment-shader>Shaders/ubershader-gbuffer.frag</fragment-shader>
<fragment-shader>Shaders/gbuffer-functions.frag</fragment-shader>
<fragment-shader>Shaders/gbuffer-encode.frag</fragment-shader>
</program>
</syntaxhighlight>

For fullscreen passes shaders, only <tt>gbuffer-functions.frag</tt> should be provided, like this :

<syntaxhighlight lang="xml">
<program>
<vertex-shader>Shaders/sunlight.vert</vertex-shader>
<fragment-shader>Shaders/sunlight.frag</fragment-shader>
<fragment-shader>Shaders/gbuffer-functions.frag</fragment-shader>
</program>
</syntaxhighlight>

In the main function of the shader, the functions referenced need to be declared first. With no #include files, the whole function prototype needs to be typed :
<syntaxhighlight lang="glsl">
void encode_gbuffer(vec3 normal, vec3 color, int mId, float specular, float shininess, float emission, float depth);

main() {
vec3 normal;
vec3 color;
int mId;
float specular;
float shininess;
float emission;
float depth;

// Do shader computations

encode_gbuffer(normal, color, mId, specular, shininess, emission, depth);
}
</syntaxhighlight>

=== Geometry Stage ===
The Geometry Stage is there to fill the G-buffer. '''Shading doesn't occur at this stage, so light or fog computation should not be part of the shader'''. The required operation in the Fragment Shader is to fill every individual buffer with sensible value :

{| class="wikitable" style="text-align: center;"
|depth (gl_FragDepth)||GL_DEPTH_COMPONENT32||colspan="4"|Fragment depth
|-
|gl_FragData[0]||GL_RG16||colspan="2"|normal.x * 0.5 + 0.5||colspan="2"|normal.y * 0.5 + 0.5
|-
|gl_FragData[1]||GL_RGBA8||diffuse.r||diffuse.g||diffuse.b||material id * 1/255.0
|-
|gl_FragData[2]||GL_RGBA8||specular.l||specular.s||emission.l||pixel valid if != 0
|}

This is the default layout expected by the sunlight shader. material Id can be used to detect a different layout



=== Additional light pass ===
There would be a single shader for each light type used. The plan is to create lights like animations in the model XML file. The light shader will retrieve scene geometry by combining screen space position converted in view space ray by the inverse of the projection matrix (an helper function should be provided), and the fragment depth at that screen position read from the depth buffer. With the help of the fragment normal, the diffuse and specular color and the properties of the light the shader implements, it will be possible to add to the lighting buffer the contribution of the light rendered.

=== Fog Pass ===
Using the fragment depth, it will be possible to compute any fog distribution. For the moment, the simple fog equation is implemented.

=== Bloom Pass ===
This is a two-pass effect that blurs the lighting buffer in a small texture. This texture is then added to the lighting buffer at the display stage.

=== Required Effects ===
Several pass are implemented using the effect system. For this purpose, some effects are referenced in the core code using reserved names. these effects are:
{| class="wikitable" cellpadding="3"
!Name
!Kind
!Purpose
|-
|<tt>Effects/ssao</tt>
|Works on a full screen quad
|Compute ambient occlusion from the normal buffer and the depth buffer
|-
|<tt>Effects/ambient</tt>
|Works on a full screen quad
|Copies the diffuse color buffer multiplied by the ambient light to the lighting buffer. Ambient Occlusion can also affect ambient light.
|-
|<tt>Effects/light-spot</tt>
|Works on real geometry of the light volume
|Computes the light contribution of a spot light defined in a <tt>light</tt> animation having a <tt>light-type</tt> of '''<tt>spot</tt>'''
|-
|<tt>Effects/fog</tt>
|Works on a full screen quad
|Computes the fog from the G-buffer and the lighting parameters
|-
|<tt>Effects/display</tt>
|Works on a full screen quad
|Renders the composite final image from the G-buffer and the lighting buffer
|}

== Guidelines for modelers ==

=== Porting aircraft ===
* Rembrandt computes shadows => no more fake shadows in the model
* Rembrandt computes ambient occlusion => no ambient occlusion baked into textures
* Rembrandt has light => static lightmap are not needed, emissive color to see models at night is not needed and would interfere
* Rembrandt has glow => incorrectly used emissive colors may blur displays and make some text unreadable. Light size may have to be adjusted
* Rembrandt has strict needs with shaders => shaders need to be adjusted to comply with the new framework otherwise the view will be plain wrong
* Rembrandt can't do transparent surfaces => transparent surface need to be properly registered to render them with the classical path

=== Registering all translucent surfaces ===

Every model is, by default, rendered using the <tt>Effects/model-default</tt> effect. This effect initialize the G-buffer, ignoring transparent surfaces, by doing alpha testing and rendering all the geometry in the default bin. It is not possible to redirect rendering to transparent bins when the associated texture has alpha channel because most models use a single texture atlas and even opaque parts are rendered with texture with alpha channel.

If a model needs to have transparent or translucent surfaces, these surface objects need to be assigned a different effect that sets explicitly the render bin to "DepthSortedBin", or sets the rendering hint to "transparent". This tells the renderer to render this object using forward rendering, so lighting and fog need to be enabled, and if a shader program is used, they should be computed in the classical way. The <tt>Effects/model-transparent</tt> can be used to register simple transparent/translucent surfaces. You assign this effect to an object (or multiple objects) like:
<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>TheObject</object-name>
</effect>

If opaque surface need to have special effect, for example to apply bump mapping, this effect should use the "RenderBin" bin, or the rendering hint set to "opaque", and the G-buffer needs to be initialized correctly in the Geometry stage.

=== Adding lights to a model ===

There are two things to consider: the appearance of the light source and the illuminated area. For the appearance of the light source (what you see when you look at the bulb), you need a model with an emissive material that will produce the glow effect and that is visible at night.

For the effect of the source on its environment (the lit area), we must have in the 3D model (the .ac file) a volume that includes the effect (Light Volume). It can be a large cone for spotlights or a sphere for point light. It's important that the light volume is closed, convex and it's normals are oriented outward.

The light volume must be part of the geometry of the model and be referenced in the animation file. No need to add a color or an effect to this volume. Light calculation is only done on the fragments covered by the light volume, but has no influence on the color or the attenuation of the light.

All available animations are possible on the light volume, except '''material''' and '''texture'''. It is not possible to change color of lights for the moment, except switching to another animation. Axis and position are in object space and are transformed by the subsequent animations.

==== Spotlights ====
{|cellpadding=10|
|valign=top|
<syntaxhighlight lang="xml">
<animation>
<type>light</type>
<light-type>spot</light-type>
<name>LightSrcRight</name>
<object-name>LightRight</object-name>
<nopreview/>
<position>
<x>0.169</x>
<y>0.570</y>
<z>0.713</z>
</position>
<direction>
<x>-0.9988</x>
<y>0.0349</y>
<z>-0.0349</z>
</direction>
<ambient>
<r>0.03</r>
<g>0.03</g>
0.03
<a>1.0</a>
</ambient>
<diffuse>
<r>0.7</r>
<g>0.7</g>
0.6
<a>1.0</a>
</diffuse>
<specular>
<r>0.7</r>
<g>0.7</g>
0.7
<a>1.0</a>
</specular>
<dim-factor>
<property>dimming/property</property>

<expression />
<interpolation />
<factor>1</factor>
<offset>0</offset>
<min>0</min>
<max>1</max>

</dim-factor>
<attenuation>
<c>1.0</c>
<l>0.002</l>
<q>0.00005</q>
</attenuation>
<exponent>30.0</exponent>
<cutoff>39</cutoff>
<near-m>3.5</near-m>
<far-m>39</far-m>
</animation>
</syntaxhighlight>
|valign=top|
{| class="wikitable" cellpadding="3"
!Name
!Purpose
|-
|<tt>type</tt>
|Install the <tt>'''light'''</tt> animation
|-
|<tt>light-type</tt>
|This is a <tt>'''spot'''</tt> light
|-
|<tt>name</tt>
|Name given to this animation
|-
|<tt>object-name</tt>
|Name of the light volume in the 3d model (typically a cone with an apex at <tt>position</tt>, along <tt>direction</tt> axis if <tt>cutoff</tt> is lesser than 90 degrees, or a sphere centered at <tt>position</tt> if <tt>cutoff</tt> is greater than 90 degrees )
|-
|<tt>nopreview</tt>
|Hide light volume in fgrun 3d preview
|-
|<tt>position</tt>
|In object space, position of the light
|-
|<tt>direction</tt>
|In object space, direction to the center of the spot
|-
|<tt>ambient</tt>
|Ambient color of the light
|-
|<tt>diffuse</tt>
|Diffuse color of the light
|-
|<tt>specular</tt>
|Specular color of the light
|-
|<tt>dim-factor</tt>
|Group of parameters to control a factor that is applied to ambient, diffuse and specular at the same time
|-
|<tt>attenuation</tt>
|Three element vector. <c> element is the constant factor, <l> element is the linear factor and <q> element is the quadratic factor. 
Attenuation of color at distance d is [[File:Spotlight_attenuation.png]]
|-
|<tt>exponent</tt>
|Attenuation is multiplied by <tt>pow( dot( lightDir, <direction> ), <exponent> )</tt>, lightDir being vector from light position to point, in camera space.
|-
|<tt>cutoff</tt>
|Point is lit by this source if <tt>dot( lightDir, <direction> ) > <cutoff></tt> , lightDir being vector from light position to point, in camera space.
|-
|<tt>near-m</tt>
|Minimum distance of influence, from position, in meters
|-
|<tt>far-m</tt>
|Maximum distance of influence, from position, in meters
|}
|}

==== Point lights ====
{|cellpadding=10|
|valign=top|
<syntaxhighlight lang="xml">
<animation>
<type>light</type>
<light-type>point</light-type>
<name>LightSrcRight</name>
<object-name>LightRight</object-name>
<nopreview/>
<position>
<x>0.169</x>
<y>0.570</y>
<z>0.713</z>
</position>
<ambient>
<r>0.03</r>
<g>0.03</g>
0.03
<a>1.0</a>
</ambient>
<diffuse>
<r>0.7</r>
<g>0.7</g>
0.6
<a>1.0</a>
</diffuse>
<specular>
<r>0.7</r>
<g>0.7</g>
0.7
<a>1.0</a>
</specular>
<dim-factor>
<property>dimming/property</property>

<expression />
<interpolation />
<factor>1</factor>
<offset>0</offset>
<min>0</min>
<max>1</max>

</dim-factor>
<attenuation>
<c>1.0</c>
<l>0.002</l>
<q>0.00005</q>
</attenuation>
<near-m>3.5</near-m>
<far-m>39</far-m>
</animation>
</syntaxhighlight>
|valign=top|
{| class="wikitable" cellpadding="3"
!Name
!Purpose
|-
|<tt>type</tt>
|Install the <tt>'''light'''</tt> animation
|-
|<tt>light-type</tt>
|This is a <tt>'''point'''</tt> light
|-
|<tt>name</tt>
|Name given to this animation
|-
|<tt>object-name</tt>
|Name of the light volume in the 3d model (typically a sphere centered on <tt>position</tt>, with a radius of <tt>far-m</tt>)
|-
|<tt>nopreview</tt>
|Hide light volume in fgrun 3d preview
|-
|<tt>position</tt>
|In object space, position of the light
|-
|<tt>ambient</tt>
|Ambient color of the light
|-
|<tt>diffuse</tt>
|Diffuse color of the light
|-
|<tt>specular</tt>
|Specular color of the light
|-
|<tt>dim-factor</tt>
|Group of parameters to control a factor that is applied to ambient, diffuse and specular at the same time
|-
|<tt>attenuation</tt>
|Three element vector. <c> element is the constant factor, <l> element is the linear factor and <q> element is the quadratic factor. 
Attenuation of color at distance d is [[File:Spotlight_attenuation.png]]
|-
|<tt>near-m</tt>
|Minimum distance of influence, from position, in meters
|-
|<tt>far-m</tt>
|Maximum distance of influence, from position, in meters
|}
|}

== TODO List ==

=== Completed tasks ===
*Fix shadow rendering when using multi threading in OSG
*Implement Cascaded Shadow Map (need to be optimized - frustum calculation and night)
*Honor 'noshadow' animation (done)
*See what happens with glow in fog : unknown landclass creates white patches in the emission buffer - scenery generation problem
*Test multi-screen (mostly done)
*Restore splashscreen
*Draw transparent objects with forward rendering (may need to capture the transparent bin from the geometry stage and move it in the display stage) (OK - needs model contribution)
*Add spotlights as animations (nearly finished)
*find a solution for ambient and emissive color of material (may need an additional buffer)
*Provide a shader for transparent objects that could render to the emissive buffer too (using MRT) not doable. Light pass can't use MRT
*Use stencil buffer to limit light range(no - done in light shader)
**needed for cockpit light to implement fake shadows and avoid lighting the runway from the cabin through the airframe
*Use effect system instead of hard-coded shaders
*Add new animation to link a light source to a model (need to provide point light animation duplicating spot light) (done)
*Tidy up the architecture (done)
*Global strength of glow or ambient occlusion via slider in rendering dialog
*Fix dim-factor in multiplayer mode (done)
*Design and implement a configurable pipeline (done)
*Document rendering pipeline configuration file format (done)

=== Near term tasks ===
*Convert existing shaders to deferred rendering
*Avoid to redraw opaque objects in the light pass. Involve OSG node mask not properly initialized.
*take care of particles and precipitation
*Fix fog on clouds
*Fix shadow matrices in multi-screen
*Implement lightfield shader

=== Long term ideas (unsorted) ===
*implement strength of glow (in the emissive buffer alpha channel)
**provide levels 0 to 5 - we are currently at level 5
**level 0 should be ok for MFDs that are currenly unreadable because blurred
*Modify shadows to allow multiple casters (limited list)
**Implement a priority list of light sources, based on priority and distance from the viewer
*Restore depth partitioning using depth ranges
*Restore stereo and other options currently available in CameraGroup
*Implement quality vs performance user control

== Gallery ==
{{#ev:youtube|PXHhtQb5yzc}} {{#ev:youtube|peEzEapavkg}} {{#ev:youtube|RIetPh8iJXk}} {{#ev:youtube|oaNFrxgQY1c}} {{#ev:youtube|8xGzy12hlis}} {{#ev:youtube|ZyuHBlm3xXU}} {{#ev:youtube|RgH9GZRukOI}} {{#ev:youtube|UQvbHnBkpaM}} {{#ev:youtube|v02phoOqWHE}}{{#ev:youtube|dlSo4sBa7Nk}}

== Appendix ==
{{Appendix|all|
* {{cite web |url=http://http.download.nvidia.com/developer/presentations/2004/6800_Leagues/6800_Leagues_Deferred_Shading.pdf |title=Deferred Shading |author=Shawn Hargreaves and Mark Harris }}
* {{cite web |url=http://bat710.univ-lyon1.fr/~jciehl/Public/educ/GAMA/2007/Deferred_Shading_Tutorial_SBGAMES2005.pdf |title=Deferred Shading Tutorial |author=Fabio Policarpo and Francisco Fonseca }}
* {{cite web |url=http://www.guerrilla-games.com/publications/dr_kz2_rsx_dev07.pdf |title=Deferred Rendering in Killzone 2 |author=Michal Valient |month=July |year=2007 }}
* {{cite web |url=http://www.anandtech.com/show/5011/nvidiaea-posts-battlefield-3-graphics-tech-talk |title=Battlefield 3 Graphics Tech Talk |author=Johan Andersson |month=October |year=2011 }}
* {{cite web |url=http://www.disney.co.uk/cms_res/blackrockstudio/pdf/Rendering_Techniques_in_SplitSecond.pdf |title=Rendering Techniques in Split/Second |author=Jeremy Moore and David Jefferies |year=2009 }}
* {{cite web |url=http://www.crytek.com/sites/default/files/A_bit_more_deferred_-_CryEngine3.ppt |title="A bit more Deferred" - CryEngine 3 (PPT) |author=Martin Mittring }}
* {{cite web |url=http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter09.html |title=Deferred Shading in S.T.A.L.K.E.R. |author=Oles Shishkovtsov }}
* {{cite web |url=http://http.developer.nvidia.com/GPUGems3/gpugems3_ch19.html |title=Deferred Shading in Tabula Rasa |author=Rusty Koonce }}
* {{cite web |url=http://aras-p.info/texts/CompactNormalStorage.html |title=Compact Normal Storage for small g-buffers |author=Aras Pranckevičius |date=4 August 2009 |accessdate=12 April 2012 }}
* {{cite web |url=http://the-witness.net/news/2010/03/graphics-tech-shadow-maps-part-1/ |title=Graphics Tech: Shadow Maps (part 1) |author=Jonathan Blow |date=3 March 2010 |accessdate=13 April 2012 }}
* {{cite web |url=http://directtovideo.wordpress.com/2009/11/13/deferred-rendering-in-frameranger/ |title=deferred rendering in frameranger. |author=Matt Swoboda |date=13 November 2009 |accessdate=8 July 2012 }}
}}

[[Category:Shader development]]
[[Category:Core development projects]]
[[en:Project Rembrandt]]

Fr/Projet Rembrandt

2012-08-30T21:48:11Z

Alexis:

Beechcraft Starship

2012-08-30T20:56:38Z

Alexis:

{{aero-stub}}
{{infobox Aircraft
|image = startship1.jpg
|name = Beechcraft Starship
|type = twin turboprop business transport
|fdm = Yasim
|authors = BARANGER Emmanuel (3D)
|fgname = starship
|status-fdm = 1
|status-systems = 1
|status-cockpit = 2
|status-model = 2
}}
The '''Beechcraft Starship''' is a futuristic-looking United States turboprop-powered six- to eight-passenger seat business [[aircraft]]. The design was originated by Beechcraft in January 1980 as Preliminary Design 330 (PD 330). Burt Rutan was subsequently retained to refine PD330 and one of the significant changes he instituted was the addition of variable geometry to the canard (he holds a patent for this). Rutan's California-based design and fabrication company Scaled Composites was then contracted to build scale-model prototypes to aid in development.

== Aircraft Help ==
{|class="prettytable"
!Key
!Function
|-
|d
|Open/Close Door
|}

== External links ==
* [http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar]
* [http://en.wikipedia.org/wiki/Beechcraft_Starship Wikipedia]

{{Beechcraft}}

[[Category:Canard aircraft]]
[[Category:Civil utility aircraft]]
[[Category:Pusher aircraft]]
[[Category:Twin-engined aircraft]]

Mudry Cap10b

2012-08-30T20:30:43Z

Alexis:

{{infobox Aircraft
|image = Cap10b.jpg
|name = Mudry CAP 10b
|type = training aerobatic aircraft
|authors = PAF team - http://equipe-flightgear.forumactif.com
|fdm = JSBsim
|status = Development
|fgname = cap10b
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|download = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330
}}

The '''Mudry CAP 10b''' is a two-seat training aerobatic aircraft.

== Description ==

=== Speed===
Vne : 340km/h

Vno : 300km/h

Vc : 300km/h

Va : 200km/h

Vfe : 160km/h

Vso : 89km/h

== Aircraft help ==

{| width="100%"
| width="30%" | Key
| width="70%" | Fonction
|-
|S
|Start/stop smoke
|}
== External links ==

[[fr:Mudry Cap10b]]

Fr/Mudry Cap10b

2012-08-30T20:30:24Z

Alexis:

{{infobox Aircraft
|image = Cap10b.jpg
|name = Mudry CAP 10b
|type = Avion d'entrainement à la voltige
|authors = PAF team - http://equipe-flightgear.forumactif.com
|fdm = JSBsim
|status = Développement
|fgname = cap10b
|status-fdm = 3
|status-systems = 3
|status-cockpit = 3
|status-model = 3
|download = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330
}}

Le '''Mudry CAP 10b''' est un avion biplace d'entrainement à la voltige.

== Description ==

=== Vitesses ===
Vne : 340km/h

Vno : 300km/h

Vc : 300km/h

Va : 200km/h

Vfe : 160km/h

Vso : 89km/h

== Aide de l'avion ==

{| width="100%"
| width="30%" | Raccourcis
| width="70%" | Fonction
|-
|S
|Fumée
|}
== Liens externes ==

[[en:Mudry Cap10b]]

Mudry Cap10b

2012-08-30T20:23:37Z

Alexis: Created page with "{{infobox Aircraft |image = Cap10b.jpg |name = Mudry CAP 10b |type = training aerobatic aircraft |authors = PAF team - http://equipe-flightgear.forumactif.com |fdm = ..."

{{infobox Aircraft
|image = Cap10b.jpg
|name = Mudry CAP 10b
|type = training aerobatic aircraft
|authors = PAF team - http://equipe-flightgear.forumactif.com
|fdm = JSBsim
|status = Development
|fgname = cap10b
|download = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330
}}

The '''Mudry CAP 10b''' is a two-seat training aerobatic aircraft.

== Description ==

=== Speed===
Vne : 340km/h

Vno : 300km/h

Vc : 300km/h

Va : 200km/h

Vfe : 160km/h

Vso : 89km/h

== Aircraft help ==

{| width="100%"
| width="30%" | Key
| width="70%" | Fonction
|-
|S
|Start/stop smoke
|}
== External links ==

[[fr:Mudry Cap10b]]

Fr/Mudry Cap10b

2012-08-30T20:21:44Z

Alexis:

{{infobox Aircraft
|image = Cap10b.jpg
|name = Mudry CAP 10b
|type = Avion d'entrainement à la voltige
|authors = PAF team - http://equipe-flightgear.forumactif.com
|fdm = JSBsim
|status = Développement
|fgname = cap10b
|download = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330
}}

Le '''Mudry CAP 10b''' est un avion biplace d'entrainement à la voltige.

== Description ==

=== Vitesses ===
Vne : 340km/h

Vno : 300km/h

Vc : 300km/h

Va : 200km/h

Vfe : 160km/h

Vso : 89km/h

== Aide de l'avion ==

{| width="100%"
| width="30%" | Raccourcis
| width="70%" | Fonction
|-
|S
|Fumée
|}
== Liens externes ==

[[en:Mudry Cap10b]]

Fr/Mudry Cap10b

2012-08-30T20:21:29Z

Alexis: Created page with "{{infobox Aircraft |image = Cap10b.jpg |name = Mudry CAP 10b |type = Avion d'entrainement à la voltige |authors = PAF team - http://equipe-flightgear.forumactif.com |f..."

{{infobox Aircraft
|image = Cap10b.jpg
|name = Mudry CAP 10b
|type = Avion d'entrainement à la voltige
|authors = PAF team - http://equipe-flightgear.forumactif.com
|fdm = JSBsim
|status = Développement
|fgname = cap10b
|download = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330
}}

Le'''Mudry CAP 10b''' est un avion biplace d'entrainement à la voltige.

== Description ==

=== Vitesses ===
Vne : 340km/h

Vno : 300km/h

Vc : 300km/h

Va : 200km/h

Vfe : 160km/h

Vso : 89km/h

== Aide de l'avion ==

{| width="100%"
| width="30%" | Raccourcis
| width="70%" | Fonction
|-
|S
|Fumée
|}
== Liens externes ==

[[en:Mudry Cap10b]]

File:Cap10b.jpg

2012-08-30T19:48:52Z

Alexis:

=={{int:filedesc}}==
{{Information
|description={{fr|1=Mudry Cap10b}}
|date=2012-08-30
|source=http://equipe-flightgear.forumactif.com/t736p240-le-cap10b
|author=Christian THIRIOT
|permission=
|other_versions=
|other_fields=
}}

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

Dassault Mirage F1 checklist

2012-08-30T12:50:04Z

Alexis: /* Taxiing */

For [[Dassault Mirage F.1]]

(Extract from Flight mirage F1 Manual)

=== Starting procedure===
* Open the '''LP''' main cock
* Switch on the '''RH''' and '''LH LP''' pumps
* Ignition/Ventilation selector : '''SWITCH TO OTHER PLUG''' (to permit alternate use of the plugs upon starting)
* Lift the starter button guard (check that the starting '''LP''' pump switch is effectively switched on
* Wait for the '''LP''' light to go out and immediately depress the starter button (for second approx : never exceed 2 seconds) and simultaneously start the stopwatch.
* Between '''300''' and '''600''' rpm - '''THROTTLE TO IDLE''' (engine cold, bring the throttle slightly beyound idle).
* The '''BOV''' light is on (at night, if the illumination of the light is not visible, momentarily increase the intensity of the failure warning panel.
In all cases, if the light does not come on, interrupt starting.
* Watch the RPM inicator and JPT indicator and check that the engine accelerates normally
* The '''OIL''' light should remain on when N < 2 000 rpm ; otherwise, interrupt starting
* During acceleration, the '''LP''' light may come on until the alternators cut in
*If starting is normal, the engine should accelerate positively and attein a speed >= 2000 rpm after approximately 15 seconds. During the same period, if the JPT increases rapidly through 700°C : close the throttle.
Exceptionally, JPT ~ 850°C is permissible for a period < 3 seconds
* The '''HYD.1''', '''HYD.2''' and '''OIL''' lights go out
*The '''BOV''' light goes out between 750 and 2200rpm
*The '''ALT.1''' and '''ALT.2''' lights go out between 2600 and 2800 rpm depending the load
* Idle rpm stabilizes close to 2900.(If the engine is cold, the speed is about 2600 to 3200 rpm : this phenomenon should disappear as soon as the engine is warmed up)
* Set the inverter control to '''RESET''' the '''EMG''' light goes out.

'''NOTE''' : Do not leave the '''LP''' main cock open for more than 15 seconds before the '''LP''' for starting pumps.

'''REMARK :'''
In case of operation of the slotted slat comparator (configuration indicator red light and '''S/F''' light on)
*Set the high-lift device selector switch to '''EMG RETR'''

=== AFTER START CHECKS ===
From right to left

* Cockpit an equipment air conditioning control box
Master valve control switch ''ON''
temperature control rheostat ''AUTO'' 12o'clock
* Heading control box
heading and vertical reference system control switch ''ON''
heading selector '''NAV 1''' or '''HDG 1'''
emergency gyromagnetic compass selector ''ON''
* VOR/ILS ''ON''
* TACAN ''REC''
* Standby horizon switch ''ON''
* Electric pump switch ''ON''
* Warning horn switch ''ON''
* Probe heat switch ''ON''
* Radar detector switch ''ON''
* Radar control box ''S''
* Doppler control panel
vertical resetting ''made''
display selector ''LAT'' or ''B/GS''
Land/sea calibration selector switch ''as required''
* Radar detector ''tested ... tone adjusted''
* Navigation indicator ''NA''
* Omnibearing selector box ''VOR/ILS or TAC''
* Sight ''ON''
* Shock cone pushbutton ''depressed''
* Standby horizon ''uncaged''
* Moving map dispay indicator ''NAV initial alignment made''
* Servos ''reset if necessary by action button''
* V/UHF (green) ''ON ... frequency selected''
* VHF (red) ''ON ... frequency selected''
*Heading transfer with transfer gyro ''made (if applicable)''
*Initial alignment of navigation start coordinates ''made''

=== Pre-taxiing checks ===
* Trims ''tested then set to neutral''
* Airbrakes : pilot's signal, jaw type hand movements ''airbrakes extended and locked''
* Flaps : after ground crew signal
** Slat/Flap lever ''full aft'
** Hight-lift device selector switch '' NORMAL check
*** slats full down
*** flaps full down
*** CBT.F light out
** Combat flap lever '''retracted

Ground crew moves aft and checks :
* Flaps
* Airbrakes
* Yaw damper '' ground crew exerts a few lateral thrusts on aft fuselage section and checks that control surface reacts by short oscillations''
* Fuel
** Emergency fuel transfer switch ''guarded''
** Refueling probe operating check :
*** Probe control switch ''up''
*** Prob in motion light ''on, then out''
*** Probe control switch ''dow, guarded''
*** Probe in motion light ''on, then out''
** Transfer/Refueling selector switch ''TRANS''
** Crossfeed switch ''OFF''
** Fuel transfer sequence selector switch ''as required
** Fuel gages '' fuselage and feeder tank quantities checked''
** Fuel remaining indicator ''operates normally''
** '''LP''', '''L/H LP''' '''R/H LP''' '''500 L''' lights ''out''
* Sight ''set''
* Hydraulic pressures ''normal''
* Failure warning panel ''lights out''
* Oxygen ''quantity pointer in green range''
* Seat/Aircraft coupling ''checked''
* Blinker ''operation checked''
* Harness '' correctly adjusted and locked''

Grand crew returns to the front; the pilot
* retracts the airbrakes
* test the nose wheel steering system through the rudder pedals and checks the control stick for full travel

=== Taxiing ===
* Slaved altimeter ''set''
* dps control ''on, flag out of view''
* Standby altimeter ''set''

==== Starting aircraft rolling ====
The canopy can be partially opened for taxiing, but it must be placed in this position with the aircraft stationary.
* Release the parking brake ''check handle in full forward position'' ('''BRAKES''')'' light out''
* Advance the throttle (600rpm)
* Start rolling, then apply the brakes :the ground crew checks the pitch damper
The aircraft is stecred with the rudder pedals WITHOUT THE ASSISTANCE OF THE BRAKES.

'''NOTE 1''' : It is recommended to avoid engine power settings between 5500 and 6000 rpm during taxiing (alternator gear change)

'''NOTE 2''' : Do not exceed a speed of 20 kt when taxiing in a staight line (heavy in particular). Turn slowly and obey these instructions even when the weather is hot and taxiing distances are long.

==== During taxiing ====
* IFF ''self-test with or without ground receiver (TOWER/RADAR)
* Sight ''adjusted and tested''
* Standby horizon ''miniature airplane adjusted
* Navigation indicator ''tested''

==== Before line-up ====
* Lower the helmet visor
* IFF ''normal''
* TACAN '''T/R''' ''tested''
* Radar'''TR''' ''tested''
* Radio-altimeter '''ON''' ''tested, altitude selected''
* Jettison buttons ''unguarded (if carrying stores)''
* Emergency regulation light ''out''
* Stopped on a reference axis (or after line-up) ''transfer of selected heading if transfer gyro has not been used

==== After line-up ====
* Headings ''checked
* Canoy '' closed and locked'' '''CAB.P''' ''light out''
* Harness ''adjust and locked
* Slats and flaps ''as required''
* Failure warning panel lights ''out
* Fuel transfer indicator lights ''out (check made with some power)
* Probe heat switch ''ON'' PITOT goes out
* Flight controls ''free''
* Takeoff power ''set''
* Flight controls ''free''

== Related Content ==
* [[Dassault Mirage F.1]]

Dassault Mirage F1 checklist

2012-08-30T11:14:57Z

Alexis: Created page with "For Dassault Mirage F.1 (Extract from Flight mirage F1 Manual) === Starting procedure=== * Open the '''LP''' main cock * Switch on the '''RH''' and '''LH LP''' pumps * I..."