Hi, On Thu, 2013-09-26 at 12:22 +0200, Christoph Fünfzig wrote: > Hi Gerrit, > > On 26.09.2013 08:10, Gerrit Voß wrote: > > Hi, > > > > On Wed, 2013-09-25 at 13:30 +0200, "Christoph Fünfzig" wrote: > >> Hi, > >> > >> thanks a lot for looking into it. > >> Just a question on the side: > >> Is it correct Collada to have ids, which start with an underscore, > >> e.g., "<visual_scene id="_entity_balken01" name="_entity_balken01">" ? > >> Because in the combination > >> "<scene> > >> <instance_visual_scene > >> url="#_entity_balken01"></instance_visual_scene> > >> </scene>" > >> it does not find the scene root node .. > > to me the reason looks more like a name clash as the root node in > > your scene has the same id : > > > > <node name="_entity_balken01" id="_entity_balken01" > > sid="_entity_balken01"> > > > > Using _entity_balken01 currently crashes so I look into this, but if I > > use _x_entity_balken01 instead it loads the scene as expected. > > > > > yes, "node id" and "visual_scene id" are the same in this case. > <visual_scene id="_entity_balken01" name="_entity_balken01"> > <node name="_entity_balken01" id="_entity_balken01" ..> > > It came to me like this, as the result of the DAE/FBX exporter from > exporting a node named "_entity_balken01", > into a file named "_entity_balken01.dae" ;-) > So really a special case, but to please Maya ..
hmm, does the scene name depend on the file name or the node name ?. I'll have to check if one can resolve it by doing local library searches if the internal collada lookup fails. In your case it finds the node first and fails on the following downcast to scene. For the general loading problem I committed a fixed. Now the loader checks for invalid indices (have to check all for primitive types though) and removes any index with -1 in it. As this leaves you without any texture coordinates I added one option to the collada loader (tryMergeInvalidIndices). In this case the loader checks if it can merge multiple invalid indices into a valid one if the -1 blocks do not overlap, e.g. for something like: index1: 1 2 3 4 -1 -1 -1 5 6 7 8 index2: -1 -1 -1 -1 11 12 13 -1 -1 -1 -1 the loader will merge: index1: 1 2 3 4 11 12 13 5 6 7 8 index2: reuse index1 As this is the case for your file you at least are able to get a geometry with texture coordinates out of the loader. kind regards gerrit ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
