Compositor: Difference between revisions

Jump to navigation Jump to search
5 bytes removed ,  17 November 2020
no edit summary
No edit summary
No edit summary
Line 22: Line 22:
{{See also|Supporting multiple renderers|Howto:Canvas View Camera Element}}
{{See also|Supporting multiple renderers|Howto:Canvas View Camera Element}}


First discussed in 03/2012 during the early [[Rembrandt]] days, Zan (Lauri Peltonen) came up with a set of patches demonstrating how to create an XML-configurable rendering pipeline.
First discussed in 03/2012 during the early [[Rembrandt]] days, Zan (Lauri Peltonen) came up with a set of patches demonstrating how to create an XML-configurable rendering pipeline. Back then, this work was considered to look pretty promising <ref>{{cite web
 
Back then, this work was considered to look pretty promising <ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28946515/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28946515/  
   |title  =  <nowiki> Re: [Flightgear-devel] [Rembrandt] the plan </nowiki>  
   |title  =  <nowiki> Re: [Flightgear-devel] [Rembrandt] the plan </nowiki>  
Line 33: Line 31:
   }}</ref> and at the time plans were discussed to unify this with the ongoing Rembrandt implementation (no longer maintained).
   }}</ref> and at the time plans were discussed to unify this with the ongoing Rembrandt implementation (no longer maintained).


Adopting Zan's approach would have meant that efforts like [[Rembrandt]] (deferred rendering) could have been implemented without requiring C++ space modifications, i.e. purely in [[Base package]] space.
Adopting Zan's approach would have meant that efforts like [[Rembrandt]] (deferred rendering) could have been implemented without requiring C++ space modifications, i.e. purely in [[Base package]] space. Rembrandt's developer (FredB) suggested to extend the format to avoid duplicating the stages when you have more than one viewport, i.e.  specifying a pipeline as a template, with conditions like in effects, and have the current camera layout refer the pipeline that would be duplicated, resized and positioned for each declared viewport <ref>{{cite web
 
Rembrandt's developer (FredB) suggested to extend the format to avoid duplicating the stages when you have more than one viewport, i.e.  specifying a pipeline as a template, with conditions like in effects, and have the current camera layout refer the pipeline that would be duplicated, resized and positioned for each declared viewport <ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28944773/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28944773/  
   |title  =  <nowiki> Re: [Flightgear-devel] [Rembrandt] the plan </nowiki>  
   |title  =  <nowiki> Re: [Flightgear-devel] [Rembrandt] the plan </nowiki>  
Line 44: Line 40:
   }}</ref>
   }}</ref>


Zan's original patches can still be found in his newcameras branches which allow the user to define the rendering pipeline in preferences.xml: {{gitorious source|proj=fg|repo=zans-flightgear|branch=newcameras|text=FlightGear}}, {{gitorious source|proj=fg|repo=zans-simgear|branch=newcameras|text=SimGear}}.
Zan's original patches can still be found in his newcameras branches which allow the user to define the rendering pipeline in preferences.xml: {{gitorious source|proj=fg|repo=zans-flightgear|branch=newcameras|text=FlightGear}}, {{gitorious source|proj=fg|repo=zans-simgear|branch=newcameras|text=SimGear}}. At that point, it didn't have everything Rembrandt's pipeline needs, but most likely could be easily enhanced to support those things. Basically, the original version added support for multiple camera passes, texture targets, texture formats, passing textures from one pass to another etc, while preserving the standard rendering line if user wants that. <ref>{{cite web
 
At that point, it didn't have everything Rembrandt's pipeline needs, but most likely could be easily enhanced to support those things.  
 
Basically, the original version added support for multiple camera passes, texture targets, texture formats, passing textures from one pass to another etc, while preserving the standard rendering line if user wants that. <ref>{{cite web
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28944733/  
   |url    =  https://sourceforge.net/p/flightgear/mailman/message/28944733/  
   |title  =  <nowiki> [Flightgear-devel] [Rembrandt] the plan </nowiki>  
   |title  =  <nowiki> [Flightgear-devel] [Rembrandt] the plan </nowiki>  
343

edits

Navigation menu