Hi Lauri, > > Hi all. > > > 3. define an XML format for describing the two possible rendering > > pipelines (the current and new). The format will introduce > > optional elements (such as shadows, ambient occlusion, glow). > > I want to point out my work on my "newcameras" branch: > https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras > which > allows user to define the rendering pipeline in preferences.xml. It > does not (yet?) have everything Rembrandt's pipeline needs, but most > likely is easily enhanced to support those things. > > Basically this version adds 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. > > I wish this work could be extended (or maybe even I can extend it ;) > to handle the Rembrandt camera system. This will not solve all > problems in the merge, but some of them.
I would like to extend the format to avoid duplicating the stages when you have more than one viewport. What I see is to specify 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 Regards, -Fred ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel