google-code-export / o3d

Automatically exported from code.google.com/p/o3d
0 stars 0 forks source link

Components cannot be converted by o3dconverter #196

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Hi

What steps will reproduce the problem?
1.building a model and make it a component (SketchUp)
2.export this component in collada format (DAE).
3.convert the COLLADA file by o3dconverter

I don't think the component is converted correctly, it cannot be loaded with 
o3djs.scene.loadScene()

Original issue reported on code.google.com by qliguan...@gmail.com on 10 Dec 2009 at 3:39

GoogleCodeExporter commented 9 years ago
Doesn't work in the simple scene viewer demo either.

I have looked at the output file from o3dconverter when using components, and 
it only 
contains scene.json (which looks too small) and aaaaaaaa.o3d. There are no 
index-
buffers.bin or vertex-buffers.bin.

Original comment by raffe...@gmail.com on 21 Apr 2010 at 7:54

GoogleCodeExporter commented 9 years ago
This does not work for me either. Only after I exploded all components in my 
SketchUp 
model, the geometries ended up in the o2dtgz.
I think this bug must be prioritized - the main purpose of 03D platform is 
development 
of interactive 3D apps. You should be able to manipulate with the model, e.g. 
show/hide  
or move some parts of it. Ideal mechanism for this could be - named components. 
Unfortunately, we cannot do this now.

Original comment by Alexande...@gmail.com on 19 May 2010 at 2:31