Hello Carsten, >> I'm not sure if OpenSG 2.0 is also affected. > > yes, it has a similar problem, but the TextureChunk is deprecated there > and replaced with TextureObjChunk and TextureEnvChunk. Anyways I'll > change the SFImage to be a child pointer field, then it should handle > this automagically. > What happens to 'osg' files written with OpenSG 1.8 and later on reading them back with OpenSG 2.0 with regard to the TextureChunk objects burried in the model?
I thougth that the 'osg' file format is stable. Isn't it? Are there other classes I can't expect to be usable in the transition. Best regards, Johannes ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Opensg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-users
