simple Cube - Crash

#1

Tried to get the object for item 12, which is not InspectorData!
Creating cyclic animation clip to hold all animations
Non-DTS scene detected: creating dummy node to hold subshape

That is the error I'm seeing in the console.log. Have you tried to get a simple box without animations into the test engine yet?

#2 This is a model without animations. Only a simple model.

#3

Quote:Creating cyclic animation clip to hold all animations

Is caused by:

<library_animations>
        <animation id="myCuberotation_Y">
            <source id="myCuberotation_Y-input">
                <float_array id="myCuberotation_Y-input-array" count="1">0 </float_array>

What this is telling me, and I could very easily be wrong, is that torque believes this to be an animated object and it cant figure out what the animation is.
Btw, this is most likely a naming glitch in your exporter.

Compare your box code with mine. This forum balked at the size of my post, so here is a zip with mine in it.

#4 And when i include your box.dae i can't see anything. Only an empty object.

#5 Lol. You are probably inside it. DeleD exports things Huge. I had to scale it down a whole lot just to get it to fit.

#6 I scaled it down to 0.2 0.2 0.2 so now i can see a textured cube.

#7 Sorry about that. I should have warned you ahead of time.

I wish I could help you figure out this problem, but it looks to me like it's the way collada is exported from lightwave. I could be wrong tho. Does lightwave have a triangulate model command? It's a problem I had with my models, so it's worth a try to see if that fixes your problem.

#8 When i export from Lightwave to Collada my geometry is automatically triangulated. That's not the problem because i tested the same model in C4. No problems.

#9 Hi Thomas,

The problem is indeed the animation data. Although there is nothing actually wrong with the collada file, it has exposed a bug in the loader (cannot handle animation channels with only a single keyframe).

Unfortunately until/if a new build comes out the only workaround I can suggest is to manually delete everything between the 'library_animations' tag before loading into Torque. This should only be required for static (non-animated) models.

Also - the model has not been triangulated. The single mesh contains 6 quads.

#10 When i import this dae into C4 i have not 6 quads. I have 12 tris.

#11 C4 is a different engine lol its not torque you need to tris your object for be for putting it in torque. your dealing with 2 different engines this is torque engine not C4.

#12 This is not true. I also triangulated the model in Lightwave. Same result.

#13 Hi Thomas,

The model you uploaded was not triangulated. Perhaps the C4 engine triangulates on load (a handy feature for the Torque loader to do eventually as well). Here is the geometry in the model you uploaded.

<polylist count="6" material="surf_Cube">
    <input offset="0" semantic="VERTEX" source="#myCube_vertices"></input>
    <input offset="1" semantic="TEXCOORD" source="#uv_cube_uvmap" set="0"></input>
    <vcount>4 4 4 4 4 4 </vcount>

6 polygons with 4 vertices each.


However, as I mentioned, the crash issue is not related to triangulation. It is a bug in the Torque loader (easily fixed, but need to get a new build generated).

#14 OK, it works now. I simply created 2 Keyframes.

#15 Cool. That's probably a better workaround than manually editing the file anyway! ;-)

#16 The "crash on single keyframe animation channels" issue is fixed in the new Collada Test build here.