20,741
edits
FlightGear Headless: Difference between revisions
→FlightGear Headless
| Line 17: | Line 17: | ||
Another option is to make FGRenderer the optional piece - James Turner started doing some work this direction in December last year. I.e without FGRenderer there is no rendering at all, and hence no scene-graph.<ref>{{cite web | Another option is to make FGRenderer the optional piece - James Turner started doing some work this direction in December last year. I.e without FGRenderer there is no rendering at all, and hence no scene-graph.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35064249/ | |||
|title = <nowiki>Re: [Flightgear-devel] Integration of the new subsystem design and | |||
the OSG scene graph management.</nowiki> | |||
|author = <nowiki>James Turner</nowiki> | |||
|date = May 4th, 2016 | |||
|added = May 4th, 2016 | |||
|script_version = 0.31 | |||
}} | |||
</ref> | |||
we should really do with with subclassing, making an SGDisplaySubsystem with: | |||
* virtual void initVisuals(); | |||
* virtual void updateVisuals(); | |||
* virtual void shutdownVisuals(); | |||
With the expectation that the manager layer (FGScenery or FGRenderer) calls initVisuals / updateVisuals / shutdownVisuals if it exists. This also forces the implementation of each subsystem to distinguish simulation pieces (modifies properties) from display pieces (reads but hopefully does not modify properties, modifies OSG state) <ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35064249/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35064249/ | ||
|title = <nowiki>Re: [Flightgear-devel] Integration of the new subsystem design and | |title = <nowiki>Re: [Flightgear-devel] Integration of the new subsystem design and | ||