FlightGear Newsletter January 2016: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter January 2016 (view source)

Revision as of 16:57, 5 February 2016

3,433 bytes removed ,  5 February 2016
Continuing cleanup
(Being cleanup for publishing)
(Continuing cleanup)
Line 8: Line 8:
[[#New ATC-pie release|New ATC-pie release]]<br>
[[#New ATC-pie release|New ATC-pie release]]<br>
[[#New version scheme and release preparations|New version scheme and release preparations]]<br>
[[#New version scheme and release preparations|New version scheme and release preparations]]<br>
[[#Project3000 and TerraSync|Project3000 and TerraSync]]<br>
[[#Python and FlightGear|Python and FlightGear]]<br>
[[#Python and FlightGear|Python and FlightGear]]<br>
[[#Experimental directional moonlight patches|Experimental directional moonlight patches]]<br>
[[#Experimental directional moonlight patches|Experimental directional moonlight patches]]<br>
Line 45: Line 44:
|date = Jan 5th, 2016
|date = Jan 5th, 2016
}}''
}}''
=== Project3000 and TerraSync ===
{{FGCquote
|1= I am thinking about making the scenery object from project3000 and osm2city available via terrasync. Just dumping the files in the models database is probably not a good idea as this would be a bit too much for many systems to render. But probably we could load those objects under individual subtrees in the scene graph and make them selectable using a new draw-mask flag? Even the loading of the scenery should be selectable by a property, at least at startup of fgfs. This should not be too complicated and would eventually needs the following tasks to be done: - work out a directory structure within the scenery system, besides /Objects /Models etc. - work out a scene graph structure for the models and a corresponding draw mask - implement the loader in SimGear (mostly copy&paste) - help me writing the automated importer/exporter script for our scenery server Anybody interested in pushing this? I don't have enough time to to this myself but I would happily help getting started.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34746310/
  | title  = <nowiki>[Flightgear-devel] Making project3000 and osm2city part of
terrasync?</nowiki>
  | author = <nowiki>Torsten Dreyer</nowiki>
  | date  = Jan 7th, 2016
  | added  = Jan 7th, 2016
  | script_version = 0.23
  }}
}}


=== Python and FlightGear ===
=== Python and FlightGear ===
{{FGCquote
Recently, some users have been experimenting with integrating Python with FlightGear. Curt has created a property tree implementation in Python,<ref>{{cite web
|1= I wrote a really quick/simple property tree implementation in python ... it doesn't do any of the fancy stuff the FlightGear property system does (like listeners, read/write tracing, etc.)  But it does implement a basic shared property tree and allows (in python) direct referencing of property tree elements. https://github.com/AuraUAS/aura-core/blob/python/src/python/props.py
|url = http://forum.flightgear.org/viewtopic.php?p=271196#p271196
|2= {{cite web
|title = <nowiki>Re: FGPython an propose for </nowiki>
  | url   = http://forum.flightgear.org/viewtopic.php?p=271196#p271196
|author = curt
  | title = <nowiki>Re: FGPython an propose for </nowiki>
|date = Jan 2nd, 2016
  | author = <nowiki>curt</nowiki>
}}</ref> while users {{usr|bugman}} and {{usr|www2}} have been working on the [[FGPythonSys]] subsystem.
  | date   = Jan 2nd, 2016
  | added  = Jan 2nd, 2016
  | script_version = 0.23
  }}
}}


{{FGCquote
''Find out more on the [http://forum.flightgear.org/viewtopic.php?f=6&t=28378 forum topic] and at [[Python in FlightGear]].''
|1= After some long forum discussions [1], followed by some private discussions with Curt about his own Python property system developments, I have written some code that might be of general interest. This started as an experiment to learn more about the design of the complicated Python object data structure, but it has expanded somewhat. The code is currently for experimentation, as only the property tree is accessible. It is written to be compatible only with Python 3k, as py2 support is not needed for an interpreter compiled into the fgfs binary.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34787850/
  | title  = <nowiki>[Flightgear-devel] A FGPythonSys implementation: The embedded
Python interpreter as a FlightGear subsystem.</nowiki>
  | author = <nowiki>Edward d'Auvergne</nowiki>
  | date  = Jan 22nd, 2016
  | added  = Jan 22nd, 2016
  | script_version = 0.23
  }}
}}


=== Experimental directional moonlight patches ===
=== Experimental directional moonlight patches ===
{{FGCquote
User {{usr|bugman}} has been working on directional moonlight in FlightGear. The current system for moonlight is quite limited, so he plans to totally upgrade it and make it more realistic. As of January 7, he has reached his first milestone, the results of which can be seen [http://forum.flightgear.org/viewtopic.php?f=47&t=28201&start=75#p271916 here].
|1= The changes here are for an initial milestone - exposing the position of the moon in the local aircraft frame and setting the amount of night-time illumination based on the phase of the moon. I have implemented some core infrastructure in Durk's ancient 1997-1998 ephemeris code (simgear), and in the flightgear time manager, ephemeris and solar system body (sun)solver code. I'll delve into full details below but, quickly, the changes are in the branches: https://sourceforge.net/u/edauvergne/flightgear/ci/directional_moonlight_v1/tree/ https://sourceforge.net/u/edauvergne/simgear/ci/directional_moonlight_v1/tree/ https://sourceforge.net/u/edauvergne/fgdata/ci/directional_moonlight_v1/tree/ More details can be found in the corresponding forum thread [1]. Initial results of the current code - specifically the automatic lighting of the ALS scene at night based on the moon's phase - are given in that thread [2], as well as below. Cheers, Edward [1] http://forum.flightgear.org/viewtopic.php?f=47&t=28201 (permanent archive: https://web.archive.org/web/http://forum.flightgear.org/viewtopic.php?f=47&t=28201 ). [2] http://forum.flightgear.org/viewtopic.php?f=47&t=28201&start=75#p271916 (permanent archive: https://web.archive.org/web/http://forum.flightgear.org/viewtopic.php?f=47&t=28201&start=75#p271916 ).
 
|2= {{cite web
''From {{cite web
  | url   = http://sourceforge.net/p/flightgear/mailman/message/34750775/
|url = http://sourceforge.net/p/flightgear/mailman/message/34750775/
  | title = <nowiki>[Flightgear-devel] Implementing directional moonlight (local
|title = <nowiki>[Flightgear-devel] Implementing directional moonlight (local position, phase-based full scene lighting, reflections, and optical effects).</nowiki>
position, phase-based full scene lighting, reflections,
|author = <nowiki>Edward d'Auvergne</nowiki>
and optical effects).</nowiki>
|date = Jan 8th, 2016
  | author = <nowiki>Edward d'Auvergne</nowiki>
}}; find out more on the [http://forum.flightgear.org/viewtopic.php?f=47&t=28201 forum topic].''
  | date   = Jan 8th, 2016
  | added  = Jan 8th, 2016
  | script_version = 0.23
  }}
}}


== In the hangar ==
== In the hangar ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/92420"

Navigation menu