DAEParser throws exception on Std::parseFloat on Neko target about away3d HOT 1 OPEN

So it seems like there isn't any noticeable problems removing the extra parseFloat and the LoadDAE example works. However, I discovered numerical issues with COLLADA files exported from Blender using defaults.

Exporting any complicated model, such as the default monkey model, will result in vertexData containing NaN values. Originally, I would load the DAE file, rotate 90 deg to fix the up-axis, and scale by 100. This would result broken geometry. But I found setting Blender's unit size to centimeter, scaling everything by 100 before exporting would avoid this issue.

I spent hours trying to debug the issue (testing on Neko, stepping through the debugger on JS), but couldn't narrow it down enough to see if it is issue with the source code conversion from ActionScript or something else. The array would suddenly contain NaNs after the Asset3DEvent event is dispatched.

Edit: I may have spoken too soon. Scaling by 100 and exporting still results in some NaN values.

from away3d.