I have a problem updating textures. I have a STL map where I keep TextureChunkPtr's to several textures, which I sometimes need to update. So, when I update a texture, I write it in the map. After that, a routine will update textures, rewriting chunk materials and using the textures from the previously mencioned map.  Without clustering everything works just fine, but when I run it in the cluster, as soon as the texture suffers the first update, it looks as if there was no texture at all. I was having an warning on the server side (something like "WARNING: can't find container id 123456"). I managed to track this id down to the image used in texture creation, and removed this warning through a Thread::getCurrentChangeList()->addCreated(pImage.getContainerId()). Now I don't get the warning but the texture-less look remains...
anybody has any idea about this?!

Bruno Marques

Reply via email to