supergoldorak / kuda

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

cannot change up_axis when using o3dconvert.exe #47

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 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 issue reported on code.google.com by raj...@gmail.com on 21 Jun 2011 at 1:20

GoogleCodeExporter commented 9 years ago
Lowering the priority on this for multiple reasons. There is a chance we may 
not be using the o3d converter for long. Also I cannot reproduce this. Are you 
specifying a vector on the command line? like so: --up-axis=0,0,1 fo z etc.

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

GoogleCodeExporter commented 9 years ago
ummm that might be the problem... I will test.  I am using batch file where I 
can drop files onto the icon and it just converts:

@echo off
echo converting file %1 to outputFolder\scene.json
@echo on
C:\o3dconverter\o3dConverter.exe --no-archive --no-binary --up-axis:x 
--pretty-print %1 outputFolder
@echo off
pause

Original comment by raj...@gmail.com on 19 Sep 2011 at 9:51

GoogleCodeExporter commented 9 years ago
Ah, thanks for showing your batch file contents. You need a vector on the 
--up-axis. That one has an 'x', so it should be --up-axis=1,0,0 for x.

Original comment by jpywt...@gmail.com on 19 Sep 2011 at 11:42

GoogleCodeExporter commented 9 years ago

Original comment by jpywt...@gmail.com on 16 Dec 2011 at 10:19

GoogleCodeExporter commented 9 years ago
Kuda2 no longer uses o3d or the converter. Kuda2 loads COLLADA directly.

Original comment by jpywt...@gmail.com on 1 Mar 2012 at 11:12