Re: [osg-submissions] Multi-threaded usage of textures

Hi Robert, I can submit a fix then. Thanks for the quick reply. Cheers, Anish robertosfield wrote: > Hi Anish, > > > > I think you are correct, the way to handle concurrrent reading/updates of an > osg::Image is to take a local copy of the osg::Image::getModifedCount() prior > to reading

Re: [osg-submissions] Multi-threaded usage of textures

Hi Anish, I think you are correct, the way to handle concurrrent reading/updates of an osg::Image is to take a local copy of the osg::Image::getModifedCount() prior to reading from the image and then use this value. This would still have the danger of the image data being updated at the same

[osg-submissions] Multi-threaded usage of textures

Hi, While modifying texture-atlases in DBPager threads we noticed an issue of thread-synchronization. Code like the snippet below (From Texture2D.cpp): else if (_image.valid() && getModifiedCount(contextID) != _image->getModifiedCount()) {

Re: [osg-submissions] Multi-threaded usage of textures

This could apply to a problem I have been having in my own application. Please post your fix once you have it. On Oct 17, 2017 5:01 AM, "Anish Thomas" wrote: > Hi Robert, > > I can submit a fix then. > Thanks for the quick reply. > > Cheers, > Anish > > > robertosfield