FlightGear Headless: Difference between revisions

Jump to navigation Jump to search
Line 4: Line 4:


= FlightGear Headless =
= FlightGear Headless =
== Motivation ==
{{FGCquote
|1= what remains true is the that overwhelming majority of the FlightGear main loop time is spent rendering the graphics.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34811441/
  | title  = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API</nowiki>
  | author = <nowiki>Curtis Olson</nowiki>
  | date  = Feb 1st, 2016
  }}
}}
{{FGCquote
|1= That's not to say there aren't some bottlenecks in our rendering pipeline that need to eventually be dealt with, but these are more tied to our use of properties and nasal in graphics system call backs (much of this we inherited from the original design which was build around plib's SG (scene graph) library.)
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34811441/
  | title  = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API</nowiki>
  | author = <nowiki>Curtis Olson</nowiki>
  | date  = Feb 1st, 2016
  }}
}}
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|450px|thumb|Screen shot showing a the performance monitor in a patched version of FlightGear 3.2  where subsystem initialization is made better configurable and increasingly optional by allowing subsystems to be explicitly disabled/enabled during startup. Decoupling internal subsystem dependencies means that we can more easily provide support for [[FlightGear Benchmark|benchmarking]], but also [[FlightGear Headless|headless]] regression testing - and eventually, also a standalone [[FGCanvas]] startup mode.]]
[[File:Patching-fg-3.2-to-make-more-subsystems-optional.png|450px|thumb|Screen shot showing a the performance monitor in a patched version of FlightGear 3.2  where subsystem initialization is made better configurable and increasingly optional by allowing subsystems to be explicitly disabled/enabled during startup. Decoupling internal subsystem dependencies means that we can more easily provide support for [[FlightGear Benchmark|benchmarking]], but also [[FlightGear Headless|headless]] regression testing - and eventually, also a standalone [[FGCanvas]] startup mode.]]


Navigation menu