Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: data converter

  1. #1

    data converter

    I'd like to convert Collada files to my game engine data file, where should I start? I thought the sample source codes in "Samples & Source Code" would be useful, wouldn't they?
    I also found FCDocument, FUtils, LibXML directories in my download files. Are they the COLLADA Parser by which I can fetch the COLLADA file data? If not, maybe I will write such a parser.

  2. #2
    Senior Member
    Join Date
    Aug 2004
    Location
    California
    Posts
    771

    Re: data converter

    Quote Originally Posted by zhouzhengchun
    I'd like to convert Collada files to my game engine data file, where should I start?
    Start with the COLLADA schema and specification.
    Quote Originally Posted by zhouzhengchun
    I thought the sample source codes in "Samples & Source Code" would be useful, wouldn't they?
    There is no source code in the 1.3 sample data posted on this forum.
    Quote Originally Posted by zhouzhengchun
    I also found FCDocument, FUtils, LibXML directories in my download files. Are they the COLLADA Parser by which I can fetch the COLLADA file data?
    That is ColladaMaya code from the sounds of it and also libxml2. You can learn more about this code at http://colladamaya.sourceforge.net/
    Quote Originally Posted by zhouzhengchun
    If not, maybe I will write such a parser.
    Certainly you will need to write a translator if you are doing off-line tools to convert content to your game engine format, or an importer for fast path integration to your game engine.

  3. #3
    Thanks marcus!
    Another question: What COLLADA DOM is? How can we take use of it?

  4. #4

    Re: data converter

    Quote Originally Posted by marcus
    That is ColladaMaya code from the sounds of it and also libxml2. You can learn more about this code at http://colladamaya.sourceforge.net/
    Yes, Thank you. Feeling Software provides such a COLLADA Parser, by which we can read COLLADA file easily. Can I use it as an importer of my converter and what I should do is to write a translater and output them as a my engine file data?

  5. #5
    Senior Member
    Join Date
    Jul 2004
    Location
    Santa Clara
    Posts
    356
    Quote Originally Posted by zhouzhengchun
    Thanks marcus!
    Another question: What COLLADA DOM is? How can we take use of it?
    COLLADA DOM is a import/export utility that provides a C++ API to COLLADA. The front end is generated automatically from the COLLADA XML Schema.
    You can compile the DOM from its sources for 1.3.1 or 1.4.0
    It is available from source forge (please see announcement section)

  6. #6
    Senior Member
    Join Date
    Apr 2005
    Location
    Feeling Software, Montreal, Quebec
    Posts
    111
    About the FS import classes (FCDx classes), that's the COLLADA parser that we keep open-source and use in our own projects, we're currently in the process of formalizing it into a real library and it is constantly evolving: COLLADA 1.4 is not an easy beast to swallow whole .

    If you are interested in an importer only and you want easy inter-operability with ColladaMaya or the 3dsMax COLLADA tools, I would suggest waiting for our first release of the library on our website. If you need to export COLLADA data or if you will need access to <extra> elements that aren't part of the MAYA or MAX3D extensions, you should look at the COLLADA DOM.

    Sincerely,
    Guillaume Laforte
    Feeling Software Inc
    http://www.feelingsoftware.com

  7. #7
    I'm a little confused about which one to choose, FCDx classes or COLLADA DOM? What I want to do is just convert COLLADA file format to my engine file format.
    I've found that FCDx classes can parse the COLLADA file and read all the data. However, The COLLADA DOM provides a means for users to write translation code to transform data loaded into the COLLADA runtime database into data structures native to their own tools or engines. But it is much more complex than FCDx.
    Give me some advice,will you?

  8. #8
    Junior Member
    Join Date
    Dec 2004
    Location
    Seattle, WA
    Posts
    11
    Hi Guillaume-

    Any estimates on when you might have a release of the library for others to play around with? I'm very interested in adding Collada support to Axiom and/or OGRE, and your library sounds like it would be a huge help.

    -Don

  9. #9
    Senior Member
    Join Date
    Jan 2006
    Location
    Foster City, CA
    Posts
    540
    Quote Originally Posted by Don
    Any estimates on when you might have a release of the library for others to play around with? I'm very interested in adding Collada support to Axiom and/or OGRE, and your library sounds like it would be a huge help.
    Is the Collada DOM no good for you?

  10. #10
    Junior Member
    Join Date
    Dec 2004
    Location
    Seattle, WA
    Posts
    11
    Quote Originally Posted by sthomas
    Is the Collada DOM no good for you?
    I didn't mean to dis the DOM. Not having seen FeelingSoftware's library, I have no clue whether it's a better or worse fit for our needs than the DOM.

    That said, Feeling Software probably has as much experience as anyone in the world at writing full-blown Collada translators. If they found their library useful for building translators then I'm inclinded to believe it's worth taking a look at before getting too deep into architecting our own translators.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •