Announcement

Collapse
No announcement yet.

ver 1.46.10, and VRmesh files not loading with DR

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

  • ver 1.46.10, and VRmesh files not loading with DR

    Anyone else having this problem?

    Everything was rendering fine on the 30th. Upgraded to Ver. 46.10 on the 1st and attempted to render a large scene with DR (9 slaves) It seems that only the local machine will load in the Vrmesh files durning rendering.

    Have tried multiple re-boots, start/stop DR, etc.

    I read through a few posts and tried coping the VRmesh files to each slave in the Max6meshes directory but that didn't help.

    Any thoughts??

  • #2
    it may just be an issue of the path listed for the *.vrmesh file. Are you using a location on a local drive or a unc path?

    For the most reliability I allways use unc naming for my files, ie:

    //server name/drive/folder/file name.*

    ok for some sick reason the back slashed I put in keep getting taken out so with the above the forward slashes are suposed to be back slashes.

    -dave
    Cheers,
    -dave
    ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

    Comment


    • #3
      It shouldn't be a path problem.

      All our files are centrally located and we always use UNC paths. again, it's been working great on all our projects right up till we upgraded to ver10.

      Comment


      • #4
        hmm there is another thread I just ran across with a similar issue and looks like it could be a file share issue. Where if 1 machine is using a proxy then none of the other slaves can. Ill post the thread if I can find it again.

        -dave
        Cheers,
        -dave
        ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

        Comment


        • #5
          I'll try to reproduce that here and I'll let you know what happens; 1.46.10 should be no different with respect to proxies than 1.46.09.

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

          Comment


          • #6
            Heres the other thread I was talking about http://www.chaoticdimension.com/foru...pic.php?t=9987

            -dave
            Cheers,
            -dave
            ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

            Comment


            • #7
              Thank you guys for the quick response.

              ran some tests over the weekend and found the following.

              A. The Proxies were not set to UNC as I had thought. They were mapped to drives. I changed the paths which has solved the problem. (Thank you)

              I went through all the previous revisions of this file. The proxies in each case were mapped to drives and it had been rendering with out issue up to this point. I'm curious, what is the problem with using mapped drives?

              B. I created a simple test file with 1 Vrmesh car. I tried several times to get it to render with Mapped drives without success. It would only work with UNC.

              Comment

              Working...
              X