Hi Robert,
Yes. "copy data and release GL buffer object" mechanism cannot be used
as it is. Unfortunately (fortunately), I'm in holidays for 3 weeks. I
can make the related corrections but I will not be able to test them.
I'll be back the 7 jan. Hope the world doesn't end during my holidays ...
By
Lionel
On 14/12/2012 15:07, Robert Osfield wrote:
HI Lionel,
On 14 December 2012 10:48, Lionel Lagarde <lionel.laga...@oktal-se.fr
<mailto:lionel.laga...@oktal-se.fr>> wrote:
Hi Robert,
osg::Image inherits from osg::BufferData. The BufferData cannot be
unreferenced separately.
Indeed, I knew this but didn't make the connection! :-)
The behavior you describe is the what happen if "unref image data
after apply" is true and "copy data and release GL buffer object"
is false (like in my submission).
Yes. I'm starting to think the BufferData level "copy data and
release GL buffer object" is misguided and broken in it's current form
and might be better off just removing it completely or doing a proper
rethink and refactor of the support for this feature.
Multi-context doesn't work if "unref image data after apply" is
true because the image is referenced only once by the texture and
not one per context.
There is support in osg::Texture for making sure all the contexts have
applied the image before the image gets unref'd.
Robert.
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
