search

omni360 / kuda

Automatically exported from code.google.com/p/kuda
GNU General Public License v2.0
0 stars 0 forks source link

O3dconvert.exe ignores <up_axis> tag #46

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When using O3dconvert.exe to convert a Collada DAE file to a O3D JSON file I am 
unable to specify the "up axis" value.  Here are the first few lines of a 
Collada file:

<?xml version="1.0" encoding="utf-8"?>
<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
  <asset>
    <unit name="meter" meter="1"/>
    <up_axis>Z_UP</up_axis>
  </asset>

See the "up_axis" tag ? It is set to the Z axis.  Now if I convert that file, 
the resulting JSON file does not conform to that specification. The up Adix 
remains Y.  The same with specifying the X axis.  The o3dconverter.exe command 
line allows for an option '--up-axis='  where you can speicify the up axis when 
you convert the file.  This doesnt work either.  When trying any of these 
options, the resulting JSON file is exactly the same on a bainary level. 

I looked online for the o3dconverter.exe source code.  I could not find. What 
do you guys think?

Original issue reported on code.google.com by raj...@gmail.com on 21 Jun 2011 at 1:16

GoogleCodeExporter commented 9 years ago 
When using O3dconvert.exe to convert a Collada DAE file to a O3D JSON file I am 
unable to specify the "up axis" value.  Here are the first few lines of a 
Collada file:

<?xml version="1.0" encoding="utf-8"?>
<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
  <asset>
    <unit name="meter" meter="1"/>
    <up_axis>Z_UP</up_axis>
  </asset>

See the "up_axis" tag ? It is set to the Z axis.  Now if I convert that file, 
the resulting JSON file does not conform to that specification. The up AXIS 
remains Y.  The same with specifying the X axis.  The o3dconverter.exe command 
line allows for an option '--up-axis='  where you can specify the up axis when 
you convert the file.  This doesn’t work either.  When trying any of these 
options, the resulting JSON file is exactly the same on a binary level. 

I looked online for the o3dconverter.exe source code.  I could not find. What 
do you guys think?

Original comment by raj...@gmail.com on 21 Jun 2011 at 1:18

GoogleCodeExporter commented 9 years ago

Original comment by raj...@gmail.com on 21 Jun 2011 at 1:18

GoogleCodeExporter commented 9 years ago 
This has been verified and made it into release 1.4.0.

Original comment by jpywt...@gmail.com on 3 Aug 2011 at 3:50