Hi Torben, On Tue, May 18, 2010 at 11:28 AM, Torben Dannhauer <z...@saguaro-fight-club.de> wrote:
> This sounds interesting! Maybe this is a better solution than my own simple > implementation based on osgDB::Serializer / boost::asio. Maybe there is a potential to integrate the two projects. osgScaleViewer does not yet distribute the scene graph itself, so using osgDB::Serializer might be a first step. It's not clear to me how (or if) you handle scene graph updates at run-time. The White Paper gives a few pointers on how data distribution can be done using Equalizer. We've done stuff like this with another SG already -- it's just a bunch of work to write the serializers. > I have some questions about how it works: > a ) Is the output a single image which is constructed from all nodes image > parts, or is it possible to use it to project large images with very high > resolution to screen, using each node rendering a defined viewport of the > screen? (just using your datatransfer and swap control functions for cluster > control) I'm not sure I understand the question. You can configure multiple output channels, planar or non-planar, at arbitrary resolutions. The rendering for these channels can be generated by the channels themselves (standard multi-display rendering) or using additional 'source channels', which may have a lower resolution (scalable rendering). > b) Is it possible to distort with eq to project on curved screens? Something > like rtt -> distort with shader -> project? Yes, although this is not implemented in Equalizer itself. There are a couple of hooks to let you know when each output channel has the result in its frame buffer. Cheers, Stefan. -- http://www.eyescale.ch http://www.equalizergraphics.com http://www.linkedin.com/in/eilemann _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
