VRay Home ::
VRay Documentation Home
System requirements
- A computer with 3dsmax 6/7/8/9 or VIZ 2005/2006/2007;
- Windows 2000/Windows XP/Windows 2003 Server;
- Intel Penium III or compatible processor at 400 MHz minimum (dual
Pentium IV or AMD Opteron or later recommended);
- 128 MB RAM and 350 MB swap minimum - recommended 1 GB or more RAM, 2.5
GB or more swap.
Automatic installation
1.
Double-click on the installation file and follow the instructions. During
the installation process you will be prompted for the root directory of
3dsmax, a directory where to install the VRay plugin files and a folder
where to install additional files required by VRay.
2. Currently the installation only includes a 32-bit version of the
required WIBU-key drivers. If you are installing on a 64-bit operating
system, you need to download and install manually the WIBU run-time
components from http://wibu.com
3. Refer to the
licensing
section for information on how to set up your license once the
installation is complete.
Manual installation
1. Unzip the file corresponding to your version of 3dsmax into the root
folder of 3dsmax (referred to as <maxroot> in the
rest of this section). This will automatically extract the files required by
VRay into the corresponding folders.
2. If you want to use the additional VRay plugins (VRayFur,
VRayPlane, VRayToon
etc), add the path to them to the plugin.ini file
in the root folder of 3dsmax:
[Directories]
Standard MAX plug-ins=<maxroot>\StdPlugs
Additional MAX plug-ins=<maxroot>\plugins
.....
VRay additional plug-ins=<maxroot>\plugins\vrayplugins |
Note that the vrayplugins folder must be listed after
the plugins folder itself.
3. If you plan to run the VRay license server on the machine, you will
also need to manually install the WIBU-key drivers required for the
operation of the VRay license server. To install the drivers, you must
execute the file WkRuntime.exe which is extracted
in the <maxoot>\VRay folder. Currently only the
32-bit version of the drivers is included in the VRay installation. If you
are installing on a 64-bit operating system you need to download and install
the 64-bit version of the WIBU run-time components from
http://wibu.com
3.1. If you plan to run the VRay license server on the machine, you will
also need to move the <maxroot>\[COMMONFILES]\ChaosGroup
folder inside your system Common files folder (so
typically the final result would be C:\Program
files\Common files\ChaosGroup).
4. Refer to the
licensing
section for information on how to set up your license.
Installing distributed rendering (DR) for 3dsmax R6/R7/R8 /R9
You don't need to set up the render client, since it automatically takes
part in the DR. For the render servers, follow these steps:
1. Install VRay on all the render servers you want to use for DR.
2. While render slaves do not require a separate license in order to
render, you must tell VRay where to look for the VRay license server. You
can do this either from the 3dsmax interface, or with the small external
program setvrlserviceXX.exe (where XX is 60 ). If
you installed VRay from a .zip file, this program is located in the
<maxroot>\VRay folder. If you installed VRay
with the installer, you can access this program from the Start menu (Start
menu > Programs > Chaos Group > VRay for 3dsmax > Licensing >
Administration > Change VRay client license settings). See the
licensing
section for more information on how to set up the license for render
slaves.
3. If you are using Autodesk VIZ for rendering, you need to create a file
vrayspawner.ini in the root folder of Viz on each render
server and add the following text in it:
[Directories]
AppName=<path to the 3dsviz.exe file> |
Replace the text in brackets
<>
with the full path to the file 3dsviz.exe, for example
C:\Program
files\Autodesk\Viz2006\3dsviz.exe
4. On each render server, start the file vrayspawnerXX.exe (where XX
is 60 ). This file should be in the root folder of 3dsmax.
That concludes the installation of VRay DR on the render slaves. You
don't need to start the vrayspawnerXX.exe file on the
client machine, since it automatically takes part in the distributed
rendering.
See the
Distributed rendering section for more information.
|