<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Tim,</div><div><br></div><div>Thanks for your reply! I've just tried to remove the parent animation elements, however the COLLADA doesn't seem to be nested and this did not solve my problem. I had second look at a DAE that is working. The structure seems the same, I don't see any more nested elements compared to the other. A difference be<font class="Apple-style-span" face="Arial">tween the two is that COLLADA Max gives each animation node an ID attribute, where COLLADA Max NextGen doens't export it with an ID as attribute. I've manually added an id attribute, which seems to solve the problem for me:</font></div><div><font class="Apple-style-span" face="Arial"><br></font></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Arial"> <library_animations></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Arial"> <animation<b> id="one"</b>></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Arial"><br></font></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 11px/normal Monaco; "><font class="Apple-style-span" face="Arial"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 12px;">I've also had a quick look on how this could be solved by the papervision code, but I haven't nailed it down yet. Maybe this gives you a clue where to solve this? Or is it a specification of the COLLADA file that animations need to have an id attribute? In that case the people at Feeling Software should try to fix this in their next release.</span></font></font></div></div><div><br></div><div>Paul</div><br><div><div>On May 1, 2009, at 6:52 PM, Tim Knip wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Paul,<br><br>There's a bug in current DAE class preventing nested <animation><br>elements to get parsed correctly.<br>Working in it.<br><br>In meantime you could try the 'old' MAX exporter, or manually change<br>the COLLADA file (rip out the 'parent' animation elements)<br><br>Tim<br><br>2009/5/1 Paul Tondeur <<a href="mailto:paul@paultondeur.nl">paul@paultondeur.nl</a>>:<br><blockquote type="cite">Hi all,<br></blockquote><blockquote type="cite">Does anybody have experience with the new released COLLADA Max NextGen<br></blockquote><blockquote type="cite">exporter? It works fine for exporting models, until you want to export<br></blockquote><blockquote type="cite">animations. At least, that's as it seems right now.<br></blockquote><blockquote type="cite">When I load a model that was exported using the nextgen exporter, I get the<br></blockquote><blockquote type="cite">following error in flash:<br></blockquote><blockquote type="cite">[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term is<br></blockquote><blockquote type="cite">undefined and has no properties.<br></blockquote><blockquote type="cite">This is caused by the DAE class on line 657, where it is looping through all<br></blockquote><blockquote type="cite">the animation channels. Animation.channels equals to null.<br></blockquote><blockquote type="cite">When I export using the same model using the normal COLLADA Max exporter,<br></blockquote><blockquote type="cite">the error disappears. Using the COLLADA Max NextGen exporter is essential<br></blockquote><blockquote type="cite">for 3ds Max 2010 users, as the older exporter doesn't work for this new<br></blockquote><blockquote type="cite">version of Max.<br></blockquote><blockquote type="cite">Both COLLADA files have information in the XML, regarding animation. I'm not<br></blockquote><blockquote type="cite">a COLLADA expert, but I can imagine that if I edit the nextgen exported file<br></blockquote><blockquote type="cite">manually, I could make this work. Has anybody done this before?<br></blockquote><blockquote type="cite">Thanks in advance,<br></blockquote><blockquote type="cite">Paul<br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">Papervision3D mailing list<br></blockquote><blockquote type="cite"><a href="mailto:Papervision3D@osflash.org">Papervision3D@osflash.org</a><br></blockquote><blockquote type="cite"><a href="http://osflash.org/mailman/listinfo/papervision3d_osflash.org">http://osflash.org/mailman/listinfo/papervision3d_osflash.org</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br>_______________________________________________<br>Papervision3D mailing list<br><a href="mailto:Papervision3D@osflash.org">Papervision3D@osflash.org</a><br>http://osflash.org/mailman/listinfo/papervision3d_osflash.org<br></div></blockquote></div><br></body></html>