20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
→Image Sharing
m (→DatabasePager) |
|||
| Line 196: | Line 196: | ||
* ImageStream is updated by a background thread. The xine-lib and QuickTime plugins both subclass from ImageStream and OpenThreads::Thread to provide a class thatautomatically runs updates on itself - this thread updates the image data on the ImageStream and then calls dirty to tell the rendering thread that it needs to download the data to any associated texture.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11405.html</ref> | * ImageStream is updated by a background thread. The xine-lib and QuickTime plugins both subclass from ImageStream and OpenThreads::Thread to provide a class thatautomatically runs updates on itself - this thread updates the image data on the ImageStream and then calls dirty to tell the rendering thread that it needs to download the data to any associated texture.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11405.html</ref> | ||
* It's better to update the data stored in the Image directly and call dirty, or to allocate the image memory separately and disable the deletion of the data on the image so the osg::Image(Stream) never calls delete on the data.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11440.html</ref> | * It's better to update the data stored in the Image directly and call dirty, or to allocate the image memory separately and disable the deletion of the data on the image so the osg::Image(Stream) never calls delete on the data.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg11440.html</ref> | ||
=== Multiple Viewers === | |||
you will be able to do is use two separate Viewer's. You are | |||
likely to want to run two threads for each of the viewers frame loops | |||
as well. To get the render to image result to the second viewer all | |||
you need to do is assign the same osg::Image to the first viewer's | |||
Camera for it to copy to, and then attach the same osg::Image to a | |||
texture in the scene of the second viewer. The OSG should | |||
automatically do the glReadPixels to the image data, dirty the Image, | |||
and then automatically the texture will update in the second viewer. | |||
You could potentially optimize things by using an PBO but the off the | |||
shelf osg::PixelBufferObject isn't suitable for read in this way so | |||
you'll need to roll you own support for this.<ref>https://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg18308.html</ref> | |||
== Motivation == | == Motivation == | ||