Compositor: Difference between revisions

No change in size ,  2 January 2019
m
shuffle around to status paragraph
mNo edit summary
m (shuffle around to status paragraph)
Line 63: Line 63:
== Status ==
== Status ==
'''01/2019'''
'''01/2019'''
The Compositor is in an usable state right now: it works but there are no effects or pipelines developed for it. There are also some bugs and features that don't work as expected because of some hardcoded assumptions in the FlightGear Viewer code.


The corresponding set of patches (topic branches) were put up for review in 08/2018 to discuss the underlying approach and hopefully get this merged in 2019. <ref>https://sourceforge.net/p/flightgear/mailman/message/36355833/</ref>
The corresponding set of patches (topic branches) were put up for review in 08/2018 to discuss the underlying approach and hopefully get this merged in 2019. <ref>https://sourceforge.net/p/flightgear/mailman/message/36355833/</ref>
Line 74: Line 76:
* Flexible, expandable and compatible with modern graphics.
* Flexible, expandable and compatible with modern graphics.
* It doesn't increase the hardware requirements, it expands the hardware range FG can run on. People with integrated GPUs (Intel HD etc) can run a Compositor with a single pass that renders directly to the screen like before, while people with more powerful cards can run a Compositor that implements deferred rendering, for example.
* It doesn't increase the hardware requirements, it expands the hardware range FG can run on. People with integrated GPUs (Intel HD etc) can run a Compositor with a single pass that renders directly to the screen like before, while people with more powerful cards can run a Compositor that implements deferred rendering, for example.
The Compositor is in an usable state right now: it works but there are no effects or pipelines developed for it. There are also some bugs and features that don't work as expected because of some hardcoded assumptions in the FlightGear Viewer code.


== Elements ==
== Elements ==