Announcement

Collapse
No announcement yet.

No module named vray.pluginmodifier

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

  • No module named vray.pluginmodifier

    Hi,
    We running V-Ray from an arbitrary location, and when we submit the job on the renderfarm, we have :

    Code:
    [2011/Nov/29|20:37:01] V-Ray: Total time translating scene for V-Ray 0h 0m 4.4s (4.4 s)
    Error: line 0: No module named vray.pluginmodifier
    # Traceback (most recent call last):
    # File "", line 1, in
    # File "/prod/exe/vray/vray2-nightly-20111112/autodesk/maya2011-x64/vray/scripts/vrayExecPostTranslateScript.py", line 5, in
    # import vray.pluginmodifier
    # ImportError: No module named vray.pluginmodifier
    It is because the PYTHONPATH is not changed.
    Question : do we need to change the PYTHONPATH to /prod/exe/vray/vray2-nightly-20111112/autodesk/maya2011-x64/vray/scripts/ ?

    There is nothing on the PYTHONPATH in : http://www.spot3d.com/vray/help/maya...l_from_dir.htm
    www.deex.info

  • #2
    It should not be necessary to change the PYTHONPATH; from my experiments, changing MAYA_SCRIPT_PATH should be enough as Maya automatically adds the directories from the MAYA_SCRIPT_PATH to the PYTHONPATH variable.

    As a last resort you could change the PYTHONPATH, but this caused other issues (PYTHONPATH specified in Maya.env was in that case ignored).

    Best regards,
    Vlado
    I only act like I know everything, Rogers.

    Comment


    • #3
      I am experiencing the same issue when running V-Ray from an arbitrary location.

      I have tried adding the [path_to_installation]/maya_vray/scripts/vray path to MAYA_SCRIPT_PATH but I still get that same error.
      Then I tried adding that path to PYTHONPATH instead but that didn't make any difference.

      Bigboss, did you come to a solution?

      Edit: I'm running the 22697 nightly build (2013-01-31).
      Last edited by Fredrik Averpil; 31-01-2013, 04:25 AM.
      Best Regards,
      Fredrik

      Comment


      • #4
        Originally posted by Fredrik Averpil View Post
        I am experiencing the same issue when running V-Ray from an arbitrary location.

        I have tried adding the [path_to_installation]/maya_vray/scripts/vray path to MAYA_SCRIPT_PATH but I still get that same error.
        Then I tried adding that path to PYTHONPATH instead but that didn't make any difference.

        Bigboss, did you come to a solution?

        Edit: I'm running the 22697 nightly build (2013-01-31).
        It is very old...I do not remember what was my solution, sorry...
        www.deex.info

        Comment


        • #5
          So, just to be clear, I'm getting that error when I try to write .vrst files using the latest nightly using the Post Translate Python script provided in the readme.txt that comes with the .vrst/deep Nuke plugin - and when running V-Ray for Maya from an arbitrary installation. It's currently prohibiting us from writing .vrst files out of V-Ray.
          Best Regards,
          Fredrik

          Comment


          • #6
            Ok, so I got it to work by setting PYTHONPATH. You need to set it to both the maya_vray/scripts folder AND the maya_vray/scripts/vray folder.

            But it would be so much nicer to control this using MAYA_SCRIPT_PATH.
            Best Regards,
            Fredrik

            Comment


            • #7
              I have exactly the same problem with Maya 2018 SP5 on linux and vray v.3.60.05 (28953)

              Tried the PYTHONPATH "You need to set it to both the maya_vray/scripts folder AND the maya_vray/scripts/vray folder." solution but it doesn't work here. Any other solutions?



              Comment

              Working...
              X