Horde3D

Animation from 3ds max 2010 crashes ColladaConv

OpenCollada 1.2.5

Animation has 50 frames (hand wave)

Animation file is 900MB (why so large).

Attempts to hide geometry in 3ds and then export crashes 3ds

max

Can you provide the collada file?

Ok, I am sending you the link

The question is, why is your Collada file already 911MB big in size? That's really huge,... it tooks minutes to open the DAE file with Notepad++.
The only crash I had, was a bad allocation error, because the converter runs out of memory... I guess, you should optimize your model quite a bit before we can try to find a bug in the converter.

Because there is a lot of vertex there? Make sure that there is no high poly model in the scene before exporting ...

ok it looks like the dae file was being imported into 3ds as a fbx instead of using opencollada.

using opencollada, the file is 73 mb instead of 300 mb. However, now we get a different error from ColladaConv

Screenshot attached.

I'm sending the model file link in an email b/c I don't have the rights to distribute it freely.

update:

We just tried exporting animation directly from Daz and it appears to be working fine there, just not when we do it from 3ds max.

I don't want to sound harsh but please don't post screenshots in such cases as they are not very helpful and we have just a limited amount of webspace.

There are hundreds of vector accesses in ColladaConv so just having the information that there is an out-of-bounds access does not really bring us further. What we need instead is the callstack to see where exactly the crash/assertion happens. It is also important to know which horde version (or svn revision) you are using.

Check the first part of Alex's post to see how a professional crash report can look like

I just tried to convert the dae file and it seems like the polylist contains indices equal and greater than 32900 although there are only 32899 vertices in the referenced positions array (meaning 98697 float values). That results in a crash because the index is invalid. The question is, is the converter missinterpreting something I currently don't see or contains the exported file invalid data. Have you tried reimporting the DAE file into 3Ds?

OK we figured it out by doing diffs of the collada files (we found a previous one that worked) and the current file.

It looks like the problem (at least) was that some of the exporter parameters got checked off

Once the following were checked on:

copy images
normals
triangulate
enable export
sample animation

we got things working again.