Hi Ryan, On 9. Aug 2013, at 10:38, "Ryan [via Software]" <[email protected]> wrote:
> One reason I want to get such information is that I desire to know the total > size of the rendered scene (2D wall), so that I can tune the viewport of each > rendering window dynamically. In my case, due to some performance > consideration, I prefer to manipulate camera as well as frustum manually, so > that I can improve program's performance by processing some cull operation > and so on. This information is available in the application thread from the segments. What 'size' do you need? Real-world meters? Pixels? Frustum corners? The 'tune the viewport of each rendering window dynamically' sounds like the DFR Equalizer? > The other reason is that I want to send some message such as mouse move/key > press to all of the rendering nodes whenever necessary, I don't think it's a > good/sufficient way to send such information through frame data just like the > example eqPly illustrated. Why not? If you send it to the nodes directly, it will not be frame-synchronized. HTH, Stefan. signature.asc (210 bytes) <http://software.1713.n2.nabble.com/attachment/7583837/0/signature.asc> -- View this message in context: http://software.1713.n2.nabble.com/runtime-problems-in-multi-nodes-rendering-tp7583773p7583837.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
