Horde3D

Next-Generation Graphics Engine
It is currently 05.04.2025, 12:05

View unanswered posts | View active topics


Board index » Horde3D Usage » Support

All times are UTC + 1 hour




Post new topic Reply to topic  Page 1 of 1
  [ 13 posts ] 
  Print view Previous topic | Next topic 
Author Message
PuG
 Post subject: Modo, Collada 1.4 Export
PostPosted: 11.06.2008, 19:47 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Hi, very new to Horde!

I was trying to import some basic geometry today and struggling to get it to appear within the engine. Using Modo and their latest Collada exporter, ive exported a simple cube (attached), when I load it into Horde nothing appears, and even an occasional crash.

Could it be the collada export is not suitable? a geo file and xml is created but only has the following for the scene.xml:

Quote:
<Model name="box" geometry="box.geo">

/>
</Model>


Any suggestions?

Best regards,


Attachments:
File comment: Box.dae file.
box.zip [1.61 KiB]
Downloaded 766 times

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
Vurlix
PostPosted: 11.06.2008, 21:20 
Offline

Joined: 19.03.2008, 01:22
Posts: 79
Currently, Horde's ColladaConverter only supports collada files exported in the triangulated format (versus polygons). There's probably an option to triangulate your meshes in the collada exporter you're using. Hopefully, though, this issue will be fixed some day.
Top
 Profile  
Reply with quote  
PuG
PostPosted: 11.06.2008, 22:06 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Hi, thanks for the reply - im triangulating the mesh manually before exporting, though now you've mentioned it im sure before for a program not related ive had to edit the .dae file to adjust the polygon tags.

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
PuG
PostPosted: 11.06.2008, 22:14 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Fixed!

You need to edit the exported dae files from modo and replace the polygons tags with triangles.

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
PuG
PostPosted: 12.06.2008, 10:16 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Okay, perhaps not - a new issue is for some reason only one triangle is imported & viewable in .geo format, from the whole mesh.

Ive tried running the .dae file through the Collada Refinery to make sure its conditioned correctly (and to convert from polygon to triangle) to suit Horde but still the same issue.

Code:
<?xml version="1.0"?>
<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
    <asset>
        <contributor>
            <author>Your Name Here</author>
            <authoring_tool>modo 302</authoring_tool>
            <comments>No comment.</comments>
            <copyright>Copyright 2008 Name of Copyright Holder.</copyright>
            <source_data>file:///G:/Clients/Horde3d/models/box.lxo</source_data>
        </contributor>
        <created>2008-06-12T08:42:00Z</created>
        <modified>2008-06-12T08:42:00Z</modified>
        <unit name="meter"/>
        <up_axis>Z_UP</up_axis>
    </asset>
    <library_images>
        <image id="Imagecube-diffuseColorMap" name="Imagecube-diffuseColorMap">
            <init_from>./grass01.tga</init_from>
        </image>
    </library_images>
    <library_effects>
        <effect id="Effectcube">
            <profile_COMMON>
                <newparam sid="Imagecube-diffuseColorMap-Surface">
                    <surface type="2D">
                        <init_from>Imagecube-diffuseColorMap</init_from>
                        <format>A8R8G8B8</format>
                    </surface>
                </newparam>
                <newparam sid="Imagecube-diffuseColorMap-Sampler">
                    <sampler2D>
                        <source>Imagecube-diffuseColorMap-Surface</source>
                        <minfilter>LINEAR_MIPMAP_LINEAR</minfilter>
                        <magfilter>LINEAR</magfilter>
                    </sampler2D>
                </newparam>
                <technique sid="phong1">
                    <phong>
                        <diffuse>
                            <texture texture="Imagecube-diffuseColorMap-Sampler" texcoord="TEX0"/>
                        </diffuse>
                        <specular>
                            <color>0.2 0.2 0.2 1</color>
                        </specular>
                        <shininess>
                            <float>256</float>
                        </shininess>
                    </phong>
                </technique>
            </profile_COMMON>
        </effect>
    </library_effects>
    <library_materials>
        <material id="Materialcube" name="Materialcube">
            <instance_effect url="#Effectcube"/>
        </material>
    </library_materials>
    <library_geometries>
        <geometry id="GeometryMesh_0000" name="GeometryMesh_0000">
            <mesh>
                <source id="GeometryMesh_0000-Position">
                    <float_array id="GeometryMesh_0000-Position-Array" count="24">-2 -2 -2 2 -2 -2 2 -2 2 -2 -2 2 -2 2 -2 2 2 -2 2 2 2 -2 2 2</float_array>
                    <technique_common>
                        <accessor count="8" source="#GeometryMesh_0000-Position-Array" stride="3">
                            <param name="X" type="float"/>
                            <param name="Y" type="float"/>
                            <param name="Z" type="float"/>
                        </accessor>
                    </technique_common>
                </source>
                <source id="GeometryMesh_0000-Normal">
                    <float_array id="GeometryMesh_0000-Normal-Array" count="18">0 -1 0 0 0 -1 1 0 0 0 0 1 -1 0 0 0 1 0</float_array>
                    <technique_common>
                        <accessor count="6" source="#GeometryMesh_0000-Normal-Array" stride="3">
                            <param name="X" type="float"/>
                            <param name="Y" type="float"/>
                            <param name="Z" type="float"/>
                        </accessor>
                    </technique_common>
                </source>
                <source id="GeometryMesh_0000-UV">
                    <float_array id="GeometryMesh_0000-UV-Array" count="28">0.25 0 0.5 0 0.5 0.333333 0.25 0.333333 1 0.666667 0.75 0.666667 0.75 0.333333 1 0.333333 0.5 0.666667 0.25 0.666667 0 0.666667 0 0.333333 0.25 1 0.5 1</float_array>
                    <technique_common>
                        <accessor count="14" source="#GeometryMesh_0000-UV-Array" stride="2">
                            <param name="S" type="float"/>
                            <param name="T" type="float"/>
                        </accessor>
                    </technique_common>
                </source>
                <vertices id="GeometryMesh_0000-Vertex">
                    <input semantic="POSITION" source="#GeometryMesh_0000-Position"/>
                </vertices>
                <triangles count="12" material="MatSym_cube">
                    <input offset="0" semantic="VERTEX" source="#GeometryMesh_0000-Vertex"/>
                    <input offset="1" semantic="NORMAL" source="#GeometryMesh_0000-Normal"/>
                    <input offset="2" semantic="TEXCOORD" source="#GeometryMesh_0000-UV"/>
                    <p>0 0 0 1 0 1 2 0 2 0 0 0 2 0 2 3 0 3 4 1 4 5 1 5 1 1 6 4 1 4 1 1 6 0 1 7 5 2 5 6 2 8 2 2 2 5 2 5 2 2 2 1 2 6 6 3 8 7 3 9 3 3 3 6 3 8 3 3 3 2 3 2 7 4 9 4 4 10 0 4 11 7 4 9 0 4 11 3 4 3 4 5 12 7 5 9 6 5 8 4 5 12 6 5 8 5 5 13</p>
                </triangles>
            </mesh>
        </geometry>
    </library_geometries>
    <library_visual_scenes>
        <visual_scene id="DefaultScene" name="untitled">
            <node id="GeometryMeshNode_0000" name="GeometryMeshNode_0000">
                <matrix>1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1</matrix>
                <instance_geometry url="#GeometryMesh_0000">
                    <bind_material>
                        <technique_common>
                            <instance_material symbol="MatSym_cube" target="#Materialcube">
                                <bind_vertex_input semantic="TEX0" input_semantic="TEXCOORD" input_set="0"/>
                            </instance_material>
                        </technique_common>
                    </bind_material>
                </instance_geometry>
            </node>
        </visual_scene>
    </library_visual_scenes>
    <scene>
        <instance_visual_scene url="#DefaultScene"/>
    </scene>
</COLLADA>


Im at a lost at what's happening, I can accept their might be an issue exporting from Modo (though it should be standardised Collada 1.4), though I would have thought the Refinery should resolve any possible incompatibilities.

Does anyone have an example DAE file I could view?

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
swiftcoder
PostPosted: 12.06.2008, 11:52 
Offline

Joined: 22.11.2007, 17:05
Posts: 707
Location: Boston, MA
I had the same problem a while ago with the FBXConverter, so I can safely tell you that you are almost there :)

Inside the triangles tag you will find a < p > tag - unfortunately, Modo and FBXConverter lump all the indices into one tag, whereas Horde requires only 3 indices per < p > tag. So split that out into groups of 3, and you should be good to go.

_________________
Tristam MacDonald - [swiftcoding]
Top
 Profile  
Reply with quote  
PuG
PostPosted: 12.06.2008, 14:35 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
:) is any chance of an example? ive tried editing the <p tags but still not figured it out. To compound the issue, I in fact had an exporter that did export the geometry correctly, but without textures and at the time not realising what was happening I must have deleted it.

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
swiftcoder
PostPosted: 12.06.2008, 23:21 
Offline

Joined: 22.11.2007, 17:05
Posts: 707
Location: Boston, MA
PuG wrote:
:) is any chance of an example? ive tried editing the < p > tags but still not figured it out.

Hmm, I just tried it out and realised I had that backwards - you are correct as is. The only problem I can find with your collada file is that you don't specify the texture coordinate set:
Code:
<input offset="2" semantic="TEXCOORD" source="#GeometryMesh_0000-UV" set="0" />


I do however have a small collada file which does work with the converter, if you would like to compare (Duck.zip, attached)

Attachment:
Duck.zip [138.81 KiB]
Downloaded 811 times

_________________
Tristam MacDonald - [swiftcoding]
Top
 Profile  
Reply with quote  
PuG
PostPosted: 13.06.2008, 07:55 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Thank you, will try and compare the files later today, but just took a quick glance and it looks fairly similar. The texture would not stop it from rendering?

Attached a picture of what the cube appears like within HordeEditor/Horde.

Other than that im at loss, I don't particularly want to go via another CAD program.


Attachments:
box.jpg
box.jpg [ 39.1 KiB | Viewed 19102 times ]

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
PuG
PostPosted: 13.06.2008, 08:18 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
Thanks for all the help! its now working.


SO for Modo users (301/302 (tested):
* Ive modified and attached a Collada exporter to this post (original version http://forums.luxology.com/discussion/t ... 20exporter).
* You will need to define your content directory (Lightwave I/0) within Modo's Prefs for the export output.
* Make sure your mesh is triangulated before exporting, and name your UV channels UV01, UV02, UV03, ... and so on.
* Convert to .geo and copy the files accordingly :)

Theirs a newer Collada exporter over at SourceForge (https://sourceforge.net/projects/colladamodo), though the output crashes Horde's Geo converter.

Added a new entry to the Horde Wiki - http://horde3d.org/wiki/index.php5?titl ... ity_Portal (link at the bottom).


Attachments:
File comment: Modified Collada Exporter.
collada_exporter_horde.zip [11.75 KiB]
Downloaded 913 times

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
marciano
PostPosted: 14.06.2008, 16:11 
Offline
Engine Developer

Joined: 10.09.2006, 15:52
Posts: 1217
It is a bit annoying that most exporters don't support the options that the COLLADA specifiaction demands (export as triangle list for example) and that all the work needs to be done on the importer side (which is a plenty if you want to support every single feature the standard offers).

At least we have a working export script now. Great work PuG and thanks for the wiki article! :)
Top
 Profile  
Reply with quote  
swiftcoder
PostPosted: 14.06.2008, 16:56 
Offline

Joined: 22.11.2007, 17:05
Posts: 707
Location: Boston, MA
marciano wrote:
It is a bit annoying that most exporters don't support the options that the COLLADA specifiaction demands (export as triangle list for example) and that all the work needs to be done on the importer side (which is a plenty if you want to support every single feature the standard offers).
Unfortunately, I think we may have to make the converter even more lenient in the future. Maintaining our own exporters for each and every modelling package works for the time being, but is going to get old pretty fast - how much work is it going to take to do triangulation in the converter?

Along the same topic, what modelling packages provide a collada exporter that works with Horde's converter out of the box? We should probably make an entire wiki section on this topic, to keep track of which packages work/don't work, and what workarounds have been found. (Edit: Section created on the community portal, blender added)

_________________
Tristam MacDonald - [swiftcoding]
Top
 Profile  
Reply with quote  
PuG
PostPosted: 15.06.2008, 09:51 
Offline

Joined: 11.06.2008, 10:34
Posts: 119
:) - Allot of the problems atleast for Modo is that the currently available exporters seem to output to different tag standards (polylist, polygon, <p></p>, UV tex etc), and the majority of these are hard coded (so theirs no user input on the Collada exporting). I don't really think that Horde needs to triangulate the mesh automatically, as most artists can/will do that on the initial export from the program of their choose, the problem arises is even though the mesh is triangulated it can still have incorrect tags.

Perhaps a log output detailing the conversion process of the import to geo would be useful, and alittle more flexibility on some of tags allowed. Something that should work is the Collada Refinery, which currently at the moment doesn't appear to.

Unfortunately im starting to run into a few new problems this morning, with polygons starting to disappear during the conversion with meshes over, or around 900 - 1000. No idea whether its the Modo Collada or geo exporter/importer. Also Shadows! they've now disappeared, originally I was leaving the model open, but after noticing a few artefacts I started closing the mesh, since then none have been cast (but it may be perhaps due to the materials used?).

(if Horde needs to use a closed mesh, perhaps a NULL/No render type texture would be useful)

_________________

Let's bring 'em out! Any old iron! Any old iron!
A door opens and a homewife brings out a rather sophisticated-looking ground-to-air missile system, and dumps it on the cart.
Thank you.
Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 1 of 1
  [ 13 posts ] 

Board index » Horde3D Usage » Support

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 23 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group