FlightGear Newsletter December 2015: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter December 2015 (view source)

Revision as of 15:54, 3 January 2016

2,140 bytes removed ,  3 January 2016
Start cleanup for publishing
(Twin Otter development)
(Start cleanup for publishing)
Line 6: Line 6:
  | valign="top" width="33%" |
  | valign="top" width="33%" |
{{Newsletter-cover-header|Development news}}<br>
{{Newsletter-cover-header|Development news}}<br>
[[#HLA Update|HLA Update]]<br>
[[#Update on HLA development|Update on HLA development]]<br>
[[#New scenemodels and TerraSync hosting needed|New scenemodels and TerraSync hosting needed]]<br>
[[#New scenemodels and TerraSync hosting needed|New scenemodels and TerraSync hosting needed]]<br>
[[#Animated Jetways revamped|Animated Jetways]]<br>
[[#Animated Jetways revamped|Animated Jetways]]<br>
Line 30: Line 30:


== Development news ==
== Development news ==
=== HLA Update ===
=== Update on HLA development ===
[[File:Hla1-12-2015-screenshot-by-Stuart-Buchanan.png|thumb|Screenshot showing HLA prototype at LOWI]]
[[File:Hla1-12-2015-screenshot-by-Stuart-Buchanan.png|thumb|Screenshot showing HLA prototype at LOWI]]
{{FGCquote
As of December 29th, Stuart has split out the AI Manager so that it is a separate federate. This enables AI scenarios to be run outside of FlightGear itself, but viewed within FlightGear. His next step will be to flesh out the data model to provide equivalent functionality to an external AI Manager running as a separate federate.
|1= Hi All, I thought you might be interested in where I've managed to get with my HLA work. I now have FlightGear reading other aircraft in the RTI Federation (RTI speak for a simulation environment) and publishing it's own position information for other clients (in RTI known as Federates) to read. There's a screenshot showing it all here: http://www.nanjika.co.uk/flightgear/hla1.png There are a number of different components in play here: 1) A python script Federate which represents the KC-135 tanker. It publishes position updates a bit like we have for MP aircraft. 2) FlightGear itself as a Federate. It too is publishing position updates, but is also subscribing to updates and displaying them if appropriate. In this case it is displaying the KC-135 Federate. 3) A python script simulating a radar screen. This is receiving updates from both the KC-135 Federate and the FlightGear Federate and displaying them. The python scripts and all the clever stuff are courtesy of Mathias. The actual flightgear code changes amount to only 1.2kloc so far. I hope to be able to push some changes to flightgear soon.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34694887/
  | title  = <nowiki>[Flightgear-devel] HLA Update</nowiki>
  | author = <nowiki>Stuart Buchanan</nowiki>
  | date  = Dec 14th, 2015
  }}
}}


{{FGCquote
''From {{cite web
|1= Hi All, I thought I should provide an update on where I've got to in HLA integration. I've managed to split the AI Manager out as a separate Federate and executable. So AI scenarios can now be run outside of FlightGear itself, and viewed within the FG instance. This took a little longer than expected, as I had to work out iteratively the minimal set of FG components required to successfully run the AI Manager. (James - when you get the chance we'll need the capability to to have two clients access the NavDB concurrently - I've hit lots of errors trying to do this) I expect that it will be fairly straightforward to extend this and run the TrafficManager as part of this Federate as well. My next step will be to spend some time fleshing out the data model (FOM) to provide equivalent function to a locally running AI Manager - so for example it is possible to launch from a carrier being run in a separate Federate. I also need to get the build changes sorted so this can be checked in, which has some external dependencies.
|url = http://sourceforge.net/p/flightgear/mailman/message/34725710/
|2= {{cite web
|title = <nowiki>[Flightgear-devel] HLA Update</nowiki>
  | url   = http://sourceforge.net/p/flightgear/mailman/message/34725710/
|author = Stuart Buchanan
  | title = <nowiki>[Flightgear-devel] HLA Update</nowiki>
|date = Dec 29th, 2015
  | author = <nowiki>Stuart Buchanan</nowiki>
}}''
  | date   = Dec 29th, 2015
  | added  = Dec 29th, 2015
  | script_version = 0.23
  }}
}}


Learn more at [[High-Level Architecture]]...
''Learn more at [[High-Level Architecture]] …''


=== New scenemodels and TerraSync hosting needed ===
=== Scenemodels and TerraSync host moved ===
{{Out of date}}
{{FGCquote
{{FGCquote
|1= New status: * Good news - The scenemodels database and web frontend is up and running on it's new (temporary) host at my home. - The terrasync SVN repository is up and running ot it's new (temporary) host at my home * Bad news - Scenemodels is not yet accesible at it's original URL scenemodels.flightgear.org - The reverse proxies/scenery cache servers still point to the original SVN server at Martin's host - The Scenery-Exporter does not run correctly, I am currently working on this. - The backup system is not yet working Next steps (in exactly that order) - get the exporter running - get the backup working - change the DNS Entries - Point the reverse proxies/scenery cache servers to the new URL
|1= New status: * Good news - The scenemodels database and web frontend is up and running on it's new (temporary) host at my home. - The terrasync SVN repository is up and running ot it's new (temporary) host at my home * Bad news - Scenemodels is not yet accesible at it's original URL scenemodels.flightgear.org - The reverse proxies/scenery cache servers still point to the original SVN server at Martin's host - The Scenery-Exporter does not run correctly, I am currently working on this. - The backup system is not yet working Next steps (in exactly that order) - get the exporter running - get the backup working - change the DNS Entries - Point the reverse proxies/scenery cache servers to the new URL
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/91267"

Navigation menu