Announcement

Collapse
No announcement yet.

DR problems in 2010

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

  • DR problems in 2010

    I'm setting up DR with Max 2010 (already setup for 2009). This is the process i've followed:

    1) Install Max 64bit
    2) Install Hotfix
    3) Install vray
    4) Override plugin.ini with one that points to network location

    I'm getting the following error when starting the spawner:

    1) Start spawner, loaded "vraydummy2010"
    2) Send scene from workstation, get "Connected to render host" message
    3) DR machine loads vray_server_scene.max
    4) Max on DR machine crashes/closes, and retries in the order above

    What can I do to debug this?

    Additionally, i've disabled the communication center on the machine, and run regular backburner at least twice since last week which has been fine.
    Last edited by duke2; 17-06-2009, 12:48 AM.

  • #2
    Can you try renaming the "AutoCamMax.gup" file on the render slaves and see if it makes things any better.

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

    Comment


    • #3
      Just tried that, no luck. Here's the vray spawner log on that machine. It doesn't seem to point to anything :\

      Code:
         0:  [2009/Jun/18|10:24:13]    ========================== Starting new session ==========================
         1:  [2009/Jun/18|10:24:13]    Got this module name: C:\Program Files\Autodesk\3ds Max 2010\vrayspawner2010.exe
         2:  [2009/Jun/18|10:24:13]    Got this INI file name: C:\Program Files\Autodesk\3ds Max 2010\VRaySpawner.ini
         3:  [2009/Jun/18|10:24:13]    *** ALERT! Could not open INI file: "C:\Program Files\Autodesk\3ds Max 2010\VRaySpawner.ini". Using defaults.
         4:  [2009/Jun/18|10:24:13]    --
         5:  [2009/Jun/18|10:24:13]      Dumping current settings...
         6:  [2009/Jun/18|10:24:13]      VRaySpawner temp dir: "C:\Program Files\Autodesk\3ds Max 2010\network"
         7:  [2009/Jun/18|10:24:13]      Application name (MAX/VIZ): "C:\Program Files\Autodesk\3ds Max 2010\3dsmax.exe"
         8:  [2009/Jun/18|10:24:13]    --
         9:  [2009/Jun/18|10:24:13]    Process id is 4252 (0x109c)
        10:  [2009/Jun/18|10:24:13]    Executing ""C:\Program Files\Autodesk\3ds Max 2010\3dsmax.exe" -server C:\Program Files\Autodesk\3ds Max 2010\network\vraydummy2010.max"
        11:  [2009/Jun/18|10:30:17]    Process id is 4252 (0x109c)
        12:  [2009/Jun/18|10:30:17]    Executing ""C:\Program Files\Autodesk\3ds Max 2010\3dsmax.exe" -server C:\Program Files\Autodesk\3ds Max 2010\network\vraydummy2010.max"
        13:  [2009/Jun/18|10:31:54]    Process id is 4252 (0x109c)
        14:  [2009/Jun/18|10:31:54]    Executing ""C:\Program Files\Autodesk\3ds Max 2010\3dsmax.exe" -server C:\Program Files\Autodesk\3ds Max 2010\network\vraydummy2010.max"

      Comment


      • #4
        Sounds like an old problem with 09 upon first install where it would close and restart repeatedly.

        The solution was to run backburner and have the slave connect to it. Then run the Vray spawner - it should work afterwards.
        LunarStudio Architectural Renderings
        HDRSource HDR & sIBL Libraries
        Lunarlog - LunarStudio and HDRSource Blog

        Comment


        • #5
          1) Started backburner Manager+Monitor
          2) Started server.exe on slave
          3) See slave on Monitor, slave has both 2009 and 2010 registered
          4) Start vrayspawner2010 on slave
          5) Try rendering again with DR, same deal Get a "Render host unknown(x.x.x.x) is not responding" now.

          Comment


          • #6
            You can take a look at the Max.log file (it should be somewhere in your local user settings folder) - perhaps it will contain some useful information. You can also first redirect the V-Ray log file (e.g. to c:\vraylog_test.txt) before submitting the scene (so that it does not get overwritten when the 3ds Max copy on the render slave is restarted) and then check the file on the slaves for any clues.

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

            Comment


            • #7
              Thanks Vlado, that helped me pin it down! This was the problem:

              I'd installed VRay on the machine, but I also have all plugins in a network location, so it was loading up both the local and networked vray plugins. Deleted the local ones (so it keeps the dll's and license stuff) and it is now fine!

              Comment

              Working...
              X