Hi,

This patch address an issue (not a bug) that I have encountered in the
exported dae files. In a nutshell, the *<library_images>* node is empty and
all the images are embedded in their corresponding <profile_COMMON> under
the <library_effects> node. Here it is how a generated dae file looks like:


    <library_effects>
        <effect id="material_18_effect">
            <profile_COMMON>
                <*image *id="material_18_effect-image" height="0" width="0">
                    <init_from>Image_18.png</init_from>
                </image>
            .....
        </effect>
     </library_effects>

The <library_images> node is not even present in the exported dae file and
if present, it would be at the same level as library_effects.

The exported files validate correctly the spec, and this is not the issue,
but it is quite common to add the images to the <library_images> node.

As an example, you can use the model duck.dae [1] which defines the image
in <library_images>. You might want to see the differences in the exported
dae file after re-converting it with osgconv :
    osgconv duck.dae duck2.dae


The attached patch just moves the images to <library_images>. Although it
has been created using the 3.4 branch, it should be valid for the trunk.


Best regards,

[1] duck.dae sample model:
https://github.com/supereggbert/GLGE/tree/master/examples/collada
-- 
Aitor Moreno
   aitormoreno [@] gmail.com

Attachment: dae_20150924_LibraryImages.patch
Description: Binary data

_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to