<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Aepcam</id>
	<title>FlightGear wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Aepcam"/>
	<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/Special:Contributions/Aepcam"/>
	<updated>2026-05-01T17:46:20Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.6</generator>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143656</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143656"/>
		<updated>2026-02-27T21:51:56Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* General Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
=== Reading Flight Data ===&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
=== Surface Controls ===&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
=== Radio and Navigation ===&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
=== Lighting ===&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
=== Camera and Views ===&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
=== MI-6PS Helicopter ===&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
=== Brakes ===&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
=== Utilities ===&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
=== Views ===&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
=== Position ===&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Radio ===&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
=== Helicopter ===&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
=== Get all flight data ===&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
=== Set up approach ===&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
=== Helicopter control ===&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
=== Camera control ===&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_logos&amp;diff=143651</id>
		<title>FlightGear logos</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_logos&amp;diff=143651"/>
		<updated>2026-02-23T00:00:12Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Feel free to add your FlightGear logo(s) here.&lt;br /&gt;
&lt;br /&gt;
== Official logo ==&lt;br /&gt;
=== 2011 - Present ===&lt;br /&gt;
[[File:FlightGear logo.png]]&lt;br /&gt;
&lt;br /&gt;
; Author: {{usr|Gijs|Gijs de Rooy}}, based on original icon.&lt;br /&gt;
; License: GNU GPL v2&lt;br /&gt;
{{inote|There is also an {{fgdata file|Docs/img/FlightGear_logo.svg|t=SVG version}} of this logo (added by {{fgdata commit|ef898e}}).}}&lt;br /&gt;
&lt;br /&gt;
=== 2000 - 2011 ===&lt;br /&gt;
[[File:Fglogosm.jpg]]&lt;br /&gt;
&lt;br /&gt;
; Author: Michael Smith &amp;lt;ref&amp;gt;{{Cite web&lt;br /&gt;
|url = http://flightgear.org/thanks.shtml&lt;br /&gt;
|title = http://flightgear.org/thanks.shtml&lt;br /&gt;
}}&amp;lt;/ref&amp;gt;&lt;br /&gt;
; Source: http://www.flightgear.org/ ([http://www.flightgear.org/legacy.shtml legacy])&lt;br /&gt;
&lt;br /&gt;
=== Until 2000 ===&lt;br /&gt;
[[File:Fglogosm_old1.jpg]]&lt;br /&gt;
&lt;br /&gt;
; Author: Unknown, uploaded by {{usr|Gijs}}&lt;br /&gt;
; Source: http://www.flightgear.org/ ([http://web.archive.org/web/19981212014011/http://flightgear.org/ archive])&lt;br /&gt;
&lt;br /&gt;
== A-10 Logo ==&lt;br /&gt;
&lt;br /&gt;
[[File:Wiki_logo.png]]&lt;br /&gt;
&lt;br /&gt;
* Author: Wes Summers&lt;br /&gt;
* License: http://creativecommons.org/licenses/by-sa/3.0/&lt;br /&gt;
* Source: [[Media:A-10_logo.pdf| Illustrator PDF]]&lt;br /&gt;
&lt;br /&gt;
== New Test Logo ==&lt;br /&gt;
[[File:Flightgear-logov2.png]]&lt;br /&gt;
&lt;br /&gt;
* Author: BBCTV (Japanese Flightgear User)&lt;br /&gt;
* License: Copyright Flightgear&lt;br /&gt;
* Source: Made with Adobe Illustrator&lt;br /&gt;
&lt;br /&gt;
== Set of logos for Wiki ==&lt;br /&gt;
&lt;br /&gt;
[[File:Fg_trails_lc.png]] [[File:Fg_wings_large.png]] [[File:Fg_wings_up.png]] [[File:Fg_trails_large.png]]&lt;br /&gt;
&lt;br /&gt;
* Author: Wes Summers&lt;br /&gt;
* License: http://creativecommons.org/licenses/by/3.0/&lt;br /&gt;
&lt;br /&gt;
== 3D logotype ==&lt;br /&gt;
[[File:FG happy new year 2.png]]&lt;br /&gt;
&lt;br /&gt;
* Author: Roman Alvarez&lt;br /&gt;
* Source: made with Cinema 4D and GIMP&lt;br /&gt;
&lt;br /&gt;
== Badge Logo ==&lt;br /&gt;
&lt;br /&gt;
[[File:Fglogo1.png]] [[File:Fglogowiki.png]][[File:Fglogoforum.png]]&lt;br /&gt;
&lt;br /&gt;
* Author: Michat&lt;br /&gt;
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.&lt;br /&gt;
&lt;br /&gt;
== FG Eagles Haunting Logo Motive ==&lt;br /&gt;
&lt;br /&gt;
[[File:FGMotive.png|left|FG Eagles Haunting logo motive]]{{-}}&lt;br /&gt;
&lt;br /&gt;
* FG Eagles Haunting logo motive&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== The F of FlightGear ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:Fglogo3baja.png|150px|The Flightgear's F  (dont search the X just try the F)72spi   -  Also available in 300dpi  high quality for printing purposes]]{{-}}&lt;br /&gt;
&lt;br /&gt;
* The F of FlightGear is also available in high resolution for printing.  [[:File:Fglogo3alta.png|Get Badged as FGSuperHero Now]]&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== FGType Logo Motive Spread the word * ==&lt;br /&gt;
[[File:Fglogo2baja.png|150px|FGType with a Waterman &amp;quot;Stylo&amp;quot; to Inkscape adventure]]{{-}}&lt;br /&gt;
&lt;br /&gt;
* FG is the Free and Open Flight Simulator&lt;br /&gt;
* FGType with a Waterman &amp;quot;inkLeak Stylo&amp;quot; to Inkscape adventure to the conquer of the FontForge&lt;br /&gt;
* Author: Michat de La Fontaine&lt;br /&gt;
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== FGsprite ==&lt;br /&gt;
&lt;br /&gt;
[[File:Fglogothesprite.png|FGSprite]]&lt;br /&gt;
&lt;br /&gt;
* Author: Michat&lt;br /&gt;
&lt;br /&gt;
== FGDesktop Icons ==&lt;br /&gt;
[[File:Logitofg.png||FG Custom Desktop Icon Green 56x50 1.2Kb PNG 90Dpi]]&lt;br /&gt;
[[File:Fgspritepurpurine.png|FG Sprite Purpurine 68x68 png]]&lt;br /&gt;
&lt;br /&gt;
* Author: Michat&lt;br /&gt;
&lt;br /&gt;
== FGAddONs ==&lt;br /&gt;
[[File:Fgaddonslogo202x89.png |FGAddONs Logo 202x89 PNG 17.8Kb 90Dpi]]&lt;br /&gt;
&lt;br /&gt;
* Author: Michat&lt;br /&gt;
== FDM YASim Yet Another Simulator ==&lt;br /&gt;
&lt;br /&gt;
[[File:Yasimlogo.png|FDM YASim Yet Another Simulator Logo]]&lt;br /&gt;
&lt;br /&gt;
== Compositor ==&lt;br /&gt;
&lt;br /&gt;
[[File:Compositor logo.png|400px|Compositor New Logo]]&lt;br /&gt;
&lt;br /&gt;
== Julia Photoscenery-GUI ==&lt;br /&gt;
[[File:FG-JPS.png]]&lt;br /&gt;
* Author: Michat&lt;br /&gt;
&lt;br /&gt;
== FG-MCP ==&lt;br /&gt;
[[File:FG-MCP.png]]&lt;br /&gt;
* Author: Michat&lt;br /&gt;
&lt;br /&gt;
== Badges ==&lt;br /&gt;
[[File:Mi6badgesmall.png||FG mi helicopter badge 123x123 PNG 90Dpi]]&lt;br /&gt;
== Understanding P-Factor for newbies ==&lt;br /&gt;
[[File:FG P-Factor.png|195px|Understanding P-Factor for newbies]]&lt;br /&gt;
&lt;br /&gt;
== Equiped and Ready logos ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Tutorialready.png|link=Tutorials]]&lt;br /&gt;
[[Image:Checklistready.png|link=Aircraft Checklists]]&lt;br /&gt;
[[Image:Routemanagerready.png|link=Route Manager]]&lt;br /&gt;
[[Image:Airrefuelingready.png|link=Howto:Aerial refueling]]&lt;br /&gt;
[[Image:Rembrandtready.png|link=Rembrandt]]&lt;br /&gt;
[[Image:Spacetripready.png|link=Category:Spaceflight]]&lt;br /&gt;
[[Image:Tooltipready.png|link=Tooltips]]&lt;br /&gt;
&lt;br /&gt;
* Author:Michat&lt;br /&gt;
* ''&amp;quot;Tooltip Ready&amp;quot;'' graphics derived from and added by mhab&lt;br /&gt;
* License: OFFGU. Only for FG (Flightgear) users. FlightGear users only.&lt;br /&gt;
&lt;br /&gt;
== Alternative ready logos == &lt;br /&gt;
[[Image:Airrefuel-ready.png|link=Howto:Aerial refueling]]&lt;br /&gt;
[[Image:Bombable-ready.png|link=Bombable]]&lt;br /&gt;
[[Image:Canvas-ready.png|link=Canvas]]&lt;br /&gt;
[[Image:Checklist-ready.png|link=Aircraft Checklists]]&lt;br /&gt;
[[Image:Dualcontrol-ready.png|link=Dual Control]]&lt;br /&gt;
[[Image:Rembrandt-ready.png|link=Rembrandt]]&lt;br /&gt;
[[Image:Space-ready.png|link=Category:Spaceflight]]&lt;br /&gt;
[[Image:Tutorial-ready.png|link=Tutorials]]&lt;br /&gt;
&lt;br /&gt;
* Author: {{usr|Bugman}} (Space-ready.png), {{usr|Red Leader}} (all the others)&lt;br /&gt;
* License: '''[http://creativecommons.org/licenses/by-sa/4.0/deed.en CC-BY-SA-4.0]''' (Space-ready.png), '''[http://creativecommons.org/licenses/by-sa/3.0/deed.en CC-BY-SA-3.0]''' (all the others)&lt;br /&gt;
&lt;br /&gt;
== Desktop Backgrounds ==&lt;br /&gt;
&lt;br /&gt;
[[File:FGBGBG.png|left|300px|1024x768 Mulberry + FG Fosfo bug]]&lt;br /&gt;
[[File:Fgorangefeather.png|300px|1024x768 FG Feather Orange]]&lt;br /&gt;
[[File:Fgbg.png|300px|1024x768 BLUE Super Relax Recommended]]&lt;br /&gt;
[[File:1024x768softuserblack2.png|300px|Desktop Background]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:1024x768softuserblack3.png|300px|Desktop Background]]&lt;br /&gt;
[[File:1024x768softuserblack4.png|300px|Desktop Background]]&lt;br /&gt;
[[File:1024x768softuserblack5.png|300px|Desktop Background]]&lt;br /&gt;
[[File:1024x768softuserblack6.png|300px|Desktop Background]]&lt;br /&gt;
&lt;br /&gt;
[[File:1366x768brazukas.png|300px|FG Brazukas]]&lt;br /&gt;
[[File:Lakeofconstance2.png|300px|Lake of Constance FG B-707 Background]]&lt;br /&gt;
[[File:1366x768cityoffriedrichshafen707.png|300px|City of Friedrichshafen 707 for The Lake of Constance Hangar]]&lt;br /&gt;
[[File:Fgmi6wallpurple.png|300px|1366x768 FG wallpaper mi6]]&lt;br /&gt;
&lt;br /&gt;
== FG Stripes ==&lt;br /&gt;
[[File:172P 01.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 02.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 03.jpg|300px|FG Stripes]]&lt;br /&gt;
&lt;br /&gt;
[[File:172P 04.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 05.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 06.jpg|300px|FG Stripes]]&lt;br /&gt;
&lt;br /&gt;
[[File:172P 07.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 08.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 09.jpg|300px|FG Stripes]]&lt;br /&gt;
&lt;br /&gt;
[[File:172P 10.jpg|300px|FG Stripes]]&lt;br /&gt;
[[File:172P 11.jpg|300px|FG Stripes]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear]]&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143650</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143650"/>
		<updated>2026-02-22T23:53:35Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Usage examples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
=== Reading Flight Data ===&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
=== Surface Controls ===&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
=== Radio and Navigation ===&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
=== Lighting ===&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
=== Camera and Views ===&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
=== MI-6PS Helicopter ===&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
=== Brakes ===&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
=== Utilities ===&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
=== Views ===&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
=== Position ===&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Radio ===&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
=== Helicopter ===&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
=== Get all flight data ===&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
=== Set up approach ===&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
=== Helicopter control ===&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
=== Camera control ===&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143649</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143649"/>
		<updated>2026-02-22T23:51:51Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Available tools */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
=== Reading Flight Data ===&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
=== Surface Controls ===&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
=== Radio and Navigation ===&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
=== Lighting ===&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
=== Camera and Views ===&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
=== MI-6PS Helicopter ===&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
=== Brakes ===&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
=== Multiplayer ===&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
=== Utilities ===&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
=== Views ===&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
=== Position ===&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Radio ===&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
=== Helicopter ===&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143648</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143648"/>
		<updated>2026-02-22T23:49:39Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Properties used */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
=== Views ===&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
=== Position ===&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Autopilot ===&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
=== Radio ===&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
=== Helicopter ===&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143647</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143647"/>
		<updated>2026-02-22T23:46:10Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* LICENSE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== License ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143646</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143646"/>
		<updated>2026-02-22T23:45:43Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* VERSION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== Version ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143645</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143645"/>
		<updated>2026-02-22T23:45:23Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* USAGE EXAMPLES */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== Usage examples ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143644</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143644"/>
		<updated>2026-02-22T23:44:36Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* KNOWN LIMITATIONS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== Know limitations ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143643</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143643"/>
		<updated>2026-02-22T23:43:48Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* ARCHITECTURE */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== Architecture ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143642</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143642"/>
		<updated>2026-02-22T23:42:37Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* PROPERTIES USED */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== Properties used ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143641</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143641"/>
		<updated>2026-02-22T23:39:10Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* AVAILABLE TOOLS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== Available tools ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143640</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143640"/>
		<updated>2026-02-22T23:37:14Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Requirements = */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ==&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143639</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143639"/>
		<updated>2026-02-22T23:36:31Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* FLIGHTGEAR CONFIGURATION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
=== Flightgear Configuration ===&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143638</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143638"/>
		<updated>2026-02-22T23:35:12Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* REQUIREMENTS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
== Requirements ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143637</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143637"/>
		<updated>2026-02-22T23:34:05Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* INSTALLATION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== Installation ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143636</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143636"/>
		<updated>2026-02-22T23:32:50Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* MAIN FEATURES */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== Main Features ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== INSTALLATION ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143635</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143635"/>
		<updated>2026-02-22T23:32:16Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* GENERAL DESCRIPTION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Description ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== MAIN FEATURES ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== INSTALLATION ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143634</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143634"/>
		<updated>2026-02-22T18:53:51Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* REQUIREMENTS */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GENERAL DESCRIPTION ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== MAIN FEATURES ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Windsurf, Claude Desktop, etc.)&lt;br /&gt;
&lt;br /&gt;
== INSTALLATION ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143633</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143633"/>
		<updated>2026-02-22T18:52:59Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* FG MCP Server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
=== FG MCP Server ===&lt;br /&gt;
[[File:FG-MCP.png|thumb|FG MCP server Logo]]&lt;br /&gt;
&lt;br /&gt;
With the help of the OpenCode IDE, using the free model integrated into this editor —named Big Pickle— and under the strict control of the loop through the Ralf Wiggum utility, Michat has developed an MCP server for FlightGear.&lt;br /&gt;
&lt;br /&gt;
The server requires python = &amp;quot;&amp;gt;=3.10&amp;quot; and fastmcp&amp;gt;=2.0.0. Initially, we faced issues with the Telnet connection, so we chose to modify the specifications to use HTTP instead.&lt;br /&gt;
&lt;br /&gt;
Through its functionalities, this MCP server allows controlling various FlightGear features via text prompts. The main ones include:&lt;br /&gt;
* Engine startup&lt;br /&gt;
* View switching&lt;br /&gt;
* Cockpit view rotation up to 30 degrees in any direction&lt;br /&gt;
* Radio panel control and selection&lt;br /&gt;
* Basic autopilot control&lt;br /&gt;
* Light management&lt;br /&gt;
* Time management&lt;br /&gt;
* Opening the Phi map in the browser&lt;br /&gt;
&lt;br /&gt;
We will continue expanding the MCP definitions and are currently working on generating a compatibility report, since not all elements are accessible through every method. For example, when using the FlightGear menu, a lack of compatibility becomes evident in certain aspects.&lt;br /&gt;
&lt;br /&gt;
We will keep you updated on the [[FG-MCP_Server]] progress.&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
===Updated aircraft===&lt;br /&gt;
&lt;br /&gt;
==== Boeing 777 ====&lt;br /&gt;
The changes that were announced in the [[FlightGear Newsletter December 2025|previous newsletter]] have been committed to FGAddon (trunk and stable 2024.1) as of February 4th 2026. Enjoy the improved CDU (by Liang Sidi), VNAV handling (by Jean-Yves Lebleu) and Hydraulics systems (by Isaak Dieleman)! More updates will probably arrive in the near future. Development takes place in [https://gitlab.com/sidi762/flightgear-777 this Gitlab repository]. Please report any issues via [https://gitlab.com/sidi762/flightgear-777/-/issues the issue tracker].&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143632</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143632"/>
		<updated>2026-02-22T18:45:46Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* FG MCP Server */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
=== FG MCP Server ===&lt;br /&gt;
[[File:FG-MCP.png|thumb|FG MCP server Logo]]&lt;br /&gt;
&lt;br /&gt;
With the help of the OpenCode IDE, using the free model integrated into this editor —named Big Pickle— and under the strict control of the loop through the Ralf Wiggum utility, Michat has developed an MCP server for FlightGear.&lt;br /&gt;
&lt;br /&gt;
The server requires python = &amp;quot;&amp;gt;=3.10&amp;quot; and fastmcp&amp;gt;=2.0.0. Initially, we faced issues with the Telnet connection, so we chose to modify the specifications to use HTTP instead.&lt;br /&gt;
&lt;br /&gt;
Through its functionalities, this MCP server allows controlling various FlightGear features via text prompts. The main ones include:&lt;br /&gt;
* Engine startup&lt;br /&gt;
* View switching&lt;br /&gt;
* Cockpit view rotation up to 30 degrees in any direction&lt;br /&gt;
* Radio panel control and selection&lt;br /&gt;
* Basic autopilot control&lt;br /&gt;
* Light management&lt;br /&gt;
* Time management&lt;br /&gt;
* Opening the Phi map in the browser&lt;br /&gt;
&lt;br /&gt;
We will continue expanding the MCP definitions and are currently working on generating a compatibility report, since not all elements are accessible through every method. For example, when using the FlightGear menu, a lack of compatibility becomes evident in certain aspects.&lt;br /&gt;
&lt;br /&gt;
We will keep you updated on progress [https://wiki.flightgear.org/FG-MCP_Server].&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
===Updated aircraft===&lt;br /&gt;
&lt;br /&gt;
==== Boeing 777 ====&lt;br /&gt;
The changes that were announced in the [[FlightGear Newsletter December 2025|previous newsletter]] have been committed to FGAddon (trunk and stable 2024.1) as of February 4th 2026. Enjoy the improved CDU (by Liang Sidi), VNAV handling (by Jean-Yves Lebleu) and Hydraulics systems (by Isaak Dieleman)! More updates will probably arrive in the near future. Development takes place in [https://gitlab.com/sidi762/flightgear-777 this Gitlab repository]. Please report any issues via [https://gitlab.com/sidi762/flightgear-777/-/issues the issue tracker].&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143631</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143631"/>
		<updated>2026-02-22T18:43:02Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Related Software tools and projects */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
=== FG MCP Server ===&lt;br /&gt;
[[File:FG-MCP.png|thumb|FG MCP server Logo]]&lt;br /&gt;
&lt;br /&gt;
With the help of the OpenCode IDE, using the free model integrated into this editor —named Big Pickle— and under the strict control of the loop through the Ralf Wiggum utility, Michat has developed an MCP server for FlightGear.&lt;br /&gt;
&lt;br /&gt;
The server requires python = &amp;quot;&amp;gt;=3.10&amp;quot; and fastmcp&amp;gt;=2.0.0. Initially, we faced issues with the Telnet connection, so we chose to modify the specifications to use HTTP instead.&lt;br /&gt;
&lt;br /&gt;
Through its functionalities, this MCP server allows controlling various FlightGear features via text prompts. The main ones include:&lt;br /&gt;
* Engine startup&lt;br /&gt;
* View switching&lt;br /&gt;
* Cockpit view rotation up to 30 degrees in any direction&lt;br /&gt;
* Radio panel control and selection&lt;br /&gt;
* Basic autopilot control&lt;br /&gt;
* Light management&lt;br /&gt;
* Time management&lt;br /&gt;
* Opening the Phi map in the browser&lt;br /&gt;
&lt;br /&gt;
We will continue expanding the MCP definitions and are currently working on generating a compatibility report, since not all elements are accessible through every method. For example, when using the FlightGear menu, a lack of compatibility becomes evident in certain aspects.&lt;br /&gt;
&lt;br /&gt;
We will keep you updated on [[https://wiki.flightgear.org/FG-MCP_Server|progress]].&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
===Updated aircraft===&lt;br /&gt;
&lt;br /&gt;
==== Boeing 777 ====&lt;br /&gt;
The changes that were announced in the [[FlightGear Newsletter December 2025|previous newsletter]] have been committed to FGAddon (trunk and stable 2024.1) as of February 4th 2026. Enjoy the improved CDU (by Liang Sidi), VNAV handling (by Jean-Yves Lebleu) and Hydraulics systems (by Isaak Dieleman)! More updates will probably arrive in the near future. Development takes place in [https://gitlab.com/sidi762/flightgear-777 this Gitlab repository]. Please report any issues via [https://gitlab.com/sidi762/flightgear-777/-/issues the issue tracker].&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143630</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143630"/>
		<updated>2026-02-22T18:37:21Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* GENERAL DESCRIPTION */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GENERAL DESCRIPTION ==&lt;br /&gt;
The '''FlightGear MCP Server''' is an MCP (Model Context Protocol) server that &lt;br /&gt;
provides remote control capabilities for the FlightGear flight simulator &lt;br /&gt;
through a standardized interface.&lt;br /&gt;
&lt;br /&gt;
It allows external applications (such as Claude Desktop, opencode, or any &lt;br /&gt;
MCP-compatible client) to interact with '''FlightGear''' via HTTP properties.&lt;br /&gt;
&lt;br /&gt;
== MAIN FEATURES ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Claude Desktop, etc.) &lt;br /&gt;
&lt;br /&gt;
== INSTALLATION ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143629</id>
		<title>FG-MCP Server</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FG-MCP_Server&amp;diff=143629"/>
		<updated>2026-02-22T18:35:21Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Created page with &amp;quot;{{WIP}}  {{Infobox Software |title               = FG-MCP Server |logo                = FG-MCP.png|128px |developedby         = Michat |developmentstatus   = Active |type                = MCP Server |latestrelease       = (rolling releases) |initialrelease      = 22.02.2026 |writtenin           = MD to Python 3.10+ |os                  = Windows, GNU/Linux, MacOS |license             = GNU General Public License v2 |devel-repo          = wip }}   == GENERAL DESCRIPTI...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = FG-MCP Server&lt;br /&gt;
|logo                = FG-MCP.png|128px&lt;br /&gt;
|developedby         = Michat&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = MCP Server&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 22.02.2026&lt;br /&gt;
|writtenin           = MD to Python 3.10+&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = wip&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== GENERAL DESCRIPTION ==&lt;br /&gt;
'''FlightGear MCP Server''' es un servidor MCP (Model Context Protocol) que &lt;br /&gt;
proporciona capacidades de control remoto para el simulador de vuelo &lt;br /&gt;
FlightGear a traves de una interfaz estandarizada.&lt;br /&gt;
&lt;br /&gt;
Permite que aplicaciones externas (como opencode, windsurf, Claude Desktop o &lt;br /&gt;
cualquier cliente compatible con MCP) interactuen con '''FlightGear''' via &lt;br /&gt;
propiedades HTTP.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== MAIN FEATURES ==&lt;br /&gt;
&lt;br /&gt;
- Reading flight data (position, velocity, attitude)&lt;br /&gt;
- Aircraft surface controls (throttle, ailerons, elevator, rudder)&lt;br /&gt;
- Autopilot management&lt;br /&gt;
- Radio and navigation equipment control&lt;br /&gt;
- Lighting system management&lt;br /&gt;
- Camera and view controls&lt;br /&gt;
- Helicopter-specific controls (MI-6PS)&lt;br /&gt;
- Multiplayer chat&lt;br /&gt;
- Environment/time controls&lt;br /&gt;
&lt;br /&gt;
=== REQUIREMENTS ===&lt;br /&gt;
- Python 3.10+&lt;br /&gt;
- FlightGear with HTTP server enabled&lt;br /&gt;
- An MCP-compatible client (opencode, Claude Desktop, etc.) &lt;br /&gt;
&lt;br /&gt;
== INSTALLATION ==&lt;br /&gt;
1. Clone or download the repository&lt;br /&gt;
2. Create virtual environment:&lt;br /&gt;
   python -m venv venv&lt;br /&gt;
   source venv/bin/activate&lt;br /&gt;
&lt;br /&gt;
3. Install dependencies:&lt;br /&gt;
   pip install -e .&lt;br /&gt;
&lt;br /&gt;
==== FLIGHTGEAR CONFIGURATION ====&lt;br /&gt;
&lt;br /&gt;
Start FlightGear with HTTP server enabled:&lt;br /&gt;
&lt;br /&gt;
   fgfs --http=8080&lt;br /&gt;
&lt;br /&gt;
Or add to launcher settings:&lt;br /&gt;
   --http=8080&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== AVAILABLE TOOLS ==&lt;br /&gt;
&lt;br /&gt;
--- Reading Flight Data ---&lt;br /&gt;
&lt;br /&gt;
get_position()           - Latitude, longitude, altitude&lt;br /&gt;
get_velocity()           - Ground speed, airspeed, vertical speed&lt;br /&gt;
get_attitude()           - Pitch, roll, heading&lt;br /&gt;
get_engine()             - Throttle, thrust&lt;br /&gt;
get_rotor()              - Helicopter rotor status&lt;br /&gt;
get_flight_data()        - All combined data&lt;br /&gt;
&lt;br /&gt;
--- Surface Controls ---&lt;br /&gt;
&lt;br /&gt;
set_throttle(value)      - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_aileron(value)       - Ailerons (-1.0 - 1.0)&lt;br /&gt;
set_elevator(value)      - Elevator (-1.0 - 1.0)&lt;br /&gt;
set_rudder(value)        - Rudder (-1.0 - 1.0)&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
&lt;br /&gt;
get_autopilot()          - Autopilot status&lt;br /&gt;
set_autopilot(engage)   - Engage/disengage autopilot&lt;br /&gt;
set_heading_bug(value)  - Heading (0-360 degrees)&lt;br /&gt;
set_altitude_target(value) - Target altitude (feet)&lt;br /&gt;
set_autopilot_altitude(mode) - Altitude mode (e.g., &amp;quot;altitude-hold&amp;quot;)&lt;br /&gt;
set_target_altitude(value) - Alternative target altitude&lt;br /&gt;
&lt;br /&gt;
--- Radio and Navigation ---&lt;br /&gt;
&lt;br /&gt;
get_radios()             - All frequencies&lt;br /&gt;
set_com1(freq)          - COM1 frequency (MHz)&lt;br /&gt;
set_com2(freq)          - COM2 frequency (MHz)&lt;br /&gt;
set_nav1(freq)          - NAV1 frequency (MHz)&lt;br /&gt;
set_transponder(code)    - Transponder code (4 digits)&lt;br /&gt;
&lt;br /&gt;
--- Lighting ---&lt;br /&gt;
&lt;br /&gt;
get_lights()             - Light system status&lt;br /&gt;
set_landing_light(on)   - Landing light on/off&lt;br /&gt;
&lt;br /&gt;
--- Camera and Views ---&lt;br /&gt;
&lt;br /&gt;
get_views()              - Current view information&lt;br /&gt;
set_view(view)           - Change camera view&lt;br /&gt;
get_zoom()              - Current field of view&lt;br /&gt;
set_zoom(value)         - Set field of view (20-120)&lt;br /&gt;
view_reset()            - Reset view to center&lt;br /&gt;
view_look(direction, degrees) - Look around&lt;br /&gt;
view_overhead()         - Look at overhead panel&lt;br /&gt;
view_console()          - Look at console&lt;br /&gt;
view_left_window()      - Look at left window&lt;br /&gt;
view_right_window()     - Look at right window&lt;br /&gt;
view_behind()           - Look behind&lt;br /&gt;
&lt;br /&gt;
Available views: pilot, copilot, engineer, navigator, left, right, &lt;br /&gt;
                  tower, chase, flyby&lt;br /&gt;
&lt;br /&gt;
--- MI-6PS Helicopter ---&lt;br /&gt;
&lt;br /&gt;
start_engine()           - Start engines&lt;br /&gt;
stop_engine()            - Stop engines&lt;br /&gt;
set_throttle_mi6(value) - Engine throttle (0.0 - 1.0)&lt;br /&gt;
set_collective(value)    - Collective pitch (-1.0 to 1.0)&lt;br /&gt;
toggle_rotor_brake(on)  - Rotor brake on/off&lt;br /&gt;
toggle_cargo_door()     - Toggle cargo door&lt;br /&gt;
&lt;br /&gt;
--- Brakes ---&lt;br /&gt;
&lt;br /&gt;
release_parking_brake()  - Release parking brake&lt;br /&gt;
set_parking_brake(value)- Set brake (0=released, 1=applied)&lt;br /&gt;
&lt;br /&gt;
--- Multiplayer ---&lt;br /&gt;
&lt;br /&gt;
set_chat(message)        - Send chat message&lt;br /&gt;
&lt;br /&gt;
--- Utilities ---&lt;br /&gt;
&lt;br /&gt;
send_key(key)           - Send key to FlightGear&lt;br /&gt;
&lt;br /&gt;
Tested keys: v, x, X, s, S, r, R, l, L, f, F, e, E, d, D, a, w,&lt;br /&gt;
               F1, F10, Escape&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== PROPERTIES USED ==&lt;br /&gt;
The server interacts with FlightGear's property tree via HTTP.&lt;br /&gt;
&lt;br /&gt;
--- Views ---&lt;br /&gt;
/sim/current-view/view-number&lt;br /&gt;
/sim/current-view/field-of-view&lt;br /&gt;
/sim/current-view/pitch-offset-deg&lt;br /&gt;
/sim/current-view/heading-offset-deg&lt;br /&gt;
&lt;br /&gt;
--- Controls ---&lt;br /&gt;
/controls/engine/throttle&lt;br /&gt;
/controls/flight/aileron&lt;br /&gt;
/controls/flight/elevator&lt;br /&gt;
/controls/flight/rudder&lt;br /&gt;
/controls/gear/brake-parking&lt;br /&gt;
&lt;br /&gt;
--- Position ---&lt;br /&gt;
/position/latitude-deg&lt;br /&gt;
/position/longitude-deg&lt;br /&gt;
/position/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Autopilot ---&lt;br /&gt;
/autopilot/locks/heading&lt;br /&gt;
/autopilot/locks/altitude&lt;br /&gt;
/autopilot/settings/heading-bug-deg&lt;br /&gt;
/autopilot/settings/altitude-ft&lt;br /&gt;
&lt;br /&gt;
--- Radio ---&lt;br /&gt;
/instrumentation/comm[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/nav[0]/frequencies/selected-mhz&lt;br /&gt;
/instrumentation/transponder/id-code&lt;br /&gt;
&lt;br /&gt;
--- Helicopter ---&lt;br /&gt;
/controls/engines/engine/cutoff&lt;br /&gt;
/controls/engines/engine/magnetos&lt;br /&gt;
/controls/engines/engine/starter&lt;br /&gt;
/rotors/main/rpm&lt;br /&gt;
/rotors/main/blade-pitch-deg&lt;br /&gt;
&lt;br /&gt;
== ARCHITECTURE ==&lt;br /&gt;
The server consists of two main files:&lt;br /&gt;
&lt;br /&gt;
- flightgear.py: Contains the FlightGearClient class that handles HTTP&lt;br /&gt;
                 communication with FlightGear&lt;br /&gt;
&lt;br /&gt;
- server.py:      Defines MCP tools using the FastMCP framework&lt;br /&gt;
&lt;br /&gt;
Communication is via stdio with the MCP client, while FlightGear &lt;br /&gt;
communication uses the HTTP JSON API.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== KNOWN LIMITATIONS ==&lt;br /&gt;
 send_key() requires the FlightGear window to be focused&lt;br /&gt;
- Nasal execution via telnet requires proper configuration&lt;br /&gt;
- Some properties may vary between aircraft&lt;br /&gt;
&lt;br /&gt;
== USAGE EXAMPLES ==&lt;br /&gt;
&lt;br /&gt;
# Get all flight data&lt;br /&gt;
get_flight_data()&lt;br /&gt;
&lt;br /&gt;
# Set up approach&lt;br /&gt;
set_com1(118.7)&lt;br /&gt;
set_nav1(109.5)&lt;br /&gt;
set_transponder(&amp;quot;4500&amp;quot;)&lt;br /&gt;
set_altitude_target(3000)&lt;br /&gt;
&lt;br /&gt;
# Helicopter control&lt;br /&gt;
start_engine()&lt;br /&gt;
set_throttle_mi6(0.5)&lt;br /&gt;
set_collective(0.3)&lt;br /&gt;
&lt;br /&gt;
# Camera control&lt;br /&gt;
set_view(&amp;quot;tower&amp;quot;)&lt;br /&gt;
set_zoom(40)&lt;br /&gt;
&lt;br /&gt;
== VERSION ==&lt;br /&gt;
v0.1.0 - Initial version with basic functions&lt;br /&gt;
v0.1.1 - Parking brake control, multiplayer chat, day/night environment&lt;br /&gt;
         control, extended autopilot properties&lt;br /&gt;
&lt;br /&gt;
== LICENSE ==&lt;br /&gt;
This project is licensed under the GNU General Public License v2.&lt;br /&gt;
See the LICENSE file for details..&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143615</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143615"/>
		<updated>2026-02-22T01:53:41Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
=== FG MCP Server ===&lt;br /&gt;
[[File:FG-MCP.png|thumb|FG MCP server Logo]]&lt;br /&gt;
&lt;br /&gt;
With the help of the OpenCode IDE, using the free model integrated into this editor —named Big Pickle— and under the strict control of the loop through the Ralf Wiggum utility, Michat has developed an MCP server for FlightGear.&lt;br /&gt;
&lt;br /&gt;
The server requires python = &amp;quot;&amp;gt;=3.10&amp;quot; and fastmcp&amp;gt;=2.0.0. Initially, we faced issues with the Telnet connection, so we chose to modify the specifications to use HTTP instead.&lt;br /&gt;
&lt;br /&gt;
Through its functionalities, this MCP server allows controlling various FlightGear features via text prompts. The main ones include:&lt;br /&gt;
* Engine startup&lt;br /&gt;
* View switching&lt;br /&gt;
* Cockpit view rotation up to 30 degrees in any direction&lt;br /&gt;
* Radio panel control and selection&lt;br /&gt;
* Basic autopilot control&lt;br /&gt;
* Light management&lt;br /&gt;
* Time management&lt;br /&gt;
* Opening the Phi map in the browser&lt;br /&gt;
&lt;br /&gt;
We will continue expanding the MCP definitions and are currently working on generating a compatibility report, since not all elements are accessible through every method. For example, when using the FlightGear menu, a lack of compatibility becomes evident in certain aspects.&lt;br /&gt;
&lt;br /&gt;
We will keep you updated on progress.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
===Updated aircraft===&lt;br /&gt;
&lt;br /&gt;
==== Boeing 777 ====&lt;br /&gt;
The changes that were announced in the [[FlightGear Newsletter December 2025|previous newsletter]] have been committed to FGAddon (trunk and stable 2024.1) as of February 4th 2026. Enjoy the improved CDU (by Liang Sidi), VNAV handling (by Jean-Yves Lebleu) and Hydraulics systems (by Isaak Dieleman)! More updates will probably arrive in the near future. Development takes place in [https://gitlab.com/sidi762/flightgear-777 this Gitlab repository]. Please report any issues via [https://gitlab.com/sidi762/flightgear-777/-/issues the issue tracker].&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:FG-MCP.png&amp;diff=143614</id>
		<title>File:FG-MCP.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:FG-MCP.png&amp;diff=143614"/>
		<updated>2026-02-22T01:09:50Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Uploaded own work with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=FG MCP server Logo}}&lt;br /&gt;
|date=2026-02-22&lt;br /&gt;
|source={{own}}&lt;br /&gt;
|author=[[User:Aepcam|Aepcam]]&lt;br /&gt;
|permission=&lt;br /&gt;
|other versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{self|cc-by-sa-4.0}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Logotypes]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2026&amp;diff=143611</id>
		<title>FlightGear Newsletter February 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_February_2026&amp;diff=143611"/>
		<updated>2026-02-17T19:36:20Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Newsletter creation, automatic preload from here&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-02}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-02}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-02}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-02 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-02 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 02]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-02 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143571</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143571"/>
		<updated>2026-01-22T18:18:13Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_December_2025&amp;diff=143570</id>
		<title>FlightGear Newsletter December 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_December_2025&amp;diff=143570"/>
		<updated>2026-01-22T18:16:18Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-12}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-12}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal &amp;quot;LIBERA ET TESSELA&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
A major update has been released for the Photoscenery GUI, introducing significant accessibility enhancements.&lt;br /&gt;
&lt;br /&gt;
The key addition is full Internationalization (i18n) support, which makes the tool more accessible to a global audience. Users can now switch between languages instantly using new flag icons located in the control panel.&lt;br /&gt;
&lt;br /&gt;
What’s New:&lt;br /&gt;
&lt;br /&gt;
Multi-language Support:&lt;br /&gt;
The interface now supports multiple languages, including: English, Italian, French, German, Spanish, Portuguese, Chinese (Simplified), Japanese, Korean, Arabic (with full Right-to-Left layout support), and Russian.&lt;br /&gt;
&lt;br /&gt;
UI Improvements:&lt;br /&gt;
A new language switcher with flag icons has been implemented. Layout and font sizes have been optimized for better readability across different languages. Spacing in the control panel has been improved for a cleaner interface.&lt;br /&gt;
&lt;br /&gt;
This update is now available in the main branch on GitHub https://github.com/abassign/Photoscenery-GUI.git. Users are encouraged to test the new features and provide feedback regarding any translation errors or suggestions for additional language support.&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=420&lt;br /&gt;
&lt;br /&gt;
=== Re-Introducing the Rain Vector Editor Addon ===&lt;br /&gt;
This tool has been around for a while, to reintroduce it there is a short video in the forum link below demonstrating its simple use. Use it to get the exact splash-x, y and z vectors that best look like rain on any specific window. Use that data to code dynamic control over the look of rain on windows and windscreens when introducing wind, prop blast and aircraft velocity through the air.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|EyRiW5aZeX0|480px||FG Rain Vector Editor Add-on}}&lt;br /&gt;
&lt;br /&gt;
To explore the Rain Vector Editor project and its assets, you can directly access its repository here:&lt;br /&gt;
&lt;br /&gt;
https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/RainVectorEditor/&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to check it out and contribute feedback!&lt;br /&gt;
&lt;br /&gt;
https://forum.flightgear.org/viewtopic.php?f=14&amp;amp;t=43932&amp;amp;sid=20078e01f815391532dbded0a512a825&amp;amp;start=45#p436889&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
=== FGUK ===&lt;br /&gt;
==== Augusta Westland AW109 &amp;quot;Grand New&amp;quot; ====&lt;br /&gt;
[[File:aw109ext2.png|400px|thumb|AW109 External shot 1]]Version 1.0 of the AW109 has been released by the team at FGUK. &lt;br /&gt;
[[File:109int3.png|thumb|400x400px|AW109 Internal shot]]&lt;br /&gt;
[[File:aw109ext1.png|400px|thumb|right|AW109 External View - HEMS configuration]]This initial release includes a new model with latest fuselage and shader effects, a functional cockpit and basic HDR compatibility. &lt;br /&gt;
&lt;br /&gt;
The FDM, in YASim, is entirely bespoke and tuned to give realistic performance across the flight envelope. V3 of the FGUK heli-autopilot is also included (help available via the in sim documentation) &lt;br /&gt;
&lt;br /&gt;
There are various configuration options selectable either manually or via the liveries (15+ included) to cover HEMS, SAR, Law Enforcement, Passenger and Military equipment levels and loadouts, with a functioning winch operator available in configurations with an appropriate winch.&lt;br /&gt;
&lt;br /&gt;
Details, downloads and discussion/updates are available directly [https://forum.fguk.me/discussion/987/augusta-westland-aw109-grand-new-now-available#latest here at the FGUK forum]&lt;br /&gt;
&lt;br /&gt;
[[File:aw109ext4.png|400x400px|thumb|AW109 &amp;quot;Grand New&amp;quot; external shot - Sunset ]]&lt;br /&gt;
&lt;br /&gt;
=== Boeing 777 ===&lt;br /&gt;
A few people have gathered to collaborate on the Boeing 777. They have taken development to a new [https://gitlab.com/sidi762/flightgear-777 gitlab repository], and will backport stable releases to FGaddon. Currently Jean-Yves Lebleu is improving the LNAV/VNAV implementation on the 777. Naviat is working on a new 3D model that will eventually replace the current 3D model, and Octal450 will be creating a [[JSBSim]] FDE to replace the old YASim.&lt;br /&gt;
&lt;br /&gt;
Isaak has made quite some progress on the hydraulics system that will soon be merged into the stable release. As this is close to finished, below are some pointers of what is possible. Checklists are currently in the working. The hydraulics system operates as close as currently possible to the Boeing 777 FCOM. A few items are still missing because they require a better electric and air system or a fault simulation. They are on a longer term to-do list for when these systems are improved.&lt;br /&gt;
&lt;br /&gt;
These features are implemented:&lt;br /&gt;
&lt;br /&gt;
* There is a new item in the &amp;quot;Aircraft settings&amp;quot; dialog: you can enable realistic hydraulic fluid depletion (due to leaks and wear). This requires the &amp;quot;Store fuel and hydraulic fluid level between sessions&amp;quot; option to be enabled as well. Hydraulic fluid will deplete at a very slow rate, based on which systems and pumps are operating. Isaak will finetune the consumption rate a bit further. The goal is to require a refill of (some) hydraulic fluid every 2 weeks of operation, to add some extra workload to the preflight checks. If a fluid reservoir runs below standpipe level or completely empty, the corresponding pumps will fail and possibly overheat if running without fluid. The hydraulic fluid levels can be checked and refilled via the ground services dialog.&lt;br /&gt;
* Hydraulics synoptics screen on the MFD (lower EICAS) is fully functional. It is selectable with the &amp;quot;Hyd&amp;quot; button on the EFIS control panel.&lt;br /&gt;
* Hydraulic pumps and valves operate as per FCOM: they require hydraulic fluid in the correct reservoir (at or below standpipe level, depending on the pump), a correct power source...&lt;br /&gt;
* If a hydraulic pump or system fails, the corresponding system will fail too: flaps will not extend, brakes might fail if the brake accumulator runs empty as well...&lt;br /&gt;
* It has become extremely important to turn on and off the hydraulic pumps in the right order: fluid transfer between the center and right system is implemented (via the brake system) so you can overfill or deplete one of the systems when you enable/disable the right hydraulic pumps at the wrong time. Follow the checklists to prevent this: always turn on the right hydraulic system before powering the others, and only switch it off after the center pumps have been switched off.&lt;br /&gt;
* Both the normal and alternate/reserve brake systems are implemented. The brake accumulator can power the brakes if it is pressurized enough. If it pressurizes the parking brake, it will slowly lose pressure over time. After about 10 hours, the parking brake will release (even though the &amp;quot;Parking Brake Set&amp;quot; will remain active on the EICAS display), so for longer times of unpowered parking: use wheel chocks to prevent an unwanted trip with the aircraft. The brake accumulator is powerful enough to bring the aircraft to a complete stop when landing without hydraulic systems.&lt;br /&gt;
* The EICAS will throw errors when pumps and/or systems are depressurized&lt;br /&gt;
&lt;br /&gt;
There are some good YouTube videos that can help you understand the Boeing 777 hydraulics systems. Almost all of this is implemented.&lt;br /&gt;
&lt;br /&gt;
* [https://www.youtube.com/watch?v=DEoniYv6GOI This series] provides a good basic understanding of normal and non-normal hydraulic systems and procedures.&lt;br /&gt;
* [https://www.youtube.com/watch?v=P_izKDUc-GY This series] provides a deeper insight in the Boeing 777 brake system.&lt;br /&gt;
&lt;br /&gt;
The hydraulics system is currently still in a separate branch, but will be merged into &amp;quot;master&amp;quot; soon.&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Octal450 Hangar ===&lt;br /&gt;
==== Boeing 727 ====&lt;br /&gt;
Progress on the new [[Boeing 727]] is continuing, with the virtual cockpit being further 3D modelled and the SP-150 autopilot being developed.&lt;br /&gt;
&lt;br /&gt;
==== McDonnell Douglas MD-11 ====&lt;br /&gt;
The [[McDonnell Douglas MD-11]] has gained the tail fuel CG management feature, an overhauled Auto Thrust System, and improved FADEC logic.&lt;br /&gt;
&lt;br /&gt;
There are a bunch of conditions required for tail fuel CG management to activate and a bunch of complex logic that decides exactly what/how it does this, but in summary, it's automatic and doesn't need babysitting. It will transfer the fuel forward when needed or when descending through ~26750 feet.&lt;br /&gt;
&lt;br /&gt;
[[File:MD-11-TFM-Demo.png]]&lt;br /&gt;
&lt;br /&gt;
==== McDonnell Douglas MD-80 ====&lt;br /&gt;
The [[McDonnell Douglas MD-80]] now has a new pedestal with all the missing controls modelled. Most of them are already hooked up to the aircraft systems, with exceptions to pressurization control. It also now has wingflex.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|IKOa8NUofw8}}&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
=== FlightGear on Facebook ===&lt;br /&gt;
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page].  If you have a Facebook account please feel free to join the page.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on Instagram ===&lt;br /&gt;
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.&lt;br /&gt;
&lt;br /&gt;
=== FlightGear on FlightSim.com ===&lt;br /&gt;
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Contributing ==&lt;br /&gt;
=== Translators needed ===&lt;br /&gt;
{|&lt;br /&gt;
| [[File:en.gif]]&lt;br /&gt;
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:fr.gif]]&lt;br /&gt;
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:de.gif]]&lt;br /&gt;
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.&lt;br /&gt;
|-&lt;br /&gt;
| [[File:nl.gif]]&lt;br /&gt;
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:es.gif]]&lt;br /&gt;
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:cat.gif]]&lt;br /&gt;
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:pt.gif]]&lt;br /&gt;
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].&lt;br /&gt;
|-&lt;br /&gt;
| [[File:zh.gif]]&lt;br /&gt;
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== FlightGear logos ===&lt;br /&gt;
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.&lt;br /&gt;
&lt;br /&gt;
=== Screenshots ===&lt;br /&gt;
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
FlightGear's Screenshot of the Month December 2025 is Orbiting at sunrise by OrbitalMartian.&lt;br /&gt;
[[File:SOTM 2025-12 Orbiting at sunrise by @OrbitalMartian.jpg|thumb|Orbiting at sunrise by OrbitalMartian]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 12]]&lt;br /&gt;
&lt;br /&gt;
[[fr:FlightGear_Newsletter_December_2025]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_December_2025&amp;diff=143557</id>
		<title>FlightGear Newsletter December 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_December_2025&amp;diff=143557"/>
		<updated>2026-01-20T05:58:28Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-12}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-12}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal &amp;quot;LIBERA ET TESSELA&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
A major update has been released for the Photoscenery GUI, introducing significant accessibility enhancements.&lt;br /&gt;
&lt;br /&gt;
The key addition is full Internationalization (i18n) support, which makes the tool more accessible to a global audience. Users can now switch between languages instantly using new flag icons located in the control panel.&lt;br /&gt;
&lt;br /&gt;
What’s New:&lt;br /&gt;
&lt;br /&gt;
Multi-language Support:&lt;br /&gt;
The interface now supports multiple languages, including: English, Italian, French, German, Spanish, Portuguese, Chinese (Simplified), Japanese, Korean, Arabic (with full Right-to-Left layout support), and Russian.&lt;br /&gt;
&lt;br /&gt;
UI Improvements:&lt;br /&gt;
A new language switcher with flag icons has been implemented. Layout and font sizes have been optimized for better readability across different languages. Spacing in the control panel has been improved for a cleaner interface.&lt;br /&gt;
&lt;br /&gt;
This update is now available in the main branch on GitHub https://github.com/abassign/Photoscenery-GUI.git. Users are encouraged to test the new features and provide feedback regarding any translation errors or suggestions for additional language support.&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=420&lt;br /&gt;
&lt;br /&gt;
=== Re-Introducing the Rain Vector Editor Addon ===&lt;br /&gt;
This tool has been around for a while, to reintroduce it there is a short video in the forum link below demonstrating its simple use. Use it to get the exact splash-x, y and z vectors that best look like rain on any specific window. Use that data to code dynamic control over the look of rain on windows and windscreens when introducing wind, prop blast and aircraft velocity through the air.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|EyRiW5aZeX0|480px||FG Rain Vector Editor Add-on}}&lt;br /&gt;
&lt;br /&gt;
To explore the Rain Vector Editor project and its assets, you can directly access its repository here:&lt;br /&gt;
&lt;br /&gt;
https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/RainVectorEditor/&lt;br /&gt;
&lt;br /&gt;
We encourage everyone to check it out and contribute feedback!&lt;br /&gt;
&lt;br /&gt;
https://forum.flightgear.org/viewtopic.php?f=14&amp;amp;t=43932&amp;amp;sid=20078e01f815391532dbded0a512a825&amp;amp;start=45#p436889&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
=== FGUK ===&lt;br /&gt;
==== Augusta Westland AW109 &amp;quot;Grand New&amp;quot; ====&lt;br /&gt;
[[File:aw109ext2.png|400px|thumb|AW109 External shot 1]]Version 1.0 of the AW109 has been released by the team at FGUK. &lt;br /&gt;
[[File:109int3.png|thumb|400x400px|AW109 Internal shot]]&lt;br /&gt;
[[File:aw109ext1.png|400px|thumb|right|AW109 External View - HEMS configuration]]This initial release includes a new model with latest fuselage and shader effects, a functional cockpit and basic HDR compatibility. &lt;br /&gt;
&lt;br /&gt;
The FDM, in YASim, is entirely bespoke and tuned to give realistic performance across the flight envelope. V3 of the FGUK heli-autopilot is also included (help available via the in sim documentation) &lt;br /&gt;
&lt;br /&gt;
There are various configuration options selectable either manually or via the liveries (15+ included) to cover HEMS, SAR, Law Enforcement, Passenger and Military equipment levels and loadouts, with a functioning winch operator available in configurations with an appropriate winch.&lt;br /&gt;
&lt;br /&gt;
Details, downloads and discussion/updates are available directly [https://forum.fguk.me/discussion/987/augusta-westland-aw109-grand-new-now-available#latest here at the FGUK forum]&lt;br /&gt;
&lt;br /&gt;
[[File:aw109ext4.png|400x400px|thumb|AW109 &amp;quot;Grand New&amp;quot; external shot - Sunset ]]&lt;br /&gt;
&lt;br /&gt;
=== Boeing 777 ===&lt;br /&gt;
A few people have gathered to collaborate on the Boeing 777. They have taken development to a new [https://gitlab.com/sidi762/flightgear-777 gitlab repository], and will backport stable releases to FGaddon. Currently Jean-Yves Lebleu is improving the LNAV/VNAV implementation on the 777. Naviat is working on a new 3D model that will eventually replace the current 3D model, and Octal450 will be creating a [[JSBSim]] FDE to replace the old YASim.&lt;br /&gt;
&lt;br /&gt;
Isaak has made quite some progress on the hydraulics system that will soon be merged into the stable release. As this is close to finished, below are some pointers of what is possible. Checklists are currently in the working. The hydraulics system operates as close as currently possible to the Boeing 777 FCOM. A few items are still missing because they require a better electric and air system or a fault simulation. They are on a longer term to-do list for when these systems are improved.&lt;br /&gt;
&lt;br /&gt;
These features are implemented:&lt;br /&gt;
&lt;br /&gt;
* There is a new item in the &amp;quot;Aircraft settings&amp;quot; dialog: you can enable realistic hydraulic fluid depletion (due to leaks and wear). This requires the &amp;quot;Store fuel and hydraulic fluid level between sessions&amp;quot; option to be enabled as well. Hydraulic fluid will deplete at a very slow rate, based on which systems and pumps are operating. Isaak will finetune the consumption rate a bit further. The goal is to require a refill of (some) hydraulic fluid every 2 weeks of operation, to add some extra workload to the preflight checks. If a fluid reservoir runs below standpipe level or completely empty, the corresponding pumps will fail and possibly overheat if running without fluid. The hydraulic fluid levels can be checked and refilled via the ground services dialog.&lt;br /&gt;
* Hydraulics synoptics screen on the MFD (lower EICAS) is fully functional. It is selectable with the &amp;quot;Hyd&amp;quot; button on the EFIS control panel.&lt;br /&gt;
* Hydraulic pumps and valves operate as per FCOM: they require hydraulic fluid in the correct reservoir (at or below standpipe level, depending on the pump), a correct power source...&lt;br /&gt;
* If a hydraulic pump or system fails, the corresponding system will fail too: flaps will not extend, brakes might fail if the brake accumulator runs empty as well...&lt;br /&gt;
* It has become extremely important to turn on and off the hydraulic pumps in the right order: fluid transfer between the center and right system is implemented (via the brake system) so you can overfill or deplete one of the systems when you enable/disable the right hydraulic pumps at the wrong time. Follow the checklists to prevent this: always turn on the right hydraulic system before powering the others, and only switch it off after the center pumps have been switched off.&lt;br /&gt;
* Both the normal and alternate/reserve brake systems are implemented. The brake accumulator can power the brakes if it is pressurized enough. If it pressurizes the parking brake, it will slowly lose pressure over time. After about 10 hours, the parking brake will release (even though the &amp;quot;Parking Brake Set&amp;quot; will remain active on the EICAS display), so for longer times of unpowered parking: use wheel chocks to prevent an unwanted trip with the aircraft. The brake accumulator is powerful enough to bring the aircraft to a complete stop when landing without hydraulic systems.&lt;br /&gt;
* The EICAS will throw errors when pumps and/or systems are depressurized&lt;br /&gt;
&lt;br /&gt;
There are some good YouTube videos that can help you understand the Boeing 777 hydraulics systems. Almost all of this is implemented.&lt;br /&gt;
&lt;br /&gt;
* [https://www.youtube.com/watch?v=DEoniYv6GOI This series] provides a good basic understanding of normal and non-normal hydraulic systems and procedures.&lt;br /&gt;
* [https://www.youtube.com/watch?v=P_izKDUc-GY This series] provides a deeper insight in the Boeing 777 brake system.&lt;br /&gt;
&lt;br /&gt;
The hydraulics system is currently still in a separate branch, but will be merged into &amp;quot;master&amp;quot; soon.&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Octal450 Hangar ===&lt;br /&gt;
==== Boeing 727 ====&lt;br /&gt;
Progress on the new [[Boeing 727]] is continuing, with the virtual cockpit being further 3D modelled and the SP-150 autopilot being developed.&lt;br /&gt;
&lt;br /&gt;
==== McDonnell Douglas MD-11 ====&lt;br /&gt;
The [[McDonnell Douglas MD-11]] has gained the tail fuel CG management feature, an overhauled Auto Thrust System, and improved FADEC logic.&lt;br /&gt;
&lt;br /&gt;
There are a bunch of conditions required for tail fuel CG management to activate and a bunch of complex logic that decides exactly what/how it does this, but in summary, it's automatic and doesn't need babysitting. It will transfer the fuel forward when needed or when descending through ~26750 feet.&lt;br /&gt;
&lt;br /&gt;
[[File:MD-11-TFM-Demo.png]]&lt;br /&gt;
&lt;br /&gt;
==== McDonnell Douglas MD-80 ====&lt;br /&gt;
The [[McDonnell Douglas MD-80]] now has a new pedestal with all the missing controls modelled. Most of them are already hooked up to the aircraft systems, with exceptions to pressurization control. It also now has wingflex.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|IKOa8NUofw8}}&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
FlightGear's Screenshot of the Month December 2025 is Orbiting at sunrise by OrbitalMartian.&lt;br /&gt;
[[File:SOTM 2025-12 Orbiting at sunrise by @OrbitalMartian.jpg|thumb|Orbiting at sunrise by OrbitalMartian]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 12]]&lt;br /&gt;
&lt;br /&gt;
[[fr:FlightGear_Newsletter_December_2025]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143556</id>
		<title>FlightGear Newsletter January 2026</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_January_2026&amp;diff=143556"/>
		<updated>2026-01-20T05:47:40Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Newsletter creation, automatic preload from here&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2026-01}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2026-01}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2026-01}} 2026 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2026-01 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2026-01 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2026 01]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2026-01 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Julia_photoscenery_generator_GUI&amp;diff=143364</id>
		<title>Julia photoscenery generator GUI</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Julia_photoscenery_generator_GUI&amp;diff=143364"/>
		<updated>2025-12-26T19:19:27Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Executing Photoscenary-GUI (Method 1) Git as a module in Julia */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{WIP}} &lt;br /&gt;
{{Infobox Software&lt;br /&gt;
|title               = Photoscenery-GUI&lt;br /&gt;
|logo                = Photoscenery-GUI-20251113-202721.jpg|128px&lt;br /&gt;
|developedby         = Adriano Bassignana&lt;br /&gt;
|developmentstatus   = Active&lt;br /&gt;
|type                = Photoscenery generator&lt;br /&gt;
|latestrelease       = (rolling releases)&lt;br /&gt;
|initialrelease      = 27.10.2025&lt;br /&gt;
|writtenin           = julia&lt;br /&gt;
|os                  = Windows, GNU/Linux, MacOS&lt;br /&gt;
|license             = [[GNU General Public License]] v2&lt;br /&gt;
|devel-repo          = https://github.com/abassign/Photoscenery-GUI&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[File:FG-JPS.png|thumb|278px|FG Julia Photoscenery-GUI Design proposal &amp;quot;LIBERA ET TESSELA&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
== Introduction ==&lt;br /&gt;
'''Photoscenery-GUI''' is the modern graphical interface for the Photoscenery tools previously available only as a command-line application.  &lt;br /&gt;
It provides an interactive map-based workflow for generating photographic scenery for '''FlightGear'''.&lt;br /&gt;
&lt;br /&gt;
The GUI was created to make scenery generation:&lt;br /&gt;
* easier  &lt;br /&gt;
* faster  &lt;br /&gt;
* visually controlled  &lt;br /&gt;
* less error‑prone  &lt;br /&gt;
&lt;br /&gt;
This version integrates:&lt;br /&gt;
* a real-time Leaflet map  &lt;br /&gt;
* FGFS live aircraft tracking  &lt;br /&gt;
* preview of tiles  &lt;br /&gt;
* route-based batch downloading  &lt;br /&gt;
* job monitoring  &lt;br /&gt;
* automatic ICAO coordinate resolution  &lt;br /&gt;
&lt;br /&gt;
== Why a GUI Version? ==&lt;br /&gt;
The original CLI tool forced users to manually enter coordinates, radii, resolutions and overwrite rules.  &lt;br /&gt;
The GUI solves this with a fully visual workflow.&lt;br /&gt;
&lt;br /&gt;
=== Improvements over CLI ===&lt;br /&gt;
* Visual map control  &lt;br /&gt;
* Colour‑coded resolutions  &lt;br /&gt;
* Coverage and date filters  &lt;br /&gt;
* One‑click ICAO resolve  &lt;br /&gt;
* Live aircraft integration  &lt;br /&gt;
* Route-based automatic patch generation  &lt;br /&gt;
* Tile previews and metadata  &lt;br /&gt;
&lt;br /&gt;
== System Requirements ==&lt;br /&gt;
* Julia 1.10 or newer. Recommended using juliaup, which is the robust official manager and updater for Julia releases.&lt;br /&gt;
* Git or Git as Julia module, read the differences below&lt;br /&gt;
* Modern browser  &lt;br /&gt;
* FlightGear (optional, for live tracking)&lt;br /&gt;
&lt;br /&gt;
==== Method 1 Git as a module in Julia ====&lt;br /&gt;
You don't need to install git beforehand, since it's already included as a module in Julia. The advantage of this installation is that the package remains protected within the Julia binaries directory, and if you want to have an isolated installation for security reasons, you can easily put it in a docker.&lt;br /&gt;
&lt;br /&gt;
==== Method 2 Git yourself ====&lt;br /&gt;
Installation by downloading from git, which requires the prerequisite. In this case, the entire application is visible in any folder we create and allows us to modify the code if necessary, perhaps even using AI tools.&lt;br /&gt;
&lt;br /&gt;
== Installing ==&lt;br /&gt;
&lt;br /&gt;
=== Method 1 - Installing juliaup - Git as a module in Julia ===&lt;br /&gt;
&amp;lt;code&amp;gt;juliaup&amp;lt;/code&amp;gt; is the recommended way to install Julia. It automatically installs the latest stable &amp;lt;code&amp;gt;julia&amp;lt;/code&amp;gt; binary and helps keep it up to date. It also supports installing and using different versions of Julia simultaneously.&lt;br /&gt;
&lt;br /&gt;
https://github.com/JuliaLang/juliaup&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In order to see the Julia's version, open a terminal then run:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ julia --version&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
julia version 1.12.2&lt;br /&gt;
&lt;br /&gt;
==== Create a folder Photoscenary-GUI, running julia inside ====&lt;br /&gt;
The name is not important, but it is useful for you as it will contain the various editable files necessary for running the application, including (if necessary) the directories containing the tiles.&lt;br /&gt;
&lt;br /&gt;
Now run Julia inside Photoscenary-GUI folder&lt;br /&gt;
&amp;lt;pre&amp;gt;~/Photoscenery-GUI&lt;br /&gt;
$ julia&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
You get next screen&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
               _&lt;br /&gt;
   _       _ _(_)_     |  Documentation: https://docs.julialang.org&lt;br /&gt;
  (_)     | (_) (_)    |&lt;br /&gt;
   _ _   _| |_  __ _   |  Type &amp;quot;?&amp;quot; for help, &amp;quot;]?&amp;quot; for Pkg help.&lt;br /&gt;
  | | | | | | |/ _` |  |&lt;br /&gt;
  | | |_| | | | (_| |  |  Version 1.12.2 (2025-11-20)&lt;br /&gt;
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org release&lt;br /&gt;
|__/                   |&lt;br /&gt;
&lt;br /&gt;
julia&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
==== Enter Julia package mode ====&lt;br /&gt;
Type the closed square bracket {{Key press|]}}&lt;br /&gt;
&lt;br /&gt;
We are now in package mode, notice the prompt now is pkg&amp;gt;&lt;br /&gt;
&lt;br /&gt;
(@v1.12) pkg&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Adding repository ====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
pkg&amp;gt; add &amp;quot;https://github.com/abassign/Photoscenery-GUI&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
You will see that Julia starts downloading the entire application and the various modules it requires, then exit with ctrl-d.&lt;br /&gt;
&lt;br /&gt;
{{Key press|Control}} + {{Key press|D}} &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
pkg&amp;gt; ^D&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Summary: Method 1 - Git as a module in Julia ====&lt;br /&gt;
You have successfully installed the modern Julia Programming Language interpreter in your FGPC using Juliaup. You have created a folder to host Photoscenery-GUI, entered the Julia package mode, and added the GitHub repository for Photoscenery-GUI. With the last commands, Julia has magically instantiated and precompiled a version for your OS, Git has been managed as a Julia module, after which you exited with Control+D.&lt;br /&gt;
&lt;br /&gt;
The advantage of this installation is that the package remains protected within the Julia binaries directory, and if you want to have an isolated installation for security reasons, you can easily put it in a docker. &lt;br /&gt;
&lt;br /&gt;
Finally, let's see Photoscenery in action.&lt;br /&gt;
&lt;br /&gt;
==== Executing Photoscenary-GUI (Method 1) Git as a module in Julia ====&lt;br /&gt;
Run in terminal only for the frist start:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
julia -e &amp;quot;using Photoscenery; Photoscenery.GuiMode.run()&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
After the initial launch, the program loads the startup commands go.sh for macOS and Linux and go.bat for Windows locally. From that point on, you only need to run the go command corresponding to your operating system:&lt;br /&gt;
&lt;br /&gt;
Linux e MacOs: '''./go.sh'''&lt;br /&gt;
&lt;br /&gt;
Windows: '''go.bat'''&lt;br /&gt;
&lt;br /&gt;
==== Open in browser ====&lt;br /&gt;
Open GUI, open next address with your browser and wait for 3 seconds:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
http://localhost:8000/&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
You'll see Photoscenery-GUI in action, similar to the picture above, in the info box.&lt;br /&gt;
&lt;br /&gt;
=== Method 2 - Installing juliaup - Git your self ===&lt;br /&gt;
&amp;lt;code&amp;gt;juliaup&amp;lt;/code&amp;gt; is the recommended way to install Julia. It automatically installs the latest stable &amp;lt;code&amp;gt;julia&amp;lt;/code&amp;gt; binary and helps keep it up to date. It also supports installing and using different versions of Julia simultaneously.&lt;br /&gt;
&lt;br /&gt;
https://github.com/JuliaLang/juliaup&lt;br /&gt;
&lt;br /&gt;
==== Download the Photoscenery-GUI project ====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
==== Calling Julia package manager to instantiate the project ====&lt;br /&gt;
From the Photoscenery-GUI directory, run in terminal&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 julia --project=. -e 'using Pkg; Pkg.instantiate()'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Summary: Method 2 Git yourself ====&lt;br /&gt;
You have successfully installed the modern Julia Programming Language interpreter in your FGPC using Juliaup. You have downloaded Photoscenery-GUI from Git, you have opened a terminal inside that folder, ordering Julia package manager to instantiate the project.&lt;br /&gt;
&lt;br /&gt;
In this case, the entire application is visible in any folder we create and allows us to modify the code if necessary.&lt;br /&gt;
&lt;br /&gt;
Finally, let's see Photoscenery-GUI in action.&lt;br /&gt;
&lt;br /&gt;
==== Executing Photoscenary-GUI (Method 2) Git your self ====&lt;br /&gt;
Run in terminal &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
julia --project=. -e 'using Photoscenery; Photoscenery.GuiMode.run()'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Open in browser ====&lt;br /&gt;
Open GUI, open next address with your browser and wait for 3 seconds:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
http://localhost:8000/&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
You'll see Photoscenery-GUI in action, similar to the picture above, in the info box.&lt;br /&gt;
&lt;br /&gt;
=== Method 3 - installing from GitHub ===&lt;br /&gt;
If you want to use the full application in a directory of your system, you can directly download the entire application from GitHub:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
git clone https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
The git command must be available on your system, and Julia must already be installed as described in the first method.&lt;br /&gt;
In this case, the application will no longer run as a Julia module, so the startup procedure will be different.&lt;br /&gt;
&lt;br /&gt;
Enter the directory automatically created by Git, then run one of the three possible go.xxx commands found inside it. Before launching the program, the command will download everything required and will configure the essential tmp directory, which is used to store image files needed to build the tiles.&lt;br /&gt;
&lt;br /&gt;
Each time you start the application, the system will check for updates on GitHub and will periodically (about once a week) update the files airports.csv and naviaids.csv.&lt;br /&gt;
&lt;br /&gt;
== Updating Photoscenery-GUI ==&lt;br /&gt;
You can update to newer version&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Julia&lt;br /&gt;
using Pkg&lt;br /&gt;
Pkg.update()&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
After update press&lt;br /&gt;
&lt;br /&gt;
{{Key press|Control}} + {{Key press|D}}&lt;br /&gt;
to exit. &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
^D&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== WIP (Work in Progress) Auto-Update Mechanism ====&lt;br /&gt;
A new way to launch the application that automatically checks for updates.&lt;br /&gt;
&lt;br /&gt;
When you start the app using these scripts, it will check if a new version is available on GitHub and ask if you want to update. This ensures you're always running the latest version with the newest features and fixes.&lt;br /&gt;
&lt;br /&gt;
Linux/macOS: Run&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
./go.sh&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Windows: Double-click&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
go.bat&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Julia: Run&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
julia --project=. go.jl&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Follow: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;sid=140c176bfaf360cf28c7f1a25d59b709&amp;amp;start=420&lt;br /&gt;
&lt;br /&gt;
== Basic Usage ==&lt;br /&gt;
=== Selecting a location ===&lt;br /&gt;
* Enter an ICAO code  &lt;br /&gt;
* Click on the map  &lt;br /&gt;
* Import aircraft position from FGFS  &lt;br /&gt;
&lt;br /&gt;
=== Configuring a patch ===&lt;br /&gt;
Parameters:&lt;br /&gt;
* Radius  &lt;br /&gt;
* Resolution  &lt;br /&gt;
* Downsampling (--sdwn)  &lt;br /&gt;
* Overwrite mode (--over)  &lt;br /&gt;
&lt;br /&gt;
=== Running a job ===&lt;br /&gt;
Press '''Patch Scenery''' to start.  &lt;br /&gt;
Completed tiles display on the map.&lt;br /&gt;
&lt;br /&gt;
== Route-Based Scenery Creation ==&lt;br /&gt;
Drag &amp;amp; drop:&lt;br /&gt;
* a GPX flight plan  &lt;br /&gt;
* or a FlightGear .xml route  &lt;br /&gt;
&lt;br /&gt;
The GUI automatically:&lt;br /&gt;
# Parses waypoints  &lt;br /&gt;
# Computes segments  &lt;br /&gt;
# Creates coverage circles  &lt;br /&gt;
# Runs jobs in sequence  &lt;br /&gt;
# Tracks progress  &lt;br /&gt;
&lt;br /&gt;
== FlightGear Integration ==&lt;br /&gt;
Before running FGFS, enable Telnet by placing the property --telnet=5000 in the additional settings box in FG-launcher. Additionally, in the add-ons section, you must specify the path to the Orthophotos folder in the additional scenery folder section.&lt;br /&gt;
&lt;br /&gt;
This is a WIP (Work in Progress); we still need to test paths and use flows.&lt;br /&gt;
&lt;br /&gt;
* Aircraft position is displayed  &lt;br /&gt;
* Live heading, altitude, speed shown  &lt;br /&gt;
* “Download Around Aircraft” available&lt;br /&gt;
&lt;br /&gt;
== Coverage Visualization ==&lt;br /&gt;
The GUI supports filtering:&lt;br /&gt;
* by resolution  &lt;br /&gt;
* by date (session/day/week/month/year)  &lt;br /&gt;
* by opacity  &lt;br /&gt;
&lt;br /&gt;
Tiles can display preview images and metadata.&lt;br /&gt;
&lt;br /&gt;
== Directory Settings ==&lt;br /&gt;
Output and backup paths can be edited directly from the interface.&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
* Ensure Julia 1.10+ is installed  &lt;br /&gt;
* Ensure no other service is using port 8000  &lt;br /&gt;
* Clear browser cache if GUI does not load tiles  &lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[TerraGear]]  &lt;br /&gt;
* [[Scenery]]  &lt;br /&gt;
* [[Howto:Install scenery]]  &lt;br /&gt;
&lt;br /&gt;
[[Category:Scenery]]&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Development]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_March_2025&amp;diff=143344</id>
		<title>FlightGear Newsletter March 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_March_2025&amp;diff=143344"/>
		<updated>2025-12-26T12:01:46Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Screenshot of the Month */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-03}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-03}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
==Development news==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==In the hangar==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff.  The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Scenery corner==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Add-ons corner ==&lt;br /&gt;
&lt;br /&gt;
=== Logbook ===&lt;br /&gt;
&lt;br /&gt;
A new version of the [[Logbook Add-on]] labelled 2.0 has been released. The main changes are related to the new FG 2024.1 release, where Logbook now uses SQLite for data storage (CSV is still possible with the export function).&lt;br /&gt;
&lt;br /&gt;
[[File:Logbook Flight-analysis.png|thumb|Logbook Flight-analysis window]]&lt;br /&gt;
Another significant change is the addition of &amp;quot;Flight Analysis&amp;quot; for both historical Logbook flights and the current session.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==AI== &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Community news==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Multiplayer events==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== FlightGear events ==&lt;br /&gt;
&lt;br /&gt;
=== University event ===&lt;br /&gt;
&lt;br /&gt;
For the second year, the FlighTeam platform was deployed for a course with 15 students of the Master 2 Information Systems Security Management program at IAE Paris-Est, the public management school of the Université Paris-Est Créteil (UPEC). The theme was Threat and Error Management (TEM). Compared with 2024, the number of simulators was doubled: six were connected in addition to the air traffic control station ([[OpenRadar]]). Four mission were carried out lasting around 90 minutes. The platform worked perfectly and no technical problems were encountered. Next week, version 2024.1 will be installed and a student project will start to discover the [[Nasal]] language. Thanks and well done to the FlightGear team!&lt;br /&gt;
&lt;br /&gt;
[[File:FlighTeam course 01.jpg|thumb|FlighTeam Course (IAE Paris-Est - March 2025).]]&lt;br /&gt;
[[File:FlighTeam course 02.jpg|thumb|FlighTeam Course (IAE Paris-Est - March 2025).]]&lt;br /&gt;
&lt;br /&gt;
'''References of this project:'''&lt;br /&gt;
&lt;br /&gt;
* Altombokshi, R., &amp;amp; Hu, I. (2022). Voler, c'est aussi manager, ''6e Colloque International Game Evolution'', en ligne, [https://hal.archives-ouvertes.fr/hal-03663363 link].&lt;br /&gt;
* Bakri, S., Collas, F., &amp;amp; Lépinard, P. (2025). Une plateforme de simulation aéronautique pour l’enseignement de la culture de la sécurité. ''8&amp;lt;sup&amp;gt;es&amp;lt;/sup&amp;gt; journées de pratique et de recherche du GT-AIMS MACCA Management'', Evry, France, [https://hal.science/hal-04879126 link].&lt;br /&gt;
* Brahami, M., Gomes, P., &amp;amp; Lépinard, P. (2023). FlightGear - Un simulateur de vol open source pour remplacer MSFS 2020. ''Micro Simulateur'', 354, 16-19.&lt;br /&gt;
* Launay, M., &amp;amp; Capgras, N. (2023). La simulation de vol : Outil d’apprentissage de la gestion de la sécurité. ''7e Colloque International Game Evolution'', en ligne, [https://hal.science/hal-04106960v1 link].&lt;br /&gt;
* Lépinard, P. (2022). FlighTeam : des simulateurs de vol pour former les étudiants au management. ''Micro Simulateur'', 342, 20-23.&lt;br /&gt;
* Lépinard, P., Mansour, S., &amp;amp; Moulai, L. (2024). La plateforme de simulation FlighTeam : Enseigner la théorie des organisations à haute fiabilité avec FlightGear. Micro Simulateur, 363, 16-19.&lt;br /&gt;
* Lépinard, P., Mansour, S., &amp;amp; Moulai, L. (2024). Crew resource management : comment peut-on s’inspirer de l’aéronautique ? Une approche pédagogique. Management &amp;amp; Data Science.&lt;br /&gt;
* Mansour, S., &amp;amp; Moulai, L. (2024). Envolée ludique : embarquez pour un cours à destination des organisations à haute fiabilité. 8e Colloque International Game Evolution, en ligne.&lt;br /&gt;
&lt;br /&gt;
=== FSWeekend 2025 ===&lt;br /&gt;
&lt;br /&gt;
Over the weekend of 15-16 March, a team of FlightGear developers travelled to [[Lelystad Airport]] (EHLE) in the Netherlands to represent FlightGear at the annual international FlightSimWeekend (FSWeekend). Over the course of two days, the Aviodrome aviation museum welcomed over 4500 visitors, ranging from young families to seasoned flightsim veterans. Many visitors tried out one of our setups for a first-hand experience of open source flying.&lt;br /&gt;
&lt;br /&gt;
See [https://www.flightgear.org/blog/fsweekend-2025/ this blog post] for an impression.&lt;br /&gt;
&lt;br /&gt;
==Screenshot of the Month==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-03}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-03}} 2025 is Scenic Flight over the Southern Alps of New Zealand by {{usr|chrisblobster}}&lt;br /&gt;
[[File:ANZ-777-300-ER.jpg|thumb|Scenic Flight over the Southern Alps of New Zealand. by chrisblobster]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-03 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-03 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 03]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:ANZ-777-300-ER.jpg&amp;diff=143342</id>
		<title>File:ANZ-777-300-ER.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:ANZ-777-300-ER.jpg&amp;diff=143342"/>
		<updated>2025-12-26T11:53:16Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Uploaded a work by @chrisblobster from https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43182&amp;amp;p=431342&amp;amp;hilit=sotm+march#p431342 with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=Scenic Flight over the Southern Alps of New Zealand. by @chrisblobster}}&lt;br /&gt;
|date=2025-04-12&lt;br /&gt;
|source=https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43182&amp;amp;p=431342&amp;amp;hilit=sotm+march#p431342&lt;br /&gt;
|author=@chrisblobster&lt;br /&gt;
|permission=&lt;br /&gt;
|other versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{cc-by-sa-4.0}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Screenshot of the month]]&lt;br /&gt;
[[Category:Boeing]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2025&amp;diff=143341</id>
		<title>FlightGear Newsletter September 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_September_2025&amp;diff=143341"/>
		<updated>2025-12-26T11:45:43Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-09}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-09}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI Beta ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-Beta-20250810.png|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana Adriano continues working on the beta version of his Julia code, which provides an interactive map-based workflow for generating photographic scenery for FlightGear. The latest release now includes a feature that shows where the system places the Orthophotos and Orthophotos-save directories.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=375&lt;br /&gt;
&lt;br /&gt;
=== Which Runway Add-on ===&lt;br /&gt;
&lt;br /&gt;
[[File:Which_Runway_main_window_v.1.3.0.png|thumb|Which Runway main window]]&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom) created a new add-on names &amp;quot;[https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&amp;quot;. This add-on uses weather data and preferred runways at the airport (ICAO.rwyuse.xml files) to indicate the best runway for takeoff or landing. It also calculates headwinds, crosswinds, and tailwinds for each airport runway (which can be useful for input into the MCDU), and provides a wealth of information about the airport and its runways, along with a graphical representation on a wind rose.&lt;br /&gt;
&lt;br /&gt;
See also [https://forum.flightgear.org/viewtopic.php?f=89&amp;amp;t=43680 forum] and [[Which_Runway_Add-on|wiki]] pages.&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-09}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-9}} 2025 is &amp;quot;Operation Market Garden&amp;quot; by @OrbitalMartian&lt;br /&gt;
&lt;br /&gt;
[[File:Operation Market Garden by @OrbitalMartian.webp|thumb|Operation Market Garden by @OrbitalMartian]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-09 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-09 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 09]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-09 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143270</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143270"/>
		<updated>2025-12-13T22:06:37Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Photoscenery-CLI */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
==== Photoscenery-CLI ====&lt;br /&gt;
&lt;br /&gt;
For all users of the Julia photoscenery in terminal in its pre-GUI version, it is a pleasure to report that the previously released &amp;quot;beta 5&amp;quot; version of Adriano Bassignana's Julia/Photoscenery (before development began on the GUI version, ver. 6) continues to work well on Flightgear installations in a Windows 10 (and possibly 11) environment. More info. on that may be found under [https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=435#p436792 this post] on the FG forum.&lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
&lt;br /&gt;
===== Flight Test &amp;amp; Personal Tweaks by VonS =====&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, VonS thought to go a (simpler) step further and merely strapped a wing to themselves (or themselves to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for their rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Laminar 13 Hang Glider for FlightGear. Flight Test &amp;amp; Tweaks by Vons |frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the latest tweaks, visit the FG forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
===== Additional Tweaks Information =====&lt;br /&gt;
&lt;br /&gt;
FlightGear users interested in these custom tweaks may also want to check the recent gliders updates (October and November 2025) for the [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p435385 ASK 13 tweaks] and [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p436217 ASG 29 tweaks]&lt;br /&gt;
&lt;br /&gt;
Review the posts carefully before downloading. Many of these adjustments, including lift, drag, and control harmonization values, were later applied to the Laminar hang glider as subtle improvements.&lt;br /&gt;
&lt;br /&gt;
These tweaks were tested in FG 2020.3.19 and should be compatible with current versions. All mentioned gliders use JSBSim flight dynamics models (FDM).&lt;br /&gt;
&lt;br /&gt;
For YASim-based tweaks by VonS, please contact him directly via PM on the FG forum, as most were not publicly released. Some exceptions are included in recent updates to Emmanuel Baranger's aircraft at the &amp;quot;Helijah FG Hangar.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Links to various modifications can be found at the bottom of the contributor's forum posts [https://forum.flightgear.org/viewtopic.php?f=3&amp;amp;t=43735 &amp;quot;Von S Various Mods&amp;quot;]. For a broader overview, see the VonS Various Mods thread in &amp;quot;Hangar Talk.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
VonS began FDM tweaking in the mid-2010s, focusing on early 1900s and WWI aircraft, and has contributed significantly to FlightGear's open-source flexibility. For early aviation examples, see [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43872&amp;amp;start=15 the Sopwith Camel thread (November 2025)] which also includes detailed technical posts by S&amp;amp;J, Lester-Boffo, Alant, and himself.&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Finished events ===&lt;br /&gt;
==== Independence Day Event 2025 ====&lt;br /&gt;
To celebrate Poland's Independence Day, the Polish Discord channel organized an Air Show with several performances. Clips are included in the video:&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|ekiLpbSXAmU|480px||Independence Day Event 2025}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]--&amp;gt;&lt;br /&gt;
&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143269</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143269"/>
		<updated>2025-12-13T22:06:08Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Photoscenery-CLI */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
==== Photoscenery-CLI ====&lt;br /&gt;
&lt;br /&gt;
For all users of the Julia Photoscenery in terminal in its pre-GUI version, it is a pleasure to report that the previously released &amp;quot;beta 5&amp;quot; version of Adriano Bassignana's Julia/Photoscenery (before development began on the GUI version, ver. 6) continues to work well on Flightgear installations in a Windows 10 (and possibly 11) environment. More info. on that may be found under [https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=435#p436792 this post] on the FG forum.&lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
&lt;br /&gt;
===== Flight Test &amp;amp; Personal Tweaks by VonS =====&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, VonS thought to go a (simpler) step further and merely strapped a wing to themselves (or themselves to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for their rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Laminar 13 Hang Glider for FlightGear. Flight Test &amp;amp; Tweaks by Vons |frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the latest tweaks, visit the FG forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
===== Additional Tweaks Information =====&lt;br /&gt;
&lt;br /&gt;
FlightGear users interested in these custom tweaks may also want to check the recent gliders updates (October and November 2025) for the [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p435385 ASK 13 tweaks] and [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p436217 ASG 29 tweaks]&lt;br /&gt;
&lt;br /&gt;
Review the posts carefully before downloading. Many of these adjustments, including lift, drag, and control harmonization values, were later applied to the Laminar hang glider as subtle improvements.&lt;br /&gt;
&lt;br /&gt;
These tweaks were tested in FG 2020.3.19 and should be compatible with current versions. All mentioned gliders use JSBSim flight dynamics models (FDM).&lt;br /&gt;
&lt;br /&gt;
For YASim-based tweaks by VonS, please contact him directly via PM on the FG forum, as most were not publicly released. Some exceptions are included in recent updates to Emmanuel Baranger's aircraft at the &amp;quot;Helijah FG Hangar.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Links to various modifications can be found at the bottom of the contributor's forum posts [https://forum.flightgear.org/viewtopic.php?f=3&amp;amp;t=43735 &amp;quot;Von S Various Mods&amp;quot;]. For a broader overview, see the VonS Various Mods thread in &amp;quot;Hangar Talk.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
VonS began FDM tweaking in the mid-2010s, focusing on early 1900s and WWI aircraft, and has contributed significantly to FlightGear's open-source flexibility. For early aviation examples, see [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43872&amp;amp;start=15 the Sopwith Camel thread (November 2025)] which also includes detailed technical posts by S&amp;amp;J, Lester-Boffo, Alant, and himself.&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Finished events ===&lt;br /&gt;
==== Independence Day Event 2025 ====&lt;br /&gt;
To celebrate Poland's Independence Day, the Polish Discord channel organized an Air Show with several performances. Clips are included in the video:&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|ekiLpbSXAmU|480px||Independence Day Event 2025}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]--&amp;gt;&lt;br /&gt;
&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143268</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143268"/>
		<updated>2025-12-13T22:04:43Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
==== Photoscenery-CLI ====&lt;br /&gt;
&lt;br /&gt;
For all users of the Photoscenery in terminal in its pre-GUI version, it is a pleasure to report that the previously released &amp;quot;beta 5&amp;quot; version of Adriano Bassignana's Julia/Photoscenery (before development began on the GUI version, ver. 6) continues to work well on Flightgear installations in a Windows 10 (and possibly 11) environment. More info. on that may be found under [https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=435#p436792 this post] on the FG forum. &lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
&lt;br /&gt;
===== Flight Test &amp;amp; Personal Tweaks by VonS =====&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, VonS thought to go a (simpler) step further and merely strapped a wing to themselves (or themselves to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for their rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Laminar 13 Hang Glider for FlightGear. Flight Test &amp;amp; Tweaks by Vons |frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the latest tweaks, visit the FG forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
===== Additional Tweaks Information =====&lt;br /&gt;
&lt;br /&gt;
FlightGear users interested in these custom tweaks may also want to check the recent gliders updates (October and November 2025) for the [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p435385 ASK 13 tweaks] and [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43713&amp;amp;start=105#p436217 ASG 29 tweaks]&lt;br /&gt;
&lt;br /&gt;
Review the posts carefully before downloading. Many of these adjustments, including lift, drag, and control harmonization values, were later applied to the Laminar hang glider as subtle improvements.&lt;br /&gt;
&lt;br /&gt;
These tweaks were tested in FG 2020.3.19 and should be compatible with current versions. All mentioned gliders use JSBSim flight dynamics models (FDM).&lt;br /&gt;
&lt;br /&gt;
For YASim-based tweaks by VonS, please contact him directly via PM on the FG forum, as most were not publicly released. Some exceptions are included in recent updates to Emmanuel Baranger's aircraft at the &amp;quot;Helijah FG Hangar.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
Links to various modifications can be found at the bottom of the contributor's forum posts [https://forum.flightgear.org/viewtopic.php?f=3&amp;amp;t=43735 &amp;quot;Von S Various Mods&amp;quot;]. For a broader overview, see the VonS Various Mods thread in &amp;quot;Hangar Talk.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
VonS began FDM tweaking in the mid-2010s, focusing on early 1900s and WWI aircraft, and has contributed significantly to FlightGear's open-source flexibility. For early aviation examples, see [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=43872&amp;amp;start=15 the Sopwith Camel thread (November 2025)] which also includes detailed technical posts by S&amp;amp;J, Lester-Boffo, Alant, and himself.&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Finished events ===&lt;br /&gt;
==== Independence Day Event 2025 ====&lt;br /&gt;
To celebrate Poland's Independence Day, the Polish Discord channel organized an Air Show with several performances. Clips are included in the video:&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|ekiLpbSXAmU|480px||Independence Day Event 2025}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]--&amp;gt;&lt;br /&gt;
&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2025&amp;diff=143259</id>
		<title>FlightGear Newsletter May 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_May_2025&amp;diff=143259"/>
		<updated>2025-12-11T05:00:18Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* Multiplayer events */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-05}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-05}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I wish you to invite you all FG'ers to the first ever &amp;quot; Bouncing Baskets&amp;quot; event for the Wednesday evening flight.&lt;br /&gt;
&lt;br /&gt;
This event is based and inspired in the superb work in sport ballooning by HerbyW for FlightGear.&lt;br /&gt;
&lt;br /&gt;
I'll provide you previous support to get familiar with the balloon and the whirlpool logic circuit.&lt;br /&gt;
&lt;br /&gt;
Estimated flight time could be 1 h and a half to several days, weeks or months... The nearest to the destination, the winner.&lt;br /&gt;
&lt;br /&gt;
Many laughs guarantied, balloon gin kana, easy and fun for all&lt;br /&gt;
&lt;br /&gt;
Those interested in participating can find the relevant information at: https://forum.flightgear.org/viewtopic.php?f=10&amp;amp;t=39025&amp;amp;start=5460#p432091&lt;br /&gt;
&lt;br /&gt;
[[File:Ballooning.png|thumb|FG Sport Ballooning, Bouncing Baskets 2025]]&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 05]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:Ballooning.png&amp;diff=143258</id>
		<title>File:Ballooning.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:Ballooning.png&amp;diff=143258"/>
		<updated>2025-12-11T04:52:49Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Uploaded a work by Michat from https://forum.flightgear.org/viewtopic.php?f=10&amp;amp;t=39213&amp;amp;p=432081#p432081 with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=FG Sport Ballooning, Bouncing Baskets 2025}}&lt;br /&gt;
|date=2025-05-15&lt;br /&gt;
|source=https://forum.flightgear.org/viewtopic.php?f=10&amp;amp;t=39213&amp;amp;p=432081#p432081&lt;br /&gt;
|author=Michat&lt;br /&gt;
|permission=&lt;br /&gt;
|other versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{cc-by-sa-4.0}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Balloons]]&lt;br /&gt;
[[Category:Events]]&lt;br /&gt;
[[Category:Event images]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143257</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143257"/>
		<updated>2025-12-11T04:13:11Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
==== Flight Test &amp;amp; Personal Tweaks by Vons ====&lt;br /&gt;
&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, I thought I'd go a (simpler) step further and merely strap a wing to myself (or me to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for my rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Flight Test &amp;amp; Tweaks Laminar 13 Hang Glider for FlightGear|frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the tweaks, visit the forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]--&amp;gt;&lt;br /&gt;
&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 11]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143256</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143256"/>
		<updated>2025-12-11T04:11:07Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
==== Flight Test &amp;amp; Personal Tweaks by Vons ====&lt;br /&gt;
&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, I thought I'd go a (simpler) step further and merely strap a wing to myself (or me to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for my rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Flight Test &amp;amp; Tweaks Laminar 13 Hang Glider for FlightGear|frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the tweaks, visit the forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 11]]&lt;br /&gt;
[[Category:Screenshot of the month/2025-11]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_July_2025&amp;diff=143255</id>
		<title>FlightGear Newsletter July 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_July_2025&amp;diff=143255"/>
		<updated>2025-12-11T04:06:14Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-07}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-07}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-07}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-07}} 2025 is Mid-day Innsbruck take off by {{usr|Fahim Dalvi}}&lt;br /&gt;
&lt;br /&gt;
[[File:SOTM-July-2025.jpg|thumb|Midday Innsbruck take off]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-06 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-06 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 07]]&lt;br /&gt;
[[Category:SOTM]]&lt;br /&gt;
[[Category:Screenshot of the month/2025-07]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-06 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:SOTM-July-2025.jpg&amp;diff=143254</id>
		<title>File:SOTM-July-2025.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:SOTM-July-2025.jpg&amp;diff=143254"/>
		<updated>2025-12-11T04:02:35Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Uploaded a work by Fahim Dalvi from https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43603 with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=Midday Innsbruck take off}}&lt;br /&gt;
|date=2025-07-09&lt;br /&gt;
|source=https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43603&lt;br /&gt;
|author=Fahim Dalvi&lt;br /&gt;
|permission=&lt;br /&gt;
|other versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{cc-by-sa-4.0}}&lt;br /&gt;
&lt;br /&gt;
[[Category:SOTM]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143253</id>
		<title>FlightGear Newsletter April 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143253"/>
		<updated>2025-12-11T03:50:06Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied to the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-04}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-04}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
==== DC-10 ====&lt;br /&gt;
The new [[DC-10]] has been uploaded to FGAddon for 2024.1 and next branches.&lt;br /&gt;
&lt;br /&gt;
[[File:DC-10-Octal.png|thumb|The DC-10-30F]]&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
==== Video tutorial ====&lt;br /&gt;
&lt;br /&gt;
An in-depth tutorial on setting up and customizing FlightGear. Includes a [https://www.youtube.com/watch?v=5TeJZF3XO0c&amp;amp;t=20m27s custom Nasal script for Thrustmaster TWCS Throttle to naturally &amp;quot;turn your head&amp;quot; and look around in the cockpit].&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|5TeJZF3XO0c}}&lt;br /&gt;
&lt;br /&gt;
==== Entertainment ====&lt;br /&gt;
New video by FGnoob Swiss001 talking about FlightGear :oops: :arrow: :roll: :mrgreen:&lt;br /&gt;
{{#ev:youtube|wyefvCO_kVg}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
[[File:SOTM-April-2025.jpg|thumb|F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by @I-FABI]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-04 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-04 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[Category:Changes after 2024.1]]--&amp;gt;&lt;br /&gt;
&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 04]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-04 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143252</id>
		<title>FlightGear Newsletter April 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143252"/>
		<updated>2025-12-11T03:45:41Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* DC-10 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied to the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-04}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-04}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
==== DC-10 ====&lt;br /&gt;
The new [[DC-10]] has been uploaded to FGAddon for 2024.1 and next branches.&lt;br /&gt;
&lt;br /&gt;
[[File:DC-10-Octal.png|thumb|The DC-10-30F]]&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
==== Video tutorial ====&lt;br /&gt;
&lt;br /&gt;
An in-depth tutorial on setting up and customizing FlightGear. Includes a [https://www.youtube.com/watch?v=5TeJZF3XO0c&amp;amp;t=20m27s custom Nasal script for Thrustmaster TWCS Throttle to naturally &amp;quot;turn your head&amp;quot; and look around in the cockpit].&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|5TeJZF3XO0c}}&lt;br /&gt;
&lt;br /&gt;
==== Entertainment ====&lt;br /&gt;
New video by FGnoob Swiss001 talking about FlightGear :oops: :arrow: :roll: :mrgreen:&lt;br /&gt;
{{#ev:youtube|wyefvCO_kVg}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
[[File:SOTM-April-2025.jpg|thumb|F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by @I-FABI]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-04 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-04 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 04]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-04 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143251</id>
		<title>FlightGear Newsletter April 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_April_2025&amp;diff=143251"/>
		<updated>2025-12-11T03:41:55Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied to the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-04}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-04}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Related Software tools and projects == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Those not being part of FlightGear itself, like for example OpenRadar, TerreMaster or flightgear-atc.alwaysdata.net. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
==== DC-10 ====&lt;br /&gt;
The new [[DC-10]] has been uploaded to FGAddon for 2024.1 and next branches.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
=== FlightGear on YouTube ===&lt;br /&gt;
&lt;br /&gt;
==== Video tutorial ====&lt;br /&gt;
&lt;br /&gt;
An in-depth tutorial on setting up and customizing FlightGear. Includes a [https://www.youtube.com/watch?v=5TeJZF3XO0c&amp;amp;t=20m27s custom Nasal script for Thrustmaster TWCS Throttle to naturally &amp;quot;turn your head&amp;quot; and look around in the cockpit].&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|5TeJZF3XO0c}}&lt;br /&gt;
&lt;br /&gt;
==== Entertainment ====&lt;br /&gt;
New video by FGnoob Swiss001 talking about FlightGear :oops: :arrow: :roll: :mrgreen:&lt;br /&gt;
{{#ev:youtube|wyefvCO_kVg}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-04}} 2025 is F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by {{usr|I-FABI}}&lt;br /&gt;
[[File:SOTM-April-2025.jpg|thumb|F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by @I-FABI]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-04 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-04 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 04]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-04 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=File:SOTM-April-2025.jpg&amp;diff=143250</id>
		<title>File:SOTM-April-2025.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=File:SOTM-April-2025.jpg&amp;diff=143250"/>
		<updated>2025-12-11T03:35:08Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: Uploaded a work by I-FABI from https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43296&amp;amp;p=431836&amp;amp;hilit=SOTM+april#p431836 with UploadWizard&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=={{int:filedesc}}==&lt;br /&gt;
{{Information&lt;br /&gt;
|description={{en|1=F14B successful landing on Nimitz in the Adriatic Sea at 40nm from LIPC (Cervia) by @I-FABI}}&lt;br /&gt;
|date=2025-05-14&lt;br /&gt;
|source=https://forum.flightgear.org/viewtopic.php?f=88&amp;amp;t=43296&amp;amp;p=431836&amp;amp;hilit=SOTM+april#p431836&lt;br /&gt;
|author=I-FABI&lt;br /&gt;
|permission=&lt;br /&gt;
|other versions=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
=={{int:license-header}}==&lt;br /&gt;
{{cc-by-sa-4.0}}&lt;br /&gt;
&lt;br /&gt;
[[Category:SOTM]]&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143249</id>
		<title>FlightGear Newsletter November 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_November_2025&amp;diff=143249"/>
		<updated>2025-12-11T01:51:43Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: /* In the hangar */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-11}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-11}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Julia photoscenery generator GUI ===&lt;br /&gt;
==== Photoscenery-GUI ====&lt;br /&gt;
&lt;br /&gt;
[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]&lt;br /&gt;
&lt;br /&gt;
Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published at the following link:&lt;br /&gt;
https://wiki.flightgear.org/Julia_photoscenery_generator_GUI&lt;br /&gt;
The manual currently contains the essential information for correct installation.&lt;br /&gt;
&lt;br /&gt;
New features in the latest version include:&lt;br /&gt;
&lt;br /&gt;
The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.&lt;br /&gt;
&lt;br /&gt;
A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.&lt;br /&gt;
&lt;br /&gt;
Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.&lt;br /&gt;
&lt;br /&gt;
The interface allows users to view radio navigation aids and airports, along with their key information.&lt;br /&gt;
&lt;br /&gt;
The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.&lt;br /&gt;
&lt;br /&gt;
Many other features will be documented on the Wiki in the future.&lt;br /&gt;
&lt;br /&gt;
https://github.com/abassign/Photoscenery-GUI.git&lt;br /&gt;
&lt;br /&gt;
For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&amp;amp;t=39066&amp;amp;start=390&lt;br /&gt;
&lt;br /&gt;
=== Framework for Canvas Add-on ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework Framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:&lt;br /&gt;
&lt;br /&gt;
# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).&lt;br /&gt;
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.&lt;br /&gt;
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.&lt;br /&gt;
# A mechanism for checking whether there is a new version of your add-on to inform users about it.&lt;br /&gt;
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).&lt;br /&gt;
# Ability to create Nasal unit tests and run them using multi-key command.&lt;br /&gt;
&lt;br /&gt;
An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.&lt;br /&gt;
&lt;br /&gt;
You can also see how his other add-ons are written, all based on the Framework (main branches):&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]&lt;br /&gt;
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]&lt;br /&gt;
&lt;br /&gt;
=== Add-ons Menu Aggregator ===&lt;br /&gt;
&lt;br /&gt;
Roman Ludwicki has created a new &amp;quot;[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]&amp;quot; add-on. The &amp;quot;Add-ons Menu Aggregator&amp;quot; add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.&lt;br /&gt;
&lt;br /&gt;
The &amp;quot;Add-ons Menu Aggregator&amp;quot; automatically aggregates menu entries from all installed add-ons and places them into one common menu item – &amp;quot;Add-ons.&amp;quot; Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
=== Aircraft reviews ===&lt;br /&gt;
==== Laminar 13 Hang Glider for FlightGear ====&lt;br /&gt;
==== Flight Test &amp;amp; Personal Tweaks by Vons ====&lt;br /&gt;
&lt;br /&gt;
Having recently become interested in gliding and soaring in FG, I thought I'd go a (simpler) step further and merely strap a wing to myself (or me to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for my rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|tHQqhl3Sf5w|||Flight Test &amp;amp; Tweaks Laminar 13 Hang Glider for FlightGear|frame}}&lt;br /&gt;
&lt;br /&gt;
If you're interested in seeing the flight test results and accessing the tweaks, visit the forum page at: https://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=42893&amp;amp;start=45#p436600&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-05}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2024.1]]&amp;lt;!--Has a new version been released this month? Use previous version!--&amp;gt;&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 05]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-05 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_October_2025&amp;diff=143248</id>
		<title>FlightGear Newsletter October 2025</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_October_2025&amp;diff=143248"/>
		<updated>2025-12-11T00:46:24Z</updated>

		<summary type="html">&lt;p&gt;Aepcam: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!--&lt;br /&gt;
&lt;br /&gt;
NOTES TO EDITORS&lt;br /&gt;
&lt;br /&gt;
* Headings&lt;br /&gt;
  * DO NOT DELETE HEADINGS prior to final cleanup&lt;br /&gt;
  * Current headings and their order is merely a suggestion based on what have been used earlier&lt;br /&gt;
  * Changes made to headings or structure should also be copied the Newsletter template http://wiki.flightgear.org/User:Skybike/Template:This_months_newsletter/Newsletter_example&lt;br /&gt;
&lt;br /&gt;
* Final cleanup before write protecting&lt;br /&gt;
  * Remove unused headings&lt;br /&gt;
  * Remove {{Appendix}} if not used.&lt;br /&gt;
  * Update &amp;quot;Category: Changes after&amp;quot; to the FG version current at the 1st of this month&lt;br /&gt;
  * Finally remove this comment&lt;br /&gt;
  * Update [[Next Newsletter]] and [[FlightGear Newsletter]]&lt;br /&gt;
&lt;br /&gt;
* Discussion, issues and suggestions&lt;br /&gt;
  * Regarding this newsletter issue, please use the discussion page&lt;br /&gt;
  * Regarding the newsletter in general, primarily use the FlightGear Newsletter discussion page (Talk:FlightGear Newsletter)&lt;br /&gt;
  * Regarding this Newsletter template, please use FIXME&lt;br /&gt;
&lt;br /&gt;
+++   {{Newsletter-header|{{#time: F | 2025-10}}}}   +++&lt;br /&gt;
--&amp;gt;{{User:Skybike/Template:Newsletter-header-translate|2025-10}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter.  If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''&lt;br /&gt;
&lt;br /&gt;
''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''&lt;br /&gt;
&lt;br /&gt;
== Development news ==&lt;br /&gt;
&amp;lt;!-- News about FlightGear itself.  The FlightGear mailing list and/or core developers are a good source. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Disclaimer|id=final-fixed-function-release}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Related Software tools and projects ==&lt;br /&gt;
=== Nasal Namespace Browser ===&lt;br /&gt;
&lt;br /&gt;
After 7 years, Roman Ludwicki resurrected [[Nasal Browser|Nasal Browser]] as an add-on. [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser] it's reimplementation of the Nasal Browser using Canvas Widgets.&lt;br /&gt;
&lt;br /&gt;
This add-on is useful for developers who want to view all the namespaces created in Nasal. It also makes it easier to understand how namespaces are organized.&lt;br /&gt;
&lt;br /&gt;
== In the hangar ==&lt;br /&gt;
&amp;lt;!-- News about new and upgraded aircraft and related stuff. The official forum and other ones usually are a good source for this. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === New aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Updated aircraft === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Liveries === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Instruments === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === Aircraft reviews === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Scenery corner ==&lt;br /&gt;
&amp;lt;!-- Scenery development news --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Scenery Models === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Airports === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Land cover === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Osm2city === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === New OSM2City areas === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Interview with a contributor == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Suggested flights == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == AI == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI traffic === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- === AI scenarios === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Community news ==&lt;br /&gt;
&amp;lt;!-- === FlightGear on YouTube === --&amp;gt;&lt;br /&gt;
&amp;lt;!-- embed video as {{#ev:youtube|VCc6PwRI1LA}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Forum news === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Wiki updates === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Article of the month === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Multiplayer events ==&lt;br /&gt;
&amp;lt;!-- === Upcoming events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- === Finished events === --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == FlightGear events == --&amp;gt;&lt;br /&gt;
&amp;lt;!-- For example presence at FSWeekend --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- == Hardware reviews == --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Screenshot of the Month ==&lt;br /&gt;
&amp;lt;!--FlightGear's Screenshot of the Month {{#time: F | 2025-10}} 2025 is FIXME by {{usr|FIXME}}&lt;br /&gt;
ADD IMAGE --&amp;gt;&lt;br /&gt;
FlightGear's Screenshot of the Month {{#time: F | 2025-10}} 2025 is Test Flight by {{usr|The epic chicken}}&lt;br /&gt;
[[File:SOTM-october-2025.jpg|thumb|777-9 Test Flight by The epic chicken]]&lt;br /&gt;
&lt;br /&gt;
If you want to participate in the screenshot contest&amp;lt;!-- of {{#time: F | 2025-05 + 1month}}--&amp;gt;, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.&amp;lt;!--Once the voting has finished, the best screenshot will be presented in the Newsletter edition of {{#time: F | 2025-05 + 1month}}--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear Newsletter|2025 10]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--[[de:FlightGear Newsletter {{#time: F Y | 2025-10 | de }}]]--&amp;gt;&lt;/div&gt;</summary>
		<author><name>Aepcam</name></author>
	</entry>
</feed>