COLLADA Max NextGen - animation problems

[Paul Tondeur]

Hi all,

Does anybody have experience with the new released COLLADA Max NextGen
exporter? It works fine for exporting models, until you want to export
animations. At least, that's as it seems right now.

When I load a model that was exported using the nextgen exporter, I
get the following error in flash:
[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term
is undefined and has no properties.
This is caused by the DAE class on line 657, where it is looping
through all the animation channels. Animation.channels equals to null.

When I export using the same model using the normal COLLADA Max
exporter, the error disappears. Using the COLLADA Max NextGen exporter
is essential for 3ds Max 2010 users, as the older exporter doesn't
work for this new version of Max.

Both COLLADA files have information in the XML, regarding animation.
I'm not a COLLADA expert, but I can imagine that if I edit the nextgen
exported file manually, I could make this work. Has anybody done this
before?

Thanks in advance,

Paul

[Tim Knip]

Hi Paul,

There's a bug in current DAE class preventing nested <animation>
elements to get parsed correctly.
Working in it.

In meantime you could try the 'old' MAX exporter, or manually change
the COLLADA file (rip out the 'parent' animation elements)

Tim

Post by Paul Tondeur
Hi all,
Does anybody have experience with the new released COLLADA Max NextGen
exporter? It works fine for exporting models, until you want to export
animations. At least, that's as it seems right now.
When I load a model that was exported using the nextgen exporter, I get the
[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term is
undefined and has no properties.
This is caused by the DAE class on line 657, where it is looping through all
the animation channels. Animation.channels equals to null.
When I export using the same model using the normal COLLADA Max exporter,
the error disappears. Using the COLLADA Max NextGen exporter is essential
for 3ds Max 2010 users, as the older exporter doesn't work for this new
version of Max.
Both COLLADA files have information in the XML, regarding animation. I'm not
a COLLADA expert, but I can imagine that if I edit the nextgen exported file
manually, I could make this work. Has anybody done this before?
Thanks in advance,
Paul
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org

[Paul Tondeur]

Hi Tim,

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 between 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:

<library_animations>
<animation id="one">

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.

Paul

Post by Tim Knip
Hi Paul,
There's a bug in current DAE class preventing nested <animation>
elements to get parsed correctly.
Working in it.
In meantime you could try the 'old' MAX exporter, or manually change
the COLLADA file (rip out the 'parent' animation elements)
Tim

Post by Paul Tondeur
Hi all,
Does anybody have experience with the new released COLLADA Max NextGen
exporter? It works fine for exporting models, until you want to export
animations. At least, that's as it seems right now.
When I load a model that was exported using the nextgen exporter, I get the
[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term is
undefined and has no properties.
This is caused by the DAE class on line 657, where it is looping through all
the animation channels. Animation.channels equals to null.
When I export using the same model using the normal COLLADA Max exporter,
the error disappears. Using the COLLADA Max NextGen exporter is
essential
for 3ds Max 2010 users, as the older exporter doesn't work for this new
version of Max.
Both COLLADA files have information in the XML, regarding
animation. I'm not
a COLLADA expert, but I can imagine that if I edit the nextgen exported file
manually, I could make this work. Has anybody done this before?
Thanks in advance,
Paul
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org

_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org

[Tim Knip]

Hi Paul,

Ehehe: yeah, crash on the lacking ID is a bug also :-S
Forgot about that on, thanks for reminding me.

Think Cinema4D does the nested animation elements.

Keep an eye on http://code.google.com/p/papervision3d/source/list

Fix should be there in 1 to 2 weeks, depending on my work schedule.

Btw: http://www.paultondeur.com/2008/03/09/drawing-a-cubic-bezier-curve-using-actionscript-3/
Did you ever solve the quadratic to normal flash curveTo thing?

Tim

Post by Paul Tondeur
Hi Tim,
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 between 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
  <library_animations>
    <animation id="one">
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.
Paul
Hi Paul,
There's a bug in current DAE class preventing nested <animation>
elements to get parsed correctly.
Working in it.
In meantime you could try the 'old' MAX exporter, or manually change
the COLLADA file (rip out the 'parent' animation elements)
Tim
Hi all,
Does anybody have experience with the new released COLLADA Max NextGen
exporter? It works fine for exporting models, until you want to export
animations. At least, that's as it seems right now.
When I load a model that was exported using the nextgen exporter, I get the
[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term is
undefined and has no properties.
This is caused by the DAE class on line 657, where it is looping through all
the animation channels. Animation.channels equals to null.
When I export using the same model using the normal COLLADA Max exporter,
the error disappears. Using the COLLADA Max NextGen exporter is essential
for 3ds Max 2010 users, as the older exporter doesn't work for this new
version of Max.
Both COLLADA files have information in the XML, regarding animation. I'm not
a COLLADA expert, but I can imagine that if I edit the nextgen exported file
manually, I could make this work. Has anybody done this before?
Thanks in advance,
Paul
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org

[Paul Tondeur]

Hi Tim,

Awesome to hear you have plans to update it within a few weeks! That
really helps! I'll keep an eye on SVN.

After my post about cubic beziers about a year ago I haven't looked
anymore at making this work with curveTo. However, I've received quite
a few mails about this. I'll send you some of it off-list :-)

Paul

Post by Tim Knip
Hi Paul,
Ehehe: yeah, crash on the lacking ID is a bug also :-S
Forgot about that on, thanks for reminding me.
Think Cinema4D does the nested animation elements.
Keep an eye on http://code.google.com/p/papervision3d/source/list
Fix should be there in 1 to 2 weeks, depending on my work schedule.
Btw: http://www.paultondeur.com/2008/03/09/drawing-a-cubic-bezier-curve-using-actionscript-3/
Did you ever solve the quadratic to normal flash curveTo thing?
Tim

Post by Paul Tondeur
Hi Tim,
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 between 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
<library_animations>
<animation id="one">
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.
Paul
Hi Paul,
There's a bug in current DAE class preventing nested <animation>
elements to get parsed correctly.
Working in it.
In meantime you could try the 'old' MAX exporter, or manually change
the COLLADA file (rip out the 'parent' animation elements)
Tim
Hi all,
Does anybody have experience with the new released COLLADA Max NextGen
exporter? It works fine for exporting models, until you want to export
animations. At least, that's as it seems right now.
When I load a model that was exported using the nextgen exporter, I get the
[ERROR] DaeDocument#readNextAnimation : TypeError: Error #1010: A term is
undefined and has no properties.
This is caused by the DAE class on line 657, where it is looping through all
the animation channels. Animation.channels equals to null.
When I export using the same model using the normal COLLADA Max exporter,
the error disappears. Using the COLLADA Max NextGen exporter is
essential
for 3ds Max 2010 users, as the older exporter doesn't work for this new
version of Max.
Both COLLADA files have information in the XML, regarding
animation. I'm not
a COLLADA expert, but I can imagine that if I edit the nextgen exported file
manually, I could make this work. Has anybody done this before?
Thanks in advance,
Paul
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org
_______________________________________________
Papervision3D mailing list
http://osflash.org/mailman/listinfo/papervision3d_osflash.org