Horde3D
http://horde3d.org/forums/

blender 25, collada exporting [SOLVED]
http://horde3d.org/forums/viewtopic.php?f=2&t=1148		 Page 1 of 1
Author:  PuG [ 15.04.2010, 16:14 ]
Post subject:  blender 25, collada exporting [SOLVED]
Hi, im running the latest blender build from SVN with the collada exporter, when shunting over to horde sometimes im finding no mesh name is being (in the .scene.xml file) assigned after converting to geo:

Code:
<Mesh name=""


If the I export two objects from one blender scene then the second object has "_2" defined as a mesh name, which does then work aslong as I remove the other object definition from the scene xml file (because it has no name).

The blender DAE file appears fine. Any suggestions?
Author:  Volker [ 15.04.2010, 19:14 ]
Post subject:  Re: blender 25, collada exporting
Can you provide the DAE file?
Author:  PuG [ 15.04.2010, 19:23 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
yes, sorry I had attached one but hadn't noticed the file extension notice. Ive renamed it to .txt

Just a simple cube.

Code:
Parsing dae asset 'scene.dae'...
Compiling model data...
Warning: Node with name '' already exists. Node was renamed to '_2'.


Okay seems to be caused by the fact collada file is missing the mesh "name" tag in the <node id= definition (thanks to Siavash for spotting this). All you need todo is copy the id and rename to "name".

Attachments:
scene.txt [6.8 KiB]
Downloaded 1026 times
Author:  Volker [ 16.04.2010, 14:24 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
Quote:
Okay seems to be caused by the fact collada file is missing the mesh "name" tag in the <node id= definition (thanks to Siavash for spotting this). All you need todo is copy the id and rename to "name".

Can you provide the original file, that caused the error. If this is not a bug in the blender exporter and supported by the collada standard, we should fix it in the converter.
Author:  PuG [ 16.04.2010, 14:40 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
the above thread has the file attached?

Im not sure if its specifically a horde fault, just blender isn't outputting a name to go along with the mesh ID. So our own converter all we've down is modified it so to use the id tag for both (id/name) which works fine.

Blender 25 output:
<node id="mymesh">

and horde is looking for the name= tag.
<node id="mymesh" name="mymesh">
Author:  Volker [ 16.04.2010, 15:21 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
The file above worked without any problems with the official SF trunk collada converter on my system.

Attachments:
scene.jpg
scene.jpg [ 216.77 KiB | Viewed 16679 times ]
Author:  PuG [ 16.04.2010, 15:26 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
interesting, see when I first tested initially it worked fine - it was only afterwards it started to complaining of failing to load resources. Well either way atleast theirs now a reference on the forums should anyone else have a similar problem.
Author:  Irdis [ 16.04.2010, 17:20 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
PuG wrote:
Hi, im running the latest blender build from SVN with the collada exporter, when shunting over to horde sometimes im finding no mesh name is being (in the .scene.xml file) assigned after converting to geo:

Code:
<Mesh name=""


If the I export two objects from one blender scene then the second object has "_2" defined as a mesh name, which does then work aslong as I remove the other object definition from the scene xml file (because it has no name).

The blender DAE file appears fine. Any suggestions?


I have the same problem (Max 2009, opencollada). It seems that the converter doesn't know how to handle groups. Judging by the debug, on the convertmodel stage converter tries to get id and name from the node, that is a group of objects (nodes). That node doesn't have neither id, nor name. For example, in my scene I have a group named "plintus_grp", that has 3 objects - Plintus_1, Plintus_2, Plintus3. Only the last one gets the correct name. The first object gets "" as a name, and the second one gets "_2".

My suggestion is to check, if the name of the node is empty, before checkNodeName( oNode ); If empty, than take the name from oNode.daeInstance. Just my opinion, though))
Author:  marciano [ 16.04.2010, 20:48 ]
Post subject:  Re: blender 25, collada exporting [SOLVED]
Irdis wrote:
I have the same problem (Max 2009, opencollada). It seems that the converter doesn't know how to handle groups. Judging by the debug, on the convertmodel stage converter tries to get id and name from the node, that is a group of objects (nodes). That node doesn't have neither id, nor name. For example, in my scene I have a group named "plintus_grp", that has 3 objects - Plintus_1, Plintus_2, Plintus3. Only the last one gets the correct name. The first object gets "" as a name, and the second one gets "_2".

Hmm, that should get fixed. Could you share a (minimal) dae test file that exhibits that behavior?
Page 1 of 1 All times are UTC + 1 hour
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/