Results 1 to 2 of 2

Thread: Fixes to Maya exporter

  1. #1
    Junior Member
    Join Date
    Nov 2004
    Posts
    13

    Fixes to Maya exporter

    I wanted to list the fixes I've made to my own copy of the Maya exporter, in the hopes that someone will integrate them into the main source tree, and that they may prove useful to others in the meantime:

    DaeAnimationLibrary.cpp:
    I made it so "constant" animation channels (where all values in the animation curve are equal to the existing target value) are not exported. This greatly reduces file sizes and parsing times at little cost in the exporter. Here's the section of my source code (my changes surrounded by #if 1):


    DaeCameraLibrary.cpp:
    "horizontalFieldOfView" is used instead of "verticalFieldOfView" for the "YFOV", which is incorrect. There are two places in the source this needs to be changed. Also, I added support for orthographic "LEFT/RIGHT" parameters for cameras:


    DAETextureLibrary.cpp:
    I modified my version of "DaeTextureLibrary::includeTexture" to search the tree of input nodes besides the immediate input node and include the first "MFn::kFileTexture" it finds, rather than just dumping out nothing if the immediate input is not a texture. I did this because our artists commonly have extra custom shader nodes in their Maya files between the texture and the image. Including this concept might be helpful to some users.

    DAEUtils.cpp:
    There is a bug in color export -- a string pointer is off by one:

    Finally, I've worked around some things in my reader rather than fixing them in the exporter. I generally have to figure out "idx" attributes which are lacking for inputs under polygons and combiner elements. In controllers, Maya adds a hash (#) to the "target" attribute of the controller which shouldn't be there according to the spec. The required "semantic" attribute is missing from the inputs under combiner elements -- I'm getting this from the "name" attribute of the "param" pointed to instead for now. Last but not least, there's the known issue that the Maya exporter doesn't support multiple UV sets. On my wish list, I'd like an option to export "baked" keyframe data for animations at a specified frame rate (I will probably add this myself soon).

    --Jason
    Edited to remove copywritten source code. Admin.

  2. #2
    Member
    Join Date
    Aug 2004
    Location
    Feeling Software, Montreal, QC, Canada
    Posts
    36

    Fixes to Maya exporter

    Jason,

    Your post couldn't be more timely. I've just been hired by Alias, to improve the quality and reliability of the Maya plug-in for Collada. I have already started merging other people's code and fixing bugs. Please send me your changes at claforte 'at' feelingsoftware . com, and I'll make sure they get included in the next release, which should happen within a week or so.

    Thank you very much for your contribution!

    Christian Laforte
    Maya API and OpenGL consultant
    www.feelingsoftware.com
    Christian Laforte
    President, Feeling Software
    http://www.feelingsoftware.com

Posting Permissions

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