FlightGear Newsletter January 2016: Difference between revisions

FlightGear Newsletter January 2016 (view source)

1,364 bytes added , 9 January 2016

20,741

edits

@@ Line 64: / Line 64: @@
 waypointlist commits
+=== 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 ===
 {{FGCquote