20,741
edits
Compositor: Difference between revisions
m
→Developer Discussion
| Line 101: | Line 101: | ||
definitely a good idea to separate new Effects from the old ones for | definitely a good idea to separate new Effects from the old ones for | ||
now.<ref>https://sourceforge.net/p/flightgear/mailman/message/36657975/</ref> | now.<ref>https://sourceforge.net/p/flightgear/mailman/message/36657975/</ref> | ||
There is a new scheme that Fernando is currently working on whereby we | |||
have a definition of the effects/shaders within the pipeline keep them | |||
within the pipeline folder structure; together with defining what the | |||
shader does (if applicable) so it can be controlled by a future UI. | |||
There is a very rough draft design doc for this available here | |||
http://www.zaretto.com/sites/zaretto.com/files/compositor-effects-registry.pdf <ref>https://sourceforge.net/p/flightgear/mailman/message/36606242/</ref> | |||
=== Availability === | === Availability === | ||
| Line 130: | Line 138: | ||
stuff that sets up the pipeline, remove the Rembrandt code and generally | stuff that sets up the pipeline, remove the Rembrandt code and generally | ||
have a good tidy up. | have a good tidy up. | ||
Tim Moore suggested to dump the legacy renderer and going with | Tim Moore suggested to dump the legacy renderer and going with | ||