Compositor: Difference between revisions

291 bytes added ,  30 November 2019
m
→‎How to enable the Compositor: https://forum.flightgear.org/viewtopic.php?f=47&t=36269&start=45#p357580
m (→‎How to enable the Compositor: https://forum.flightgear.org/viewtopic.php?f=47&t=36269&start=45#p357580)
Line 87: Line 87:


Currently the Compositor can only be enabled at compile time via the <code>-DENABLE_COMPOSITOR=ON</code> CMake flag in FlightGear. SimGear doesn't require any extra parameters. Once you have a binary with the Compositor enabled and you run it, you will be presented with the default rendering pipeline. At the time of writing, this is the low spec rendering pipeline. If you want to try the ALS pipeline, start FlightGear with the command line argument: <code>--compositor=Compositor/ALS/als</code>
Currently the Compositor can only be enabled at compile time via the <code>-DENABLE_COMPOSITOR=ON</code> CMake flag in FlightGear. SimGear doesn't require any extra parameters. Once you have a binary with the Compositor enabled and you run it, you will be presented with the default rendering pipeline. At the time of writing, this is the low spec rendering pipeline. If you want to try the ALS pipeline, start FlightGear with the command line argument: <code>--compositor=Compositor/ALS/als</code>
== Good to know ==
* shadows are only supported on the ALS pipeline <ref>https://forum.flightgear.org/viewtopic.php?f=47&t=36269&start=60#p357586</ref>
* Transparency on trees require MSAA (anti-aliasing) <ref>https://forum.flightgear.org/viewtopic.php?f=47&t=36269&start=45#p357580</ref>


== Notes for aircraft developers ==
== Notes for aircraft developers ==