Re: [osg-users] StateSet and Text, state sets may be shared inadvertently

On 05/01/12 18:25, Robert Osfield wrote: Hi Juan, osgText::Text is a special case in that the way the text is rendered is using textures and to for best performance and memory usage you need to share these textures, and also share the rest of the text state as well. OK, I see, I didn't think of

Re: [osg-users] StateSet and Text, state sets may be shared inadvertently

Hi Juan, osgText::Text is a special case in that the way the text is rendered is using textures and to for best performance and memory usage you need to share these textures, and also share the rest of the text state as well. If you want to decorate the Text with your custom StateSet than it's be

[osg-users] StateSet and Text, state sets may be shared inadvertently

Dear all, Trying to use different StateSet with different osgText::Text objects it happens that all text objects transparently may share the same StateSet depending on how the state sets are created. Image that we have two text objects t1 and t2, then the following calling sequences behave as f