Results 1 to 2 of 2

Thread: MR batch bake:a serious of unfortunate bugs

  1. #1
    Join Date
    May 2006
    Location
    Montreal
    Posts
    326

    Default MR batch bake:a serious of unfortunate bugs

    I have been working extensively lately with the bake tool, and really don't how Autodesk still insist on marketing Maya as a game tool when it fails to achieve basic baking tasks, here is what I am talking about:

    Half window missing:
    when launching a bake, minimizing the MR batch bake window and then remaximising the window, half the window is missing, you will have to close the tool window and reopen it. Doing this each time is very annoying. Yes Maya team, we really need the other half.

    Naming:
    If you bake a lightmap and name it "A", then do another bake and name it "B", there is no garantee Maya will name it "B", instead it can choose to name it "A" and overwrite your previous baked lightmap that took a day to render.

    Magical internal lottery:
    Whenever baking 200 or more objects at the same time, Maya runs an internal lottery to choose which objects MR should bake and which to discard. Yes Autodesk, users have sense of adventure and risk too, we too love casinos, but not while working.

    No progress preview:
    When baking the progress bar (in the help tab) freezes at 0, and gets to 100 when it's done. Since the MR batch bake tool is super buggy, we have to trouble shoot all the time (instead of focusing on art), and we really need to know what's happening when the bake is taking 7 hours and still didn't finish. Yes we too have the sense of suspense when not knowing what;s coming next but not while working.

    Multithreading issue:
    We have been told that MR batch bake supports multithreading in 'Multiple objects" mode, but that's not true, when baking 100 objects at the same time, the cpu usage never reaches 99% it reaches 40/50 usage at the max.

    We really don't expect from MR4Maya to compete with Vray or other modern renderers, but could you guys at least make the existing tools obey orders, don't think it's very complicated.

    Thanks

  2. #2
    Join Date
    Dec 2005
    Location
    Hollywood
    Posts
    1,989

    Default

    This really sounds like something that should be on the Autodesk Area and as a bug report to Autodesk.

    I know you sometimes cross post but not checked the Area in some time. The vast majority of how this is implemented is controlled by Autodesk, and you are their direct customer. Do you have Subscription with direct support? You can cross reference bug numbers and it makes it easier to solve.

    ARC and Autodesk can follow the logged bug to the source and fix it with the renewed relationship. But it means you have to log and reproduce the bug with Autodesk to make it happen most effectively.

    This has already been done for quite a few things since the initial release of Maya. Things that will be apparent in the Hotfix. As well as the already released ptex shaders by ARC.

    I might also suggest you try and get onto the Autodesk Betas (or your company) beta.autodesk.com

    You can pinpoint things in the development cycle.
    "Don't let anyone drive you crazy when you know it's in walking distance."

    "I occasionally confuse my desire for revenge with my desire for justice. Oops." -me

    http://elementalray.wordpress.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
  •