From Dietmar Funck, "I've noticed an issue when writing arrays of type Vec2D and Vec3D to a .osgb file. A number is written to the output stream to identify the array type. In case of Vec2D and Vec3D arrays Vec4D is written as array type - I guess this is a copy and paste mistake. Writing the correct array types fixes the issue - in my case it fixes writing and afterwards reading geometry instances."
From Dietmar Funck, "I've noticed an issue when writing arrays of type Vec2D and Vec3D to a .osgb file. A number is written to the output stream to identify the array type. In case of Vec2D and Vec3D arrays Vec4D is written as array type - I guess this is a copy and paste mistake.
Writing the correct array types fixes the issue - in my case it fixes writing and afterwards reading geometry instances."



stmh/osg,koshman86/osg,artoolkit/osg,stmh/osg,ntoand/osg,XiaoCC/osg,omega-hub/osg,ghub/osg,ghub/osg,omega-hub/osg,koshman86/osg,stmh/osg,omega-hub/osg,XiaoCC/osg,artoolkit/osg,XiaoCC/osg,ntoand/osg,XiaoCC/osg,omega-hub/osg,ntoand/osg,koshman86/osg,XiaoCC/osg,stmh/osg,stmh/osg,ghub/osg,ntoand/osg,artoolkit/osg,koshman86/osg,artoolkit/osg,ghub/osg