Announcement

Collapse
No announcement yet.

unifiedRenderGlobalsWindow was not modified

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • unifiedRenderGlobalsWindow was not modified

    Hello,

    I am using Maya 2018 update 3, on Windows Seven 64bit.
    I have installed vray_adv_36005_maya2018_x64.exe (VRay 3.60.05 "Stable" Nightly Build 28291, released on 30/05/2018 .

    The installation process is supposed to modify a few maya mel scripts. It does for most of them, but it leaves untouched this one : unifiedRenderGlobalsWindow.mel
    Here is the file that VRay uses to know what to modify : mod_unifiedRenderGlobalsWindowMel.txt
    It contains this :
    Code:
    5
            if (($createProc == "createMayaSoftwareCommonGlobalsTab")
                || ($createProc == "createMayaSoftwareGlobalsTab"))
            {
                eval($createProc);
            }
    6
            // V-Ray's changes start here.
            // Like this every renderer which comply with the name convention
            // will work properly, on first render settings opening.
            else if (gmatch($createProc, "*reate*CommonGlobalsTab"))
                eval($createProc);
    Here is the relevant part of the original Autodesk unifiedRenderGlobalsWindow.mel file :
    Code:
            if (($createProc == "createMayaSoftwareCommonGlobalsTab")
                || ($createProc == "createMayaSoftwareGlobalsTab"))
    
            {
                eval($createProc);
            }
            else
            {
                callbacks -executeCallbacks -hook "rendererAddOneTabToGlobalsWindowCreateProc" $createProc;
            }
    As you see, Autodesk modified this script, your current mod file can't work anymore.
    Cheers.

  • #2
    If I remember correctly, this change by Autodesk practically removed the need for the V-Ray installer to modify this particular file. I'm almost certain that the change is for Maya 2018, but I'll have to look at the autodesk changelogs to find the cause for the change.
    In any case - since the change, our gmatch didn't work anymore, which meant that we could just not change anything on our side to keep the behavior for all Maya versions.
    Is there something that concerns you about this?
    Alex Yolov
    Product Manager
    V-Ray for Maya, Chaos Player
    www.chaos.com

    Comment


    • #3
      No, this is not problem for us, I was just wondering if this behavior was intended.
      Thank you.

      Comment


      • #4
        Yes, it's intended
        Alex Yolov
        Product Manager
        V-Ray for Maya, Chaos Player
        www.chaos.com

        Comment

        Working...
        X