Announcement

Collapse
No announcement yet.

Error while loading the plugin

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

  • Error while loading the plugin

    Hi,

    I just installed the wibu-key drivers, the licserver and vray on a workstation with Linux CentOS. Installations went fine, no errors. When i try to load the plugin in maya i get an error:

    Code:
    V-Ray warning: Loading shaders failed: no <*.txt> file in .
    V-Ray warning: Loading shaders failed: no <*.txt> file in .
    V-Ray warning: Loading shaders failed: no <*.txt> file in .
    V-Ray error: Could not register VRayGeoSun (kFailure): Unexpected Internal Failure
    registerTransform failed: (kFailure): Unexpected Internal Failure
    Versions:
    Maya2011x64,
    CentOS 5.4,
    Vray build 12830

    Any suggestions?
    Sorry if this is discussed anywhere else, didn't find anything.

    Thank you!
    Last edited by pechart; 06-10-2010, 07:53 AM.

  • #2
    EDIT: Solved, works now after 2 rebbots and one or two restarts of the licserver and maya.

    Comment


    • #3
      I looks like the environment variables were not set properly the first few times.

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

      Comment


      • #4
        ok, thanks!

        Comment


        • #5
          I cannot get the V-Ray plugin to work.
          I get this in a terminal window when starting maya:
          [2014/Oct/6|13:56:15] V-Ray: V-Ray for Maya version 2.40.02 from May 14 2014, 16:13:09
          [2014/Oct/6|13:56:15] V-Ray: V-Ray core version is 2.00.02
          [2014/Oct/6|13:56:15] V-Ray warning: Loading shaders failed: no <*.txt> files in .
          [2014/Oct/6|13:56:15] V-Ray warning: Loading shaders failed: no <*.txt> files in .
          [2014/Oct/6|13:56:15] V-Ray warning: Loading shaders failed: no <*.txt> files in .

          Logging out/in doesn't solve the problem. Any hints?
          Maya 2015 SP4
          Slackware 14.1
          Vray 2.4.002

          Comment


          • #6
            It's the same thing; environment variables are not set up properly. The installation tries to set this up, but maybe it fails to do that for your Linux distribution. There is some more information here (although it describes how to set things up for a .zip installation, it also gives a list of the required environment variables):
            http://docs.chaosgroup.com/display/V...om+a+.zip+File

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

            Comment


            • #7
              Thanks for the reply. I'm using the .zip installation method and I've got it mostly working now.

              Comment

              Working...
              X