FlightGear Headless: Difference between revisions

Jump to navigation Jump to search
m
mNo edit summary
Line 2: Line 2:


{{Portability Navbar}}
{{Portability Navbar}}
'''Headless mode''' is still something that could be improved; currently it seems limited to <code>--disable-gui</code>  which is more about disabling user
input (message boxes etc) that may block unattended activities. SimGear
can be configured to be built in headless mode which probably isn't what
you want.
Currently there are parts of FG that require the scenery to be loaded
(for the ground elevation) - the easiest fix for this is probably to
either not have any scenery or to default to a position in the ocean (we
always used to use lat -25, lon-25) and/or use a small window.<ref>https://sourceforge.net/p/flightgear/mailman/message/37344888/</<ref>
A set of different headless modes was always in Edward's TODO list for the
test suite infrastructure, however he ran out of time for now. 
Anyoneelse can add it though.  Edward's idea was to build it up in steps, having
unit as well as system/functional tests for each.  Firstly running the
fg main loop in the absence of a scene graph and with a minimal set of
subsystems present, then with a basic scene graph (no scenery, testing
with basic geometric objects, and a basic 'sphere world'), and then
rendering frames to bitmaps on disk or in memory for per-pixel checks.
Scenery loading would be absent from all these basic tests, simply due
to not having access to it - the test suite would require very basic
and tiny test-suite specific scenery tiles for efficient testing.
Edward would recommend following such a route if more advanced 'headless'
modes are desired, as that would help with long-term stability of
these modes, and bring in a major piece of infrastructure into the
test suite that the project could really benefit from!<ref>https://sourceforge.net/p/flightgear/mailman/message/37345003/</ref>


= FlightGear Headless =
= FlightGear Headless =

Navigation menu