Announcement

Collapse
No announcement yet.

About texture and other file paths...

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

  • About texture and other file paths...

    Well, right now, Maya for Linux users haven't license server for linux, so, they need a Windows/Mac machine and a network connection for get working Vray for linux, and at the same time, benefiting from the distributed render feature.. But:

    1) Do a simple ethernet-to-ethernet network connection between two computers, one with windows xp and other with windows 7 appears to be impossible.

    2) If you connect Windows Xp (or Seven) with Linux, and prepare all for Distributed Rendering, a new problem arises: In Windows Vray tries to find the textures in a Windows path ("C:/Docum.."), while Linux looks in paths like: "/home/user/....". So, if final vrScene haves the textures referenced like "C:/...", Vray try to find the texture in a Windows machine, although it be runing under linux, OR vrScene haves the textures referenced like "/home/use...", although it be running under windows.


    How we can Linux users, one time we have brought all light maps, textures... to Linux from Windows, do Vray finds the right textures (or Viceversa, vrScene created in linux and use Windows machine for distributed rendering, besides take the license from there), if the paths cant be equal?

  • #2
    I see I cant edit the previous post, so, of course, its possible to replace the paths inside the vrScene file, but we are talking about a final render.

    The issue I am talking is while you are working and adjusting all parameters. If you're working form linux with a windows machine attached by network, you can use windows machine besides the network license computer, like distributed rendering machine, but if you're working with textures (and the textures are, probably in /home/user/maya/..., the DR windows machine gonna search this textures there (/home/user...), and its impossible that Vray form windows machine finds the textures in a path like that because all Windows paths born with "C:" (or some other letter).

    What can do Maya for Linux users, besides wait the linux license server release?.

    Comment


    • #3
      You can use the VRAY_ASSETS_PATH environment variable (for example before running the V-Ray render server) and specify paths where V-Ray should look for textures.

      I realize it's not the most convenient way and we'll probably think of something else, but for the time being it should work...

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

      Comment


      • #4
        Buff, Environment variables!, this gonne be funny!.

        Thanks again, Vlado, and happy new year!.

        Comment


        • #5
          is there a tutorial on how to setup the "Vray Assets Path" for maya on the mac?

          Comment


          • #6
            Originally posted by ripster8690 View Post
            is there a tutorial on how to setup the "Vray Assets Path" for maya on the mac?
            In order to set up the environment variable VRAY_ASSETS_PATH on Mac OS, you need to do the following:

            1) Open a Terminal.app from /Applications/Utilities/
            2) Enter the following command in the terminal window:

            export VRAY_ASSETS_PATH=/path/to/textures/:/another/path/to/textures/

            3) In the same terminal window start V-Ray render slave by typing:

            [MAYA_ROOT]/vray/bin/vrayslave

            Where [MAYA_ROOT] should be substituted by the path to Maya folder. For example it is like /Application/Autodesk/maya2015

            V-Ray render slave started should use the paths set in VRAY_ASSETS_PATH.
            Svetlozar Draganov | Senior Manager 3D Support | contact us
            Chaos & Enscape & Cylindo are now one!

            Comment


            • #7
              Or you can use the option for automatic asset transfer.

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

              Comment

              Working...
              X