FlightGear wiki - User contributions [en]

Follow me e-tron

2025-01-02T04:55:31Z

Sidiliang: Revised introduction

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

The vehicle implements a detailed electric powertrain and electrical system in Nasal, along with key features including an advanced steering helper and systems such as 'AutoCrash' and 'AutoSpeed' for driving assistance. Additional functionalities encompass an Auto Hold feature, parking radar, working airbags, and an experimental Advanced Emergency Braking (AEB) system.

The model offers multiple interior configurations with functional controls and different instrument panel options, including a Canvas-based glass display. Customization options extend to Chinese-style license plates and various livery choices. A stretched limousine variant is also available.

The vehicle is fully equipped for multiplayer with multiplayer passengers supported. It also has a dynamic scenery object placement system, allowing vehicles-related objects such as highway tollgates and recharging stations to be placed on the scenery for more immersive driving.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV inside ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png|Three Followme EVs lining up
File:Followme EV in a charging station.png|Followme EVs in a charging station, showcasing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png|Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png|Followme EV inside a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png|Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png|Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png|Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Follow me e-tron

2025-01-02T04:35:15Z

Sidiliang: Tweaks to wordings

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

At its core is a realistic electric engine, meticulously programmed in Nasal, complemented by a detailed electrical system, also written in Nasal. For driving assistance, it includes an advanced steering helper and unique systems like 'AutoCrash' and 'AutoSpeed'. The vehicle's functionality is further enhanced with an Auto Hold feature, parking radar, and working airbags. It also experiments with an Advanced Emergency Braking (AEB) system.

The interior of the Follow me EV is highly customizable, offering several fully remodeled interiors with operational switches. Users can choose from various instrument styles, including a Canvas glass display instrument tailored for specific interior designs.

For personalization, the Follow me EV offers selectable license plates in a Chinese style and a variety of liveries. It is fully equipped for multiplayer interaction, supporting multiplayer passengers, dynamic scenery object placement, and management.

A standout feature is its limo variant, adding a touch of luxury and uniqueness.

These features collectively make the Follow me EV a pioneering model in the FlightGear universe, combining realism, customization, and innovation.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV inside ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png|Three Followme EVs lining up
File:Followme EV in a charging station.png|Followme EVs in a charging station, showcasing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png|Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png|Followme EV inside a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png|Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png|Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png|Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Changelog 2024.1

2024-11-16T05:39:11Z

Sidiliang: i18n for Chinese

{{Draft}}

{{WIP}}

== General ==

* Many crashes and memory leaks fixed.
* Preview of World Scenery 3.0. This is a new scenery system that uses multiple levels of detail to provide higher frame-rates and lower memory occupancy at bigger visibility ranges.
* Many improvements to the FlightGear launcher.

== Graphics ==

* Compositor multi-pass rendering.
* Real-time shadows and lights.
* Improved photoscenery support.
* Improved scenery object support, including defining and rendering large numbers of scenery lights in STG files, and support for generic instantiation of objects (e.g. windmills, pylons).
* Add the Milky Way to the night sky.
* Optional ShaderVG, a shader based version if ShivaVG.

== Interfaces ==

* Flight data can now be saved to file as a continuous uncompressed file stream.
* Compressed video encoding is now supported.
* IO channels can be re-initialized and are exposed on the property tree under /io/channels/.

== FDM ==

* Synchronization with JSBSim v1.1.11.
* Better support for frozen lakes.

== Environment ==

* Update for world magnetic model data set from WMM2015 to WMM2020.
* Replace season selection (--season) with improved climate modeling, including seasonal variation, ocean temperatures, dew point, snow line and other environmental factors.

== Translations ==

* Localization support for add-ons as well as aircraft
* Improve translations for the following languages:
** French
** Spanish
** Polish
** Italian
** German
** Dutch
** Slovak
** Georgian
** Russian
** Chinese

== Hardware Device Support ==
Support for the following hardware devices has been added or updated:

* Honeycomb Alpha Flight Controls
* Honeycomb Bravo Throttle Quadrant
* Saitek Pro Flight Rudder Pedals
* Saitek Pro Flight Switch Panel
* CH Combatstick
* Logitech G25 Racing Wheel
* Thrustmaster T-Flight Rudder Pedals

== AI Traffic & Liveries ==

* Many improvements to make AI aircraft behavior more realistic.

Traffic and/or liveries have been added for the following airlines:

* Delta Airlines
* United Airlines
* AeroUnion Mexico
* AeroMexico
* AeroMexicoConnect
* Amerijet Cargo
* Airest Cargo
* Air Caraibes
* DHL
* Amazon Air
* EuroWings
* Polar Air Cargo
* Northern Air Cargo
* Eastern Airways UK
* ANA Wings
* Ibex Japan
* Solaseed Japan
* AirHongKong
* AirHongKong Cargo
* AirChina
* UNI Air Japan
* Southern Air Cargo
* SATA Air Acores
* Azores Airlines
* European Air Transport Leipzig
* SykyLeaseCargo
* Blue Air
* Cyprus Airways
* DirectFlight Airtask Shetland
*
* Corsair
* LOT Polish Airlines
* Braethens
* Transavia NL
* Transavia France
* Tunisair Group

Traffic and/or liveries have been removed for the following airlines:

* GermanWings (defunct)

== Canvas ==
fc16b827a Fix OSM imagery in the canvas map (fixes #2912)**

<nowiki>**</nowiki>f0a740333 Remove OpenAIP map support from Canvas Map (see #2913)**

== Nasal ==

== Phi ==
<nowiki>**</nowiki>7b36d498f Fix a variety of broken or unsupported maps in Phi

725ce7d3f Phi: Add map option to disable repositioning own aircraft by dragging

fc3b7b8b5 Phi: Highlight "follow aircraft" button if enabled

5626dc51f Phi: Remove unused css rule

88788dc6a Fix attributes for multiplayer and AI airplanes in Phi (fix #2274)

660fda829 Phi: automatically use latest AIRAC cycle for OpenFlightMaps

57483a999 Phi: fix midnight time offset

== Aircraft Carriers ==
The following [[Aircraft carrier|Aircraft carriers]] have been added:

* Admiral Kuznetsov
* Liaoning

== Misc. ==
f9ad4124f Route manager add total dist, dist remaining, ete, flight time

* Highlighting tool enabled by setting /sim/highlighting/enabled=true which highlights any animated objects under the pointed along with any other objects animated by the same or related properties.

== Legacy ==

* Remove [[Rembrandt]] command-line options

Zh/2020.3

2024-10-23T03:24:21Z

Sidiliang: Point next changelog to 2024.1, in accordance to the changes in English version

{{changelogs|prev=2020.1|next=2024.1}}

可用语言: [[Zh/2020.3|中文]]，[[Changelog_2020.3|English]], [[Pl/Changelog_2020.3|Polish]]. 

请协助我们将其翻译为更多语言!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

自由、开源的飞行模拟器FlightGear即将迎来2020.3版本更新。这是FlightGear开始同时提供长期支持版本和预览版本之后的第二个长期支持版本，代表了全球的志愿者们为期两年的开发工作的结晶。FlightGear由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的且无比贴近真实的飞行模拟器。 FlightGear通常被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。

自v2018.3 LTS以来的主要更新包括：
*增加了即将到来的Compositor图形框架的预览，作为单独的二进制文件共同分发。
*对JSBSim和YASim飞行动力学模型进行了更新
*增加了DDS贴图缓存以减少加载时间
*加载更快、更节省内存的建筑
*改善了对航空母舰的支持

此外，官方机库中增加了30架全新的机模，71架机模得到了重大更新。

{{Disclaimer|id=final-fixed-function-release-Chinese}}

始于1997年，FlightGear以其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构为特色。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。

FlightGear - 自由飞翔！

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== 启动器 ==
* 添加了在首次启动时出现的欢迎屏幕，为首次使用的用户提供一些有用的信息。
* 机模插件现在可被标记为个人收藏，并可进行筛选，使得在数百个机模插件中寻找您喜爱的机模变得更容易。
* 启动器增加了对航空母舰的支持，现可在启动器中选择航空母舰以及设置起始位置。
* 当你想开始飞行的时候，现在只需要按下<code> Ctrl-F </code>快捷键！
* 增强了对停机坪和水上机场的支持，增加了对当前的飞机型号的检测。
* 大量错误修正和稳定性改进，尤其对机模和插件选项卡进行了改进。

== 画面 ==
* 此发行版随附[[Compositor]]渲染器以便开发人员预览使用。Compositor渲染器提供了全面支持XML配置的多通道渲染合成方式，并且支持ALS与集群着色。*增加了对DDS贴图缓存的支持，缩短了贴图文件的加载时间。
* 恒星能见度现可根据恒星大小和大气条件进行配置。
* 现可通过设置<code>/rendering/triangle-direction-lights=false</code>，可以使用不定向点精灵（non-directional point sprites）以便在不支持三角形点精灵（triangles of point sprites）的图形驱动器上正确运行。
* 添加了全新的Tower AGL视角。该视角与塔台视角类似，不同之处在于它使地面保持在飞机的正下方，并在飞机移动时平稳地缩放和平移。这使得该视角适合用于观察降落。
* 改善了机场草地贴图
* 新增了沿海地区的潮汐效果。
* 更新了加利福尼亚地区、亚洲地区、巴西北部、冰岛和扬马延（Jan Mayen）岛的区域材质定义（regional material definitions）。
* 增加了新的活火山 - Katla, Eyjafjallajokull, Surtsey.
* 新增基于实例的随机建筑与OpenStreetMap建筑，提高了性能并显著提高了画面质量。
* 改进了机翼弯折着色器。
* 现可从“View”菜单中启用/禁用飞行员模型。

== JSBSim ==
[以下部分翻译使用机器翻译，故部分内容或许将不准确或不自然。欢迎更多志愿者加入到翻译的行列中！] 
[Some part of the following translation is made by a machine translator, so it may be inaccurate or awkward. Any contributions to the translation are welcomed! ]
* 新增了设置涡轮机启动和加速时间的功能（参数<code><n1spinup></code>，<code><n2spinup></code>，<code><n1startrate></code>， <code><n2startrate></code>）。
* 现在，可以通过将<code><integrator></code>过滤器的<code><trigger></code>属性设置为负值，将其重置为0.0。
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* 现在可以在<code><function></code>中使用以下功能：<code>floor</code>，<code>ceil</code>和<code>fmod</code>。它们的功能与相应的C / C ++函数相同。
* <code> <function> </code>现在检查其参数数量。
* 新的系统组件linear_actuator
* 将燃料密度导出到属性树
* 为FCS组件添加了循环裁剪
* 增加了控制涡轮发动机转速下降因子的功能
* [向后兼容性损坏]陀螺仪现在正在测量转速而不是旋转加速度。测量旋转加速度的陀螺仪在现实世界中不存在。
* 飞行控制元件的输出属性不再绑定。这样可以节省许多虚假的警告消息，并允许在多个飞行控制中直接引用相同的属性。
* 现在通过质量分数而不是分压来管理大气中的水蒸气。前者是压力和温度变化时保留的物理量。
* 在尝试修整地面之前，请检查至少3个触点。
* 为FG UDP接口增加了仿真时间的可选传输
* 现在在执行过程中而不是在解析XML定义时检查用于表无关var的属性的存在。这放宽了需要在XML定义文件中声明过滤器，表格以及更一般的飞行控件的顺序。
* 电动引擎RPM现在已在UDP套接字中导出。
* 参数<code><ignitionn2></code>现在影响N2而不是N1。
* 现在在<code><clipto></code>中的max<min时给出警告，而不是引发异常
* 添加了使用新的fgfs可执行参数<code>-jsbsim-output-directive-file</code>在CSV文件中记录属性的功能

== YASim ==
* 改变了静摩擦力
* 新增支持跨音速效果.
* 现可通过设置<code>/fdm/yasim/respect-external-gear-state=true</code>来控制初始起落架状态。
* 新增对电动引擎的支持。

== 气象和环境 ==
* 在活火山附近湍流强度将会增加。
* 现可对METAR URL进行配置。
* 新增对METAR字符串的解码并以可读的形式显示在天气对话框中。

== 航空母舰 ==
* 启动器现支持两种全新的标准状态: <code>carrier-takeoff</code> 与 <code>carrier-approach</code>.
* 加入了全新的命令行参数 <code>--carrier-position</code>。这可用于选择航空母舰上的飞机起始位置。可选择的选项包括航母弹射器(e.g. <code>cat-1</code>)、停机位(e.g. <code>park-1</code>)、FLOLS进近位(<code>flols</code>)或abeam位置(<code>abeam</code>)。
* 现在即使在启动时不可用，GUI也可以检测到MPCarrier。要启用此功能，请设置<code>/sim/mp-carriers/auto-attach=true</code>。

== AI ==
* 增加了新的fgcommands：<code>add-aiobject</code>和<code>remove-aiobject</code>，可用于向AI子系统添加或移除物体。
* 增加了新的AI飞机, 包括波音747货机、CRJ900、SR-71、Saab 340.
* 对许多AI交通时刻表与航空公司涂装进行了更新。
* 新增在KEDW的Space Shuttle TAEM与进近场景。
* 新增了来自当地飞行员的准确Britten-Norman Islander性能数据。

== 联机飞行 ==
* 现可通过GUI使用swift以连接到VATSIM。
* FGComm现在支持COM1和COM2以及音量设置。
* 由机模定义的视角（飞行员视角（Pilot view），直升机视角（Helicopter view），塔台视角（Tower view）等）现在可以在联机飞行中的其他飞机上使用。通过单击“飞行员列表（Pilot List）”对话框的“视图（view）”列，可以查看特定的联机飞机（可在“Multiplayer/Pilot List”菜单下找到）。
* 新增<code>-disable-hold-short </code>选项，当进入联机飞行时，允许用户在跑道上出生。请谨慎使用此选项——突然在跑道上出现会对其他飞行员与ATC造成极大的困扰。
* 回放器现可记录联机中其他飞机的数据。

== Nasal 脚本语言 ==
* 现可配置核心Nasal模块的加载顺序。
* 增加了对通信接口Emesary的改进和错误修复。
* 增加了对核心代码库的改进。
* 改进了垃圾回收机制以降低画面卡顿。
* 增加了对可重新载入的nasal模块的支持。
* 更新了Canvas EFIS框架。
* 在Canvas Image中新增了三种设置像素颜色的方法。

== 飞机模型 ==
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持（例如为G500制作SVG）。FG1000 目前在 Cessna 182T, J3 Cub, Diamond DA40上可用。
* 改进了滑翔机的vario仪。
* 新增的机模:
** Airbus A320 - 客机
** Alisport Silent2Electro - 带有电动维持电机的滑翔机
** Bombardier Q400 DHC8-402 - 短途涡桨客机
** Breguet Atlantic BR 1150 - 远程海军巡逻飞机
** Cessna 140 - 通航飞机
** Cessna 208B Caravan - 短程客机，货机和多用途飞机
** Cirrus SR22T - 通航飞机
** Diamond DA40 NG - 通航飞机, 包括了带有 FG1000 玻璃仪表的驾驶舱
** Diamond DA62 Twinstar- 双引擎通航飞机
** Diamond HK36 Super Dimona - 滑翔机
** Dornier DO 28 Skyservant - 双引擎STOL多用途飞机
** Douglas TBD Devastator - 第二次世界大战鱼雷轰炸机
** Draco Wilga - 涡桨后三点野地起降飞机
** Fokker T.V - 双引擎轰炸机
** Glasfluegel H201B Standard Libelle - 滑翔机
** Grumman F11-Tiger - 舰载战斗机
** Grumman HU-16A Albatross - 双引擎两栖飞机
** McDonnell Douglas MD-11 - 玻璃驾驶舱宽体三引擎飞机
** Petliakov PE-8 (Ant-42/TB-7) - 第二次世界大战轰炸机
** Piper PA28-161 Warrior II - 通航飞机
** Pipistrel Alpha Electro - 电动教练飞机
** Pipistrel Taurus Electro G2.5 - 带有电动维持电机的滑翔机
** Rolladen Schneider LS8sc neo - 带有电动维持电机的标准滑翔机
** Robin DR400 Ecoflyer - 通航飞机
** Scheibe Bergfalke II/55 - 教练滑翔机
** Schempp-Hirth Arcus S - 高性能滑翔机
** Schleicher Ka6(CR) "Rhoensegler" - 教练滑翔机
** SEPECAT Jaguar GR.1 - 喷气攻击机
** SUMPAC - 人力飞机
** Supermarine Swift - 喷气战机
** Yak 52 - 教练机
* 对超过70个机模进行了更新，包括 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== 其他 ==
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 地图对话框现可显示直升机坪并可配置光标平移。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 屏幕截图的文件名现已修改为日期与时间。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.1之后的更新=
自2020.1预览版以来的变化包括：
* 对启动器进行了许多改进，包括新增欢迎屏幕与<code> Ctrl-F </code>开始飞行快捷键。
* 更新了加利福尼亚地区、巴西北部与冰岛的区域材质定义（regional material definitions），改进了机场草地贴图。
* 新增了沿海地区的潮汐效果。
* 增加了新的波音747货机 AI模型，更新了许多AI飞机涂装与时刻表。
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持。
* 机库中新增了许多飞机： HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* 大量机模得到了更新，包括 CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.3.0之后的更新=

由于2020.3 是收到长期支持的版本，我们会根据用户反馈与自动崩溃报告对其进行问题修复与改进。以下列出了每个版本的主要变化。

==2020.3.1==
* 为启动器加入了帮助页面
* 修复了对直升机坪的处理
* 在移植到新的机库版本时移植已安装的机型
* TerraSync：提升了Windows下的启动性能

==2020.3.2==
* TerraSync 现在将等待模型完成同步过程，以避免启动时缺失模型
* 首次启动页面：增加了一个”滚动至底部“按钮
* Erik Hofman 进行了对潮汐的修复
* 启动器中使用了更好的滚动条，解决了一些与较长的机型列表有关的问题
* 支持 Apt.dat v1000 联络频率
* 修复了一个更改位置时的ATC崩溃
* 修复了许多 Michael Danilov 识别的翻译错误
* 显著改进了 Brazilian cerradio 区域 (SBMQ附近)
* 俄文翻译更新
* 修复了冰岛区域材质

==2020.3.3==
* 修复了右键拖动时的意外点击
* 修复了我们在'setup root'对话框中推荐的下载位置

==2020.3.4==
* 现可正确处理更多的METAR字符串，包括风传感器故障
* 修复了气团速度被两次应用在子模型上（例如在侧风中释放载荷时）的错误
* 修复了退出模拟器时与属性代码有关的崩溃
* 西班牙文翻译更新
* 禁用了前往EGEL的航班以防止AI交通代码中的崩溃

==2020.3.5==
* 将Windows下默认下载路径改为 %USERS%\FlightGear\Downloads, 来避免 Windows Defender 阻止不受信任的应用向此前使用的Documents文件夹中写入导致的问题。
* 修复了从其他应用返回FlightGear后滚动滚轮或点击鼠标时可能发生的崩溃
* 避免了使用基于 UIUC 的机型，例如莱特飞行者时发生的崩溃
* 修复了macOS中当摇杆无法开启时发生的崩溃
* 更新了macOS上的应用图标
* 修复了重置（reset）模拟器时Nasal发生的崩溃
* Canvas: 现允许各向异性过滤（Anisotropic filtering）
* 改进并使用了更大的月亮贴图
* 将 UFO 的速度调整为 11
* 修复了在一些特定的画质设置下滑行道标记消失的问题

==2020.3.6==
* 修复了下载默认机型目录时发生的崩溃
* 修复了在海洋中的地景启动时的停止响应
* 修复了在一些特定METAR下错误的天空与驾驶舱渲染
* 在启动器增加了新手上路（getting-started）提示（目前仅支持英文）
* 修复了航天飞机的AI场景（AI scenarios）
* 改进了飞行计划模式
* 修复了月亮/太阳的比例
* 修复子模型（submodels）的初始位置
* macOS: 增加了在临时镜像中运行时的警告
* Windows: 检测OpenGL驱动器是否缺失
* 修复 UIUC FDM 的崩溃
* 修复了与无效视角编号（view numbers）有关的崩溃
* 更恰当地处理FDM的NaN错误
* 改进了 KAP-140 进近模式（Approach mode）
* 更新了AI交通与涂装

==2020.3.7==
*TerraSync启用了全球范围内OSM2City建筑的分发
*C172 更新与错误修正
* 改进了欧洲与加利福尼亚地区的区域材质定义
*允许移动聊天框
*修复了与粒子系统有关的崩溃
*修复了北京及周边地区时区错误的问题
*修复了Canvas中显示non-Latin1字符串的问题
*修复了联网飞行模式下在跑道启动的逻辑，现可正确地将飞机放置于跑道外等待位置
*macOS: 修复了使用一些特定字体时的崩溃问题
*修复了当系统语言包括script specifier时启动器语言选择的问题（如zh-Hans-CN）
*修复了从机库加载时与aircraft-id属性有关的问题 ( https://sourceforge.net/p/flightgear/codetickets/2502/ )
*改进了Windows下对过时Intel图形驱动的检测

==2020.3.8==
*修复了<code><local></code>粒子系统的行为
*修复了秋季树木的外观

== 2020.3.9 ==
* 修复了与 Swift 有关的崩溃
* 修正了联机协议中使用的时间
* 修正了 FGData 的 URL
* 修复了重新加载缓存对话框中的错误
* 对 ATC 界面进行了改进，使其正确显示频率

== 2020.3.10 ==
* 应答机：现standby模式可正常工作
* 启动器：现可识别命令行中的地景与机模路径
* 启动器：改变了存储位置的方式以避免运行多个版本的FlightGear及在不同版本之间切换时出现问题
* 启动器：增加了“在退出时重启”（‘restart on quit’）的选项
* 修复了在加载ShapeFile数据时的NavCache报错
* 修复了在运行多个FlightGear副本时的NavCache报错

== 2020.3.11 ==
* 修复了一个2020.3.10中被引入的崩溃
* 改进了当机模搜索路径不存在时的报错信息
* 修复了未正确配置AI飞机滑行路径导致的崩溃
* 更新了AI交通的时间表

== 2020.3.12 ==
* 增加了对机模路径名称的验证
* 增加了更进一步的抗锯齿（8x）
* 增加了允许机模将自定义字体用于osg::Text的功能
* 增加了通用化的，结合了ALS procedural lights与Compositor lights的灯光
* 为澳大利亚地区增加了新的区域材质定义
* 修复了Basic Weather引擎输出无效气压高度的问题
* 修复了预览图路径搜索中存在的问题
* 修复了接近max-dist范围时声音系统存在的问题
* 修复了重置时发生的崩溃问题
* 修复了当AI飞机的目的地跑道无效时崩溃的问题
* 修复了Mapstructure RTE图层中的报错
* 修复了 --view-offset，使其使用正确的属性
* HUD：使垂直刻度的样式与水平刻度保持一致
* 改进了俄语和意大利语翻译
* 对天气对话框进行了数项改进
* 属性树浏览器（Property browser）：将文件夹的值以冗长的模式（verbose mode）显示
* 航路管理器（Route manager)：在存在同名航路点时现将自动选择正确的航路点
* 更新了AI交通的时间表，增加了新的AI飞机模型

== 2020.3.13 ==
* 修复了联机飞行员名单不出现的问题
* 修复了 JSBsim 线性执行器在特定条件下表现不佳的问题

== 2020.3.14 ==
* 增加了对add-ons路径的支持
* 新增了即时音频队列
* 对canvas对话框进行了改进，使其不抢占FG的鼠标焦点（与PUI对话框的行为类似）

== 2020.3.15 ==
* 修复了无线电音频摩尔斯电码的问题

== 2020.3.16 ==
* 修复了音频缩进问题。

== 2020.3.17 ==
* 导航无线电：更改选定频率或离开GPS从属模式时禁用低通滤波器。更改选定频率或离开 GPS 从属模式时，将禁用应用于信号质量的低通滤波器。
* 导航无线电：修复了一些新引入的问题并优化了旧代码。更新的内容：更改待机频率禁用了下一次调用 updateReceiver() 的低通滤波器; 这必须在更改选定频率时发生，但不在更改待机频率时发生。
* 自动驾驶仪输入：向自动驾驶仪的输入添加属性路径支持。允许间接定义自动驾驶仪（通过字符串属性），以便可以从-set.xml配置或在运行时进行调整。
* 在启动器中将五边进场的选项`--on-ground=false`替换为`--in-air`选项，以免产生误导。

== 2020.3.18 ==

* 新增对卫星地景 photoscenery 的支持。
* 全新的简单自动驾驶系统。
* 修复了 Navigraph 程序文件中 'between' 类型导致的崩溃。
==2020.3.19==
*增加了AI子模型碰撞效果
*修复了无效METAR字符串导致的崩溃
* 修复了一个在特定画质设置下OSM建筑会变为蓝色的渲染错误

== 参考 ==
{{Appendix}}

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

[[Category:FlightGear changelogs‎]]
[[En:Changelog_2020.3]]
[[Pl:Changelog_2020.3]]

Zh/2020.3

2024-07-28T09:01:41Z

Sidiliang: Sync changelog

{{changelogs|prev=2020.1|next=2022.1}}

可用语言: [[Zh/2020.3|中文]]，[[Changelog_2020.3|English]], [[Pl/Changelog_2020.3|Polish]]. 

请协助我们将其翻译为更多语言!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

自由、开源的飞行模拟器FlightGear即将迎来2020.3版本更新。这是FlightGear开始同时提供长期支持版本和预览版本之后的第二个长期支持版本，代表了全球的志愿者们为期两年的开发工作的结晶。FlightGear由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的且无比贴近真实的飞行模拟器。 FlightGear通常被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。

自v2018.3 LTS以来的主要更新包括：
*增加了即将到来的Compositor图形框架的预览，作为单独的二进制文件共同分发。
*对JSBSim和YASim飞行动力学模型进行了更新
*增加了DDS贴图缓存以减少加载时间
*加载更快、更节省内存的建筑
*改善了对航空母舰的支持

此外，官方机库中增加了30架全新的机模，71架机模得到了重大更新。

{{Disclaimer|id=final-fixed-function-release-Chinese}}

始于1997年，FlightGear以其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构为特色。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。

FlightGear - 自由飞翔！

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== 启动器 ==
* 添加了在首次启动时出现的欢迎屏幕，为首次使用的用户提供一些有用的信息。
* 机模插件现在可被标记为个人收藏，并可进行筛选，使得在数百个机模插件中寻找您喜爱的机模变得更容易。
* 启动器增加了对航空母舰的支持，现可在启动器中选择航空母舰以及设置起始位置。
* 当你想开始飞行的时候，现在只需要按下<code> Ctrl-F </code>快捷键！
* 增强了对停机坪和水上机场的支持，增加了对当前的飞机型号的检测。
* 大量错误修正和稳定性改进，尤其对机模和插件选项卡进行了改进。

== 画面 ==
* 此发行版随附[[Compositor]]渲染器以便开发人员预览使用。Compositor渲染器提供了全面支持XML配置的多通道渲染合成方式，并且支持ALS与集群着色。*增加了对DDS贴图缓存的支持，缩短了贴图文件的加载时间。
* 恒星能见度现可根据恒星大小和大气条件进行配置。
* 现可通过设置<code>/rendering/triangle-direction-lights=false</code>，可以使用不定向点精灵（non-directional point sprites）以便在不支持三角形点精灵（triangles of point sprites）的图形驱动器上正确运行。
* 添加了全新的Tower AGL视角。该视角与塔台视角类似，不同之处在于它使地面保持在飞机的正下方，并在飞机移动时平稳地缩放和平移。这使得该视角适合用于观察降落。
* 改善了机场草地贴图
* 新增了沿海地区的潮汐效果。
* 更新了加利福尼亚地区、亚洲地区、巴西北部、冰岛和扬马延（Jan Mayen）岛的区域材质定义（regional material definitions）。
* 增加了新的活火山 - Katla, Eyjafjallajokull, Surtsey.
* 新增基于实例的随机建筑与OpenStreetMap建筑，提高了性能并显著提高了画面质量。
* 改进了机翼弯折着色器。
* 现可从“View”菜单中启用/禁用飞行员模型。

== JSBSim ==
[以下部分翻译使用机器翻译，故部分内容或许将不准确或不自然。欢迎更多志愿者加入到翻译的行列中！] 
[Some part of the following translation is made by a machine translator, so it may be inaccurate or awkward. Any contributions to the translation are welcomed! ]
* 新增了设置涡轮机启动和加速时间的功能（参数<code><n1spinup></code>，<code><n2spinup></code>，<code><n1startrate></code>， <code><n2startrate></code>）。
* 现在，可以通过将<code><integrator></code>过滤器的<code><trigger></code>属性设置为负值，将其重置为0.0。
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* 现在可以在<code><function></code>中使用以下功能：<code>floor</code>，<code>ceil</code>和<code>fmod</code>。它们的功能与相应的C / C ++函数相同。
* <code> <function> </code>现在检查其参数数量。
* 新的系统组件linear_actuator
* 将燃料密度导出到属性树
* 为FCS组件添加了循环裁剪
* 增加了控制涡轮发动机转速下降因子的功能
* [向后兼容性损坏]陀螺仪现在正在测量转速而不是旋转加速度。测量旋转加速度的陀螺仪在现实世界中不存在。
* 飞行控制元件的输出属性不再绑定。这样可以节省许多虚假的警告消息，并允许在多个飞行控制中直接引用相同的属性。
* 现在通过质量分数而不是分压来管理大气中的水蒸气。前者是压力和温度变化时保留的物理量。
* 在尝试修整地面之前，请检查至少3个触点。
* 为FG UDP接口增加了仿真时间的可选传输
* 现在在执行过程中而不是在解析XML定义时检查用于表无关var的属性的存在。这放宽了需要在XML定义文件中声明过滤器，表格以及更一般的飞行控件的顺序。
* 电动引擎RPM现在已在UDP套接字中导出。
* 参数<code><ignitionn2></code>现在影响N2而不是N1。
* 现在在<code><clipto></code>中的max<min时给出警告，而不是引发异常
* 添加了使用新的fgfs可执行参数<code>-jsbsim-output-directive-file</code>在CSV文件中记录属性的功能

== YASim ==
* 改变了静摩擦力
* 新增支持跨音速效果.
* 现可通过设置<code>/fdm/yasim/respect-external-gear-state=true</code>来控制初始起落架状态。
* 新增对电动引擎的支持。

== 气象和环境 ==
* 在活火山附近湍流强度将会增加。
* 现可对METAR URL进行配置。
* 新增对METAR字符串的解码并以可读的形式显示在天气对话框中。

== 航空母舰 ==
* 启动器现支持两种全新的标准状态: <code>carrier-takeoff</code> 与 <code>carrier-approach</code>.
* 加入了全新的命令行参数 <code>--carrier-position</code>。这可用于选择航空母舰上的飞机起始位置。可选择的选项包括航母弹射器(e.g. <code>cat-1</code>)、停机位(e.g. <code>park-1</code>)、FLOLS进近位(<code>flols</code>)或abeam位置(<code>abeam</code>)。
* 现在即使在启动时不可用，GUI也可以检测到MPCarrier。要启用此功能，请设置<code>/sim/mp-carriers/auto-attach=true</code>。

== AI ==
* 增加了新的fgcommands：<code>add-aiobject</code>和<code>remove-aiobject</code>，可用于向AI子系统添加或移除物体。
* 增加了新的AI飞机, 包括波音747货机、CRJ900、SR-71、Saab 340.
* 对许多AI交通时刻表与航空公司涂装进行了更新。
* 新增在KEDW的Space Shuttle TAEM与进近场景。
* 新增了来自当地飞行员的准确Britten-Norman Islander性能数据。

== 联机飞行 ==
* 现可通过GUI使用swift以连接到VATSIM。
* FGComm现在支持COM1和COM2以及音量设置。
* 由机模定义的视角（飞行员视角（Pilot view），直升机视角（Helicopter view），塔台视角（Tower view）等）现在可以在联机飞行中的其他飞机上使用。通过单击“飞行员列表（Pilot List）”对话框的“视图（view）”列，可以查看特定的联机飞机（可在“Multiplayer/Pilot List”菜单下找到）。
* 新增<code>-disable-hold-short </code>选项，当进入联机飞行时，允许用户在跑道上出生。请谨慎使用此选项——突然在跑道上出现会对其他飞行员与ATC造成极大的困扰。
* 回放器现可记录联机中其他飞机的数据。

== Nasal 脚本语言 ==
* 现可配置核心Nasal模块的加载顺序。
* 增加了对通信接口Emesary的改进和错误修复。
* 增加了对核心代码库的改进。
* 改进了垃圾回收机制以降低画面卡顿。
* 增加了对可重新载入的nasal模块的支持。
* 更新了Canvas EFIS框架。
* 在Canvas Image中新增了三种设置像素颜色的方法。

== 飞机模型 ==
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持（例如为G500制作SVG）。FG1000 目前在 Cessna 182T, J3 Cub, Diamond DA40上可用。
* 改进了滑翔机的vario仪。
* 新增的机模:
** Airbus A320 - 客机
** Alisport Silent2Electro - 带有电动维持电机的滑翔机
** Bombardier Q400 DHC8-402 - 短途涡桨客机
** Breguet Atlantic BR 1150 - 远程海军巡逻飞机
** Cessna 140 - 通航飞机
** Cessna 208B Caravan - 短程客机，货机和多用途飞机
** Cirrus SR22T - 通航飞机
** Diamond DA40 NG - 通航飞机, 包括了带有 FG1000 玻璃仪表的驾驶舱
** Diamond DA62 Twinstar- 双引擎通航飞机
** Diamond HK36 Super Dimona - 滑翔机
** Dornier DO 28 Skyservant - 双引擎STOL多用途飞机
** Douglas TBD Devastator - 第二次世界大战鱼雷轰炸机
** Draco Wilga - 涡桨后三点野地起降飞机
** Fokker T.V - 双引擎轰炸机
** Glasfluegel H201B Standard Libelle - 滑翔机
** Grumman F11-Tiger - 舰载战斗机
** Grumman HU-16A Albatross - 双引擎两栖飞机
** Petliakov PE-8 (Ant-42/TB-7) - 第二次世界大战轰炸机
** Piper PA28-161 Warrior II - 通航飞机
** Pipistrel Alpha Electro - 电动教练飞机
** Pipistrel Taurus Electro G2.5 - 带有电动维持电机的滑翔机
** Rolladen Schneider LS8sc neo - 带有电动维持电机的标准滑翔机
** Robin DR400 Ecoflyer - 通航飞机
** Scheibe Bergfalke II/55 - 教练滑翔机
** Schempp-Hirth Arcus S - 高性能滑翔机
** Schleicher Ka6(CR) "Rhoensegler" - 教练滑翔机
** SEPECAT Jaguar GR.1 - 喷气攻击机
** SUMPAC - 人力飞机
** Supermarine Swift - 喷气战机
** Yak 52 - 教练机
* 对超过70个机模进行了更新，包括 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== 其他 ==
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 地图对话框现可显示直升机坪并可配置光标平移。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 屏幕截图的文件名现已修改为日期与时间。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.1之后的更新=
自2020.1预览版以来的变化包括：
* 对启动器进行了许多改进，包括新增欢迎屏幕与<code> Ctrl-F </code>开始飞行快捷键。
* 更新了加利福尼亚地区、巴西北部与冰岛的区域材质定义（regional material definitions），改进了机场草地贴图。
* 新增了沿海地区的潮汐效果。
* 增加了新的波音747货机 AI模型，更新了许多AI飞机涂装与时刻表。
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持。
* 机库中新增了许多飞机： HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* 大量机模得到了更新，包括 CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.3.0之后的更新=

由于2020.3 是收到长期支持的版本，我们会根据用户反馈与自动崩溃报告对其进行问题修复与改进。以下列出了每个版本的主要变化。

==2020.3.1==
* 为启动器加入了帮助页面
* 修复了对直升机坪的处理
* 在移植到新的机库版本时移植已安装的机型
* TerraSync：提升了Windows下的启动性能

==2020.3.2==
* TerraSync 现在将等待模型完成同步过程，以避免启动时缺失模型
* 首次启动页面：增加了一个”滚动至底部“按钮
* Erik Hofman 进行了对潮汐的修复
* 启动器中使用了更好的滚动条，解决了一些与较长的机型列表有关的问题
* 支持 Apt.dat v1000 联络频率
* 修复了一个更改位置时的ATC崩溃
* 修复了许多 Michael Danilov 识别的翻译错误
* 显著改进了 Brazilian cerradio 区域 (SBMQ附近)
* 俄文翻译更新
* 修复了冰岛区域材质

==2020.3.3==
* 修复了右键拖动时的意外点击
* 修复了我们在'setup root'对话框中推荐的下载位置

==2020.3.4==
* 现可正确处理更多的METAR字符串，包括风传感器故障
* 修复了气团速度被两次应用在子模型上（例如在侧风中释放载荷时）的错误
* 修复了退出模拟器时与属性代码有关的崩溃
* 西班牙文翻译更新
* 禁用了前往EGEL的航班以防止AI交通代码中的崩溃

==2020.3.5==
* 将Windows下默认下载路径改为 %USERS%\FlightGear\Downloads, 来避免 Windows Defender 阻止不受信任的应用向此前使用的Documents文件夹中写入导致的问题。
* 修复了从其他应用返回FlightGear后滚动滚轮或点击鼠标时可能发生的崩溃
* 避免了使用基于 UIUC 的机型，例如莱特飞行者时发生的崩溃
* 修复了macOS中当摇杆无法开启时发生的崩溃
* 更新了macOS上的应用图标
* 修复了重置（reset）模拟器时Nasal发生的崩溃
* Canvas: 现允许各向异性过滤（Anisotropic filtering）
* 改进并使用了更大的月亮贴图
* 将 UFO 的速度调整为 11
* 修复了在一些特定的画质设置下滑行道标记消失的问题

==2020.3.6==
* 修复了下载默认机型目录时发生的崩溃
* 修复了在海洋中的地景启动时的停止响应
* 修复了在一些特定METAR下错误的天空与驾驶舱渲染
* 在启动器增加了新手上路（getting-started）提示（目前仅支持英文）
* 修复了航天飞机的AI场景（AI scenarios）
* 改进了飞行计划模式
* 修复了月亮/太阳的比例
* 修复子模型（submodels）的初始位置
* macOS: 增加了在临时镜像中运行时的警告
* Windows: 检测OpenGL驱动器是否缺失
* 修复 UIUC FDM 的崩溃
* 修复了与无效视角编号（view numbers）有关的崩溃
* 更恰当地处理FDM的NaN错误
* 改进了 KAP-140 进近模式（Approach mode）
* 更新了AI交通与涂装

==2020.3.7==
*TerraSync启用了全球范围内OSM2City建筑的分发
*C172 更新与错误修正
* 改进了欧洲与加利福尼亚地区的区域材质定义
*允许移动聊天框
*修复了与粒子系统有关的崩溃
*修复了北京及周边地区时区错误的问题
*修复了Canvas中显示non-Latin1字符串的问题
*修复了联网飞行模式下在跑道启动的逻辑，现可正确地将飞机放置于跑道外等待位置
*macOS: 修复了使用一些特定字体时的崩溃问题
*修复了当系统语言包括script specifier时启动器语言选择的问题（如zh-Hans-CN）
*修复了从机库加载时与aircraft-id属性有关的问题 ( https://sourceforge.net/p/flightgear/codetickets/2502/ )
*改进了Windows下对过时Intel图形驱动的检测

==2020.3.8==
*修复了<code><local></code>粒子系统的行为
*修复了秋季树木的外观

== 2020.3.9 ==
* 修复了与 Swift 有关的崩溃
* 修正了联机协议中使用的时间
* 修正了 FGData 的 URL
* 修复了重新加载缓存对话框中的错误
* 对 ATC 界面进行了改进，使其正确显示频率

== 2020.3.10 ==
* 应答机：现standby模式可正常工作
* 启动器：现可识别命令行中的地景与机模路径
* 启动器：改变了存储位置的方式以避免运行多个版本的FlightGear及在不同版本之间切换时出现问题
* 启动器：增加了“在退出时重启”（‘restart on quit’）的选项
* 修复了在加载ShapeFile数据时的NavCache报错
* 修复了在运行多个FlightGear副本时的NavCache报错

== 2020.3.11 ==
* 修复了一个2020.3.10中被引入的崩溃
* 改进了当机模搜索路径不存在时的报错信息
* 修复了未正确配置AI飞机滑行路径导致的崩溃
* 更新了AI交通的时间表

== 2020.3.12 ==
* 增加了对机模路径名称的验证
* 增加了更进一步的抗锯齿（8x）
* 增加了允许机模将自定义字体用于osg::Text的功能
* 增加了通用化的，结合了ALS procedural lights与Compositor lights的灯光
* 为澳大利亚地区增加了新的区域材质定义
* 修复了Basic Weather引擎输出无效气压高度的问题
* 修复了预览图路径搜索中存在的问题
* 修复了接近max-dist范围时声音系统存在的问题
* 修复了重置时发生的崩溃问题
* 修复了当AI飞机的目的地跑道无效时崩溃的问题
* 修复了Mapstructure RTE图层中的报错
* 修复了 --view-offset，使其使用正确的属性
* HUD：使垂直刻度的样式与水平刻度保持一致
* 改进了俄语和意大利语翻译
* 对天气对话框进行了数项改进
* 属性树浏览器（Property browser）：将文件夹的值以冗长的模式（verbose mode）显示
* 航路管理器（Route manager)：在存在同名航路点时现将自动选择正确的航路点
* 更新了AI交通的时间表，增加了新的AI飞机模型

== 2020.3.13 ==
* 修复了联机飞行员名单不出现的问题
* 修复了 JSBsim 线性执行器在特定条件下表现不佳的问题

== 2020.3.14 ==
* 增加了对add-ons路径的支持
* 新增了即时音频队列
* 对canvas对话框进行了改进，使其不抢占FG的鼠标焦点（与PUI对话框的行为类似）

== 2020.3.15 ==
* 修复了无线电音频摩尔斯电码的问题

== 2020.3.16 ==
* 修复了音频缩进问题。

== 2020.3.17 ==
* 导航无线电：更改选定频率或离开GPS从属模式时禁用低通滤波器。更改选定频率或离开 GPS 从属模式时，将禁用应用于信号质量的低通滤波器。
* 导航无线电：修复了一些新引入的问题并优化了旧代码。更新的内容：更改待机频率禁用了下一次调用 updateReceiver() 的低通滤波器; 这必须在更改选定频率时发生，但不在更改待机频率时发生。
* 自动驾驶仪输入：向自动驾驶仪的输入添加属性路径支持。允许间接定义自动驾驶仪（通过字符串属性），以便可以从-set.xml配置或在运行时进行调整。
* 在启动器中将五边进场的选项`--on-ground=false`替换为`--in-air`选项，以免产生误导。

== 2020.3.18 ==

* 新增对卫星地景 photoscenery 的支持。
* 全新的简单自动驾驶系统。
* 修复了 Navigraph 程序文件中 'between' 类型导致的崩溃。
==2020.3.19==
*增加了AI子模型碰撞效果
*修复了无效METAR字符串导致的崩溃
* 修复了一个在特定画质设置下OSM建筑会变为蓝色的渲染错误

== 参考 ==
{{Appendix}}

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

[[Category:FlightGear changelogs‎]]
[[En:Changelog_2020.3]]
[[Pl:Changelog_2020.3]]

Discord

2024-04-11T15:08:14Z

Sidiliang: /* Aircraft-specific */ Update link for 777 discord dev server

'''Discord''' is used in the FlightGear community as an alternative to [[Mumble]], [[TeamSpeak]], [[FGCom]] or [[Ventrilo]].

Discord is a free voice and chat software that can be downloaded as an app or used in a browser.

== Invite links ==
{{note|1=Its advised that you create a permanent account, instead of creating guest accounts as some people create duplicate accounts which clogs up the member logs and makes it more difficult to @mention people.}}

Furthermore many other FlightGear servers exist that you may need an personal invite to join. The easiest way to find them is to go to the FlightGear server and ask or ask in forums.

== FlightGear Communities on Discord ==

=== General, Help and Support, Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear
| https://discord.gg/rzuV2DR
|-
| FlightGear FDM School
| https://discord.gg/Uyrtsar
|-
| FlightGear Air Race League
| https://discord.gg/HCAuU9D
|-
| FlightGear Virtual Alliance
| https://discord.gg/VqzTG2N
|-
| FG Events
| https://discord.gg/GY4N6Cu
|-
| FG FDM School
| https://discord.gg/U5KXyMU
|-
| FlightGear Republic, A friendly community about FlightGear.
| https://discord.gg/sBJy46Uq7z
|-
|FlightGear soaring club
|https://discord.gg/NvJjmzMfRP
|}

=== Military Aviation Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| Operation Red Flag military FG community (OPRF)
| https://discord.gg/ptVapkE
|-
| Combined Joint Task Force 50 (OPRF event planning/hosting and more)
| https://discord.gg/2nxjb6y
|-
| Warbirds, WWII-era aircraft
| https://discord.gg/yJaP5Wn
|}

=== Country Specific Communities ===

{| class=wikitable
! Topic !! Invite link
|-
| FlightGear Australia (Scenery Development & Community)
| https://discord.gg/JzTEXsZ
|-
| FlightGear Italia (ITA Mercenaries)
| https://discord.gg/5RzyXRf
|-
| FlightGear Germany
| https://discord.gg/FNnpjCPSze
|-
| FlightGear Indian Community
| https://discord.gg/Tu7n5FmG5S
|-
| FlightGear Asia
| https://discord.gg/7saCkA2jQj
|-
| FlightGear Hong Kong
| https://discord.gg/9QVKcT6skU
|-
|FlightGear Myanmar
|https://discord.gg/VbT88KEGrk
|-
|FlightGear Poland (FlightGear Polska)
|https://discord.gg/5J7uVYRhZV
|}

=== Aircraft-specific ===
{| class="wikitable"
! Aircraft !! Invite link
|-
| Aermacchi MB-339
| https://discord.gg/vNZ5ZPv
|-
| Airbus [[Airbus A320 Family|A320]] & A330 Development
| https://discord.gg/7kzg9Te
|-
| Airbus A350 Development
| https://discord.gg/vK5f2s6
|-
| Boeing F/A-18C Hornet
| https://discord.gg/8GzpdK4j8P
|-
| LincolnWorks (747 and A380)
| https://discord.gg/2DMVpnJ
|-
| F-111 Aardvark
| https://discord.gg/DSrSbmx
|-
| [[General Dynamics F-16 Fighting Falcon]]
| https://discord.gg/8RcYnjA
|-
| [[PZL-Koliber-family | PZL Koliber family]]
| https://discord.gg/beADn2sWM6
|-
| Octal450 Hangar Development
| https://discord.gg/gxAhC3j
|-
| [[Mikoyan-Gurevich MiG-21bis]]
| https://discord.gg/bs8xyz3
|-
| [[Mirage 2000]]
| https://discord.gg/xZ3r2KR
|-
| Panavia Tornado
| https://discord.gg/SYxgzkCrSG
|-
| [[Saab 37 Viggen]]
| https://discord.gg/RJTwS9a
|-
| SEPECAT Jaguar
| https://discord.gg/G5q5XYN
|-
| FG-1000 Stealth Fighter
| https://discord.gg/3MFZauxyPW
|-
|Boeing 777
|https://discord.gg/k5RXxFgGDA
|-
|A-10 Warthog
|https://discord.gg/RmtjmsT5vS
|-
|Soviet Aviation for FGFS
|https://discord.gg/YC2EYGK5Xf
|-
|B-1 Lancer
|https://discord.gg/d2bhwFCnX2
|}

==External links==
*https://discord.com/ Official website

[[de:Discord]]

[[Category:Software]]
[[Category:Community]]
[[Category:Air Traffic Control]]

Translation requests

2024-04-06T07:35:33Z

Sidiliang: /* Open translation requests */

Please post your translation requests here, so that other people can more easily track what's going on, hopefully avoiding duplicate efforts.

*How to translate is described here: [[Help:Translate]].

== Currently work in progress ==
*Please see table below.
*Please add {{tl|BeingTranslated}} to articles that are being translated, remove this when you are finished.
*Please add {{tl|UpdateTranslation}} to articles that have an up-to-date English version but an out-of-date local version.
*Also look at [[:Category:Articles being translated]].

== Open translation requests ==
Check out [[Special:Statistics]] for the most viewed pages:

{| class="wikitable" style="text-align: center"
! [[#Language map|en]]
! [[#Language map|ar]] 
! [[#Language map|ca]] 
! [[#Language map|de]] 
! [[#Language map|el]] 
! [[#Language map|es]] 
! [[#Language map|fa]] 
! [[#Language map|fi]] 
! [[#Language map|fr]] 
! [[#Language map|it]] 
! [[#Language map|ja]] 
! [[#Language map|nl]] 
! [[#Language map|pl]] 
! [[#Language map|pt]] 
! [[#Language map|pt-br]] 
! [[#Language map|ru]] 
! [[#Language map|sl]] 
! [[#Language map|sr]] 
! [[#Language map|sv]] 
! [[#Language map|th]] 
! [[#Language map|zh]] 
|- style="font-weight:bold"
| style="text-align: left" | [[Help:Translate]]
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:ca:Help:Traduir}} 
|| {{progressbar|100|10|link=:de:Help:Übersetzen}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:es:Help:Traducir}} 
|| {{progressbar|100|10|link=:Fa:راهنمایی:ترجمه}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:fr:Help:Traduire}} 
|| {{progressbar|100|10|link=:it:Help:Tradurre}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:nl:Help:Vertalen}} 
|| {{progressbar|100|10|link=:pl:Pomoc:Tłumaczenie}} 
|| {{progressbar|100|10|link=:pt:Help:Traduzir}} 
|| {{progressbar|100|10|link=:pt-br:Help:_Traduzir}} 
|| {{progressbar|100|10|link=:ru:Справка:Перевод}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:sv:Hjälp:Översättning}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|- style="font-weight:bold"
| style="text-align: left" | [[Main Page]]
|| {{progressbar|90|10|link=:ar:Main_Page}} 
|| {{progressbar|100|10|link=:ca:Portada}} 
|| {{progressbar|100|10|link=:de:Hauptseite}} 
|| {{progressbar|0|10|link=:el:Αρχική}} 
|| {{progressbar|100|10|link=:es:Portada}} 
|| {{progressbar|100|10|link=:fa:Persian}} 
|| {{progressbar|100|10|link=:fi:Etusivu}} 
|| {{progressbar|100|10|link=:fr:Accueil}} 
|| {{progressbar|100|10|link=:it:Pagina principale}} 
|| {{progressbar|80|10|link=:ja:トップページ}} 
|| {{progressbar|100|10|link=:nl:Hoofdpagina}} 
|| {{progressbar|100|10|link=:pl:Strona główna}} 
|| {{progressbar|100|10|link=:pt:Página principal}} 
|| {{progressbar|0|10|link=:pt-br:Página principal}} 
|| {{progressbar|100|10|link=:ru:Заглавная страница}} 
|| {{progressbar|80|10|link=:sl:Main Page}} 
|| {{progressbar|80|10|link=:sr:Main Page}} 
|| {{progressbar|0|10|link=Main Page}} 
|| {{progressbar|80|10|link=:th:Main Page}} 
|| {{progressbar|100|10|link=:zh:首页}} 
|-
| style="text-align: left" | [[Aircraft]]
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:ca:Aeronau}} 
|| {{progressbar|100|10|link=:de:Flugzeuge}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:es:Aeronaves}} 
|| {{progressbar|100|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:fi:Lentokoneet}} 
|| {{progressbar|100|10|link=:fr:Avions}} 
|| {{progressbar|100|10|link=:it:Aerei}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:nl:Luchtvaartuigen}} 
|| {{progressbar|100|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:pt:Aeronaves}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:ru:Самолет}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|-
| style="text-align: left" | [[Altitude]]
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:ca:Altitud}} 
|| {{progressbar|90|10|link=:de:Flughöhe}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:es:Altitud}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:fr:Altitude}} 
|| {{progressbar|100|10|link=:it:Altitude}}
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:nl:Vlieghoogte}} 
|| {{progressbar|100|10|link=pl:Wysokość}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:ru:Высота полёта}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|-
| style="text-align: left" | [[Cessna 172P]]
|| {{progressbar|90|10|link=:ar:Cessna 172P}} 
|| {{progressbar|100|10|link=:ca:Cessna 172P}} 
|| {{progressbar|100|10|link=:de:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:es:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|50|10|link=:fr:Cessna 172}} 
|| {{progressbar|100|10|link=:it:Cessna_172P}}
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:nl:Cessna 172P}} 
|| {{progressbar|100|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:ru:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|90|10|link=:zh:Cessna 172P}}
|-
| style="text-align: left" | [[FGAddon]]
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|40|10|link=:ca:FGAddon}} 
|| {{progressbar|50|10|link=:de:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|100|10|link=:fr:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|100|10|link=:nl:FGAddon}} 
|| {{progressbar|100|10|link=:pl:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|-
| style="text-align: left" | [[FlightGear]]
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:ca:FlightGear}} 
|| {{progressbar|100|10|link=:de:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:es:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:fr:FlightGear}} 
|| {{progressbar|100|10|link=:it:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|50|10|link=:nl:FlightGear}} 
|| {{progressbar|100|10|link=:pl:FlightGear}} 
|| {{progressbar|100|10|link=:pt:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|-
| style="text-align: left" | [[FlightGear hangars]]
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|100|10|link=:ca:Hangars de Flightgear}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|90|10|link=:es:Hangares_Flightgear}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|90|10|link=:fr:FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|100|10|link=pl:FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|-
| style="text-align: left" | [[FlightGear Launch Control]]
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:de:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:fr:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:nl:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|-
| style="text-align: left" | [[Flying the helicopter]]
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:de:Fliegen mit dem Helikopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:es:Volando el helicoptero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:fr:Piloter l'hélicoptère}} 
|| {{progressbar|100|10|link=:it:Pilotare un elicottero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:nl:Vliegen met de helicopter}} 
|| {{progressbar|50|10|link=:pl:Lot śmigłowcem}} 
|| {{progressbar|50|10|link=:pt:Voando de Helicóptero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|-
| style="text-align: left" | [[Frequently asked questions]]
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:de:FAQ}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:es:Preguntas frecuentes}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:fr:Foire aux questions}} 
|| {{progressbar|100|10|link=:it:Domande_frequenti}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:nl:veel gestelde vragen}} 
|| {{progressbar|100|10|link=:pl:FAQ}} 
|| {{progressbar|50|10|link=:pt:FAQ}} 
|| {{progressbar|0|10|link=:pt-br:Perguntas frequentes}} 
|| {{progressbar|10|10|link=:ru:ЧаВо}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|-
| style="text-align: left" | [[Howto:Install scenery]]
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:de:Szenerie installieren}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:es:Instalación de escenarios}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:fr:Installer une scène}} 
|| {{progressbar|50|10|link=:it:Come fare:Installare scenari}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:nl:Scenery_installeren}} 
|| {{progressbar|100|10|link=:pl:Instalowanie scenerii}} 
|| {{progressbar|100|10|link=:pt:Instalando Cenário}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|-
| style="text-align: left" | [[Howto:Multiplayer]]
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:de:Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:es:Howto:Multijugador}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:fr:Howto:Multijoueur}} 
|| {{progressbar|50|10|link=:it:Come fare:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:nl:Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:pl:Konfiguracja trybu multiplayer}} 
|| {{progressbar|100|10|link=:pt:Tutorial de Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|-
| style="text-align: left" | [[Help:Gallery of messagebox templates|Messagebox templates]] 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|20|10|link=:de:Help:Messagebox Vorlagengalerie}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|20|10|link=:fr:Help:Galerie de modèles de messagebox}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|-
| style="text-align: left" | [[New to FlightGear]]
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:ca:Nou a FlightGear}} 
|| {{progressbar|50|10|link=:de:Neu bei FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:es:Nuevo en FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:fr:Nouveau sur flightgear}} 
|| {{progressbar|50|10|link=:it:Nuovo per FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:nl:Nieuw bij FlightGear}} 
|| {{progressbar|100|10|link=:pl:Nowy_w_FlightGear}} 
|| {{progressbar|100|10|link=:pt:Novo no FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:zh:FlightGear新手}} 
|-
| style="text-align: left" | [[Portal:User]]
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:ca:Portal:Usuari}} 
|| {{progressbar|100|10|link=:de:Portal:Benutzer}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|50|10|link=:es:Portal:Usuario}} 
|| {{progressbar|40|10|link=Fa:Portal:کاربر}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|50|10|link=:fr:Portal:Utilisateur}} 
|| {{progressbar|100|10|link=:it:Portal:Utente}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:nl:Portal:Gebruiker}} 
|| {{progressbar|90|10|link=:pl:Portal:Dla użytkowników}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=:pt-br:Portal:Usuario}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:zh:Portal:用户}} 
|-
| style="text-align: left" | {{obr}}[[Template:infobox aircraft#Full_translation|infobox aircraft]]{{cbr}}
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|90|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|50|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|-
| style="text-align: left" | {{tl|Main page/Languages}}
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|0|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|-
| style="text-align: left" | [[TerraSync]]
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:de:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:es:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:fr:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|100|10|link=:nl:Terrasync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|-
| style="text-align: left" | [[Troubleshooting problems]]
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:de:Problemlösung}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:es:Resolviendo_problemas}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:fr:Troubleshooting Problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:nl:Problemen oplossen}} 
|| {{progressbar|100|10|link=:pl:Rozwiązywanie_problemów}} 
|| {{progressbar|100|10|link=:pt:Resolvendo Problemas}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|-
| style="text-align: left" | New article
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|}

* Please help to translate any pages that are not complete. Carefully check the history of the article to be sure that someone else is not currently translating the article.
* For completed entries, please compare to the English version of the article to make sure that new content has been translated.
* English is the primary language of this wiki. Content present in a translation but not in the English article will be, with time, deleted. Always add new content to both the translation and the original English.
* A translated page must be linked to from all other translated pages.
* Help and keep this page up-to-date please (so to avoid double work).

=== Language map ===

Here is an alphabetically ordered language map:

{| class="wikitable" style="text-align: center"
! ISO language code
! Name
! English name
|-
| en || English || English
|-
| ar || العربية || Arabic
|-
| ca || Català || Catalan
|-
| de || Deutsch || German
|-
| el || Ελληνικά || Greek
|-
| es || Español || Spanish
|-
| fa || فارسی || Persian
|-
| fi || Suomi || Finnish
|-
| fr || Français || French
|-
| it || Italiano || Italian
|-
| ja || 日本語 || Japanese
|-
| nl || Nederlands || Dutch
|-
| pl || Polski || Polish
|-
| pt || Português || Portuguese
|-
| pt-br || Português do Brasil || Brazilian Portuguese
|-
| ru || Русский || Russian
|-
| sl || Slovenščina || Slovene
|-
| sr || Српски / srpski || Serbian
|-
| sv || Svenska || Swedish
|-
| th || ไทย || Thai
|-
| zh || 中文 || Chinese
|}

[[Category:Contribution requests]]

Zh/Cessna 172P

2024-04-06T07:32:32Z

Sidiliang: Updated figures according to the English version

{{:{{#titleparts:{{PAGENAME}}||2}}/info}}
塞斯纳172P “天鹰” 是一架四座位、单引擎、固定上单翼飞机。该机型首飞于1955年，至今仍在生产。塞斯纳172是目前为止世界上生产数量最大的飞机。
自2000年开始，塞斯纳172就是Flightgear的默认机型，取代了原有的Navion飞机。这个机模经过了长时间的的开发，具有很多优秀的特性。2015年，开发者对这个机模进行了大更新，加入了引擎选项、选择轮胎大小以及浮筒等功能，并更新了全新的驾驶舱贴图。这个全新的C172版本成为了FlightGear 3.6及后续版本的默认机型。
== 特性 ==

这架全新的C172P拥有非常完善的3D（三维）模型以及非常完整的贴图。您可以操作驾驶舱内所有的开关。这架飞机同时还拥有一个很好的空气动力学模型（FDM）、复杂的飞行程序以及全新的，真实的检查单、全新的声音效果与损坏效果模拟。如果在您飞行时发生失误，飞机将可能被损坏，例如重着陆时起落架可能会坍塌。[[File:c172p-preview5.jpg|center|700px]]这架机模目前有五个变种，可以在飞机菜单中选择：
* 常规轮胎
* 26" 轮胎
* 31" 轮胎
* 浮筒
* 水陆两用浮筒
* 雪橇

同时，在同一个菜单下，您可选择两种不同功率的引擎：
* 160 HP
* 180 HP (推荐在使用浮筒、水陆两用浮筒以及雪橇时选择)

目前这架飞机在撞击、坠毁、重着陆或大过载的情况下，将发生损坏。损坏效果包含了起落架坍塌、机翼折断等。您在飞机菜单中可以选择关闭损坏功能。同时，在飞机菜单中还可选择修复飞机。

现在本机模的机窗拥有起雾和起霜效果，是否起雾起霜取决于机舱外部与内部的气温。飞行员必须使用机舱加热和机舱气流控制杆（位于襟翼操作杆右侧）来控制舱内气温。这个效果亦可在飞机菜单中被关闭。该效果依赖于FlightGear 3.5及以后版本中的ALS实现，在FlightGear 3.5以前的版本中会出现窗户变灰的现象。

该机模的空气动力模型十分精确。比如说，飞机可能会在进入不对称失速时进入螺旋状态。本机模的气动模型（FDM）也可以模拟在水上起降时的气动效果，以及使用新的180HP引擎时的气动效果。

这架飞机有许多涂装可供选用，包括一些在涂装选择界面标注了“HD”的高清涂装。每一个高清涂装都包括了独特的驾驶舱和客舱贴图。

这架飞机模拟了 [[Bendix/King KAP140 Autopilot]].

与此同时，如果您在FlightGear中启用了ALS (Atmospheric light scattering)渲染功能，便可以在 "Cessna 172P" 菜单中开启手电筒功能，并可在白光、红光中切换。

现在，本飞机支持航前检查。你可以安放、取下轮档、固定绳以及皮托管套，也可以进行燃油管理，检查燃油是否被水污染。这两项功能可以在Aircraft Options中启用。

本机模还模拟了化油器结冰的情况。化油器中积聚的冰会导致动力损失。开启化油器加热有助于融化积冰。如果在使用化油器加热时发动机开始发出异响，这意味着化油器中确实积聚了冰，现在正在融化。可以调节混合比以减少在融化过程中的异响。

从2016.3版本开始，可以在地勤设备对话框（Ground Equipment）中调出静态物体。这些物体包括翼下的锥桶、燃油车、地面电源装置和梯子。地面电源可以用来给电池充电，燃油车可以用来加注燃料。驾驶员可以通过朝着梯子走动爬上梯子，这样就可以轻松抵达油箱盖以进行加油。[[File:c172p-ALS-flashlight2.jpg|500px|center|Cessna 172P's flashlight in the cockpit]]

== 掌控这架飞机 ==

=== 航前准备 ===
[[File:C172p-secured-Aosta.jpg|270px||thumb|Cessna 172P secured at Aosta Airport]]
建议在执行以下程序时使用外部视图或激活步行者（walker）功能。
* 燃油量：通过点击每个机翼上方的燃油箱盖来添加燃料（您也可以在地勤设备对话框中添加梯子，然后用步行者爬上梯子）。
* 左机翼：移除系留
* 左机翼：移除皮托管套
* 左机翼：点击机翼下方检查燃料是否受污染，并取燃料样本。如果样本呈浅蓝色，表示燃料未受污染，可以放回燃油箱。如果样本是透明或部分透明的，必须丢弃它，并取新样本直到完全呈浅蓝色。
* 机尾：移除系留
* 右机翼：移除系留
* 右机翼：检查燃料是否受污染
* 机头：通过点击机头的机油门来检查机油油量。两台引擎的关键油位为5.0夸脱。
* 机头：移除轮档

=== 引擎启动 (复杂的手动启动) ===
* 喷油（Priming）: 至少进行3次喷油操作
* 混合比：富油（将红色推杆完全推入）
* 油门：开启1/8（将黑色推杆推至20%左右的位置）
* 驻车刹车：已开启 ({{Key press|Shift|B}})
* 螺旋桨区域: 净空
* 主开关：打开 (两个引擎)
* 电磁开关：两者均打开 (按下 {{Key press|<nowiki>}</nowiki>}} 三次)
* 点火: 启动 ({{Key press|S}})

=== 引擎启动 (使用AutoStart自动启动) ===
* 点击“Cessna C172P”菜单，选择“Autostart”以启动飞机。请注意，Autostart尝试以完全富油的混合比来启动引擎，因此如果您从非常高海拔的机场起飞，可能需要手动启动飞机。

=== 起飞 ===
[[File:c172p-cockpit.jpg|270px||thumb|Cessna 172P ready for take off]]
* 无襟翼
* 油门推满
* 空速55节时抬头

=== 爬升 ===
* 无襟翼
* 油门推满
* 空速保持75节

=== 巡航 ===
* 油门65%
* 混合器富油
* 空速保持在100节左右

=== 着陆 ===
[[File:c172p-landing2.jpg|270px||thumb|Cessna 172P about to touch down]]
* 满襟翼
* 空速60节

=== 空速 ===
: ''另外参见 [[Aircraft speed#V speeds]]''

该部分的信息基于外部资料提供。<ref>[http://www.triangleaviation.com/1982_172r.html Triangle Aviation]{{dead link|2015-10}}</ref><ref>[http://www.otisair.com/c172info.html OtisAir's Airborne Observations]{{dead link|2015-10}}</ref><ref>{{cite web |url=http://www.airweb.faa.gov/Regulatory_and_Guidance_Library/rgMakeModel.nsf/0/724e90061c5bf3b1862576260063e599/$FILE/3A12.pdf |title=Type Certificate No. 3A12, Revision 79 |date=27 August 2009 |work= |publisher=FAA |format=pdf |accessdate=9 October 2015}}</ref>

{| class="wikitable"
! Airspeed !! CAS
|-
| Stall speed, landing configuration, VS0 || 33 kt
|-
| Stall speed, clean, VS1 || 44 kt
|-
| Rotation speed, VR || 55 kt
|-
| Best angle of climb speed, VX || 59 kt
|-
| Best rate of climb speed, VY || 76 kt
|-
| Maximum flap extended speed, VFE || 85 kt
|-
| rowspan="2" valign="top" | Maneuvering speed, VA || 96 kt (floatplane)
|-
| 99 kt (landplane)
|-
| Maximum structural cruising speed, VNO || 127 kt
|-
| Never exceed speed, VNE || 158 kt
|}

== 常见问题 ==

这里列出了一些人们频繁询问的有关本机模的问题：

问：为什么我的飞机窗户是灰色的？

答：如果你的飞机窗户呈灰色，您可能使用的是不正确的FlightGear版本。此飞机要求使用3.5版本或以上。

问：为什么飞机一直向左转？

答：请参考[[understanding Propeller Torque and P-Factor]]。如果在坚实的跑道上使用浮筒构型，注意在滑行时需要使用差速刹车（随着飞机加速，方向舵会变得越来越有效）。

问：为什么引擎无法启动？

答：您可以通过点击“Cessna C172P”菜单，然后选择“Autostart”来自动启动引擎。对于手动启动，请按照“帮助”菜单下的“飞机检查单”中提供的清单进行操作。如上所示，启动前必须进行“预喷油（Prime）”。如果开启了机油模拟功能，您必须确保引擎有足够的机油（超过5.0夸脱）才能正常工作。如果开启了燃料污染模拟，燃料必须呈浅蓝色才能使引擎正常工作。您还必须确保电池电量足够（可以在“飞机选项”对话框中检查并对其充电）。

问：为什么Autostart无法启动引擎？

答：可能是因为您正试图从非常高海拔的机场起飞。Autostart始终尝试以混合比完全富油的方式启动引擎，如果未能正常完成，那么您必须在适当倾斜混合比后手动启动引擎。

 
问：为什么引擎启动后立即熄火？

答：可能是因为启动后油门加得太急，引擎需要几秒钟来稳定下来。

问：为什么无法以引擎启动好的状态进入模拟器？

答：您可以！转到“Cessna C172P”菜单，选择“飞机选项”，然后勾选“以已启动引擎启动（Start with engine running）”。

问：为什么电池经常耗尽？

答：就像在真实飞机中一样，当引擎未运行时，保持电池开关打开不是一个好主意，因为电池会耗尽电量。当引擎运行时，交流发电机会确保电池始终在被充电。如果电池电量用尽，可以在“飞机选项”对话框中充电。

问：为什么飞机不动？

答：如果您打开了驻车制动，或者机翼系留、机尾系留或轮档中有任何一个还在位（如果在飞机菜单中启用了“允许固定飞机”的选项），飞机将不会移动。

问：为什么空速指示器不起作用？

答：如果在飞机菜单中启用了“允许固定飞机”的选项，那么很可能是您忘记了移除皮托管套。

问：如何切换到大轮胎/浮筒/两栖飞机构型？

答：通过点击“Cessna 172P”菜单，选择“飞机选项”，然后选择其他起落架选项来切换。

问：如何切换到180 HP引擎？

答：也是通过点击“Cessna 172P”菜单，选择“飞机选项”，然后选择引擎功率选项来切换。

问：为什么我无法在不损坏飞机的情况下从水面起飞？

答：在水面起降可能会有些难度。尝试在加速到55节KIAS时轻轻向后施加升力。建议使用180 HP引擎而不是默认的160 HP引擎，因为浮筒的额外重量会使使用默认引擎难以爬升。

问：为什么模拟器卡得那么厉害？

答：与旧版本相比，这个新版本的C172p模型对计算机的要求更高，就像其他复杂的3D模型一样。如果性能有问题，尝试使用分辨率较低的非高清涂装，以及其他可以改善性能的解决方案（在渲染选项中禁用某些图形选项，降低FlightGear的分辨率等）。

一些提高帧率的技巧包括禁用所有GUI窗口，包括菜单栏和屏幕底部的橙色fps计数器。您可以通过“调试”菜单，然后选择“循环屏幕统计信息”来在左上角显示备用fps计数器。确保按F10隐藏菜单栏以查看计数器。

第二个技巧是如果您不介意，禁用所有云层的渲染：使用"--prop:/sim/rendering/draw-mask/clouds=0"启动FlightGear。

如果您飞越某些景观时出现严重的减速，并且在终端或日志文件中看到FlightGear生成了许多“Warning:: Picked up error in TriangleIntersect”消息，您可以通过使用"--prop:/sim/rendering/osg-notify-level=fatal"启动FlightGear来禁用此功能。

问：为什么窗户开始起雾/结冰？

答：如果机舱内空气温度的露点高于风挡的表面温度，窗户将变得雾化或结冰。使用机舱加热（Cabin Heat）和机舱通风（Cabin Air）推杆（位于襟翼右侧）来控制它。机舱内的湿度和温度上升，露点也会上升，而且上升速度比风挡温度能够调整的速度要快，导致发生暂时的起雾现象。如果空气非常湿润，露点很可能非常接近机舱温度，这使得露点可能高于风挡温度。额外的乘客会在机舱内产生更多的湿空气。尝试通过使用机舱通风控制杆或机舱顶部气流口来增加气流，以减少湿度或温度。或者，通过转到“Cessna 172P”菜单，选择“飞机选项”，然后禁用“启用结霜和雾化”选项来禁用此效果。

问：如何增加机舱空气温度？

答：通过打开机舱加热控制杆来增加机舱空气温度。为了真正获得加热的气流，您需要中等或高的EGT（排气气温，可以从位于操纵杆和ADF仪器之间的仪表查看），以及足够的空速和/或足够的螺旋桨转速。

问：如何点击被操纵杆遮挡的开关？

答：您可以通过点击它来隐藏操纵杆，或者转到“Cessna 172P”菜单，选择“隐藏/显示操纵杆”。

问：为什么我的引擎似乎失去了动力？

答：假设您已经根据海拔和大气压正确调整了混合比，那么另一个可能性是发生了化油器积冰，导致动力丧失。开启化油器加热，冰应该会慢慢融化。注意，如果在应用化油器加热时引擎出现异响，说明正在冰正在被融解，这表明的确发生了化油器结冰。您可以调整混合比以减少在融化过程中的异响。

== 开发状态/问题/TODO ==

对于本机模的开发依然正在进行，您可以在[https://github.com/Juanvvc/c172p-detailed repository]进行查看，同时您还可以查看[https://github.com/Juanvvc/c172p-detailed/issues list of issues and future enhancements]。

== 画廊 ==

<gallery mode="packed">
File:C172p-plane5.jpg|巴西Chapada Diamantina上空的塞斯纳172P
File:C172p-plane4.jpg|塞斯纳12P从 Compiegne Margny (LFAD)起飞
File:C172p-cockpit2.jpg|即将降落。这张图片展示了全新的驾驶舱ALS阴影效果。
File:C172p-floats.jpg|旧金山上空的浮筒版本
File:C172p-plane3.jpg|Cessna 172P 在高空飞过意大利的 Lago di Garda
File:C172p-landing.jpg|在Aosta Airport(LIMW)的五边
File:C172p-cockpit3.jpg|新C172P的内饰，贴图均经过重新制作
File:C172p-night.jpg|一次夜间飞行，这张截图展示了仪表灯光
File:C172p-particles.jpg|水上起飞，这张图片展示了粒子效果
File:C172p-plane1.jpg|在巴西 Serra do Mar 上空
File:C172p-plane2.jpg|翱翔于夕阳之中
File:C172p-winter.jpg|欧罗巴冬日
File:C172p-damage.jpg|重着陆导致的起落架坍塌
File:C172p-frost.jpg|如果条件恰到好处，窗户上将出现薄霜或薄雾。
File:C172p-taubate.jpg|在巴西 Taubate 上空飞行
</gallery>

==外部链接 ==
* [http://en.wikipedia.org/wiki/Cessna_172 Wikipedia article]
* [http://www.aerodynamicaviation.com/wp-content/uploads/2016/03/C172P-checklist.pdf Cessna 172 checklist at aerodynamicaviation.com]

{{Appendix}}

{{Cessna}}

[[Category:Aircraft with a cockpit-only autopilot]]

[[ar:Cessna 172P]]
[[ca:Cessna 172P]]
[[de:Cessna 172P]]
[[en:Cessna 172P]]
[[es:Cessna 172P]]
[[fr:Cessna 172P]]
[[nl:Cessna 172P]]
[[ru:Cessna 172P]]

Translation requests

2024-04-06T07:31:17Z

Sidiliang: Updated translation status

Please post your translation requests here, so that other people can more easily track what's going on, hopefully avoiding duplicate efforts.

*How to translate is described here: [[Help:Translate]].

== Currently work in progress ==
*Please see table below.
*Please add {{tl|BeingTranslated}} to articles that are being translated, remove this when you are finished.
*Please add {{tl|UpdateTranslation}} to articles that have an up-to-date English version but an out-of-date local version.
*Also look at [[:Category:Articles being translated]].

== Open translation requests ==
Check out [[Special:Statistics]] for the most viewed pages:

{| class="wikitable" style="text-align: center"
! [[#Language map|en]]
! [[#Language map|ar]] 
! [[#Language map|ca]] 
! [[#Language map|de]] 
! [[#Language map|el]] 
! [[#Language map|es]] 
! [[#Language map|fa]] 
! [[#Language map|fi]] 
! [[#Language map|fr]] 
! [[#Language map|it]] 
! [[#Language map|ja]] 
! [[#Language map|nl]] 
! [[#Language map|pl]] 
! [[#Language map|pt]] 
! [[#Language map|pt-br]] 
! [[#Language map|ru]] 
! [[#Language map|sl]] 
! [[#Language map|sr]] 
! [[#Language map|sv]] 
! [[#Language map|th]] 
! [[#Language map|zh]] 
|- style="font-weight:bold"
| style="text-align: left" | [[Help:Translate]]
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:ca:Help:Traduir}} 
|| {{progressbar|100|10|link=:de:Help:Übersetzen}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:es:Help:Traducir}} 
|| {{progressbar|100|10|link=:Fa:راهنمایی:ترجمه}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:fr:Help:Traduire}} 
|| {{progressbar|100|10|link=:it:Help:Tradurre}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:nl:Help:Vertalen}} 
|| {{progressbar|100|10|link=:pl:Pomoc:Tłumaczenie}} 
|| {{progressbar|100|10|link=:pt:Help:Traduzir}} 
|| {{progressbar|100|10|link=:pt-br:Help:_Traduzir}} 
|| {{progressbar|100|10|link=:ru:Справка:Перевод}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|100|10|link=:sv:Hjälp:Översättning}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|| {{progressbar|0|10|link=Help:Translate}} 
|- style="font-weight:bold"
| style="text-align: left" | [[Main Page]]
|| {{progressbar|90|10|link=:ar:Main_Page}} 
|| {{progressbar|100|10|link=:ca:Portada}} 
|| {{progressbar|100|10|link=:de:Hauptseite}} 
|| {{progressbar|0|10|link=:el:Αρχική}} 
|| {{progressbar|100|10|link=:es:Portada}} 
|| {{progressbar|100|10|link=:fa:Persian}} 
|| {{progressbar|100|10|link=:fi:Etusivu}} 
|| {{progressbar|100|10|link=:fr:Accueil}} 
|| {{progressbar|100|10|link=:it:Pagina principale}} 
|| {{progressbar|80|10|link=:ja:トップページ}} 
|| {{progressbar|100|10|link=:nl:Hoofdpagina}} 
|| {{progressbar|100|10|link=:pl:Strona główna}} 
|| {{progressbar|100|10|link=:pt:Página principal}} 
|| {{progressbar|0|10|link=:pt-br:Página principal}} 
|| {{progressbar|100|10|link=:ru:Заглавная страница}} 
|| {{progressbar|80|10|link=:sl:Main Page}} 
|| {{progressbar|80|10|link=:sr:Main Page}} 
|| {{progressbar|0|10|link=Main Page}} 
|| {{progressbar|80|10|link=:th:Main Page}} 
|| {{progressbar|100|10|link=:zh:首页}} 
|-
| style="text-align: left" | [[Aircraft]]
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:ca:Aeronau}} 
|| {{progressbar|100|10|link=:de:Flugzeuge}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:es:Aeronaves}} 
|| {{progressbar|100|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:fi:Lentokoneet}} 
|| {{progressbar|100|10|link=:fr:Avions}} 
|| {{progressbar|100|10|link=:it:Aerei}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:nl:Luchtvaartuigen}} 
|| {{progressbar|100|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:pt:Aeronaves}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|100|10|link=:ru:Самолет}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|| {{progressbar|0|10|link=Aircraft}} 
|-
| style="text-align: left" | [[Altitude]]
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:ca:Altitud}} 
|| {{progressbar|90|10|link=:de:Flughöhe}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:es:Altitud}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:fr:Altitude}} 
|| {{progressbar|100|10|link=:it:Altitude}}
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:nl:Vlieghoogte}} 
|| {{progressbar|100|10|link=pl:Wysokość}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|100|10|link=:ru:Высота полёта}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|| {{progressbar|0|10|link=Altitude}} 
|-
| style="text-align: left" | [[Cessna 172P]]
|| {{progressbar|90|10|link=:ar:Cessna 172P}} 
|| {{progressbar|100|10|link=:ca:Cessna 172P}} 
|| {{progressbar|100|10|link=:de:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:es:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|50|10|link=:fr:Cessna 172}} 
|| {{progressbar|100|10|link=:it:Cessna_172P}}
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:nl:Cessna 172P}} 
|| {{progressbar|100|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|100|10|link=:ru:Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|0|10|link=Cessna 172P}} 
|| {{progressbar|10|10|link=:zh:Cessna 172P}}
|-
| style="text-align: left" | [[FGAddon]]
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|40|10|link=:ca:FGAddon}} 
|| {{progressbar|50|10|link=:de:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|100|10|link=:fr:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|100|10|link=:nl:FGAddon}} 
|| {{progressbar|100|10|link=:pl:FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|| {{progressbar|0|10|link=FGAddon}} 
|-
| style="text-align: left" | [[FlightGear]]
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:ca:FlightGear}} 
|| {{progressbar|100|10|link=:de:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:es:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|100|10|link=:fr:FlightGear}} 
|| {{progressbar|100|10|link=:it:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|50|10|link=:nl:FlightGear}} 
|| {{progressbar|100|10|link=:pl:FlightGear}} 
|| {{progressbar|100|10|link=:pt:FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|| {{progressbar|0|10|link=FlightGear}} 
|-
| style="text-align: left" | [[FlightGear hangars]]
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|100|10|link=:ca:Hangars de Flightgear}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|90|10|link=:es:Hangares_Flightgear}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|90|10|link=:fr:FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|100|10|link=pl:FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|| {{progressbar|0|10|link=FlightGear hangars}} 
|-
| style="text-align: left" | [[FlightGear Launch Control]]
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:de:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:fr:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|100|10|link=:nl:FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|| {{progressbar|0|10|link=FlightGear Launch Control}} 
|-
| style="text-align: left" | [[Flying the helicopter]]
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:de:Fliegen mit dem Helikopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:es:Volando el helicoptero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:fr:Piloter l'hélicoptère}} 
|| {{progressbar|100|10|link=:it:Pilotare un elicottero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|100|10|link=:nl:Vliegen met de helicopter}} 
|| {{progressbar|50|10|link=:pl:Lot śmigłowcem}} 
|| {{progressbar|50|10|link=:pt:Voando de Helicóptero}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|| {{progressbar|0|10|link=Flying the helicopter}} 
|-
| style="text-align: left" | [[Frequently asked questions]]
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:de:FAQ}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:es:Preguntas frecuentes}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:fr:Foire aux questions}} 
|| {{progressbar|100|10|link=:it:Domande_frequenti}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|100|10|link=:nl:veel gestelde vragen}} 
|| {{progressbar|100|10|link=:pl:FAQ}} 
|| {{progressbar|50|10|link=:pt:FAQ}} 
|| {{progressbar|0|10|link=:pt-br:Perguntas frequentes}} 
|| {{progressbar|10|10|link=:ru:ЧаВо}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|| {{progressbar|0|10|link=Frequently asked questions}} 
|-
| style="text-align: left" | [[Howto:Install scenery]]
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:de:Szenerie installieren}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:es:Instalación de escenarios}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:fr:Installer une scène}} 
|| {{progressbar|50|10|link=:it:Come fare:Installare scenari}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|100|10|link=:nl:Scenery_installeren}} 
|| {{progressbar|100|10|link=:pl:Instalowanie scenerii}} 
|| {{progressbar|100|10|link=:pt:Instalando Cenário}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|| {{progressbar|0|10|link=Howto:Install scenery}} 
|-
| style="text-align: left" | [[Howto:Multiplayer]]
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:de:Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:es:Howto:Multijugador}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:fr:Howto:Multijoueur}} 
|| {{progressbar|50|10|link=:it:Come fare:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:nl:Howto:Multiplayer}} 
|| {{progressbar|100|10|link=:pl:Konfiguracja trybu multiplayer}} 
|| {{progressbar|100|10|link=:pt:Tutorial de Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|| {{progressbar|0|10|link=Howto:Multiplayer}} 
|-
| style="text-align: left" | [[Help:Gallery of messagebox templates|Messagebox templates]] 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|20|10|link=:de:Help:Messagebox Vorlagengalerie}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|20|10|link=:fr:Help:Galerie de modèles de messagebox}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|| {{progressbar|0|10|link=Help:Gallery of messagebox templates}} 
|-
| style="text-align: left" | [[New to FlightGear]]
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:ca:Nou a FlightGear}} 
|| {{progressbar|50|10|link=:de:Neu bei FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:es:Nuevo en FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:fr:Nouveau sur flightgear}} 
|| {{progressbar|50|10|link=:it:Nuovo per FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:nl:Nieuw bij FlightGear}} 
|| {{progressbar|100|10|link=:pl:Nowy_w_FlightGear}} 
|| {{progressbar|100|10|link=:pt:Novo no FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|0|10|link=New to FlightGear}} 
|| {{progressbar|100|10|link=:zh:FlightGear新手}} 
|-
| style="text-align: left" | [[Portal:User]]
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:ca:Portal:Usuari}} 
|| {{progressbar|100|10|link=:de:Portal:Benutzer}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|50|10|link=:es:Portal:Usuario}} 
|| {{progressbar|40|10|link=Fa:Portal:کاربر}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|50|10|link=:fr:Portal:Utilisateur}} 
|| {{progressbar|100|10|link=:it:Portal:Utente}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:nl:Portal:Gebruiker}} 
|| {{progressbar|90|10|link=:pl:Portal:Dla użytkowników}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=:pt-br:Portal:Usuario}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|0|10|link=Portal:User}} 
|| {{progressbar|100|10|link=:zh:Portal:用户}} 
|-
| style="text-align: left" | {{obr}}[[Template:infobox aircraft#Full_translation|infobox aircraft]]{{cbr}}
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|90|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|50|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} 
|| {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} 
|-
| style="text-align: left" | {{tl|Main page/Languages}}
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|0|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|| {{progressbar|100|10|link=Template:Main_page/Languages}} 
|-
| style="text-align: left" | [[TerraSync]]
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:de:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:es:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|50|10|link=:fr:TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|100|10|link=:nl:Terrasync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|| {{progressbar|0|10|link=TerraSync}} 
|-
| style="text-align: left" | [[Troubleshooting problems]]
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:de:Problemlösung}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:es:Resolviendo_problemas}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:fr:Troubleshooting Problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|100|10|link=:nl:Problemen oplossen}} 
|| {{progressbar|100|10|link=:pl:Rozwiązywanie_problemów}} 
|| {{progressbar|100|10|link=:pt:Resolvendo Problemas}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|| {{progressbar|0|10|link=Troubleshooting problems}} 
|-
| style="text-align: left" | New article
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|| {{progressbar|0|10|link=}} 
|}

* Please help to translate any pages that are not complete. Carefully check the history of the article to be sure that someone else is not currently translating the article.
* For completed entries, please compare to the English version of the article to make sure that new content has been translated.
* English is the primary language of this wiki. Content present in a translation but not in the English article will be, with time, deleted. Always add new content to both the translation and the original English.
* A translated page must be linked to from all other translated pages.
* Help and keep this page up-to-date please (so to avoid double work).

=== Language map ===

Here is an alphabetically ordered language map:

{| class="wikitable" style="text-align: center"
! ISO language code
! Name
! English name
|-
| en || English || English
|-
| ar || العربية || Arabic
|-
| ca || Català || Catalan
|-
| de || Deutsch || German
|-
| el || Ελληνικά || Greek
|-
| es || Español || Spanish
|-
| fa || فارسی || Persian
|-
| fi || Suomi || Finnish
|-
| fr || Français || French
|-
| it || Italiano || Italian
|-
| ja || 日本語 || Japanese
|-
| nl || Nederlands || Dutch
|-
| pl || Polski || Polish
|-
| pt || Português || Portuguese
|-
| pt-br || Português do Brasil || Brazilian Portuguese
|-
| ru || Русский || Russian
|-
| sl || Slovenščina || Slovene
|-
| sr || Српски / srpski || Serbian
|-
| sv || Svenska || Swedish
|-
| th || ไทย || Thai
|-
| zh || 中文 || Chinese
|}

[[Category:Contribution requests]]

Follow me e-tron

2024-01-01T08:29:14Z

Sidiliang: v5.2

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

At its core is a realistic electric engine, meticulously programmed in Nasal, complemented by a detailed electrical system, also written in Nasal. For driving assistance, it includes an advanced steering helper and unique systems like 'AutoCrash' and 'AutoSpeed'. The vehicle's functionality is further enhanced with an Auto Hold feature, parking radar, and working airbags. It also experiments with an Advanced Emergency Braking (AEB) system.

The interior of the Follow me EV is highly customizable, offering several fully remodeled interiors with operational switches. Users can choose from various instrument styles, including a Canvas glass display instrument tailored for specific interior designs.

For personalization, the Follow me EV offers selectable license plates in a Chinese style and a variety of liveries. It is fully equipped for multiplayer interaction, supporting multiplayer passengers, dynamic scenery object placement, and management.

A standout feature is its limo variant, adding a touch of luxury and uniqueness.

These features collectively make the Follow me EV a pioneering model in the FlightGear universe, combining realism, customization, and innovation.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me EV is currently released as v5.2.

=== Change Log ===
V5.2 Updates:

* The advanced steering received a major update and renamed to realistic steering, adapted the Pacejka tire model into the calculation which should provide more realism.

* Various bug fixes and optimization.

* Improved aircraft help and documentation.

* Added drifting sound.

* New splash screen images.

* New preview image.

V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figures below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png| Three Followme EVs lining up
File:Followme EV in a charging station.png| Followme EVs in a charging station, showing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png| Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png| Followme EV in a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png| Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png | Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png| Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Follow me e-tron/info

2024-01-01T04:57:42Z

Sidiliang:

<includeonly>{{infobox aircraft
| name = Follow Me e-tron
| aircraft = Follow Me e-tron
| image = Preview-etron 4.0.jpg
| image2 = Preview-etron.png
| type = Automobile/Utility vehicle
| devel-team = FlightGear China
| authors = 梁思地 Sidi Liang/罗启元 Qiyuan Luo/ValKmjolnir/李维昊 Weihao Lee/Marsdolphin
| fdm = JSBsim
| fgname = followmeEV/followme-PAX
| status-fdm = 4
| status-systems = 3
| status-cockpit = 5
| status-model = 4
| craft = vehicle
| ready = tutorials
| devel-website = https://www.fgprc.org.cn/followmeev.html
| devel-repo = https://github.com/FGPRC-FlightGearChina/followme_e-tron
| download = https://github.com/sidi762/followme_e-tron/archive/refs/tags/v5.1.zip
| forumtid = 36211
| licence = GPLv2
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Follow me e-tron]].
[[Category:Aircraft infobox documentation]]
</noinclude>

Follow me e-tron

2024-01-01T04:35:55Z

Sidiliang: Added more description

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

At its core is a realistic electric engine, meticulously programmed in Nasal, complemented by a detailed electrical system, also written in Nasal. For driving assistance, it includes an advanced steering helper and unique systems like 'AutoCrash' and 'AutoSpeed'. The vehicle's functionality is further enhanced with an Auto Hold feature, parking radar, and working airbags. It also experiments with an Advanced Emergency Braking (AEB) system.

The interior of the Follow me EV is highly customizable, offering several fully remodeled interiors with operational switches. Users can choose from various instrument styles, including a Canvas glass display instrument tailored for specific interior designs.

For personalization, the Follow me EV offers selectable license plates in a Chinese style and a variety of liveries. It is fully equipped for multiplayer interaction, supporting multiplayer passengers, dynamic scenery object placement, and management.

A standout feature is its limo variant, adding a touch of luxury and uniqueness.

These features collectively make the Follow me EV a pioneering model in the FlightGear universe, combining realism, customization, and innovation.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me e-tron is currently released as v5.1.

=== Change Log ===
V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figure below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png| Three Followme EVs lining up
File:Followme EV in a charging station.png| Followme EVs in a charging station, showing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png| Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png| Followme EV in a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png| Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png | Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png| Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Zh/FlightGear新手

2023-12-27T14:12:34Z

Sidiliang: Finished and polished the Chinese translation of New to FlightGear

{| class=toccolours align="center" style="text-align: center; width: 80%; font-size: 85%; clear:both; margin-top:1em; margin-bottom:-0.5em; border-left: 15px solid orange;"
| '''当前中译本翻译自英文页面的[https://wiki.flightgear.org/w/index.php?title=New_to_FlightGear&oldid=137880 137880版本]。'''
若根据英文页面的后续版本更新此中文翻译，不要忘了将所参考英文页面的版本号一并更新到上面。
|}

欢迎来到[[FlightGear]]！接下来我们会尽力在最短时间内带你在虚拟天空里飞起来。我们也会向你介绍该飞行模拟器的一些特性以及我们社区的若干信息。

== 安装与设置 ==
=== 硬件需求 ===
（译注：FlightGear一般来说不吃配置，只要不是很老的低配电脑都可以试一试，当然可能需要调整画质等设置）

为了流畅地运行FlightGear，您需要一块有OpenGL 2.0或更高版本驱动程序的显卡。一般来说这不是问题，但您可以查看[[Hardware Recommendations|硬件建议]]以获得更好的了解。

由于笔记本显卡通常较为低端，已知很多笔记本运行FlightGear时存在一些问题。对一些笔记本的评测见[[Laptops known to run FlightGear|已知可以运行 FlightGear 的笔记本]]。

=== 获取FlightGear ===
{| class=toccolours align="center" style="text-align: center; width: 80%; font-size: 85%; clear:both; margin-top:1em; margin-bottom:-0.5em; border-left: 15px solid orange;"
| '''强烈建议中国内地用户从[https://mirrors.tuna.tsinghua.edu.cn/flightgear/ftp/ TUNA镜像站]下载FlightGear，以保证下载速度。'''
安装文件位于其中的<code>release-<大版本号></code>文件夹下，Windows用户请选择下载该文件夹下的<code>FlightGear-<小版本号>.exe</code>。该镜像站也提供部分机模与地景下载。
'''此外，[[FlightGear China|FlightGear中国飞友会（或FGPRC）]][https://www.fgprc.org.cn 官网]也可下载macOS和Windows平台最新LTS版本的FlightGear。'''
|}

您可以从 [http://www.flightgear.org/download/ FlightGear 下载] 页面下载最新版本的文件。根据您的系统选择源代码或二进制文件。2020.3 LTS 及之后的版本还提供了适用于 Linux 的 {{Wikipedia|AppImage|AppImage}}二进制文件。大多数Linux用户会发现大多数发行版都有打包的FlightGear版本（包名可能是<code>fgfs</code>或<code>flightgear</code>）。

如果有足够的技术专长，您可以选择FlightGear的[[Git]]开发版本。[[Git]]开发版本通常具有更多功能，而且许多最新的开发中飞机需要其支持，但可能不稳定，对非Windows用户来说获取更复杂。一般来说不建议普通用户使用开发版本，但如果您希望做一些测试，可以从[[FlightGear build server|FlightGear 构建服务器]]下载Windows或Mac的夜间构建（nightly builds），或者每天更新的Ubuntu PPA。现在（2021年3月），夜间构建可从 [https://download.flightgear.org/builds/nightly/ download.flightgear.org] 获取（截止2023年12月该方法依然适用——译者注）。如果您使用 Git 版本控制的 FlightGear 副本，您可以选择使用版本控制的 [[FGAddon|FGAddon 飞机开发仓库]] 同步更新您的飞机。

=== 在Windows上安装 ===
下载安装程序后，运行并遵照指示安装FlightGear。

某些杀毒软件可能会误认为FlightGear有病毒。如果发生这种情况，您可以在安装期间临时禁用您的杀毒软件。

在Windows安装程序中可选择FlightGear的安装位置。[[$FG ROOT]]目录为<code><你选择的目录>/data</code>。

=== 在 macOS 上安装 ===
在 macOS 上安装FlightGear非常简单。只需将FlightGear图标拖放到 <code>/Applications</code> 文件夹即可。

第一次运行FlightGear时，它的图标会在Dock上弹起数秒钟，期间会加载机场和飞机信息。当GUI启动器出现时，选择飞机和机场，之后点击“开始飞行！”就可以启动模拟器。您可以用GUI启动器配置更多选项。更多详情见[http://flightgear.sourceforge.net/manual/next/en/getstart-ench4.html#takeoff-how-to-start-the-program 官方手册]。

如果你想要从命令行启动Flightgear，运行<code>/Applications/Utilities/Terminal.app</code>并键入以下内容。

cd /Applications/FlightGear.app/Contents/Resources
./fgfs --options.....

[[$FG ROOT]]和[[$FG SCENERY]]在macOS上并未设置。如果您想自行指定这些变量供命令行使用，在Terminal.app运行以下内容:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=[[$FG_ROOT]]/Scenery

在运行GUI启动器后，<code>$HOME/Documents/Flightgear/<version></code>将成为[[$FG ROOT]]的别名，因此您可以用Finder来浏览数据目录。

注：Mac用户在安装FlightGear后，在Finder中打开应用程序文件夹，右键点击FlightGear，然后点击“显示软件包内容”，即可找到[[$FG ROOT]]文件夹。这样可以进入FlightGear文件夹访问所有文件，包括可用于[[Howto: Install aircraft#Macintosh OS X|安装新机模]]的Data/Aircraft。（译者注：根据个人使用经验，更推荐将机模安装在一个另外的地方，然后在GUI启动器中添加安装机模的路径，这样在更新FlightGear的时候更方便。）

=== 配置OpenGL ===
FlightGear最适合在当前版本的[[OpenGL]]驱动程序上运行。如果您运行FlightGear时碰到问题，请参见[[Configuring OpenGL|配置OpenGL]]。

=== 获取地景 ===
FlightGear安装时自带少量[[scenery|地景]]，在 FlightGear 2020.3 LTS中包括：
* 版本特色机场[[Keflavik_Airport|凯夫拉维克国际机场]]（BIKF）
* [[Zh/Cessna_172P|塞斯纳172P]]的教程机场[[Hilo_International_Airport|希洛国际机场]]（PHTO）

在FlightGear中，地景一般存放在你的[[$FG ROOT]]目录内，分为三类数据：
* '''机场'''包括跑道用途和停机位等机场数据。
* '''对象'''和'''模型'''为建筑、桥梁和塔台等三维结构。
* '''地形'''代表了轮廓、海拔以及你飞行或滑行所经过的地面类型。

“安装”新地景的现行方式为启用[[TerraSync]]，它会自动下载并更新你到达的任何地方，即使是飞行过程中也可以。如果你的电脑和/或网络缓慢，也可以使用[[TerraMaster]]等地景管理器作为替代。另外也可以手动下载并安装新地景部件，无论是官方的[[World Scenery|世界地景]]还是自定义地景。

官方地景可从FlightGear网站的[http://www.flightgear.org/download/scenery/ 地景下载区]下载（虽然已经过时），并按照[[Howto: Install scenery]]的指导安装。当有更多、更新的地景对象时，可从[http://scenemodels.flightgear.org/ FlightGear地景数据库]获取。'''（建议网速慢或电脑性能差的用户使用此方法）'''

自定义地景在很多地方都有，如{{forum link|f=5|text=FlightGear论坛}}或仓库内，应当可以通过网络搜索找到。部分近期发布的地景见[[Suggested_custom_scenery|推荐自定义地景]]。

FlightGear 2020.3.7 LTS及以上版本实验性地推出了基于整个世界OpenStreetMap数据的三维建筑、道路和对象，将其加入自动下载的TerraSync数据，见[[OSM2City 1st Worldbuild|1st OSM2City world-build]]注释（2021年3月）。[[Areas populated with osm2city scenery|osm2City下载]]页面有一些区域或国家的三维结构的手动下载链接。

=== 获取机模 ===
更多[[aircraft|机模]]可通过[[Qt-launcher|启动器]]下载及安装。或者也可以访问FlightGear网站并前往[http://www.flightgear.org/download/ 下载页面]，然后选择适合你FlightGear版本的机模下载链接。此外还有许多第三方[[hangars|机库]]。安装教程见[[Howto: Install aircraft]]。

== 运行FlightGear ==
=== 启动 FlightGear ===
启动FlightGear最简单的方法就是使用桌面图标。这样会打开图形界面[[FlightGear Qt launcher|FlightGear Qt启动器]]，其中可以选择飞机、起始位置等。需要注意的是，Qt启动器只有开始飞行的基本选项。图形、地景、[[Weather|气象]]、[https://www.flightgear.org/tours/simulating-the-ever-changing-scenery/ 环境]、[[Input_device|输入设备]]等大量选项在模拟器内的菜单中。

很多用户仍然选择直接从命令行启动FlightGear。可执行文件名为<code>fgfs</code>，无需选项即可运行。如果报告“找不到”，则它很有可能不在你的PATH变量里。其位置与你的系统及你在编译及安装时所做的选择有关。很多选项（如欲使用机模）的变更需要使用一系列的[[Command Line Parameters|命令行参数]]，其中最主要的是：

fgfs --launcher # 打开FlightGear Qt启动器
fgfs --show-aircraft # 显示已安装机模的列表
fgfs --aircraft=c172p # 使用机模"c172p"启动FlightGear（从列表选择）

对于通常在模拟器内部菜单中更改的选项，以及只能通过命令行使用的高级选项，用户也可在Qt启动器中添加命令行参数（2020年8月时）。

=== 使用键盘和/或鼠标 ===
缺少[[joystick|操纵杆]]或其他控制器的用户有时会用键盘或鼠标控制飞机。使用键盘来飞行是一件有难度的事情，所以比起键盘更推荐用鼠标飞行，但即使是廉价操纵杆也能够极大地提升体验。

在FlightGear运行时，要获取键盘命令帮助，请前往''Help''菜单，选择下面的''Basic Keys''（模拟器相关命令）、''Common Aircraft Keys''（所有机模通用的命令）和''Aircraft Help''（机模特有的按键命令) 。若主菜单被隐藏请按{{key press|F10}}。

如果以前使用过其他模拟器，则FlightGear与其他模拟器之间按键命令的区别见[[key commands compared to other simulators]]。

要使用鼠标飞行，按{{key press|Tab}}（鼠标指针应变为十字形）并移动鼠标引导飞机，再次按{{key press|Tab}}可以环视四周（鼠标指针应变为双箭头），再次按{{key press|Tab}}回到普通模式点击驾驶舱内的东西。不过该操作有可能不适用于某些飞机，如[[A320neo]]及[[Airbus A330 (disambiguation)|A330]]等（这取决于机模开发者的设计——译者注），所以只能通过右击环视四周，鼠标模式无法使用。好在这些飞机是很稳定的客机，用键盘飞起来也很容易。

=== 首次进入驾驶舱 ===
第一次进入驾驶舱并想搞清楚情况的时候可能还是有些吓人的。

虚拟驾驶舱在哪？并不是所有FlightGear机模都有内部驾驶舱模型的，一些研究项目甚至连外部模型都没有。有时2D面板会显示在3D驾驶舱（如果存在）之上。如果要关掉，可以打开''Main Menu'' > ''View'' > ''View Options''然后在''Display Options''部分里取消选中''Show 2D panel''，或者按{{key press|Shift|P}}。在这些情况以外，正常情况下，只要选中了Cockpit View，FlightGear启动时你就应该已经坐在虚拟驾驶舱里了（如果没有，按{{key press|Ctrl|V}}应该可以切换到飞行员视图）。

或许你会觉得仪表板上的一些显示器和仪表难以阅读。可以把鼠标切换到视图模式（按{{key press|Tab}}至鼠标指针变为双箭头）拖动视图或使用鼠标滚轮缩放，也可用摇杆帽移动视图并按{{key press|X}}和{{key press|Shift|X}}缩放。

在进入陌生的驾驶舱时，常用的一项操作是按{{key press|Ctrl|C}}突出显示所有“热点”，即仪表控件、按钮、旋钮等。很多机模也提供专有的帮助菜单。

某些功能，如启动器或磁电机，可能难以使用或根本没有可点击的“热点”，尤其是在开发中的机模上。一般来说可以使用2D面板上的相应控制，或直接使用键盘。根据''Help''所述的按键分配，键盘总是可用的，但有时这些会因为机模或设置的原因被重新分配。一定记得查阅所有的帮助对话框！

=== 起动发动机 ===
你迫不及待地想飞行，但发动机却还没有起动。嗯，发动机的起动并非总是轻而易举。有些机模的自定义菜单中有''自动起动''（autostart）项，不过以下的一般程序应该在很多情况下都管用：

在活塞式飞机上，要起动发动机，一般来说需要：
# 燃油：有些机模在模拟器启动时没有燃油，可在''Equipment'' > ''Fuel and Payload''中添加。
# 正确的燃料混合比：一般是''浓''（rich），所以要把红色操纵柄按到底，或者按{{key press|m}}加浓（{{key press|Shift|m}}是减淡）。
# 磁电机调到''both''：拧钥匙或按{{key press|}}}''三次''，依次切换至''R''、''L''、''Both''。
# 油门：有些发动机放一点油门会有利于起动。
# 接通起动机：点击面板上钥匙的''Start''位置，或者按{{key press|s}}。起动机的接通需要保持足够长的时间，甚至长达10秒。

在多发飞机上起动所有发动机与在单发飞机上类似，只不过每个发动机都需要遵循相同的起动流程。FlightGear提供了一个简便方法，可以一次性为所有发动机应用这一操作：按{{key press|~}}，之后上述的所有程序都会在所有发动机上生效。不过需要注意，默认的2D面板仅连接至''单台发动机''，{{key press|~}}键技巧可能无效。另外，放一点油门保证所有发动机都已起动。

这些指导可能不适用于喷气式飞机、直升机或其它具有复杂起动流程的飞机类型。查阅机模帮助菜单（按{{key press|?}}）内的指导和/或看看[[Aircraft|本wiki上该机模的页面]]。一般来说，要起动喷气式飞机的发动机，需要：
# Set cutoff ''ON''
# 接通起动机
# 一旦发动机转速达到约5% N1， set cutoff ''OFF''
# 当发动机达到运行转速时切断起动机

=== 在线多人飞行 ===
FlightGear有若干联机服务器，可以让你在更热闹的天空中飞行，详见[[Howto: Multiplayer]]。还有让你可以充当[[Air traffic control|空中交通管制员]]的独立程序[[OpenRadar]]和[[ATC-pie]]。

还有[[MPMap|多人地图]]让你看到当前有谁在线，甚至是附近有何[[Navaids|导航台]]。

== 学习飞行 ==
=== 教程 ===
很多机模都有自己的教程。有了教程，不仅可以学习特定机模的操作，也可以学习飞行。前往''Main menu'' > ''Help'' > ''Tutorial''即可访问教程。塞斯纳172P机模的教程是入门的理想选择，这种飞机在现实中一般用于固定翼飞机的飞行教学。

如果教程启动时没有跑道，四周被水环绕，则该教程所设定的机场相应的地景没有安装到您的FlightGear中。地景的获取见前面[[#获取地景]]一节。

== 进行你的第一次飞行 ==
=== 真实性 ===
对于任何飞行模拟器，尤其是FlightGear，初学飞行员最常问的一个问题是”为什么我的飞机老是向左偏？“或许是因为跑道上有侧风，但这更可能是由于[[Understanding Propeller Torque and P-Factor|螺旋桨扭矩和P因素]]。

在某些其他市售飞行模拟器中，尽管其宣传口号与此相反，他们对某些参数进行了刻意调整来减少包括上述“左偏”在内的许多效果，以使飞机更容易飞行。与此不同的是，在FlightGear中这种忠于'''真实性'''的特性总是默认开启的。

以下列出了一些FlightGear里包含的，可能使许多刚入门的飞行员感到迷惑的现实特性。

* 由于上述原因出现的"左偏综合症"
* 磁罗盘转弯错误:磁罗盘在飞行时受各种力的影响，倾向于在短时间内向相反方向转动，然后再定位在正确的航向上。这不是故障（另见维基百科文章{{wikipedia|Aircraft compass turns}}）。
* 垂直速度指示器（VSI）也容易出错。
* 水平情况指示器（HSI）由陀螺仪驱动（这就是为什么有时叫它方向陀螺仪），它受到“陀螺仪漂移”（“gyro drift”）影响。指示器将从其当前航向漂移，并必须定时（大概每15分钟）校准以与磁罗盘航向一致。
* 你不能只是通过将操纵杆或摇杆居中来取消转弯或爬升。你必须将摇杆或杆向另一个方向转动或推动，以获得水平姿态和水平飞行。但即便在这之后，飞机也不会自己保持其高度或航向。一个常见的错误是试图找到一个可以松开手的操纵杆位置。虽然正确使用配平可以让手空出几秒钟，但要让飞机保持稳定飞行必须使用自动驾驶仪或不断调整操纵杆。（译者注：在一些使用电传飞控的现代化飞机上部分实现了这方面的简化，FlightGear中有许多机模也真实地模拟了这一点，如波音777和空客A320系列。）

飞机飞行时以及控制和导航使用的[[avionics and instruments|航空电子设备和仪器]]上都作用着许多力，这些力可能违反直觉。飞行员必须学会识别这些现象并修正它们的影响。''FlightGear模拟了现实世界中存在的仪表误差''。

=== 机场和导航辅助设备 ===
当您第一次启动FlightGear时，无论是通过命令行还是启动器的图形界面，您可能想知道如何确定哪些机场可用。启动器显示了机场列表，但您不会看到如塔台或[[ILS]]频率等详细信息，也无法找到显示[[VOR]]及其频率的地图。您可以做什么？请查看[[Getting aeronautical charts|获取航空图表]]。

在模拟中，您可以在''主菜单'' > ''设备'' > ''地图''中使用地图，这将使您能够查看导航数据和机场及辅助设施的位置。想要获得更多导航帮助，请参阅[[Understanding navigation|理解导航]]。

=== 使用自动驾驶仪飞行 ===
一些飞机需要您使用''Autopilot''菜单中提供的[[autopilot|自动驾驶仪]]，这是原始的FlightGear自动驾驶仪，是一个"通用"自动驾驶仪。许多飞机都配备了自己特定的自动驾驶仪，通常是现实存在的型号。

对于提供自己的自动驾驶仪的飞机，您应该使用虚拟驾驶舱中可用的自动驾驶仪控制面板，可以通过点击虚拟驾驶舱中的仪表板来操作。在某些提供了自己的自动驾驶仪的飞机中，包括一些空客机模和[[Cessna 172P|C172P]]，自动驾驶仪菜单将变灰且不可用。

塞斯纳172配备了[[Bendix/King KAP140 自动驾驶仪]]。您不能在此飞机上使用菜单中的“Autopilot”对话框，而是必须使用虚拟驾驶舱中的自动驾驶仪设备。

== FlightGear社区 ==
=== 获取帮助 ===
此页面旨在向用户提供他们首次使用FlightGear时需要了解的基本事项。除了本百科站的[[Portal:User|用户门户]]，您可能还想阅读以下页面：
*[[Troubleshooting problems|故障排除]]，帮助您解决最常见的问题；
*[[Frequently asked questions|常见问题解答]]；
...以及可以用来获取信息或请求帮助的沟通渠道：
*[[FlightGear Manual|FlightGear手册]]，这是初学者的必读之物；(译者注：可以在Github上找到佟辉同志译著的该手册的中文翻译版)
*{{forum link|text=FlightGear论坛}}及其子论坛；
*[[Discord|FlightGear的Discord服务器]]，这是获取帮助最快的方式；
*[[FlightGear IRC channel|FlightGear IRC频道]]；
*[[Mailing list|FlightGear用户邮件列表]]，这是与核心开发者联系的最好方式；
*发行安装包中自带的帮助文档。

=== 在不编译的情况下自定义FlightGear ===
[https://www.flightgear.org/download/ 我们的网站]提供了预编译的二进制文件，可供在Windows、macOS和Linux上下载和安装。此外，大多数Linux发行版在其仓库中提供打包版本。

（译者注：服务器位于国内的[https://www.fgprc.org.cn/ FGPRC官网]也提供了macOS和Windows下的二进制文件，这些二进制文件与官网提供的版本完全一致，在中国大陆境内下载速度会快很多。）

注意：FlightGear的配置非常灵活，你可以通过编辑[[XML]] 文件来修改飞机模型或者其他特性，只要你喜欢。当然，这样做没有任何风险，我们鼓励你这么做。同样你也可以与其他FlightGear用户分享你的成果。飞机模型并不是二进制文件，而且一旦你有足够的知识，修改起来很简单。尽管安装文件是二进制的程序，但是FlightGear的绝大部分系统可以通过XML文件和[[NASAL scripting]]来修改。

尽管软件是二进制的，FlightGear的大多数系统都可以通过[[XML]]文件和[[NASAL scripting|NASAL脚本]]配置。您可以自由对机模、地景、贴图、OpenGL[[shader|着色器]]以及您为了满足个人需求或希望与其他FlightGear用户共享的任何其他功能进行更改，并且我们''鼓励''您这样做。如果这正是您的打算，请查看[[Portal:Developer|开发者门户]]。

== 您能做些什么来帮助我们 ==
{{Main article|Volunteer}}
FlightGear 是一个开源的、基于志愿者的项目。这意味着这里的一切都来自于志愿者的热情和业余时间。这包括模拟器本身、地景、飞机、百科文章、{{forum link|text=论坛}}以及其他一切。志愿者，本质上是''做事情的人''，对这个项目至关重要。没有他们，项目就不会向前迈出一步。因此，让贡献者在他们所做的事情中找到乐趣是至关重要的。

如果您希望为这个项目做出贡献，可以先查看一些文章。这些文章可能会给您一些启示：
*[[Howto:Understand the FlightGear development process|如何理解FlightGear开发过程]]
*[[Implementing new features for FlightGear|为FlightGear实现新功能]]
*[[How the FlightGear project works|FlightGear项目是如何运作的]]

贡献者永远不嫌多，而需要志愿者贡献力量的领域有许多：
;测试：
*[[Building FlightGear|构建]]最新的Git代码或从[[FlightGear Build Server|FlightGear构建服务器]]下载快照
*[https://sourceforge.net/p/flightgear/codetickets/ 提交错误报告]
*通过valgrind运行FlightGear以跟踪内存泄漏

;支持：
*帮助新用户下载、编译、安装并运行FlightGear（{{forum link|text=在论坛上}}或在IRC上）
*提供想法和建议，参见：[[Feature Requests / Proposals / Ideas|功能请求/提议/想法]]
*帮助清理和整理这个百科站
*为缺失的百科页面提供新内容

;开发：
*C/C++编程：
**提供源代码清理（本质上是帮助过渡到以SGSharedPtr为主的智能指针基础的内存管理方法）
**提供[[Bugs|错误]]修复或新功能
**参与其他FlightGear相关项目
*机模开发（3D建模、贴图、空气动力学模型（FDM)、脚本编写）
*地景开发（地形、模型、天气）

[[Category:FlightGear]]

[[ca:Nou a FlightGear]]
[[de:Neu bei FlightGear]]
[[es:Nuevo en FlightGear]]
[[fi:Uusi_käyttäjä]]
[[fr:Nouveau sur flightgear]]
[[it:Nuovo per FlightGear]]
[[ja:FlightGear入門]]
[[nl:Nieuw bij FlightGear]]
[[pl:Nowy w FlightGear]]
[[pt:Novo no FlightGear]]
[[sr:Novi u FlightGear-u]]
[[th:New to FlightGear]]
[[zh:FlightGear新手]]

FlightGear China

2023-12-27T07:24:31Z

Sidiliang: Updates

{{User
|name = FlightGear China
|age = 7 (Founded August 2016)
|website = https://www.fgprc.org.cn https://www.fgprc.org
}}

'''FlightGear China''' ('''FGPRC''') is a organization for FlightGear users and fans in China.

[[File:FGPRC logo.png|thumbnail]]

== Services ==
MPMap: https://mpmap.fgprc.org 

MPMap (hosted in China): https://mpmap.fgprc.org.cn

== MP Server ==
We have an MP server network that is not yet connected to the official FlightGear MPServer Network. 

mpcn01.fgprc.org (Located in Beijing, China) (Not available as of December 2023 due to server cost) 

mpcn02.fgprc.org (Located in Singapore) 

== Current Members ==
Currently (as of Dec 2023), we have 179 members in our QQ group.

== Links ==
[https://www.fgprc.org.cn Official Website (Chinese)]
[http://www.fgprc.org Official Website (English)]
[https://github.com/fgprc-flightgearchina Github]

[[Category:Community|China]]

FlightGear China

2023-12-27T07:19:24Z

Sidiliang: /* Current Members */

{{User
|name = FlightGear China
|age = 4 (Founded August 2016)
|website = https://www.fgprc.org https://www.fgprc.org.cn
}}

'''FlightGear China''' ('''FGPRC''') is a organization for FlightGear users and fans in China.

[[File:FGPRC logo.png|thumbnail]]

== Services ==
MPMap: https://mpmap.fgprc.org 

MPMap (hosted in China): https://mpmap.fgprc.org.cn

== MP Server ==
We have an MP server network that is not yet connected to the official FlightGear MPServer Network. 

mpcn01.fgprc.org (Located in NewYork, US) 

mpcn02.fgprc.org (Located in Hangzhou, China) 

== Current Members ==
Currently (as of Dec 2023), we have 179 members in our QQ group.

== Download ==
[https://www.fgprc.org Official Website]
[https://github.com/fgprc-flightgearchina Github]

[[Category:Community|China]]

Template:Disclaimer

2023-12-27T07:09:35Z

Sidiliang:

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{Note|FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| final-fixed-function-release-Chinese = {{
Note|FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试<ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>。
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响运行帧数（无论是变高还是变低）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>。}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Zh/2020.3

2023-12-27T07:07:52Z

Sidiliang:

{{changelogs|prev=2020.1|next=2022.1}}

可用语言: [[Zh/2020.3|中文]]，[[Changelog_2020.3|English]], [[Pl/Changelog_2020.3|Polish]]. 

请协助我们将其翻译为更多语言!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

自由、开源的飞行模拟器FlightGear即将迎来2020.3版本更新。这是FlightGear开始同时提供长期支持版本和预览版本之后的第二个长期支持版本，代表了全球的志愿者们为期两年的开发工作的结晶。FlightGear由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的且无比贴近真实的飞行模拟器。 FlightGear通常被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。

自v2018.3 LTS以来的主要更新包括：
*增加了即将到来的Compositor图形框架的预览，作为单独的二进制文件共同分发。
*对JSBSim和YASim飞行动力学模型进行了更新
*增加了DDS贴图缓存以减少加载时间
*加载更快、更节省内存的建筑
*改善了对航空母舰的支持

此外，官方机库中增加了30架全新的机模，71架机模得到了重大更新。

{{Disclaimer|id=final-fixed-function-release-Chinese}}

始于1997年，FlightGear以其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构为特色。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。

FlightGear - 自由飞翔！

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== 启动器 ==
* 添加了在首次启动时出现的欢迎屏幕，为首次使用的用户提供一些有用的信息。
* 机模插件现在可被标记为个人收藏，并可进行筛选，使得在数百个机模插件中寻找您喜爱的机模变得更容易。
* 启动器增加了对航空母舰的支持，现可在启动器中选择航空母舰以及设置起始位置。
* 当你想开始飞行的时候，现在只需要按下<code> Ctrl-F </code>快捷键！
* 增强了对停机坪和水上机场的支持，增加了对当前的飞机型号的检测。
* 大量错误修正和稳定性改进，尤其对机模和插件选项卡进行了改进。

== 画面 ==
* 此发行版随附[[Compositor]]渲染器以便开发人员预览使用。Compositor渲染器提供了全面支持XML配置的多通道渲染合成方式，并且支持ALS与集群着色。*增加了对DDS贴图缓存的支持，缩短了贴图文件的加载时间。
* 恒星能见度现可根据恒星大小和大气条件进行配置。
* 现可通过设置<code>/rendering/triangle-direction-lights=false</code>，可以使用不定向点精灵（non-directional point sprites）以便在不支持三角形点精灵（triangles of point sprites）的图形驱动器上正确运行。
* 添加了全新的Tower AGL视角。该视角与塔台视角类似，不同之处在于它使地面保持在飞机的正下方，并在飞机移动时平稳地缩放和平移。这使得该视角适合用于观察降落。
* 改善了机场草地贴图
* 新增了沿海地区的潮汐效果。
* 更新了加利福尼亚地区、亚洲地区、巴西北部、冰岛和扬马延（Jan Mayen）岛的区域材质定义（regional material definitions）。
* 增加了新的活火山 - Katla, Eyjafjallajokull, Surtsey.
* 新增基于实例的随机建筑与OpenStreetMap建筑，提高了性能并显著提高了画面质量。
* 改进了机翼弯折着色器。
* 现可从“View”菜单中启用/禁用飞行员模型。

== JSBSim ==
[以下部分翻译使用机器翻译，故部分内容或许将不准确或不自然。欢迎更多志愿者加入到翻译的行列中！] 
[Some part of the following translation is made by a machine translator, so it may be inaccurate or awkward. Any contributions to the translation are welcomed! ]
* 新增了设置涡轮机启动和加速时间的功能（参数<code><n1spinup></code>，<code><n2spinup></code>，<code><n1startrate></code>， <code><n2startrate></code>）。
* 现在，可以通过将<code><integrator></code>过滤器的<code><trigger></code>属性设置为负值，将其重置为0.0。
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* 现在可以在<code><function></code>中使用以下功能：<code>floor</code>，<code>ceil</code>和<code>fmod</code>。它们的功能与相应的C / C ++函数相同。
* <code> <function> </code>现在检查其参数数量。
* 新的系统组件linear_actuator
* 将燃料密度导出到属性树
* 为FCS组件添加了循环裁剪
* 增加了控制涡轮发动机转速下降因子的功能
* [向后兼容性损坏]陀螺仪现在正在测量转速而不是旋转加速度。测量旋转加速度的陀螺仪在现实世界中不存在。
* 飞行控制元件的输出属性不再绑定。这样可以节省许多虚假的警告消息，并允许在多个飞行控制中直接引用相同的属性。
* 现在通过质量分数而不是分压来管理大气中的水蒸气。前者是压力和温度变化时保留的物理量。
* 在尝试修整地面之前，请检查至少3个触点。
* 为FG UDP接口增加了仿真时间的可选传输
* 现在在执行过程中而不是在解析XML定义时检查用于表无关var的属性的存在。这放宽了需要在XML定义文件中声明过滤器，表格以及更一般的飞行控件的顺序。
* 电动引擎RPM现在已在UDP套接字中导出。
* 参数<code><ignitionn2></code>现在影响N2而不是N1。
* 现在在<code><clipto></code>中的max<min时给出警告，而不是引发异常
* 添加了使用新的fgfs可执行参数<code>-jsbsim-output-directive-file</code>在CSV文件中记录属性的功能

== YASim ==
* 改变了静摩擦力
* 新增支持跨音速效果.
* 现可通过设置<code>/fdm/yasim/respect-external-gear-state=true</code>来控制初始起落架状态。
* 新增对电动引擎的支持。

== 气象和环境 ==
* 在活火山附近湍流强度将会增加。
* 现可对METAR URL进行配置。
* 新增对METAR字符串的解码并以可读的形式显示在天气对话框中。

== 航空母舰 ==
* 启动器现支持两种全新的标准状态: <code>carrier-takeoff</code> 与 <code>carrier-approach</code>.
* 加入了全新的命令行参数 <code>--carrier-position</code>。这可用于选择航空母舰上的飞机起始位置。可选择的选项包括航母弹射器(e.g. <code>cat-1</code>)、停机位(e.g. <code>park-1</code>)、FLOLS进近位(<code>flols</code>)或abeam位置(<code>abeam</code>)。
* 现在即使在启动时不可用，GUI也可以检测到MPCarrier。要启用此功能，请设置<code>/sim/mp-carriers/auto-attach=true</code>。

== AI ==
* 增加了新的fgcommands：<code>add-aiobject</code>和<code>remove-aiobject</code>，可用于向AI子系统添加或移除物体。
* 增加了新的AI飞机, 包括波音747货机、CRJ900、SR-71、Saab 340.
* 对许多AI交通时刻表与航空公司涂装进行了更新。
* 新增在KEDW的Space Shuttle TAEM与进近场景。
* 新增了来自当地飞行员的准确Britten-Norman Islander性能数据。

== 联机飞行 ==
* 现可通过GUI使用swift以连接到VATSIM。
* FGComm现在支持COM1和COM2以及音量设置。
* 由机模定义的视角（飞行员视角（Pilot view），直升机视角（Helicopter view），塔台视角（Tower view）等）现在可以在联机飞行中的其他飞机上使用。通过单击“飞行员列表（Pilot List）”对话框的“视图（view）”列，可以查看特定的联机飞机（可在“Multiplayer/Pilot List”菜单下找到）。
* 新增<code>-disable-hold-short </code>选项，当进入联机飞行时，允许用户在跑道上出生。请谨慎使用此选项——突然在跑道上出现会对其他飞行员与ATC造成极大的困扰。
* 回放器现可记录联机中其他飞机的数据。

== Nasal 脚本语言 ==
* 现可配置核心Nasal模块的加载顺序。
* 增加了对通信接口Emesary的改进和错误修复。
* 增加了对核心代码库的改进。
* 改进了垃圾回收机制以降低画面卡顿。
* 增加了对可重新载入的nasal模块的支持。
* 更新了Canvas EFIS框架。
* 在Canvas Image中新增了三种设置像素颜色的方法。

== 飞机模型 ==
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持（例如为G500制作SVG）。FG1000 目前在 Cessna 182T, J3 Cub, Diamond DA40上可用。
* 改进了滑翔机的vario仪。
* 新增的机模:
** Airbus A320 - 客机
** Alisport Silent2Electro - 带有电动维持电机的滑翔机
** Bombardier Q400 DHC8-402 - 短途涡桨客机
** Breguet Atlantic BR 1150 - 远程海军巡逻飞机
** Cessna 140 - 通航飞机
** Cessna 208B Caravan - 短程客机，货机和多用途飞机
** Cirrus SR22T - 通航飞机
** Diamond DA40 NG - 通航飞机, 包括了带有 FG1000 玻璃仪表的驾驶舱
** Diamond DA62 Twinstar- 双引擎通航飞机
** Diamond HK36 Super Dimona - 滑翔机
** Dornier DO 28 Skyservant - 双引擎STOL多用途飞机
** Douglas TBD Devastator - 第二次世界大战鱼雷轰炸机
** Draco Wilga - 涡桨后三点野地起降飞机
** Fokker T.V - 双引擎轰炸机
** Glasfluegel H201B Standard Libelle - 滑翔机
** Grumman F11-Tiger - 舰载战斗机
** Grumman HU-16A Albatross - 双引擎两栖飞机
** Petliakov PE-8 (Ant-42/TB-7) - 第二次世界大战轰炸机
** Piper PA28-161 Warrior II - 通航飞机
** Pipistrel Alpha Electro - 电动教练飞机
** Pipistrel Taurus Electro G2.5 - 带有电动维持电机的滑翔机
** Rolladen Schneider LS8sc neo - 带有电动维持电机的标准滑翔机
** Robin DR400 Ecoflyer - 通航飞机
** Scheibe Bergfalke II/55 - 教练滑翔机
** Schempp-Hirth Arcus S - 高性能滑翔机
** Schleicher Ka6(CR) "Rhoensegler" - 教练滑翔机
** SEPECAT Jaguar GR.1 - 喷气攻击机
** SUMPAC - 人力飞机
** Supermarine Swift - 喷气战机
** Yak 52 - 教练机
* 对超过70个机模进行了更新，包括 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== 其他 ==
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 地图对话框现可显示直升机坪并可配置光标平移。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 屏幕截图的文件名现已修改为日期与时间。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.1之后的更新=
自2020.1预览版以来的变化包括：
* 对启动器进行了许多改进，包括新增欢迎屏幕与<code> Ctrl-F </code>开始飞行快捷键。
* 更新了加利福尼亚地区、巴西北部与冰岛的区域材质定义（regional material definitions），改进了机场草地贴图。
* 新增了沿海地区的潮汐效果。
* 增加了新的波音747货机 AI模型，更新了许多AI飞机涂装与时刻表。
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持。
* 机库中新增了许多飞机： HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* 大量机模得到了更新，包括 CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.3.0之后的更新=

由于2020.3 是收到长期支持的版本，我们会根据用户反馈与自动崩溃报告对其进行问题修复与改进。以下列出了每个版本的主要变化。

==2020.3.1==
* 为启动器加入了帮助页面
* 修复了对直升机坪的处理
* 在移植到新的机库版本时移植已安装的机型
* TerraSync：提升了Windows下的启动性能

==2020.3.2==
* TerraSync 现在将等待模型完成同步过程，以避免启动时缺失模型
* 首次启动页面：增加了一个”滚动至底部“按钮
* Erik Hofman 进行了对潮汐的修复
* 启动器中使用了更好的滚动条，解决了一些与较长的机型列表有关的问题
* 支持 Apt.dat v1000 联络频率
* 修复了一个更改位置时的ATC崩溃
* 修复了许多 Michael Danilov 识别的翻译错误
* 显著改进了 Brazilian cerradio 区域 (SBMQ附近)
* 俄文翻译更新
* 修复了冰岛区域材质

==2020.3.3==
* 修复了右键拖动时的意外点击
* 修复了我们在'setup root'对话框中推荐的下载位置

==2020.3.4==
* 现可正确处理更多的METAR字符串，包括风传感器故障
* 修复了气团速度被两次应用在子模型上（例如在侧风中释放载荷时）的错误
* 修复了退出模拟器时与属性代码有关的崩溃
* 西班牙文翻译更新
* 禁用了前往EGEL的航班以防止AI交通代码中的崩溃

==2020.3.5==
* 将Windows下默认下载路径改为 %USERS%\FlightGear\Downloads, 来避免 Windows Defender 阻止不受信任的应用向此前使用的Documents文件夹中写入导致的问题。
* 修复了从其他应用返回FlightGear后滚动滚轮或点击鼠标时可能发生的崩溃
* 避免了使用基于 UIUC 的机型，例如莱特飞行者时发生的崩溃
* 修复了macOS中当摇杆无法开启时发生的崩溃
* 更新了macOS上的应用图标
* 修复了重置（reset）模拟器时Nasal发生的崩溃
* Canvas: 现允许各向异性过滤（Anisotropic filtering）
* 改进并使用了更大的月亮贴图
* 将 UFO 的速度调整为 11
* 修复了在一些特定的画质设置下滑行道标记消失的问题

==2020.3.6==
* 修复了下载默认机型目录时发生的崩溃
* 修复了在海洋中的地景启动时的停止响应
* 修复了在一些特定METAR下错误的天空与驾驶舱渲染
* 在启动器增加了新手上路（getting-started）提示（目前仅支持英文）
* 修复了航天飞机的AI场景（AI scenarios）
* 改进了飞行计划模式
* 修复了月亮/太阳的比例
* 修复子模型（submodels）的初始位置
* macOS: 增加了在临时镜像中运行时的警告
* Windows: 检测OpenGL驱动器是否缺失
* 修复 UIUC FDM 的崩溃
* 修复了与无效视角编号（view numbers）有关的崩溃
* 更恰当地处理FDM的NaN错误
* 改进了 KAP-140 进近模式（Approach mode）
* 更新了AI交通与涂装

==2020.3.7==
*TerraSync启用了全球范围内OSM2City建筑的分发
*C172 更新与错误修正
* 改进了欧洲与加利福尼亚地区的区域材质定义
*允许移动聊天框
*修复了与粒子系统有关的崩溃
*修复了北京及周边地区时区错误的问题
*修复了Canvas中显示non-Latin1字符串的问题
*修复了联网飞行模式下在跑道启动的逻辑，现可正确地将飞机放置于跑道外等待位置
*macOS: 修复了使用一些特定字体时的崩溃问题
*修复了当系统语言包括script specifier时启动器语言选择的问题（如zh-Hans-CN）
*修复了从机库加载时与aircraft-id属性有关的问题 ( https://sourceforge.net/p/flightgear/codetickets/2502/ )
*改进了Windows下对过时Intel图形驱动的检测

==2020.3.8==
*修复了<code><local></code>粒子系统的行为
*修复了秋季树木的外观

== 2020.3.9 ==
* 修复了与 Swift 有关的崩溃
* 修正了联机协议中使用的时间
* 修正了 FGData 的 URL
* 修复了重新加载缓存对话框中的错误
* 对 ATC 界面进行了改进，使其正确显示频率

== 2020.3.10 ==
* 应答机：现standby模式可正常工作
* 启动器：现可识别命令行中的地景与机模路径
* 启动器：改变了存储位置的方式以避免运行多个版本的FlightGear及在不同版本之间切换时出现问题
* 启动器：增加了“在退出时重启”（‘restart on quit’）的选项
* 修复了在加载ShapeFile数据时的NavCache报错
* 修复了在运行多个FlightGear副本时的NavCache报错

== 2020.3.11 ==
* 修复了一个2020.3.10中被引入的崩溃
* 改进了当机模搜索路径不存在时的报错信息
* 修复了未正确配置AI飞机滑行路径导致的崩溃
* 更新了AI交通的时间表

== 2020.3.12 ==
* 增加了对机模路径名称的验证
* 增加了更进一步的抗锯齿（8x）
* 增加了允许机模将自定义字体用于osg::Text的功能
* 增加了通用化的，结合了ALS procedural lights与Compositor lights的灯光
* 为澳大利亚地区增加了新的区域材质定义
* 修复了Basic Weather引擎输出无效气压高度的问题
* 修复了预览图路径搜索中存在的问题
* 修复了接近max-dist范围时声音系统存在的问题
* 修复了重置时发生的崩溃问题
* 修复了当AI飞机的目的地跑道无效时崩溃的问题
* 修复了Mapstructure RTE图层中的报错
* 修复了 --view-offset，使其使用正确的属性
* HUD：使垂直刻度的样式与水平刻度保持一致
* 改进了俄语和意大利语翻译
* 对天气对话框进行了数项改进
* 属性树浏览器（Property browser）：将文件夹的值以冗长的模式（verbose mode）显示
* 航路管理器（Route manager)：在存在同名航路点时现将自动选择正确的航路点
* 更新了AI交通的时间表，增加了新的AI飞机模型

== 2020.3.13 ==
* 修复了联机飞行员名单不出现的问题
* 修复了 JSBsim 线性执行器在特定条件下表现不佳的问题

== 2020.3.14 ==
* 增加了对add-ons路径的支持
* 新增了即时音频队列
* 对canvas对话框进行了改进，使其不抢占FG的鼠标焦点（与PUI对话框的行为类似）

== 2020.3.15 ==
* 修复了无线电音频摩尔斯电码的问题

== 2020.3.16 ==
* 修复了音频缩进问题。

== 2020.3.17 ==
* 导航无线电：更改选定频率或离开GPS从属模式时禁用低通滤波器。更改选定频率或离开 GPS 从属模式时，将禁用应用于信号质量的低通滤波器。
* 导航无线电：修复了一些新引入的问题并优化了旧代码。更新的内容：更改待机频率禁用了下一次调用 updateReceiver() 的低通滤波器; 这必须在更改选定频率时发生，但不在更改待机频率时发生。
* 自动驾驶仪输入：向自动驾驶仪的输入添加属性路径支持。允许间接定义自动驾驶仪（通过字符串属性），以便可以从-set.xml配置或在运行时进行调整。
* 在启动器中将五边进场的选项`--on-ground=false`替换为`--in-air`选项，以免产生误导。

== 2020.3.18 ==

* 新增对卫星地景 photoscenery 的支持。
* 全新的简单自动驾驶系统。
* 修复了 Navigraph 程序文件中 'between' 类型导致的崩溃。
==2020.3.19==
*增加了AI子模型碰撞效果
*修复了无效METAR字符串导致的崩溃

== 参考 ==
{{Appendix}}

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

[[Category:FlightGear changelogs‎]]
[[En:Changelog_2020.3]]
[[Pl:Changelog_2020.3]]

Template:Disclaimer

2023-12-27T07:06:11Z

Sidiliang:

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{Note|FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| final-fixed-function-release-Chinese = {{
Note|FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响FPS（无论是变高还是变低…）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Zh/2020.3

2023-12-27T07:05:22Z

Sidiliang: Switch the disclaimer to the Chinese version

{{changelogs|prev=2020.1|next=2022.1}}

可用语言: [[Zh/2020.3|中文]]，[[Changelog_2020.3|English]], [[Pl/Changelog_2020.3|Polish]]. 

请协助我们将其翻译为更多语言!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

自由、开源的飞行模拟器FlightGear即将迎来2020.3版本更新。这是FlightGear开始同时提供长期支持版本和预览版本之后的第二个长期支持版本，代表了全球的志愿者们为期两年的开发工作的结晶。FlightGear由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的且无比贴近真实的飞行模拟器。 FlightGear通常被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。

自v2018.3 LTS以来的主要更新包括：
*增加了即将到来的Compositor图形框架的预览，作为单独的二进制文件共同分发。
*对JSBSim和YASim飞行动力学模型进行了更新
*增加了DDS贴图缓存以减少加载时间
*加载更快、更节省内存的建筑
*改善了对航空母舰的支持

此外，官方机库中增加了30架全新的机模，71架机模得到了重大更新。

{{Disclaimer|id=final-fixed-function-release-Chinese}}

项目开始于1997年，FlightGear的特色包括其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。

FlightGear - 自由飞翔！

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== 启动器 ==
* 添加了在首次启动时出现的欢迎屏幕，为首次使用的用户提供一些有用的信息。
* 机模插件现在可被标记为个人收藏，并可进行筛选，使得在数百个机模插件中寻找您喜爱的机模变得更容易。
* 启动器增加了对航空母舰的支持，现可在启动器中选择航空母舰以及设置起始位置。
* 当你想开始飞行的时候，现在只需要按下<code> Ctrl-F </code>快捷键！
* 增强了对停机坪和水上机场的支持，增加了对当前的飞机型号的检测。
* 大量错误修正和稳定性改进，尤其对机模和插件选项卡进行了改进。

== 画面 ==
* 此发行版随附[[Compositor]]渲染器以便开发人员预览使用。Compositor渲染器提供了全面支持XML配置的多通道渲染合成方式，并且支持ALS与集群着色。*增加了对DDS贴图缓存的支持，缩短了贴图文件的加载时间。
* 恒星能见度现可根据恒星大小和大气条件进行配置。
* 现可通过设置<code>/rendering/triangle-direction-lights=false</code>，可以使用不定向点精灵（non-directional point sprites）以便在不支持三角形点精灵（triangles of point sprites）的图形驱动器上正确运行。
* 添加了全新的Tower AGL视角。该视角与塔台视角类似，不同之处在于它使地面保持在飞机的正下方，并在飞机移动时平稳地缩放和平移。这使得该视角适合用于观察降落。
* 改善了机场草地贴图
* 新增了沿海地区的潮汐效果。
* 更新了加利福尼亚地区、亚洲地区、巴西北部、冰岛和扬马延（Jan Mayen）岛的区域材质定义（regional material definitions）。
* 增加了新的活火山 - Katla, Eyjafjallajokull, Surtsey.
* 新增基于实例的随机建筑与OpenStreetMap建筑，提高了性能并显著提高了画面质量。
* 改进了机翼弯折着色器。
* 现可从“View”菜单中启用/禁用飞行员模型。

== JSBSim ==
[以下部分翻译使用机器翻译，故部分内容或许将不准确或不自然。欢迎更多志愿者加入到翻译的行列中！] 
[Some part of the following translation is made by a machine translator, so it may be inaccurate or awkward. Any contributions to the translation are welcomed! ]
* 新增了设置涡轮机启动和加速时间的功能（参数<code><n1spinup></code>，<code><n2spinup></code>，<code><n1startrate></code>， <code><n2startrate></code>）。
* 现在，可以通过将<code><integrator></code>过滤器的<code><trigger></code>属性设置为负值，将其重置为0.0。
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* 现在可以在<code><function></code>中使用以下功能：<code>floor</code>，<code>ceil</code>和<code>fmod</code>。它们的功能与相应的C / C ++函数相同。
* <code> <function> </code>现在检查其参数数量。
* 新的系统组件linear_actuator
* 将燃料密度导出到属性树
* 为FCS组件添加了循环裁剪
* 增加了控制涡轮发动机转速下降因子的功能
* [向后兼容性损坏]陀螺仪现在正在测量转速而不是旋转加速度。测量旋转加速度的陀螺仪在现实世界中不存在。
* 飞行控制元件的输出属性不再绑定。这样可以节省许多虚假的警告消息，并允许在多个飞行控制中直接引用相同的属性。
* 现在通过质量分数而不是分压来管理大气中的水蒸气。前者是压力和温度变化时保留的物理量。
* 在尝试修整地面之前，请检查至少3个触点。
* 为FG UDP接口增加了仿真时间的可选传输
* 现在在执行过程中而不是在解析XML定义时检查用于表无关var的属性的存在。这放宽了需要在XML定义文件中声明过滤器，表格以及更一般的飞行控件的顺序。
* 电动引擎RPM现在已在UDP套接字中导出。
* 参数<code><ignitionn2></code>现在影响N2而不是N1。
* 现在在<code><clipto></code>中的max<min时给出警告，而不是引发异常
* 添加了使用新的fgfs可执行参数<code>-jsbsim-output-directive-file</code>在CSV文件中记录属性的功能

== YASim ==
* 改变了静摩擦力
* 新增支持跨音速效果.
* 现可通过设置<code>/fdm/yasim/respect-external-gear-state=true</code>来控制初始起落架状态。
* 新增对电动引擎的支持。

== 气象和环境 ==
* 在活火山附近湍流强度将会增加。
* 现可对METAR URL进行配置。
* 新增对METAR字符串的解码并以可读的形式显示在天气对话框中。

== 航空母舰 ==
* 启动器现支持两种全新的标准状态: <code>carrier-takeoff</code> 与 <code>carrier-approach</code>.
* 加入了全新的命令行参数 <code>--carrier-position</code>。这可用于选择航空母舰上的飞机起始位置。可选择的选项包括航母弹射器(e.g. <code>cat-1</code>)、停机位(e.g. <code>park-1</code>)、FLOLS进近位(<code>flols</code>)或abeam位置(<code>abeam</code>)。
* 现在即使在启动时不可用，GUI也可以检测到MPCarrier。要启用此功能，请设置<code>/sim/mp-carriers/auto-attach=true</code>。

== AI ==
* 增加了新的fgcommands：<code>add-aiobject</code>和<code>remove-aiobject</code>，可用于向AI子系统添加或移除物体。
* 增加了新的AI飞机, 包括波音747货机、CRJ900、SR-71、Saab 340.
* 对许多AI交通时刻表与航空公司涂装进行了更新。
* 新增在KEDW的Space Shuttle TAEM与进近场景。
* 新增了来自当地飞行员的准确Britten-Norman Islander性能数据。

== 联机飞行 ==
* 现可通过GUI使用swift以连接到VATSIM。
* FGComm现在支持COM1和COM2以及音量设置。
* 由机模定义的视角（飞行员视角（Pilot view），直升机视角（Helicopter view），塔台视角（Tower view）等）现在可以在联机飞行中的其他飞机上使用。通过单击“飞行员列表（Pilot List）”对话框的“视图（view）”列，可以查看特定的联机飞机（可在“Multiplayer/Pilot List”菜单下找到）。
* 新增<code>-disable-hold-short </code>选项，当进入联机飞行时，允许用户在跑道上出生。请谨慎使用此选项——突然在跑道上出现会对其他飞行员与ATC造成极大的困扰。
* 回放器现可记录联机中其他飞机的数据。

== Nasal 脚本语言 ==
* 现可配置核心Nasal模块的加载顺序。
* 增加了对通信接口Emesary的改进和错误修复。
* 增加了对核心代码库的改进。
* 改进了垃圾回收机制以降低画面卡顿。
* 增加了对可重新载入的nasal模块的支持。
* 更新了Canvas EFIS框架。
* 在Canvas Image中新增了三种设置像素颜色的方法。

== 飞机模型 ==
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持（例如为G500制作SVG）。FG1000 目前在 Cessna 182T, J3 Cub, Diamond DA40上可用。
* 改进了滑翔机的vario仪。
* 新增的机模:
** Airbus A320 - 客机
** Alisport Silent2Electro - 带有电动维持电机的滑翔机
** Bombardier Q400 DHC8-402 - 短途涡桨客机
** Breguet Atlantic BR 1150 - 远程海军巡逻飞机
** Cessna 140 - 通航飞机
** Cessna 208B Caravan - 短程客机，货机和多用途飞机
** Cirrus SR22T - 通航飞机
** Diamond DA40 NG - 通航飞机, 包括了带有 FG1000 玻璃仪表的驾驶舱
** Diamond DA62 Twinstar- 双引擎通航飞机
** Diamond HK36 Super Dimona - 滑翔机
** Dornier DO 28 Skyservant - 双引擎STOL多用途飞机
** Douglas TBD Devastator - 第二次世界大战鱼雷轰炸机
** Draco Wilga - 涡桨后三点野地起降飞机
** Fokker T.V - 双引擎轰炸机
** Glasfluegel H201B Standard Libelle - 滑翔机
** Grumman F11-Tiger - 舰载战斗机
** Grumman HU-16A Albatross - 双引擎两栖飞机
** Petliakov PE-8 (Ant-42/TB-7) - 第二次世界大战轰炸机
** Piper PA28-161 Warrior II - 通航飞机
** Pipistrel Alpha Electro - 电动教练飞机
** Pipistrel Taurus Electro G2.5 - 带有电动维持电机的滑翔机
** Rolladen Schneider LS8sc neo - 带有电动维持电机的标准滑翔机
** Robin DR400 Ecoflyer - 通航飞机
** Scheibe Bergfalke II/55 - 教练滑翔机
** Schempp-Hirth Arcus S - 高性能滑翔机
** Schleicher Ka6(CR) "Rhoensegler" - 教练滑翔机
** SEPECAT Jaguar GR.1 - 喷气攻击机
** SUMPAC - 人力飞机
** Supermarine Swift - 喷气战机
** Yak 52 - 教练机
* 对超过70个机模进行了更新，包括 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== 其他 ==
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 地图对话框现可显示直升机坪并可配置光标平移。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 屏幕截图的文件名现已修改为日期与时间。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.1之后的更新=
自2020.1预览版以来的变化包括：
* 对启动器进行了许多改进，包括新增欢迎屏幕与<code> Ctrl-F </code>开始飞行快捷键。
* 更新了加利福尼亚地区、巴西北部与冰岛的区域材质定义（regional material definitions），改进了机场草地贴图。
* 新增了沿海地区的潮汐效果。
* 增加了新的波音747货机 AI模型，更新了许多AI飞机涂装与时刻表。
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持。
* 机库中新增了许多飞机： HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* 大量机模得到了更新，包括 CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.3.0之后的更新=

由于2020.3 是收到长期支持的版本，我们会根据用户反馈与自动崩溃报告对其进行问题修复与改进。以下列出了每个版本的主要变化。

==2020.3.1==
* 为启动器加入了帮助页面
* 修复了对直升机坪的处理
* 在移植到新的机库版本时移植已安装的机型
* TerraSync：提升了Windows下的启动性能

==2020.3.2==
* TerraSync 现在将等待模型完成同步过程，以避免启动时缺失模型
* 首次启动页面：增加了一个”滚动至底部“按钮
* Erik Hofman 进行了对潮汐的修复
* 启动器中使用了更好的滚动条，解决了一些与较长的机型列表有关的问题
* 支持 Apt.dat v1000 联络频率
* 修复了一个更改位置时的ATC崩溃
* 修复了许多 Michael Danilov 识别的翻译错误
* 显著改进了 Brazilian cerradio 区域 (SBMQ附近)
* 俄文翻译更新
* 修复了冰岛区域材质

==2020.3.3==
* 修复了右键拖动时的意外点击
* 修复了我们在'setup root'对话框中推荐的下载位置

==2020.3.4==
* 现可正确处理更多的METAR字符串，包括风传感器故障
* 修复了气团速度被两次应用在子模型上（例如在侧风中释放载荷时）的错误
* 修复了退出模拟器时与属性代码有关的崩溃
* 西班牙文翻译更新
* 禁用了前往EGEL的航班以防止AI交通代码中的崩溃

==2020.3.5==
* 将Windows下默认下载路径改为 %USERS%\FlightGear\Downloads, 来避免 Windows Defender 阻止不受信任的应用向此前使用的Documents文件夹中写入导致的问题。
* 修复了从其他应用返回FlightGear后滚动滚轮或点击鼠标时可能发生的崩溃
* 避免了使用基于 UIUC 的机型，例如莱特飞行者时发生的崩溃
* 修复了macOS中当摇杆无法开启时发生的崩溃
* 更新了macOS上的应用图标
* 修复了重置（reset）模拟器时Nasal发生的崩溃
* Canvas: 现允许各向异性过滤（Anisotropic filtering）
* 改进并使用了更大的月亮贴图
* 将 UFO 的速度调整为 11
* 修复了在一些特定的画质设置下滑行道标记消失的问题

==2020.3.6==
* 修复了下载默认机型目录时发生的崩溃
* 修复了在海洋中的地景启动时的停止响应
* 修复了在一些特定METAR下错误的天空与驾驶舱渲染
* 在启动器增加了新手上路（getting-started）提示（目前仅支持英文）
* 修复了航天飞机的AI场景（AI scenarios）
* 改进了飞行计划模式
* 修复了月亮/太阳的比例
* 修复子模型（submodels）的初始位置
* macOS: 增加了在临时镜像中运行时的警告
* Windows: 检测OpenGL驱动器是否缺失
* 修复 UIUC FDM 的崩溃
* 修复了与无效视角编号（view numbers）有关的崩溃
* 更恰当地处理FDM的NaN错误
* 改进了 KAP-140 进近模式（Approach mode）
* 更新了AI交通与涂装

==2020.3.7==
*TerraSync启用了全球范围内OSM2City建筑的分发
*C172 更新与错误修正
* 改进了欧洲与加利福尼亚地区的区域材质定义
*允许移动聊天框
*修复了与粒子系统有关的崩溃
*修复了北京及周边地区时区错误的问题
*修复了Canvas中显示non-Latin1字符串的问题
*修复了联网飞行模式下在跑道启动的逻辑，现可正确地将飞机放置于跑道外等待位置
*macOS: 修复了使用一些特定字体时的崩溃问题
*修复了当系统语言包括script specifier时启动器语言选择的问题（如zh-Hans-CN）
*修复了从机库加载时与aircraft-id属性有关的问题 ( https://sourceforge.net/p/flightgear/codetickets/2502/ )
*改进了Windows下对过时Intel图形驱动的检测

==2020.3.8==
*修复了<code><local></code>粒子系统的行为
*修复了秋季树木的外观

== 2020.3.9 ==
* 修复了与 Swift 有关的崩溃
* 修正了联机协议中使用的时间
* 修正了 FGData 的 URL
* 修复了重新加载缓存对话框中的错误
* 对 ATC 界面进行了改进，使其正确显示频率

== 2020.3.10 ==
* 应答机：现standby模式可正常工作
* 启动器：现可识别命令行中的地景与机模路径
* 启动器：改变了存储位置的方式以避免运行多个版本的FlightGear及在不同版本之间切换时出现问题
* 启动器：增加了“在退出时重启”（‘restart on quit’）的选项
* 修复了在加载ShapeFile数据时的NavCache报错
* 修复了在运行多个FlightGear副本时的NavCache报错

== 2020.3.11 ==
* 修复了一个2020.3.10中被引入的崩溃
* 改进了当机模搜索路径不存在时的报错信息
* 修复了未正确配置AI飞机滑行路径导致的崩溃
* 更新了AI交通的时间表

== 2020.3.12 ==
* 增加了对机模路径名称的验证
* 增加了更进一步的抗锯齿（8x）
* 增加了允许机模将自定义字体用于osg::Text的功能
* 增加了通用化的，结合了ALS procedural lights与Compositor lights的灯光
* 为澳大利亚地区增加了新的区域材质定义
* 修复了Basic Weather引擎输出无效气压高度的问题
* 修复了预览图路径搜索中存在的问题
* 修复了接近max-dist范围时声音系统存在的问题
* 修复了重置时发生的崩溃问题
* 修复了当AI飞机的目的地跑道无效时崩溃的问题
* 修复了Mapstructure RTE图层中的报错
* 修复了 --view-offset，使其使用正确的属性
* HUD：使垂直刻度的样式与水平刻度保持一致
* 改进了俄语和意大利语翻译
* 对天气对话框进行了数项改进
* 属性树浏览器（Property browser）：将文件夹的值以冗长的模式（verbose mode）显示
* 航路管理器（Route manager)：在存在同名航路点时现将自动选择正确的航路点
* 更新了AI交通的时间表，增加了新的AI飞机模型

== 2020.3.13 ==
* 修复了联机飞行员名单不出现的问题
* 修复了 JSBsim 线性执行器在特定条件下表现不佳的问题

== 2020.3.14 ==
* 增加了对add-ons路径的支持
* 新增了即时音频队列
* 对canvas对话框进行了改进，使其不抢占FG的鼠标焦点（与PUI对话框的行为类似）

== 2020.3.15 ==
* 修复了无线电音频摩尔斯电码的问题

== 2020.3.16 ==
* 修复了音频缩进问题。

== 2020.3.17 ==
* 导航无线电：更改选定频率或离开GPS从属模式时禁用低通滤波器。更改选定频率或离开 GPS 从属模式时，将禁用应用于信号质量的低通滤波器。
* 导航无线电：修复了一些新引入的问题并优化了旧代码。更新的内容：更改待机频率禁用了下一次调用 updateReceiver() 的低通滤波器; 这必须在更改选定频率时发生，但不在更改待机频率时发生。
* 自动驾驶仪输入：向自动驾驶仪的输入添加属性路径支持。允许间接定义自动驾驶仪（通过字符串属性），以便可以从-set.xml配置或在运行时进行调整。
* 在启动器中将五边进场的选项`--on-ground=false`替换为`--in-air`选项，以免产生误导。

== 2020.3.18 ==

* 新增对卫星地景 photoscenery 的支持。
* 全新的简单自动驾驶系统。
* 修复了 Navigraph 程序文件中 'between' 类型导致的崩溃。
==2020.3.19==
*增加了AI子模型碰撞效果
*修复了无效METAR字符串导致的崩溃

== 参考 ==
{{Appendix}}

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

[[Category:FlightGear changelogs‎]]
[[En:Changelog_2020.3]]
[[Pl:Changelog_2020.3]]

Template:Disclaimer

2023-12-27T07:04:51Z

Sidiliang:

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{Note|FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| final-fixed-function-release-Chinese = {{
请注意|FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响FPS（无论是变高还是变低…）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Template:Disclaimer

2023-12-27T07:03:16Z

Sidiliang:

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{Note: FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}
| final-fixed-function-release-Chinese = {{
请注意：FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响FPS（无论是变高还是变低…）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Template:Disclaimer

2023-12-27T07:00:25Z

Sidiliang: Update Chinese translation for final-fixed-function-release disclaimer

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{LangSwitch
| en = 
: Note: FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>

| zh = 
: 请注意：FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响FPS（无论是变高还是变低…）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>
}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Template:Disclaimer

2023-12-27T06:58:00Z

Sidiliang:

<noinclude>{{Stub}}</noinclude>

{{#ifeq: {{Current release|cr}} | 2020.3 |

{{#switch: {{{id|missing}}}
| final-fixed-function-release = {{LangSwitch
| en = 
: Note|FlightGear is currently undergoing a lot of huge changes. More importantly: Adopting {{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>, moving to the [[#Status|OpenGL core profile]], [[World Scenery 3.0 roadmap|WS 3.0]], [[Osm2city]] buildings, [[Photoscenery]] and [[Compositor#Notes_for_aircraft_developers|Compositor shadows & lights]].

In addition, adopting OSG 3.6 means that the experimental [[CompositeViewer Support]] can be more widely enabled and tested<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref> (it is already enabled by default on '''next''').

Also, as part of the [[CompositeViewer_support#Status_updates|CompositeViewer effort]], [[Canvas]] FBO rendering is in the process of being [[Canvas_news#Dedicated_prerender_cams|moved out of the scene graph into dedicated viewer-level cameras]], which provides better support/integration with OSG threading and fixes the long-standing issue where Canvas textures were being rendered twice per view unnecessarily due to the original new/far camera scheme.

Furthermore, to support Canvas (actually CanvasPath/all SVG handling) on Core profile, the plan is to migrate our [[Canvas Path]] backend from Shiva to ‘something else’ (see [[Shiva Alternatives]]) which implements the required drawing operations, unlike Shiva, ShaderVG or NanoVG can target Core-profile OpenGL.<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

It is likely the non-shader code path (fixed-function pipeline) will also go away in the next twelve months (~ early/mid 2022).
We tried to communicate this: [[Changelog 2020.3|2020.3]] is the last release that will work on really old hardware: '[[FlightGear_Git|next]]' and future releases will need a more modern machine with an OpenGL 4 / DX12 class GPU.<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' is work-in-progress: likely 12 or 18 months before it becomes a release. In that time the build dependencies, [[Hardware_requirements|minimum system requirements]], performance baseline and basically everything else are going to change (and keep changing). Of course, we'll try to make it work on as wide a range of hardware as possible, but right now we don't know, and it would be incorrect to speculate or promise anything. (Eg, we cannot say 'an Intel 4000 will work but an Intel 3000 won't - we have no idea!)

If '[[FlightGear_Git|next]]' works for someone, that is great, but if you want stability, stable FPS and compatibility with older hardware, there is an easy answer: use [[Changelog 2020.3|2020.3]]. That's what we recommend for everyone who wants to fly and enjoy flying. <ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
The macOS and Windows nightly builds are now running OSG 3.6.5, so people can hopefully start testing WS3.0 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
Also, be aware that the binary builds also switched to OSG 3.6, so that may have an FPS impact as well (either higher or lower…)<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>

| zh = 
:请注意|FlightGear目前正在经历许多重大变化，特别是：采用{{Abbr|OSG|OpenSceneGraph}} 3.6+<ref>https://sourceforge.net/p/flightgear/mailman/message/37285557/</ref>，转向使用[[#Status|OpenGL core profile]]，[[World Scenery 3.0 roadmap|第三代全球地景WS 3.0]]，[[Osm2city]] 建筑，[[Photoscenery|卫星地景（Photoscenery）]] 以及[[Compositor#Notes_for_aircraft_developers|Compositor 阴影与灯光]]。

此外，采用 OSG 3.6 意味着可以更广泛地启用和测试实验性的[[CompositeViewer Support | CompositeViewer]]<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#76c9</ref>（它已经在 '''next''' 分支上默认启用）。

同时，作为[[CompositeViewer_support#Status_updates|CompositeViewer 相关努力]]的一部分，[[Canvas]] FBO 渲染正处于[[Canvas_news#Dedicated_prerender_cams|从场景图（scene graph）移出到专用查看器级别的相机（dedicated viewer-level cameras）]]的过程中，这有利于更好地支持/整合OSG多线程，并解决了Canvas长久以来的因原始新/远摄像头方案而需要对贴图进行无谓的重复渲染的问题。

为了在Core Profile上支持Canvas（实际上是CanvasPath和所有SVG处理），我们计划将[[Canvas Path]]后端从Shiva迁移到其他方案（见[[Shiva Alternatives|Shiva替代方案]]，如ShaderVG或NanoVG：与Shiva不同，它们在实现了所需的绘图操作同时，可以支持OpenGL Core Profile。<ref>https://sourceforge.net/p/flightgear/mailman/message/37606487/</ref>

非着色器代码路径（non-shader code path）（固定功能管线，fixed-function pipeline）可能也会在接下来的十二个月内（~2022年初/中期）消失。（译者注：该声明撰写于这个日期之前，实际上这个预估显然过于乐观，截止到今天（2023年末）这些都还未实现。）
我们希望传达这个信息：[[Changelog 2020.3|2020.3]]是最后一个能在非常旧的硬件上工作的版本：'[[FlightGear_Git|next]]' 和未来的版本将需要更现代的设备，配备 OpenGL 4 / DX12 类 GPU。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#f6f6</ref> '[[FlightGear_Git|next]]' 是进行中的工作：可能需要12或18个月才能发布（译者注：目前看，可能还需要更长的时间。）。在此期间，构建依赖、[[Hardware_requirements|最低系统要求]]、性能基线以及几乎所有其他事项都将发生变化（并持续变化）。当然，我们会尽可能使其在尽可能广泛的硬件范围内运行，但现在我们还无法给出结论。我们不希望不正确地猜测或承诺任何事情（例如，我们不能说“可以在英特尔4000上运行，但英特尔3000不行 - 因为我们不知道！）。

如果 '[[FlightGear_Git|next]]' 在一些人的设备上可以正确运行，那自然很好，但如果你想要稳定性、稳定的运行帧数（FPS）和与旧硬件的兼容性，有一个简单的答案：使用[[Changelog 2020.3|2020.3]]。这就是我们为所有想飞行和享受飞行的人推荐的版本。<ref>https://sourceforge.net/p/flightgear/codetickets/2560/#5802</ref>
与此同时，macOS和Windows的夜间构建（nightly builds）现在使用OSG 3.6.5，所以理论上大家可以使用这个版本开始对WS3.0进行测试 <ref>https://sourceforge.net/p/flightgear/mailman/message/37288272/</ref>
另外，请注意，二进制构建也已经切换到OSG 3.6，这可能也会影响FPS（无论是变高还是变低…）<ref>https://sourceforge.net/p/flightgear/mailman/message/37288035/</ref>

}}

| baz = Baz
| missing = {{Note|
template expects an id argument
}}
}}

|  }}

Zh/首页

2023-12-27T06:31:02Z

Sidiliang: Wording

{{Main page/Header
|title = 欢迎来到[[FlightGear wiki|FlightGear百科]]！
|subtitle = ''自由飞行！''
|rightbox = {{Main page/Languages}}
|introduction =
[[Help:Your first article|欢迎您加入到]] FlightGear 百科的中文翻译中!

|rightcolumn1 = [[File:Portal user.png|40px]]</div>
[[Zh/Portal:用户|使用入门]] 
'''[[Zh/FlightGear新手|FlightGear新手上路]]''' 
[[Frequently asked questions|常见问题]] • [[Troubleshooting problems|解决问题]] 
[[Howto: Install scenery|安装地景]] • [[Howto: Install aircraft|安装机模]] 
[[Howto: Fly a helicopter|驾驶直升飞机]]
|rightcolumn2 = [[File:Portal developer.png|40px]]</div>
[[:zh:Portal:Developer|开发]] 

[[Portal:Developer/Aircraft|机模]] • [[Portal:Developer/Scenery|地景]] • [[Portal:Embedded|嵌入式相关]] 
[[Howto: Place 3D objects with the UFO|在地景中放置物件]] • [[Howto: Create custom terrain|编辑地形]] [[Howto:Improve scenery in your area, or area of interest|地景: 如何改善你所在的区域]] [[编译和本地化FlightGear]] 
[[How the FlightGear project works|FlightGear项目的运作方式]]
|rightcolumn3 = [[File:Portal wiki.png|40px]]</div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|关于 FlightGear Wiki百科]] • [[zh:Help:Contents|帮助]] 
[[Help:Your first article|撰写你的第一篇文章]] • [[Help:Translate|翻译]] 
[[Special:Categories|其他分类]]

|sections =
{{Main page/Leftbox
|title = 关于FlightGear
|logo = FlightGear logo.png
|contents = '''[[FlightGear]]''' 是一个由来自世界各地的志愿者创建的飞行模拟器，以免费、开源的 [[GNU General Public License|GPL]] 软件形式发布。 FlightGear 已被广泛用于 [[Professional and educational FlightGear users|学术研究、教育]], 以及娱乐。

FlightGear 附带一套图文并茂的文档, 特别是安装包内附带的 "[http://flightgear.sourceforge.net/manual/2020.3/ 用户手册]"。本百科站提供了更多与使用及开发有关的文档。

=== 我正在寻找 … ===
* [[Zh/Portal:用户|使用FlightGear方面的帮助]]
* [[:zh:Portal:Developer|如何为FlightGear项目做出贡献]]
* [[table of models|有关所有为FlightGear开发的机模（飞机插件）的信息]]
}}
{{Main page/Leftbox
|title = 新闻
|logo = Nuvola apps knewsticker.png
|contents = {{News}}
}}
{{Main page/Leftbox
|title = 你是否知道......
|logo = Nuvola apps ktip.png
|contents = {{Did you know}}
}}

}}

{{Main page/Rightcolumn
|title = 精彩呈现
|contents = <center style="padding-top: 0.9em">[[File:Innsbruck_at_night_in_FlighGear_with_OSM2City_worldbuild_03.jpg|frameless]]</center>
|padding-right = 23px
}}奥地利因斯布鲁克上空的景色。 '''FlightGear 2020.3.8''' 已经 [https://www.flightgear.org/download/ 在官网发布] ，带来了'''全球范围'''的基于OSM2City的 3D 建筑, 道路, 以及其他物件。更多详见 [[OSM2City 1st Worldbuild|'''OSM2City的第一版全球地景''']].{{Main page/Rightcolumn
|title = [[:Category:Screenshot of the month|月度最佳截图]]
|contents = <center style="padding-top: 0.9em">{{POTM/{{#time: Y-m }}}}</center>
|padding-right = 23px
}}
{{Main page/Rightcolumn end
|title = [[FlightGear and Git|开发仓库状态]]
|contents = <center style="padding-top: 0.9em">{{GitStatus}}</center>
|padding-right = 23px
}}

[[Category:FlightGear wiki]]

Template talk:GitStatus

2023-12-27T06:29:19Z

Sidiliang: /* Chinese Translation */

== Updating and improving the status template(s) ==
{{tl|GitStatus}}, {{tl|GitStatus:closed}}, {{tl|GitStatus:frozen}} and {{tl|GitStatus:open}}

As they are largely undocumented, do not use parameters and some data, like the next release and the dates is repeated many times and have to be edited in many places, maintenance is a hassle. In essence they could be more automated and better documented so that maintaining them would be more straight forward.

Some things I could see useful is having the current and next releases as separate templates (they could be useful in other places as well) and having to edit the dates only in special circumstances and doing that through parameters in those cases. Also, why four separate templates?

Are there other functionality you guys always have wanted but have not figured out or taken time to add?

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

: See [[FlightGear wiki:Village pump/Archive 2013#Automating Template:Git status]]
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:57, 18 December 2014 (UTC)

:: Ah, I had completely forgotten about that. Thanks Gijs.

:: There seem to be some things that could be using parameters:
::; backlog, next_changelog: Link to the next changelog
::; next_version: Next version
::; closed_until: Forcing a closed state by giving the (estimated) end of the closed state.
::; frozen_until: Forcing a frozen state by giving the (estimated) end of the frozen state. ''For situations like the release of 3.2(?).''

:: The year used by the defaults could and probably should be completely automated using <code><nowiki>{{CURRENTYEAR}}</nowiki></code>.

:: In order to call {{tl|GitStatus}} without parameter there could be a subtemplate, for example <code><nowiki>{{GitStatus/main}}</nowiki></code> called from {{tl|GitStatus}} using those parameters. That way any irregular updates would only have to be added to the parameters {{tl|GitStatus}} use when calling <code><nowiki>{{GitStatus/main}}</nowiki></code>.

:: The template would be shown just like before for now.

:: A draft of the documentation of the functionality is for now available in [[User:Johan G/GitStatus/main|my sandbox]].

:: Any comments or further ideas are most welcome!

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

== Please update Polish translation ==

| pl = 
'''Aktualna wersja:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pl}}) '''Następne wydanie:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] ({{Current release|nrd}} od teraz) Zobacz szczegóły [[release plan|planu wydawniczego]]

[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 14:48, 6 August 2023 (UTC)

== Chinese Translation ==

| zh = 
'''当前发布版本：''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:Y"年"Mj"日"|{{Current release|fulldate}}|zh}}) '''下次更新版本：''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|(距今还有{{Current release|nrd}})|}} 详见[[release plan |发布计划]].

[[User:Sidiliang|Sidiliang]] ([[User talk:Sidiliang|talk]]) 06:28, 27 December 2023 (UTC)

Template talk:GitStatus

2023-12-27T06:29:04Z

Sidiliang: /* Chinese Translation */

== Updating and improving the status template(s) ==
{{tl|GitStatus}}, {{tl|GitStatus:closed}}, {{tl|GitStatus:frozen}} and {{tl|GitStatus:open}}

As they are largely undocumented, do not use parameters and some data, like the next release and the dates is repeated many times and have to be edited in many places, maintenance is a hassle. In essence they could be more automated and better documented so that maintaining them would be more straight forward.

Some things I could see useful is having the current and next releases as separate templates (they could be useful in other places as well) and having to edit the dates only in special circumstances and doing that through parameters in those cases. Also, why four separate templates?

Are there other functionality you guys always have wanted but have not figured out or taken time to add?

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

: See [[FlightGear wiki:Village pump/Archive 2013#Automating Template:Git status]]
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:57, 18 December 2014 (UTC)

:: Ah, I had completely forgotten about that. Thanks Gijs.

:: There seem to be some things that could be using parameters:
::; backlog, next_changelog: Link to the next changelog
::; next_version: Next version
::; closed_until: Forcing a closed state by giving the (estimated) end of the closed state.
::; frozen_until: Forcing a frozen state by giving the (estimated) end of the frozen state. ''For situations like the release of 3.2(?).''

:: The year used by the defaults could and probably should be completely automated using <code><nowiki>{{CURRENTYEAR}}</nowiki></code>.

:: In order to call {{tl|GitStatus}} without parameter there could be a subtemplate, for example <code><nowiki>{{GitStatus/main}}</nowiki></code> called from {{tl|GitStatus}} using those parameters. That way any irregular updates would only have to be added to the parameters {{tl|GitStatus}} use when calling <code><nowiki>{{GitStatus/main}}</nowiki></code>.

:: The template would be shown just like before for now.

:: A draft of the documentation of the functionality is for now available in [[User:Johan G/GitStatus/main|my sandbox]].

:: Any comments or further ideas are most welcome!

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

== Please update Polish translation ==

| pl = 
'''Aktualna wersja:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pl}}) '''Następne wydanie:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] ({{Current release|nrd}} od teraz) Zobacz szczegóły [[release plan|planu wydawniczego]]

[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 14:48, 6 August 2023 (UTC)

== Chinese Translation ==

| zh = 
'''当前发布版本：''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:Y"年"Mj"日"|{{Current release|fulldate}}|zh}}) '''下次更新版本：''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|(距今还有{{Current release|nrd}})|}} 详见 [[release plan | 发布计划]].

[[User:Sidiliang|Sidiliang]] ([[User talk:Sidiliang|talk]]) 06:28, 27 December 2023 (UTC)

Template talk:GitStatus

2023-12-27T06:28:34Z

Sidiliang: /* Chinese Translation */

== Updating and improving the status template(s) ==
{{tl|GitStatus}}, {{tl|GitStatus:closed}}, {{tl|GitStatus:frozen}} and {{tl|GitStatus:open}}

As they are largely undocumented, do not use parameters and some data, like the next release and the dates is repeated many times and have to be edited in many places, maintenance is a hassle. In essence they could be more automated and better documented so that maintaining them would be more straight forward.

Some things I could see useful is having the current and next releases as separate templates (they could be useful in other places as well) and having to edit the dates only in special circumstances and doing that through parameters in those cases. Also, why four separate templates?

Are there other functionality you guys always have wanted but have not figured out or taken time to add?

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

: See [[FlightGear wiki:Village pump/Archive 2013#Automating Template:Git status]]
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:57, 18 December 2014 (UTC)

:: Ah, I had completely forgotten about that. Thanks Gijs.

:: There seem to be some things that could be using parameters:
::; backlog, next_changelog: Link to the next changelog
::; next_version: Next version
::; closed_until: Forcing a closed state by giving the (estimated) end of the closed state.
::; frozen_until: Forcing a frozen state by giving the (estimated) end of the frozen state. ''For situations like the release of 3.2(?).''

:: The year used by the defaults could and probably should be completely automated using <code><nowiki>{{CURRENTYEAR}}</nowiki></code>.

:: In order to call {{tl|GitStatus}} without parameter there could be a subtemplate, for example <code><nowiki>{{GitStatus/main}}</nowiki></code> called from {{tl|GitStatus}} using those parameters. That way any irregular updates would only have to be added to the parameters {{tl|GitStatus}} use when calling <code><nowiki>{{GitStatus/main}}</nowiki></code>.

:: The template would be shown just like before for now.

:: A draft of the documentation of the functionality is for now available in [[User:Johan G/GitStatus/main|my sandbox]].

:: Any comments or further ideas are most welcome!

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

== Please update Polish translation ==

| pl = 
'''Aktualna wersja:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pl}}) '''Następne wydanie:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] ({{Current release|nrd}} od teraz) Zobacz szczegóły [[release plan|planu wydawniczego]]

[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 14:48, 6 August 2023 (UTC)

== Chinese Translation ==

| zh = 
'''当前发布版本：''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:Y"年"Mj"日"|{{Current release|fulldate}}|zh}}) '''下次更新版本：''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|(距今还有{{Current release|nrd}})|}} 详见 [[release plan]].

[[User:Sidiliang|Sidiliang]] ([[User talk:Sidiliang|talk]]) 06:28, 27 December 2023 (UTC)

Template talk:GitStatus

2023-12-27T06:26:16Z

Sidiliang: /* Chinese Translation */ new section

== Updating and improving the status template(s) ==
{{tl|GitStatus}}, {{tl|GitStatus:closed}}, {{tl|GitStatus:frozen}} and {{tl|GitStatus:open}}

As they are largely undocumented, do not use parameters and some data, like the next release and the dates is repeated many times and have to be edited in many places, maintenance is a hassle. In essence they could be more automated and better documented so that maintaining them would be more straight forward.

Some things I could see useful is having the current and next releases as separate templates (they could be useful in other places as well) and having to edit the dates only in special circumstances and doing that through parameters in those cases. Also, why four separate templates?

Are there other functionality you guys always have wanted but have not figured out or taken time to add?

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

: See [[FlightGear wiki:Village pump/Archive 2013#Automating Template:Git status]]
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:57, 18 December 2014 (UTC)

:: Ah, I had completely forgotten about that. Thanks Gijs.

:: There seem to be some things that could be using parameters:
::; backlog, next_changelog: Link to the next changelog
::; next_version: Next version
::; closed_until: Forcing a closed state by giving the (estimated) end of the closed state.
::; frozen_until: Forcing a frozen state by giving the (estimated) end of the frozen state. ''For situations like the release of 3.2(?).''

:: The year used by the defaults could and probably should be completely automated using <code><nowiki>{{CURRENTYEAR}}</nowiki></code>.

:: In order to call {{tl|GitStatus}} without parameter there could be a subtemplate, for example <code><nowiki>{{GitStatus/main}}</nowiki></code> called from {{tl|GitStatus}} using those parameters. That way any irregular updates would only have to be added to the parameters {{tl|GitStatus}} use when calling <code><nowiki>{{GitStatus/main}}</nowiki></code>.

:: The template would be shown just like before for now.

:: A draft of the documentation of the functionality is for now available in [[User:Johan G/GitStatus/main|my sandbox]].

:: Any comments or further ideas are most welcome!

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

== Please update Polish translation ==

| pl = 
'''Aktualna wersja:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pl}}) '''Następne wydanie:''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] ({{Current release|nrd}} od teraz) Zobacz szczegóły [[release plan|planu wydawniczego]]

[[User:PlayeRom|PlayeRom]] ([[User talk:PlayeRom|talk]]) 14:48, 6 August 2023 (UTC)

== Chinese Translation ==

| zh = 
'''当前发布版本：''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:Y"年"Mj|{{Current release|fulldate}}|zh}}) '''下次更新版本：''' [[Changelog {{Current release|nr}}|{{Current release|nr}}]] {{#if: {{Current release|nrd}}|(距今还有{{Current release|nrd}})|}} 详见 [[release plan]].

Template:News

2023-12-27T06:14:53Z

Sidiliang:

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: Y"年"F | {{{date|last month}}} | zh }}通讯（英文）]] （[[FlightGear Newsletter|所有历史通讯]]）
}}
{{Localized Release Announcement |date=18-10-2023 |version=2020.3.19}}
{{Localized Release Announcement |date=21-03-2023 |version=2020.3.18}}
{{Localized Release Announcement |date=09-12-2022 |version=2020.3.18 |codename=RC}}
{{Localized Release Announcement |date=22-11-2022 |version=2020.3.17}}
{{Localized Release Announcement |date=20-10-2022 |version=2020.3.16}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:News

2023-12-27T06:12:01Z

Sidiliang:

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: Y"年"F | {{{date|last month}}} | zh }}通讯]] ([[FlightGear Newsletter|历史归档]])
}}
{{Localized Release Announcement |date=18-10-2023 |version=2020.3.19}}
{{Localized Release Announcement |date=21-03-2023 |version=2020.3.18}}
{{Localized Release Announcement |date=09-12-2022 |version=2020.3.18 |codename=RC}}
{{Localized Release Announcement |date=22-11-2022 |version=2020.3.17}}
{{Localized Release Announcement |date=20-10-2022 |version=2020.3.16}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:News

2023-12-27T06:11:25Z

Sidiliang:

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: Y"年" F | {{{date|last month}}} | zh }} 通讯]] ([[FlightGear Newsletter|历史归档]])
}}
{{Localized Release Announcement |date=18-10-2023 |version=2020.3.19}}
{{Localized Release Announcement |date=21-03-2023 |version=2020.3.18}}
{{Localized Release Announcement |date=09-12-2022 |version=2020.3.18 |codename=RC}}
{{Localized Release Announcement |date=22-11-2022 |version=2020.3.17}}
{{Localized Release Announcement |date=20-10-2022 |version=2020.3.16}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:News

2023-12-27T06:10:27Z

Sidiliang:

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: F"年" Y | {{{date|last month}}} | zh }} 月度简讯]] ([[FlightGear Newsletter|历史归档]])
}}
{{Localized Release Announcement |date=18-10-2023 |version=2020.3.19}}
{{Localized Release Announcement |date=21-03-2023 |version=2020.3.18}}
{{Localized Release Announcement |date=09-12-2022 |version=2020.3.18 |codename=RC}}
{{Localized Release Announcement |date=22-11-2022 |version=2020.3.17}}
{{Localized Release Announcement |date=20-10-2022 |version=2020.3.16}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:Localized Release Announcement

2023-12-27T06:07:42Z

Sidiliang:

<includeonly>{{LangSwitch
| en =  
*'''{{#time: F d"," Y | {{{date}}} | en}}:''' {{#if: {{{version|}}}  | FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} is released.  | {{{en|{{{en|{{{1|}}}}}}}}}}}
| ca = 
* '''{{#time: d F Y | {{{date}}} | ca}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} llançat.
| {{{ca|{{{en|{{{1|}}}}}}}}}}}
| de = 
* '''{{#time: d"." F Y | {{{date}}} | de}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} wird veröffentlicht.
| {{{de|{{{en|{{{1|}}}}}}}}}}}
| es = 
*'''{{#time: d "de" F "de" Y | {{{date}}} | es}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} lanzado.
| {{{es|{{{en|{{{1|}}}}}}}}}}}
| fr = 
*'''{{#time: d F Y | {{{date}}} | fr}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} publiée.
| {{{fr|{{{en|{{{1|}}}}}}}}}}}
| it = 
* '''{{#time: d F Y | {{{date}}} | it}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} rilasciato.
| {{{it|{{{en|{{{1|}}}}}}}}}}}
| nl = 
* '''{{#time: d F Y | {{{date}}} | nl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} vrijgegeven.
| {{{nl|{{{en|{{{1|}}}}}}}}}}}
| pl = 
* '''{{#time: d F Y | {{{date}}} | pl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} wydana.
| {{{pl|{{{en|{{{1|}}}}}}}}}}}
| pt = 
* '''{{#time: d "de" F "de" Y | {{{date}}} | pt}}:''' {{#if: {{{version|}}}
| Lançado o FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}}.
| {{{pt|{{{en|{{{1|}}}}}}}}}}}
| ru = 
* '''{{#time: d F Y | {{{date}}} | ru}}:''' {{#if: {{{version|}}}
| ??????? FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}}.
| {{{ru|{{{en|{{{1|}}}}}}}}}}}
| sl = 
* '''{{#time: d. F Y | {{{date}}} | sl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} objaviti.
| {{{ru|{{{en|{{{1|}}}}}}}}}}}
| zh = 
* '''{{#time: Y"年"m"月"d"日" | {{{date}}} | zh}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} 版本正式发布。
| {{{zh|{{{en|{{{1|}}}}}}}}}}}
| lang={{{lang|}}}
}}</includeonly><noinclude>
{{WIP|<big>'''It all works. We could use this template right away!'''</big>}}
{{Informative template|1=
== Goal ==
This template is used for translating news in the {{tl|news}} template displayed on the [[Main Page]].

* Translated dates based on language prefix of the main page.
* For a new FlightGear release it will show (translated) texts.
* You can also type in custom text and its translations for not release-specific news (but keep the dates).

== Usage ==
{{obr}}'''Localized Release Announcement'''{{!}}date= {{!}}version= {{!}}codename= {{!}}''lang=''{{cbr}}
{{obr}}'''Localized Release Announcement'''{{!}}date= {{!}}en={{!}}ca={{!}}de={{!}}es={{!}}fr={{!}}it={{!}}nl={{!}}pl={{!}}pt={{!}}ru={{!}}sl={{cbr}}

All parameters but '''date''' are optional.

; date: Date of the release in any format like ''<d>-<m>-<yyyy>'' (or ''<Month> <d>, <yyyy>''), for example '''{{#time: d-m-Y|now}}'''.

; version: Version of the release, for example '''3.4''' or '''{{Current release|cr}}.2'''. (optional)

; codename: Default airport or name of release, for example '''Bergen'''. (optional)

; LE(en/es/fr): For other news to be used like {{tl|LangSwitch}}, for example <code><nowiki>| en = Hello World | de = Hallo Welt | es...</nowiki></code> (optional)

; lang: Language override for testing and demonstration purposes. (optional)

== Example ==
===With Codename===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}} {{!}}version={{Current release|cr}} {{!}}codename=Bergen{{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|version={{Current release|cr}}|codename=Bergen}}
or in Português:
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|version={{Current release|cr}}|codename=Bergen|lang=pt}}
----
===Without Codename===
{{obr}}Localized Release Announcement {{!}}date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}} {{!}}version=3.6{{cbr}} (Spanish [[Es/Portada]])
{{Localized Release Announcement|date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}|version=3.6}}
On a spanish Page like [[Es/Portada]]:
{{Localized Release Announcement|date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}|version=3.6|lang=es}}
----
===Translated Date only===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}} {{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}}}
or Russian {{Localized Release Announcement|date={{#time: d-m-Y|now}}|lang=ru}}
Then add your message.
----
===Other News===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}}
{{!}}en=Hello World
{{!}}de=Hallo Welt
{{!}}pt=Olá mundo
{{!}}it=Ciao mondo
{{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo}}
Italian:
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo|lang=it}}
Dutch (nl) - no translation for message given here, shows english message and dutch date (just like {{tl|LangSwitch}})
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo|lang=nl}}
== Related templates ==
* {{tl|news}}

}}

[[Category:Templates]]
</noinclude>

Template:Localized Release Announcement

2023-12-27T06:05:44Z

Sidiliang:

<includeonly>{{LangSwitch
| en =  
*'''{{#time: F d"," Y | {{{date}}} | en}}:''' {{#if: {{{version|}}}  | FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} is released.  | {{{en|{{{en|{{{1|}}}}}}}}}}}
| ca = 
* '''{{#time: d F Y | {{{date}}} | ca}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} llançat.
| {{{ca|{{{en|{{{1|}}}}}}}}}}}
| de = 
* '''{{#time: d"." F Y | {{{date}}} | de}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} wird veröffentlicht.
| {{{de|{{{en|{{{1|}}}}}}}}}}}
| es = 
*'''{{#time: d "de" F "de" Y | {{{date}}} | es}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} lanzado.
| {{{es|{{{en|{{{1|}}}}}}}}}}}
| fr = 
*'''{{#time: d F Y | {{{date}}} | fr}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} publiée.
| {{{fr|{{{en|{{{1|}}}}}}}}}}}
| it = 
* '''{{#time: d F Y | {{{date}}} | it}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} rilasciato.
| {{{it|{{{en|{{{1|}}}}}}}}}}}
| nl = 
* '''{{#time: d F Y | {{{date}}} | nl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} vrijgegeven.
| {{{nl|{{{en|{{{1|}}}}}}}}}}}
| pl = 
* '''{{#time: d F Y | {{{date}}} | pl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} wydana.
| {{{pl|{{{en|{{{1|}}}}}}}}}}}
| pt = 
* '''{{#time: d "de" F "de" Y | {{{date}}} | pt}}:''' {{#if: {{{version|}}}
| Lançado o FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}}.
| {{{pt|{{{en|{{{1|}}}}}}}}}}}
| ru = 
* '''{{#time: d F Y | {{{date}}} | ru}}:''' {{#if: {{{version|}}}
| ??????? FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}}.
| {{{ru|{{{en|{{{1|}}}}}}}}}}}
| sl = 
* '''{{#time: d. F Y | {{{date}}} | sl}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} objaviti.
| {{{ru|{{{en|{{{1|}}}}}}}}}}}
| zh = 
* '''{{#time: Y m d | {{{date}}} | zh}}:''' {{#if: {{{version|}}}
| FlightGear [[Changelog {{{version}}}|{{{version}}}]] {{#if:{{{codename|}}}|"{{{codename}}}"}} 版本正式发布。
| {{{zh|{{{en|{{{1|}}}}}}}}}}}
| lang={{{lang|}}}
}}</includeonly><noinclude>
{{WIP|<big>'''It all works. We could use this template right away!'''</big>}}
{{Informative template|1=
== Goal ==
This template is used for translating news in the {{tl|news}} template displayed on the [[Main Page]].

* Translated dates based on language prefix of the main page.
* For a new FlightGear release it will show (translated) texts.
* You can also type in custom text and its translations for not release-specific news (but keep the dates).

== Usage ==
{{obr}}'''Localized Release Announcement'''{{!}}date= {{!}}version= {{!}}codename= {{!}}''lang=''{{cbr}}
{{obr}}'''Localized Release Announcement'''{{!}}date= {{!}}en={{!}}ca={{!}}de={{!}}es={{!}}fr={{!}}it={{!}}nl={{!}}pl={{!}}pt={{!}}ru={{!}}sl={{cbr}}

All parameters but '''date''' are optional.

; date: Date of the release in any format like ''<d>-<m>-<yyyy>'' (or ''<Month> <d>, <yyyy>''), for example '''{{#time: d-m-Y|now}}'''.

; version: Version of the release, for example '''3.4''' or '''{{Current release|cr}}.2'''. (optional)

; codename: Default airport or name of release, for example '''Bergen'''. (optional)

; LE(en/es/fr): For other news to be used like {{tl|LangSwitch}}, for example <code><nowiki>| en = Hello World | de = Hallo Welt | es...</nowiki></code> (optional)

; lang: Language override for testing and demonstration purposes. (optional)

== Example ==
===With Codename===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}} {{!}}version={{Current release|cr}} {{!}}codename=Bergen{{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|version={{Current release|cr}}|codename=Bergen}}
or in Português:
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|version={{Current release|cr}}|codename=Bergen|lang=pt}}
----
===Without Codename===
{{obr}}Localized Release Announcement {{!}}date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}} {{!}}version=3.6{{cbr}} (Spanish [[Es/Portada]])
{{Localized Release Announcement|date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}|version=3.6}}
On a spanish Page like [[Es/Portada]]:
{{Localized Release Announcement|date={{CURRENTMONTHNAME}} {{CURRENTDAY}}, {{CURRENTYEAR}}|version=3.6|lang=es}}
----
===Translated Date only===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}} {{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}}}
or Russian {{Localized Release Announcement|date={{#time: d-m-Y|now}}|lang=ru}}
Then add your message.
----
===Other News===
{{obr}}Localized Release Announcement {{!}}date={{#time: d-m-Y|now}}
{{!}}en=Hello World
{{!}}de=Hallo Welt
{{!}}pt=Olá mundo
{{!}}it=Ciao mondo
{{cbr}}
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo}}
Italian:
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo|lang=it}}
Dutch (nl) - no translation for message given here, shows english message and dutch date (just like {{tl|LangSwitch}})
{{Localized Release Announcement|date={{#time: d-m-Y|now}}|en=Hello World|de=Hallo Welt|pt=Olá mundo|it=Ciao mondo|lang=nl}}
== Related templates ==
* {{tl|news}}

}}

[[Category:Templates]]
</noinclude>

Template:News

2023-12-27T05:53:45Z

Sidiliang: Updated Chinese translation for News

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|历史归档]])
}}
{{Localized Release Announcement |date=18-10-2023 |version=2020.3.19}}
{{Localized Release Announcement |date=21-03-2023 |version=2020.3.18}}
{{Localized Release Announcement |date=09-12-2022 |version=2020.3.18 |codename=RC}}
{{Localized Release Announcement |date=22-11-2022 |version=2020.3.17}}
{{Localized Release Announcement |date=20-10-2022 |version=2020.3.16}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Zh/首页

2023-12-27T05:50:42Z

Sidiliang:

{{Main page/Header
|title = 欢迎来到[[FlightGear wiki|FlightGear百科]]！
|subtitle = ''自由飞行！''
|rightbox = {{Main page/Languages}}
|introduction =
[[Help:Your first article|欢迎您加入到]] FlightGear 百科的中文翻译中!

|rightcolumn1 = [[File:Portal user.png|40px]]</div>
[[Zh/Portal:用户|使用入门]] 
'''[[Zh/FlightGear新手|FlightGear新手上路]]''' 
[[Frequently asked questions|常见问题]] • [[Troubleshooting problems|解决问题]] 
[[Howto: Install scenery|安装地景]] • [[Howto: Install aircraft|安装机模]] 
[[Howto: Fly a helicopter|驾驶直升飞机]]
|rightcolumn2 = [[File:Portal developer.png|40px]]</div>
[[:zh:Portal:Developer|开发]] 

[[Portal:Developer/Aircraft|机模]] • [[Portal:Developer/Scenery|地景]] • [[Portal:Embedded|嵌入式相关]] 
[[Howto: Place 3D objects with the UFO|在地景中放置物件]] • [[Howto: Create custom terrain|编辑地形]] [[Howto:Improve scenery in your area, or area of interest|地景: 如何改善你所在的区域]] [[编译和本地化FlightGear]] 
[[How the FlightGear project works|FlightGear项目的运作方式]]
|rightcolumn3 = [[File:Portal wiki.png|40px]]</div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|关于 FlightGear Wiki百科]] • [[zh:Help:Contents|帮助]] 
[[Help:Your first article|撰写你的第一篇文章]] • [[Help:Translate|翻译]] 
[[Special:Categories|其他分类]]

|sections =
{{Main page/Leftbox
|title = 关于FlightGear
|logo = FlightGear logo.png
|contents = '''[[FlightGear]]''' 是一个由来自世界各地的志愿者创建的飞行模拟器，以免费、开源的 [[GNU General Public License|GPL]] 软件形式发布。 FlightGear 已被广泛用于 [[Professional and educational FlightGear users|学术研究、教育]], 以及娱乐。

FlightGear 附带一套图文并茂的文档, 特别是安装包内附带的 "[http://flightgear.sourceforge.net/manual/2020.3/ 用户手册]"。本百科站提供了更多与使用及开发有关的文档。

=== 我正在寻找 … ===
* [[Zh/Portal:用户|使用FlightGear方面的帮助]]
* [[:zh:Portal:Developer|如何为FlightGear项目做出贡献]]
* [[table of models|有关所有为FlightGear开发的机模（飞机插件）的信息]]
}}
{{Main page/Leftbox
|title = 新闻
|logo = Nuvola apps knewsticker.png
|contents = {{News}}
}}
{{Main page/Leftbox
|title = 你是否知道......
|logo = Nuvola apps ktip.png
|contents = {{Did you know}}
}}

}}

{{Main page/Rightcolumn
|title = 高亮内容
|contents = <center style="padding-top: 0.9em">[[File:Innsbruck_at_night_in_FlighGear_with_OSM2City_worldbuild_03.jpg|frameless]]</center>
|padding-right = 23px
}}奥地利因斯布鲁克上空的景色。 '''FlightGear 2020.3.8''' 已经 [https://www.flightgear.org/download/ 在官网发布] ，带来了'''全球范围'''的基于OSM2City的 3D 建筑, 道路, 以及其他物件。更多详见 [[OSM2City 1st Worldbuild|'''OSM2City的第一版全球地景''']].{{Main page/Rightcolumn
|title = [[:Category:Screenshot of the month|月度最佳截图]]
|contents = <center style="padding-top: 0.9em">{{POTM/{{#time: Y-m }}}}</center>
|padding-right = 23px
}}
{{Main page/Rightcolumn end
|title = [[FlightGear and Git|开发仓库状态]]
|contents = <center style="padding-top: 0.9em">{{GitStatus}}</center>
|padding-right = 23px
}}

[[Category:FlightGear wiki]]

Template:Did you know

2023-12-27T05:49:04Z

Sidiliang: Updated Chinese translation for did you know

{{LangSwitch
| ca = 
*...FlightGear s'utilitza en diversos [http://www.atcflightsim.com/ simuladors aprovats per la FAA]?
*...podeu simular fallades aleatòries del sistema de forma realista?
*...qualsevol pot editar el codi font de FlightGear i contribuir al projecte?
*...tota la ciutat de París, França està disponible en models 3D?
*...hi ha [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles en aquest wiki?
| de = 
*... dass zufällige Systemausfälle realistisch simuliert werden können?
*... dass Sie den Quellcode von FlightGear bearbeiten können?
*... dass jeder dazu eingeladen ist, sich an der Entwicklung von FlightGear zu beteiligen?
*... dass das ganze Stadtzentrum von Paris in 3D nachgebaut ist?
*... dass Sie Ihr Flugzeug [[Dual control|zusammen mit einem (Co-) Piloten]] über [[Multiplayer_Howto|Multiplayer]] steuern können?
| en = 
*...that FlightGear is used in several [http://www.atcflightsim.com/ FAA approved simulators]?
*...that you can simulate random system failures realistically?
*...that anyone can edit FlightGear source and contribute to the project?
*...that the whole city of Barcelona, Spain is [[Suggested_airports#Developed_airports_situated_in_developed_regions|available]] in 3D models?
*...that there are [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles on this wiki?
| es = 
* ...puedes simular fallos aleatorios de sistemas realísticamente?
* ...cualquiera puede editar el código fuente de FlightGear y contribuir al proyecto?
* ...la ciudad de París en Francia está completamente modelada en 3D?
* ...que puedes usar [[Dual control/es|Control Dual|cabina compartida]] en algunos aviones para poder jugar con otros pilotos en la red multijugador?
| fa = 
*...در چندین شبیه ساز مورد تائید اداره هوانوردی فدرال استفاده می شود؟
*...که شما می توانید از کار افتادن سامانه های پروازی را شبیه سازی کنید؟
*...که هر کسی می تواند کدهای این شبیه ساز را ویرایش و در توسعه آن همکاری کند؟
*...تمام منطقه پروازی کشور ایران و عوارض سطح زمین آن شبیه سازی شده اند؟
*...که تعداد [[Special:Statistics|{{NUMBEROFARTICLES}}]] مقاله در این ویکی وجود دارد؟
| fr = 
*...que FlightGear est en service dans plusieurs [http://www.atcflightsim.com/ Simulateurs approuvés par la FAA] ?
*...que vous pouvez simuler des pannes système aléatoires de manière réaliste ?
*...que n'importe qui peut éditer le code source de FlightGear et contribuer au projet ?
*...que toute la ville de Barcelone, en Espagne, est [[Suggested_airports#Developed_airports_situated_in_developed_regions|disponible]] dans des modèles 3D ?
*...qu'il y a [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles dans ce wiki ?
| it = 
* ...puoi simulare realisticamente guasti casuali?
* ...tutti possono modificare il codice di FlightGear e contribuire al progetto?
* ...per l'intera città di Parigi sono disponibili modelli 3D degli edifici?
* ...puoi [[Dual control|condividere il cruscotto]] (di alcuni velivoli) con un altro utente tramite la rete in modalità multiplayer?
| nl = 
*...het mogelijk is om willekeurige afwijkingen realistisch te simuleren?
*...iedereen de broncode van FlightGear kan aanpassen en zo bij kan dragen aan het project?
*...het centrum van Parijs, met gebouwen en landschap, beschikbaar is?
*...het mogelijk is om de cockpit te [[Dual control|delen]] (bij sommige vliegtuigen) met iemand anders via het [[:nl:Howto: Multiplayer|MP netwerk]]?
| pl = 
* ...FlightGear jest używany w kilku [http://www.atcflightsim.com/ symulatorach zatwierdzonych przez FAA]?
* ...można losowo symulować realistyczną awarię?
* ...każdy może edytować źródła FlightGeara i ulepszać projekt?
* ...całe miasto Barcelona w Hiszpanii jest [[Suggested_airports#Developed_airports_situated_in_developed_regions|wymodelowane]] w 3D?
* ...istnieje [[Special:Statistics|{{NUMBEROFARTICLES}}]] artykułów na tej wiki?
| pt = 
*...que você pode simular falhas realistas no sistema?
*...que qualquer um pode editar o FlightGear e contribuir?
*...que toda a cidade de Paris, França, está completamente modelada em 3D?
*...que você pode [[Pt/Controle duplo|compartilhar o controle]] (de algumas aeronaves) com outro usuário via [[Pt/Tutorial de Multiplayer|multiplayer]]?
| ru = 
*...что FlightGear используется в нескольких [http://www.atcflightsim.com/ симуляторах, одоборенных Федеральным управлением гражданской авиации США (FAA)]?
*...что вы можете реалистично симулировать случайные ошибки в системах?
*...что кто угодно может редактировать исходный код FlightGear и вносить свой вклад в проект?
*...что целый город Париж, Франция доступен в виде 3D-моделей?
*...что на этой Вики уже [[Special:Statistics|{{NUMBEROFARTICLES}}]] статей?

| zh = 
* ...FlightGear 被用于多个[http://www.atcflightsim.com/ 美国联邦航空管理局(FAA)批准的模拟器]？
* ...你可以真实地模拟随机的系统故障？
* ...任何人都可以编辑 FlightGear 的源代码并为该项目做出贡献？
* ...整个西班牙巴塞罗那市的地景都有[[Suggested_airports#Developed_airports_situated_in_developed_regions|可用的]]3D模型？
* ...这个百科上有[[Special:Statistics|{{NUMBEROFARTICLES}}]]篇文章？
| lang = {{{lang|}}}
}}<noinclude>
{{Informative template|1=
== Goal ==
This template is used on the main page to show some hints and tips.

If a language is not available the template will show the English text.
__TOC__
== Usage ==
<nowiki>{{</nowiki>'''did you know''' <nowiki>|</nowiki>''lang=''<nowiki>}}</nowiki>

; lang: Optional parameter that will override the language selection. Useful for debugging purposes.

== Alternative lines ==
Every now and then we can change the "Did you know" lines, replacing them by some of the ones below, or create new.

Each line should start with (for English):
*...that

=== English ===
==== Unused ====
*...that everyone can control our aircraft [[carriers]]?
*...that pressing the middle mouse button can control the throttle?

==== Already shown ====
'''These have already been shown, only reshow them if the list above is empty!'''
*...that you can [[Dual control|share the cockpit]] (of some aircraft) with another user over the multiplayer network?
*...that FlightGear is used by almost 25.000 users?
*...that some planes can perform [[dogfights]]?
*...that FlightGears [[scenery]] covers the whole globe?
*...that you can move your head around by holding the middle mouse button in view mode?
*...that you can chat live with both developers and users in our [http://flightgear.org/mail.html IRC channel]?
*...that you can toggle the [[menubar]] on or off by pressing F10, and even change the GUI style by pressing Shift + F10?
*...that FlightGear changed from [[PLIB]] to [[OSG]] as of version 1.9?
*...that you can walk through some of the [[aircraft]] cabins?
*...that FlightGear's first release was in July 1997?
*...that there are over 230 aircraft available?
*...that there's a total of over 150 liveries, based on real airlines, available for various planes?
*...that FlightGear is available in over 5 languages?
*...that everyone can control [[ATC-aircraft|air traffic]] as of version 1.9?
*...that crashes ignite real fires in the development version?
*...that MPDummy is positioned near runway 28L at [[KSFO]] to test your [[Howto: Multiplayer|multiplayer]] settings?
*...that FlightGear can simulate the real weather at any location at a given moment?
*...that [[Howto: Edit a livery|creating liveries]] is one of the easiest ways to contribute to the FlightGear project?
*...that you can set up full heigth storms with lightning and turbulence?
*...that FlightGear is used for research by several companies, including universities?
*...that [[OSG]] is able to render reflections on water?

=== Dutch ===
==== Unused ====
*...dat je met de middenste muisknop gas kan geven?
*...dat iedereen de [[carriers|vliegdekschepen]] kan besturen?
*...dat FlightGear ruim 25.000 gebruikers kent?
*...dat sommige gevechtsvliegtuigen echt in [[dogfights|gevecht]] kunnen gaan?
*...dat het FlightGear [[scenery|landschap]] de gehele aardbol omvat?
*...dat je de zitpositie kan veranderen door de middelste muistoets ingedrukt te houden in "view mode"?
*...dat een live chat sessie, via ons [http://flightgear.org/mail.html IRC kanaal], met gebruikers en ontwikkelaars mogelijk is?
*...dat je de [[menubar]] aan en uit kunt doen met F10, zelfs de window-stijl kan aanpassen met Shift-F10?
*...dat oudere versies van FlightGear [[PLIB]] gebruikten en dat nu [[OSG]] gebruikt wordt?
*...dat je in sommige vliegtuigen heen en weer kunt lopen, zelfs kasjes open en dicht kan doen?
*...dat de eerste publicatie van FlightGear in juli 1997 was?
*...dat er ruim 230 vliegtuigen beschikbaar zijn?
*...dat gebruikers ruim 150 verschillende vliegtuig-paintjobs (Liveries) voor ons hebben gemaakt?
*...dat FlightGear beschikbaar is in 5 verschillende talen?
*...dat iedereen [[ATC-aircraft|luchtverkeersleider]] kan zijn, op elk vliegveld?
*...dat een ongeluk in FlightGear [[Wildfire simulation|vuur]] kan veroorzaken?
*...dat FlightGear het huidige (echte) weer kan tonen en gebruiken, over de gehele wereld?
*...dat het maken van een [[Howto: Edit a livery|vliegtuig-paintjob]] (Liveries) één van de eenvoudigste manieren is om bij te dragen aan FlightGear.
*...dat het mogelijk is om stormen te simuleren, tot in de hoogste atmosfeer, met bliksem en turbulentie?
*...dat FlightGear gebruikt wordt als simulator bij bedrijven en universiteiten?
*...dat [[OSG]] in staat is om water-reflecties te tonen?

== Related templates ==
* {{tl|news}} – The template used on the main page to show the latest news.

}}

[[Category:Templates]]
</noinclude>

Zh/首页

2023-12-27T05:34:19Z

Sidiliang: Updated the Chinese main page to reflect the current content of the English page

{{Main page/Header
|title = 欢迎来到[[FlightGear wiki|FlightGear百科]]！
|subtitle = ''自由飞行！''
|rightbox = {{Main page/Languages}}
|introduction =
[[Help:Your first article|欢迎您加入到]] FlightGear 百科的中文翻译中!

|rightcolumn1 = [[File:Portal user.png|40px]]</div>
[[Zh/Portal:用户|使用入门]] 
'''[[Zh/FlightGear新手|FlightGear新手上路]]''' 
[[Frequently asked questions|常见问题]] • [[Troubleshooting problems|解决问题]] 
[[Howto: Install scenery|安装地景]] • [[Howto: Install aircraft|安装机模]] 
[[Howto: Fly a helicopter|驾驶直升飞机]]
|rightcolumn2 = [[File:Portal developer.png|40px]]</div>
[[:zh:Portal:Developer|开发]] 

[[Portal:Developer/Aircraft|机模]] • [[Portal:Developer/Scenery|地景]] • [[Portal:Embedded|嵌入式相关]] 
[[Howto: Place 3D objects with the UFO|在地景中放置物件]] • [[Howto: Create custom terrain|编辑地形]] [[Howto:Improve scenery in your area, or area of interest|地景: 如何改善你所在的区域]] [[编译和本地化FlightGear]] 
[[How the FlightGear project works|FlightGear项目的运作方式]]
|rightcolumn3 = [[File:Portal wiki.png|40px]]</div>
 [[Portal:Wiki|Wiki]] 

[[FlightGear Wiki|关于 FlightGear Wiki百科]] • [[zh:Help:Contents|帮助]] 
[[Help:Your first article|撰写你的第一篇文章]] • [[Help:Translate|翻译]] 
[[Special:Categories|其他分类]]

|sections =
{{Main page/Leftbox
|title = 关于FlightGear
|logo = FlightGear logo.png
|contents = '''[[FlightGear]]''' 是一个由来自世界各地的志愿者创建的飞行模拟器，以免费、开源的 [[GNU General Public License|GPL]] 软件形式发布。 FlightGear 已被广泛用于 [[Professional and educational FlightGear users|学术研究、教育]], 以及娱乐。

FlightGear 附带一套图文并茂的文档, 特别是安装包内附带的 "[http://flightgear.sourceforge.net/manual/2020.3/ 用户手册]"。本百科站提供了更多与使用及开发有关的文档。

=== 我正在寻找 … ===
* [[Zh/Portal:用户|使用FlightGear方面的帮助]]
* [[:zh:Portal:Developer|如何为FlightGear项目做出贡献]]
* [[table of models|有关所有为FlightGear开发的机模（飞机插件）的信息]]
}}
{{Main page/Leftbox
|title = 新闻
|logo = Nuvola apps knewsticker.png
|contents = {{News}}
}}
{{Main page/Leftbox
|title = 你知道吗？
|logo = Nuvola apps ktip.png
|contents = {{Did you know}}
}}

}}

{{Main page/Rightcolumn
|title = 高亮内容
|contents = <center style="padding-top: 0.9em">[[File:Innsbruck_at_night_in_FlighGear_with_OSM2City_worldbuild_03.jpg|frameless]]</center>
|padding-right = 23px
}}奥地利因斯布鲁克上空的景色。 '''FlightGear 2020.3.8''' 已经 [https://www.flightgear.org/download/ 在官网发布] ，带来了'''全球范围'''的基于OSM2City的 3D 建筑, 道路, 以及其他物件。更多详见 [[OSM2City 1st Worldbuild|'''OSM2City的第一版全球地景''']].{{Main page/Rightcolumn
|title = [[:Category:Screenshot of the month|月度最佳截图]]
|contents = <center style="padding-top: 0.9em">{{POTM/{{#time: Y-m }}}}</center>
|padding-right = 23px
}}
{{Main page/Rightcolumn end
|title = [[FlightGear and Git|开发仓库状态]]
|contents = <center style="padding-top: 0.9em">{{GitStatus}}</center>
|padding-right = 23px
}}

[[Category:FlightGear wiki]]

Zh/2020.3

2023-10-21T07:32:04Z

Sidiliang: 2020.3.19

{{changelogs|prev=2020.1|next=2022.1}}

可用语言: [[Zh/2020.3|中文]]，[[Changelog_2020.3|English]], [[Pl/Changelog_2020.3|Polish]]. 

请协助我们将其翻译为更多语言!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

自由、开源的飞行模拟器FlightGear即将迎来2020.3版本更新。这是FlightGear开始同时提供长期支持版本和预览版本之后的第二个长期支持版本，代表了全球的志愿者们为期两年的开发工作的结晶。FlightGear由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的且无比贴近真实的飞行模拟器。 FlightGear通常被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。

自v2018.3 LTS以来的主要更新包括：
*增加了即将到来的Compositor图形框架的预览，作为单独的二进制文件共同分发。
*对JSBSim和YASim飞行动力学模型进行了更新
*增加了DDS贴图缓存以减少加载时间
*加载更快、更节省内存的建筑
*改善了对航空母舰的支持

此外，官方机库中增加了30架全新的机模，71架机模得到了重大更新。

{{Disclaimer|id=final-fixed-function-release}}

项目开始于1997年，FlightGear的特色包括其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。

FlightGear - 自由飞翔！

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== 启动器 ==
* 添加了在首次启动时出现的欢迎屏幕，为首次使用的用户提供一些有用的信息。
* 机模插件现在可被标记为个人收藏，并可进行筛选，使得在数百个机模插件中寻找您喜爱的机模变得更容易。
* 启动器增加了对航空母舰的支持，现可在启动器中选择航空母舰以及设置起始位置。
* 当你想开始飞行的时候，现在只需要按下<code> Ctrl-F </code>快捷键！
* 增强了对停机坪和水上机场的支持，增加了对当前的飞机型号的检测。
* 大量错误修正和稳定性改进，尤其对机模和插件选项卡进行了改进。

== 画面 ==
* 此发行版随附[[Compositor]]渲染器以便开发人员预览使用。Compositor渲染器提供了全面支持XML配置的多通道渲染合成方式，并且支持ALS与集群着色。*增加了对DDS贴图缓存的支持，缩短了贴图文件的加载时间。
* 恒星能见度现可根据恒星大小和大气条件进行配置。
* 现可通过设置<code>/rendering/triangle-direction-lights=false</code>，可以使用不定向点精灵（non-directional point sprites）以便在不支持三角形点精灵（triangles of point sprites）的图形驱动器上正确运行。
* 添加了全新的Tower AGL视角。该视角与塔台视角类似，不同之处在于它使地面保持在飞机的正下方，并在飞机移动时平稳地缩放和平移。这使得该视角适合用于观察降落。
* 改善了机场草地贴图
* 新增了沿海地区的潮汐效果。
* 更新了加利福尼亚地区、亚洲地区、巴西北部、冰岛和扬马延（Jan Mayen）岛的区域材质定义（regional material definitions）。
* 增加了新的活火山 - Katla, Eyjafjallajokull, Surtsey.
* 新增基于实例的随机建筑与OpenStreetMap建筑，提高了性能并显著提高了画面质量。
* 改进了机翼弯折着色器。
* 现可从“View”菜单中启用/禁用飞行员模型。

== JSBSim ==
[以下部分翻译使用机器翻译，故部分内容或许将不准确或不自然。欢迎更多志愿者加入到翻译的行列中！] 
[Some part of the following translation is made by a machine translator, so it may be inaccurate or awkward. Any contributions to the translation are welcomed! ]
* 新增了设置涡轮机启动和加速时间的功能（参数<code><n1spinup></code>，<code><n2spinup></code>，<code><n1startrate></code>， <code><n2startrate></code>）。
* 现在，可以通过将<code><integrator></code>过滤器的<code><trigger></code>属性设置为负值，将其重置为0.0。
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* 现在可以在<code><function></code>中使用以下功能：<code>floor</code>，<code>ceil</code>和<code>fmod</code>。它们的功能与相应的C / C ++函数相同。
* <code> <function> </code>现在检查其参数数量。
* 新的系统组件linear_actuator
* 将燃料密度导出到属性树
* 为FCS组件添加了循环裁剪
* 增加了控制涡轮发动机转速下降因子的功能
* [向后兼容性损坏]陀螺仪现在正在测量转速而不是旋转加速度。测量旋转加速度的陀螺仪在现实世界中不存在。
* 飞行控制元件的输出属性不再绑定。这样可以节省许多虚假的警告消息，并允许在多个飞行控制中直接引用相同的属性。
* 现在通过质量分数而不是分压来管理大气中的水蒸气。前者是压力和温度变化时保留的物理量。
* 在尝试修整地面之前，请检查至少3个触点。
* 为FG UDP接口增加了仿真时间的可选传输
* 现在在执行过程中而不是在解析XML定义时检查用于表无关var的属性的存在。这放宽了需要在XML定义文件中声明过滤器，表格以及更一般的飞行控件的顺序。
* 电动引擎RPM现在已在UDP套接字中导出。
* 参数<code><ignitionn2></code>现在影响N2而不是N1。
* 现在在<code><clipto></code>中的max<min时给出警告，而不是引发异常
* 添加了使用新的fgfs可执行参数<code>-jsbsim-output-directive-file</code>在CSV文件中记录属性的功能

== YASim ==
* 改变了静摩擦力
* 新增支持跨音速效果.
* 现可通过设置<code>/fdm/yasim/respect-external-gear-state=true</code>来控制初始起落架状态。
* 新增对电动引擎的支持。

== 气象和环境 ==
* 在活火山附近湍流强度将会增加。
* 现可对METAR URL进行配置。
* 新增对METAR字符串的解码并以可读的形式显示在天气对话框中。

== 航空母舰 ==
* 启动器现支持两种全新的标准状态: <code>carrier-takeoff</code> 与 <code>carrier-approach</code>.
* 加入了全新的命令行参数 <code>--carrier-position</code>。这可用于选择航空母舰上的飞机起始位置。可选择的选项包括航母弹射器(e.g. <code>cat-1</code>)、停机位(e.g. <code>park-1</code>)、FLOLS进近位(<code>flols</code>)或abeam位置(<code>abeam</code>)。
* 现在即使在启动时不可用，GUI也可以检测到MPCarrier。要启用此功能，请设置<code>/sim/mp-carriers/auto-attach=true</code>。

== AI ==
* 增加了新的fgcommands：<code>add-aiobject</code>和<code>remove-aiobject</code>，可用于向AI子系统添加或移除物体。
* 增加了新的AI飞机, 包括波音747货机、CRJ900、SR-71、Saab 340.
* 对许多AI交通时刻表与航空公司涂装进行了更新。
* 新增在KEDW的Space Shuttle TAEM与进近场景。
* 新增了来自当地飞行员的准确Britten-Norman Islander性能数据。

== 联机飞行 ==
* 现可通过GUI使用swift以连接到VATSIM。
* FGComm现在支持COM1和COM2以及音量设置。
* 由机模定义的视角（飞行员视角（Pilot view），直升机视角（Helicopter view），塔台视角（Tower view）等）现在可以在联机飞行中的其他飞机上使用。通过单击“飞行员列表（Pilot List）”对话框的“视图（view）”列，可以查看特定的联机飞机（可在“Multiplayer/Pilot List”菜单下找到）。
* 新增<code>-disable-hold-short </code>选项，当进入联机飞行时，允许用户在跑道上出生。请谨慎使用此选项——突然在跑道上出现会对其他飞行员与ATC造成极大的困扰。
* 回放器现可记录联机中其他飞机的数据。

== Nasal 脚本语言 ==
* 现可配置核心Nasal模块的加载顺序。
* 增加了对通信接口Emesary的改进和错误修复。
* 增加了对核心代码库的改进。
* 改进了垃圾回收机制以降低画面卡顿。
* 增加了对可重新载入的nasal模块的支持。
* 更新了Canvas EFIS框架。
* 在Canvas Image中新增了三种设置像素颜色的方法。

== 飞机模型 ==
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持（例如为G500制作SVG）。FG1000 目前在 Cessna 182T, J3 Cub, Diamond DA40上可用。
* 改进了滑翔机的vario仪。
* 新增的机模:
** Airbus A320 - 客机
** Alisport Silent2Electro - 带有电动维持电机的滑翔机
** Bombardier Q400 DHC8-402 - 短途涡桨客机
** Breguet Atlantic BR 1150 - 远程海军巡逻飞机
** Cessna 140 - 通航飞机
** Cessna 208B Caravan - 短程客机，货机和多用途飞机
** Cirrus SR22T - 通航飞机
** Diamond DA40 NG - 通航飞机, 包括了带有 FG1000 玻璃仪表的驾驶舱
** Diamond DA62 Twinstar- 双引擎通航飞机
** Diamond HK36 Super Dimona - 滑翔机
** Dornier DO 28 Skyservant - 双引擎STOL多用途飞机
** Douglas TBD Devastator - 第二次世界大战鱼雷轰炸机
** Draco Wilga - 涡桨后三点野地起降飞机
** Fokker T.V - 双引擎轰炸机
** Glasfluegel H201B Standard Libelle - 滑翔机
** Grumman F11-Tiger - 舰载战斗机
** Grumman HU-16A Albatross - 双引擎两栖飞机
** Petliakov PE-8 (Ant-42/TB-7) - 第二次世界大战轰炸机
** Piper PA28-161 Warrior II - 通航飞机
** Pipistrel Alpha Electro - 电动教练飞机
** Pipistrel Taurus Electro G2.5 - 带有电动维持电机的滑翔机
** Rolladen Schneider LS8sc neo - 带有电动维持电机的标准滑翔机
** Robin DR400 Ecoflyer - 通航飞机
** Scheibe Bergfalke II/55 - 教练滑翔机
** Schempp-Hirth Arcus S - 高性能滑翔机
** Schleicher Ka6(CR) "Rhoensegler" - 教练滑翔机
** SEPECAT Jaguar GR.1 - 喷气攻击机
** SUMPAC - 人力飞机
** Supermarine Swift - 喷气战机
** Yak 52 - 教练机
* 对超过70个机模进行了更新，包括 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== 其他 ==
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 地图对话框现可显示直升机坪并可配置光标平移。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 屏幕截图的文件名现已修改为日期与时间。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.1之后的更新=
自2020.1预览版以来的变化包括：
* 对启动器进行了许多改进，包括新增欢迎屏幕与<code> Ctrl-F </code>开始飞行快捷键。
* 更新了加利福尼亚地区、巴西北部与冰岛的区域材质定义（regional material definitions），改进了机场草地贴图。
* 新增了沿海地区的潮汐效果。
* 增加了新的波音747货机 AI模型，更新了许多AI飞机涂装与时刻表。
* 更新了FG1000玻璃面板显示屏，更新内容包括可配置的VFR应答器代码、音量控制、增加了新的面板，可调整大小的UI以及对自定义SVG文件的支持。
* 机库中新增了许多飞机： HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* 大量机模得到了更新，包括 CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* 更新了中文，荷兰文，法文，德文，意大利文，波兰文和斯洛伐克文翻译。
* 对Terrasync的速度进行了优化：现在Terrasync将在第一次启动时下载一个包含机场信息的tarball压缩包并不再每次启动时进行检查更新，而是每24小时检查一次更新。
* 支持了GPS fly-by模式。
* 集成了 Sentry.io 以提供集中的崩溃报告。
* 新增了线程安全的粒子管理器，预计可减少因粒子导致的崩溃。

=2020.3.0之后的更新=

由于2020.3 是收到长期支持的版本，我们会根据用户反馈与自动崩溃报告对其进行问题修复与改进。以下列出了每个版本的主要变化。

==2020.3.1==
* 为启动器加入了帮助页面
* 修复了对直升机坪的处理
* 在移植到新的机库版本时移植已安装的机型
* TerraSync：提升了Windows下的启动性能

==2020.3.2==
* TerraSync 现在将等待模型完成同步过程，以避免启动时缺失模型
* 首次启动页面：增加了一个”滚动至底部“按钮
* Erik Hofman 进行了对潮汐的修复
* 启动器中使用了更好的滚动条，解决了一些与较长的机型列表有关的问题
* 支持 Apt.dat v1000 联络频率
* 修复了一个更改位置时的ATC崩溃
* 修复了许多 Michael Danilov 识别的翻译错误
* 显著改进了 Brazilian cerradio 区域 (SBMQ附近)
* 俄文翻译更新
* 修复了冰岛区域材质

==2020.3.3==
* 修复了右键拖动时的意外点击
* 修复了我们在'setup root'对话框中推荐的下载位置

==2020.3.4==
* 现可正确处理更多的METAR字符串，包括风传感器故障
* 修复了气团速度被两次应用在子模型上（例如在侧风中释放载荷时）的错误
* 修复了退出模拟器时与属性代码有关的崩溃
* 西班牙文翻译更新
* 禁用了前往EGEL的航班以防止AI交通代码中的崩溃

==2020.3.5==
* 将Windows下默认下载路径改为 %USERS%\FlightGear\Downloads, 来避免 Windows Defender 阻止不受信任的应用向此前使用的Documents文件夹中写入导致的问题。
* 修复了从其他应用返回FlightGear后滚动滚轮或点击鼠标时可能发生的崩溃
* 避免了使用基于 UIUC 的机型，例如莱特飞行者时发生的崩溃
* 修复了macOS中当摇杆无法开启时发生的崩溃
* 更新了macOS上的应用图标
* 修复了重置（reset）模拟器时Nasal发生的崩溃
* Canvas: 现允许各向异性过滤（Anisotropic filtering）
* 改进并使用了更大的月亮贴图
* 将 UFO 的速度调整为 11
* 修复了在一些特定的画质设置下滑行道标记消失的问题

==2020.3.6==
* 修复了下载默认机型目录时发生的崩溃
* 修复了在海洋中的地景启动时的停止响应
* 修复了在一些特定METAR下错误的天空与驾驶舱渲染
* 在启动器增加了新手上路（getting-started）提示（目前仅支持英文）
* 修复了航天飞机的AI场景（AI scenarios）
* 改进了飞行计划模式
* 修复了月亮/太阳的比例
* 修复子模型（submodels）的初始位置
* macOS: 增加了在临时镜像中运行时的警告
* Windows: 检测OpenGL驱动器是否缺失
* 修复 UIUC FDM 的崩溃
* 修复了与无效视角编号（view numbers）有关的崩溃
* 更恰当地处理FDM的NaN错误
* 改进了 KAP-140 进近模式（Approach mode）
* 更新了AI交通与涂装

==2020.3.7==
*TerraSync启用了全球范围内OSM2City建筑的分发
*C172 更新与错误修正
* 改进了欧洲与加利福尼亚地区的区域材质定义
*允许移动聊天框
*修复了与粒子系统有关的崩溃
*修复了北京及周边地区时区错误的问题
*修复了Canvas中显示non-Latin1字符串的问题
*修复了联网飞行模式下在跑道启动的逻辑，现可正确地将飞机放置于跑道外等待位置
*macOS: 修复了使用一些特定字体时的崩溃问题
*修复了当系统语言包括script specifier时启动器语言选择的问题（如zh-Hans-CN）
*修复了从机库加载时与aircraft-id属性有关的问题 ( https://sourceforge.net/p/flightgear/codetickets/2502/ )
*改进了Windows下对过时Intel图形驱动的检测

==2020.3.8==
*修复了<code><local></code>粒子系统的行为
*修复了秋季树木的外观

== 2020.3.9 ==
* 修复了与 Swift 有关的崩溃
* 修正了联机协议中使用的时间
* 修正了 FGData 的 URL
* 修复了重新加载缓存对话框中的错误
* 对 ATC 界面进行了改进，使其正确显示频率

== 2020.3.10 ==
* 应答机：现standby模式可正常工作
* 启动器：现可识别命令行中的地景与机模路径
* 启动器：改变了存储位置的方式以避免运行多个版本的FlightGear及在不同版本之间切换时出现问题
* 启动器：增加了“在退出时重启”（‘restart on quit’）的选项
* 修复了在加载ShapeFile数据时的NavCache报错
* 修复了在运行多个FlightGear副本时的NavCache报错

== 2020.3.11 ==
* 修复了一个2020.3.10中被引入的崩溃
* 改进了当机模搜索路径不存在时的报错信息
* 修复了未正确配置AI飞机滑行路径导致的崩溃
* 更新了AI交通的时间表

== 2020.3.12 ==
* 增加了对机模路径名称的验证
* 增加了更进一步的抗锯齿（8x）
* 增加了允许机模将自定义字体用于osg::Text的功能
* 增加了通用化的，结合了ALS procedural lights与Compositor lights的灯光
* 为澳大利亚地区增加了新的区域材质定义
* 修复了Basic Weather引擎输出无效气压高度的问题
* 修复了预览图路径搜索中存在的问题
* 修复了接近max-dist范围时声音系统存在的问题
* 修复了重置时发生的崩溃问题
* 修复了当AI飞机的目的地跑道无效时崩溃的问题
* 修复了Mapstructure RTE图层中的报错
* 修复了 --view-offset，使其使用正确的属性
* HUD：使垂直刻度的样式与水平刻度保持一致
* 改进了俄语和意大利语翻译
* 对天气对话框进行了数项改进
* 属性树浏览器（Property browser）：将文件夹的值以冗长的模式（verbose mode）显示
* 航路管理器（Route manager)：在存在同名航路点时现将自动选择正确的航路点
* 更新了AI交通的时间表，增加了新的AI飞机模型

== 2020.3.13 ==
* 修复了联机飞行员名单不出现的问题
* 修复了 JSBsim 线性执行器在特定条件下表现不佳的问题

== 2020.3.14 ==
* 增加了对add-ons路径的支持
* 新增了即时音频队列
* 对canvas对话框进行了改进，使其不抢占FG的鼠标焦点（与PUI对话框的行为类似）

== 2020.3.15 ==
* 修复了无线电音频摩尔斯电码的问题

== 2020.3.16 ==
* 修复了音频缩进问题。

== 2020.3.17 ==
* 导航无线电：更改选定频率或离开GPS从属模式时禁用低通滤波器。更改选定频率或离开 GPS 从属模式时，将禁用应用于信号质量的低通滤波器。
* 导航无线电：修复了一些新引入的问题并优化了旧代码。更新的内容：更改待机频率禁用了下一次调用 updateReceiver() 的低通滤波器; 这必须在更改选定频率时发生，但不在更改待机频率时发生。
* 自动驾驶仪输入：向自动驾驶仪的输入添加属性路径支持。允许间接定义自动驾驶仪（通过字符串属性），以便可以从-set.xml配置或在运行时进行调整。
* 在启动器中将五边进场的选项`--on-ground=false`替换为`--in-air`选项，以免产生误导。

== 2020.3.18 ==

* 新增对卫星地景 photoscenery 的支持。
* 全新的简单自动驾驶系统。
* 修复了 Navigraph 程序文件中 'between' 类型导致的崩溃。
==2020.3.19==
*增加了AI子模型碰撞效果
*修复了无效METAR字符串导致的崩溃

== 参考 ==
{{Appendix}}

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

[[Category:FlightGear changelogs‎]]
[[En:Changelog_2020.3]]
[[Pl:Changelog_2020.3]]

Follow me e-tron

2023-10-16T10:47:51Z

Sidiliang: /* Newer Versions */

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me e-tron is currently released as v5.1.

=== Change Log ===
V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figure below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png| Three Followme EVs lining up
File:Followme EV in a charging station.png| Followme EVs in a charging station, showing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png| Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png| Followme EV in a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png| Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png | Followme EV in a valley on the G318 Sichuan-Tibet Route
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png| Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Follow me e-tron

2023-10-16T10:47:24Z

Sidiliang: /* Newer Versions */ New images

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me e-tron is currently released as v5.1.

=== Change Log ===
V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figure below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png| Three Followme EVs lining up
File:Followme EV in a charging station.png| Followme EVs in a charging station, showing the dynamic scenery object system
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png| Followme EV in front of the Wapenyao toll station, at the endpoint of G1 National Highway
File:Followme EV in a service station.png| Followme EV in a service station
File:Followme EV on the G318 Sichuan-Tibet Route.png| Followme EV on the famous G318 Sichuan-Tibet Route
File:Followme EV in a valley.png
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png| Followme EV recharging alongside the G318 Sichuan-Tibet Route
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Follow me e-tron

2023-10-16T10:45:19Z

Sidiliang: /* Newer Versions */

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me e-tron is currently released as v5.1.

=== Change Log ===
V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figure below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
File:Followme EV.png
File:Followme EV in a charging station.png
File:Followme EV in front of a toll station, at the endpoint of G1 National Highway.png
File:Followme EV in a service station.png
File:Followme EV on the G318 Sichuan-Tibet Route.png
File:Followme EV in a valley.png
File:Followme EV recharging alongside the G318 Sichuan-Tibet Route.png
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

Follow me e-tron

2023-10-16T10:32:45Z

Sidiliang:

{{:{{PAGENAME}}/info}}
The '''Follow me e-tron''' or '''Follow me EV''' is a semi-fictional Follow-me vehicle based on [[Follow_me|Gijs's work]], but an electric-powered version with Chinese characteristics. It was made just for fun.

== Features ==
Being the '''very first electric car''' in FlightGear, the Follow me e-tron features a realistic electric supercar driving experience while having an exterior of the classic Renault Kangoo I Follow me vehicle.

[[File:FollowmeEV广州.png|center|700px|Screenshot of the FollowmeEV in Guangzhou]]

* Realistic electric engine written in Nasal.
* Detailed electrical system written in Nasal.
* Advanced steering helper (experimental)
* 'AutoCrash' system, which tries its best to keep you on the road.
* 'AutoSpeed' system, which keeps your speed constant.
* Auto Hold function
* Parking radar that detects terrain and alerts driver.
* Working airbags.
* Experimental AEB system.
* Configurable interior with several fully remodeled interior and working switches.
* Configurable instruments with several styles to choose from.
* Canvas glass display instrument for certain interior styles
* Compositor light support.
* Selectable license plate in Chinese style.
* Various of liveries
* Various of messages
* Full multiplayer support.
* Multiplayer passenger.
* Dynamic scenery object placement and management
* Limo variant
* Tutorials support in different languages
* Different interior styles to choose from.
* Save / Resume function.

== Videos ==
{{#ev:youtube|p-P6SkRu6PE}}
{{#ev:youtube|pq6Lb5GA3Bc}}
{{#ev:youtube|MGZU85t5LCo}}

== Version ==
The Follow me e-tron is currently released as v5.1.

=== Change Log ===
V5.1 Updates:

* Major improvements to the reset function
* Bug fixes and improvements

V5.0 Updates:

* Added an option to adjust brake intensity for keyboard control
* Further tuned engine and fixed the bug related to gear changing
* New liveries: Blackwhite, C919 Memorial
* Interior updates
* New magic bush tyre option for driving on killer grass
* New interior: 404Design 2.0, 404Design 2022 and Luxury 2.0
* New charging pile
* Exterior model improvements, especially on charging cap, wheels and doors
* Added rear plate with multiplayer support
* Improvements on sounds
* Added option to re-enable ALS procedural lights
* Default interior switched to 404Design
* Added door warnings for smart instruments
* General improvements, cleanups and bug fixes

V4.0 New Features:

* Added a limo varient
* New texture selector which works better under multiplayer
* New interior style: Race, 404Design
* New canvas glass display instrument for 404Design Interior
* New dynamic scenery object system
* New models for service station, toll gates, etc
* Added reverse indicator light

Updates and improvements:

* Major updates to the UV
* Major update to the Engine & electrical systems, (much) more realistic performance
* FDM improvements
* AEB improvements
* Minor texture and exterior/interior model updates
* Sounds updates
* Added multiplayer model detection support to radar(and AEB which relies on the radar)
* Many bug fixes

Changes after v4.0 alpha:

* Added battery remaining display
* Improvements to Nasal performance
* Huge bug fixes to the electrical system
* Many minor bug fixes
* Added option to adjust steering

Changes after v4.0 beta.1:

* Added error message to the smart instruments after the battery is drained
* Bug fixes

Changes after v4.0 beta.2:

* Bug fixes

V3.0 New Features:

* Configurable interior with several fully remodeled interior and working switches
* Functioning Airbags
* Experimental AEB system
* Experimental compositor light support
* Auto Hold function
* Save / Resume
* New tutorials

Improvements:

* Electrical system
* Brake system
* Sounds
* Effects
* Several bugs fixed

V2.0:

Updated features:

* Updated interior
* Exterior improvements
* Autospeed system
* New experimental steering system
* Parking radar system
* Sound improvements
* FDM improvements
* Liveries updates
* Tons of bug fixes

V1.0:

Initial Release

== Statistics ==
''Note: The figure below was measured before the v4.0 release. The entire engine received an update in the v4.0 release and the performance is now way more realistic.''

Top speed:
≤300kts/555.6km/h
=== Acceleration ===
Accelerate up to:
100km/h: 2.48 seconds
200km/h: 7.20 seconds
=== Battery ===
Electricity usage:
---km/charge (Yet to be determined)

== Gallery ==

=== Newer Versions ===
<gallery mode="packed">
File:Followme EV interior preview 2.jpg|Followme EV Interior
File:Followme EV in ZBNY.jpg|Followme EV in ZBNY
File:Followme EV interior preview.jpg|Followme EV Interior
</gallery>

=== Earlier Versions ===
<gallery mode="packed">
Followme EV historical screenshot.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot2.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot3.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot4.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot5.png|Screenshot of early versions of the Followme EV
Followme EV historical screenshot6.png|Screenshot of early versions of the Followme EV
FollowmeEV广州.png|Screenshot of the FollowmeEV in Guangzhou
FollowmeEV武汉2.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉3.png|Screenshot of the FollowmeEV in Wuhan
FollowmeEV武汉4.png|Screenshot of the FollowmeEV in Wuhan
</gallery>

== Related content ==
=== Forum topic ===
* {{forum link|title=Grand Tour with Follow me: From Beijing to Shenzhen|t=36211}}
===FlightGear China===
[http://www.fgprc.org FGPRC]

File:Followme EV Parked.png

2023-10-16T10:24:36Z