Template:Affected by Compositor
IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.2 (6/2020). Please see: Compositor for further information
You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum . talk page. |
Goal
This template can be used on top of pages related to projects that will be affected or obsoleted by the development of the new Compositor, FlightGear's fully XML/property-configurable rendering framework.
Adding this template to a page in the article namespace will automatically add Category:Affected by Compositor to that page.
Usage
Put this template on top of the page.
{{Affected by Compositor|alternate page}}
- alternate page
- Optional alternate Compositor related page pointed to for further information (such as e.g. MapStructure or NavDisplay, defaults to Compositor.
Examples
Using no parameters
{{Affected by Compositor}}
IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.2 (6/2020). Please see: Compositor for further information
You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum . talk page. |
Linking to an alternate page
{{Affected by Compositor|Foo}}
IMPORTANT: Some, and possibly most, of the features/ideas discussed below are likely to be affected, and possibly even deprecated, by the ongoing work on providing a property tree-configurable rendering pipeline accessible via XML using the new Compositor system available since FlightGear 2020.2 (6/2020). Please see: Foo for further information
You are advised not to start working on anything directly related to this without first discussing/coordinating your ideas with other FlightGear contributors using the FlightGear developers mailing list or the Effects & Shaders subforum . talk page. |