• 3d Max Vray Tutorial
• 3ds Max Vray Materials
• 3ds Max Vray Tutorial Pdf

Experience the joy of Corona for 3ds Max. Download a free 45 day unlimited trial / demo. There are no resolution limitations or watermarks and you can even use it for. System Requirements. This page provides information on what hardware and operating systems are required for V-Ray to work properly. Autodesk® 3ds Max.

Before you can showcase your 3D designs, you need renders of your work that really pop. Learn how to render with Rhino and V-Ray in this course, which includes three fun sample projects: a penguin with glasses, a retro TV frame, and a funky birdhouse. First, author Dave Schultze shows how to install V-Ray and demystifies 3D concepts such as global illumination and raytrace rendering. He demonstrates techniques for rendering quickly with both Rhino's built-in rendering and V-Ray, and explains how to customize materials, enhance them with texture mapping, and add realistic surface textures using bump and displacement maps. Along the way, Dave shares insider tips and tricks on rendering, while showing how to get the right lighting for your scene, use color correction tools, and render with the V-Ray frame buffer.

Topics include:. Why use V-Ray?.

Installing DR Spawner. Understanding 3D terminology. Activating V-Ray. Adjusting quality settings. Get quick previews with the material override. Understanding lighting types. Exploring materials in the Material Editor.

Creating your own materials. Texture mapping materials with bitmaps and procedurals. Saving time with V-Ray presets.

Getting the right size for your render with output settings. Working with environment lighting.

Strategies for working with cameras and camera settings. Ensuring accurate color for your scene with color correction. Rendering tips and tricks. You started this assessment previously and didn't complete it. You can pick up where you left off, or start over. Resume Start Over VRay for SketchUp Manual Distributed Rendering Distributed Rendering is the capability to render a single image across multiple computers.

This has the possibility of utilizing multiple computers which can greatly increase rendering speed. VRay can use up to ten computers with just one license. In order for V-Ray to utilize these extra machines there are two things that need to be done. First, there needs to be a way for V-Ray to actually use the other machine.

Secondly, V-Ray needs to be told to look for those machines. The way in which V-Ray communicates with other computers (known as the slave machines) is through a stand alone application which is installed and run on the slaves.

Any machine which has V-Ray for SketchUp installed on it should have the Distributed Render Spawner already on the machine. If it does not, or you would like to install the DR Spawner that does not have V-Ray for SketchUp you will need to access your installation file or disk. Once the installation is started you will need to choose Custom setup type. Within the custom setup there will be four components, one of them being the DR Spawner. Disable all of the other components and click next to install the DR Spawner.

The last piece of information that you will need in order to utilize the slave machine is the IP address. You can get this one of two ways. The first is to go to Network and Internet Connections in the Control Panel. From there double click on Network Connections. This will bring you to a window containing all of your internet connections. Double click on the connection you intend to connect through and that will bring up dialog box containing the status of that connection. At the top, click on the second tab labeled Support.

Take note of the IP address as you will need this information in a few moments. The second way of retrieving your IP address is to use the run command. You can get this by going to the start menu and clicking on Run. Now type IPCONFIG which will tell you the IP address of you machine. If your computer only flashes the result, than you can type CMD.EXE into the Run window and then IPCONFIG in the resulting DOS interface. Once the DR Spawner is installed on the slave machine you will need to start the application. In the folder C: Documents and Settings All Users Application Data ASGvis you will find a folder called DRSpawner.

Open that folder and you will find the DR Spawner. Double clicking on the DR Spawner will launch it, and once it has successfully loaded the Spawner it is ready to go. Now that the slave machines are ready to go we need to tell the main computer where to render from, also known as the client, not only that, we will be using other computers to render but also how to access them. This is very simple as well. Within the Systems rollout of V-Ray's options you will see a checkbox and button for Distributed Rendering. To enable Distributed Rendering simply click the checkbox next to the button. Clicking on the button will bring up a window which will allow you to input the IP addresses of any slave machines you wish to use.

Within the Distributed Rendering window at the top you will notice the option to Add a Server. This is where you will input the IP addresses of any machines that you will connect to. After you input any IP addresses you will want to click Resolve servers. With using Distributed Rendering you might run into several possible issues. When trying to connect to slave machines you may have issues of not actually getting them to render.

Check any firewalls that may be on the host or slave machine as well as any routers that you may have. Also, textures will not be transferred to the host machine by the DR software. Optimally, textures should be in a single network location that is accessible to all machines being used, but if this is not possible then you must manually transfer the textures manually to a folder on the slave machine(s) that is the same path as on the host machine. Also, if you have the capability to use Remote Desktop Connection or a similar software, it may make the task of monitoring slave machines an easier task. VRay for Rhino Manual Distributed Rendering Distributed Rendering is the capability to render a single image across multiple computers.

This has the possibility of utilizing multiple computers which can greatly increase rendering speed. V-Ray can use up to ten computers with just one license. In order for V-Ray to utilize these extra machines there are two things that need to be done.

First, there are needs to be a way for V-Ray for actually use the other machine. Secondly, V-Ray needs to be told to look for those machines. The way in which V-Ray communicates with other computers ( know as the slave machines) is through a stand alone application which is installed and run on the slaves. Any machine which has V-Ray for Rhino installed on it should have the Distributed Render Spawner already on the machine. If it does not, or you would like to install the DR Spawner that does not have V-Ray for Rhino you will need to access your installation file or disk. Once the installation is started you will need to choose Custom setup type.

Within the custom setup there will be four components, one of them being the DR Spawner. Disable all of the other components and click next to install the DR Spawner. The last piece of information that you will need in order to utilize the slave machine is the IP address. You can get this one of two ways.

The first is to go to Network and Internet Connections in the Control Panel. From there double click on Network Connections. This will bring you to a window containing all of your internet connections.

3d Max Vray Tutorial

Double click on the connection you intend to connect through and that will bring up dialog box containing the status of that connection. At the top, click on the second tab labeled Support. Take note of the IP address as you will need this information in a few moments. The second way of retrieving your IP address is to use the run command. You can get this by going to the start menu and clicking on Run. Now type IPCONFIG which will tell you the IP address of you machine.

If your computer only flashes the result, than you can type CMD.EXE into the Run window and then IPCONFIG in the resulting DOS interface. Once the DR Spawner is installed on the slave machine you will need to start the application. In the folder C: Documents and Settings All Users Application Data ASGvis you will find a folder called DRSpawner. Open that folder and you will find the DR Spawner. Double clicking on the DR Spawner will launch it, and once it has successfully loaded the Spawner it is ready to go. Now that the slave machines are ready to go we need to tell the main computer that we are render from, also known as the client, not only that we will be using other computers to render but also how to access them. This is very simple as well.

Within the Systems rollout of V-Ray's options you will see a checkbox and button for Distributed Rendering. To enable Distributed Rendering simply click the checkbox next to the button. Clicking on the button will bring up a window which will allow you to input the IP addresses of any slave machines you wish to use. Within the Distributed Rendering window at the top you will notice the option to Add a Server. This is where you will input the IP addresses of any machines that you will connect to.

After you input any IP addresses the folder C: Documents and Settings All Users Application Data ASGvis you will find a folder called DRSpawner. Open that folder and you will find the DR Spawner.

Double clicking on the DR Spawner will launch it, and once it has successfully loaded the Spawner it is ready to go. You will want to click Resolve servers. With using Distributed Rendering you might run into several possible issues. When trying to connect to slave machines you may have issues of not actually getting them to render.

Check any firewalls that may be on the host or slave machine as well as any routers that you may have. Also, textures will not be transferred to the host machine by the DR software. Optimally, textures should be in a single network location that is accessible to all machines being used, but if this is not possible then you must manually transfer the textures manually to a folder on the slave machine(s) that is the same path as on the host machine. Also, if you have the capability to use Remote Desktop Connection or a similar software, it may make the task of monitoring slave machines an easier task. This page introduces and provides information on setting up Distributed Rendering. Page Contents Overview Distributed rendering is a technique for distributing a single render job within a single frame across many computers in a network. There are different approaches of doing this, but the main concept is to reduce the render times by dividing different parts of the rendering pipeline and giving each participant different parts of the job.

The most common way to do this is to divide the frame to be rendered into small regions (buckets) and give each machine to render a number of them; then get the results and combine them into the final image. Organization V-Ray supports DR. It divides the frame into regions and spreads them across the participants in the distributed rendering. This is done completely through TCP/IP protocol which is the standard protocol of the Internet and thus the most common protocol that is supported by the hardware. V-Ray itself does not need additional file or directory sharing (note that you may actually need some file/directory sharing for the bitmaps or other additional files used during rendering). The distribution management is divided into Render Clients and Render Servers. Render Clients The render client is the computer that the user is currently using and from which the rendering is started.

It divides the frame into rendering regions and spreads it across the Render Servers. It distributes data to the render servers for processing and collects the results. Render Servers A render server is a computer that is part of the so-called render farm - it requests render data from the render client, processes it and sends the result back. Installation notes. If you create a fresh install of 3ds Max on a machine, you will need run at least one Backburner job with this machine as a server, before you can use the machine for distributed rendering. How to Test First start with the testing of the render server: Start the vrayspawnerXX.exe program from the Start menu (Start menu Programs Chaos Group V-Ray for 3dsmax Distributed rendering Launch V-Ray DR spawner).

3ds Max Vray Materials

It will automatically try to find the 3dsmax.exe file and start it in server mode. You should end up with 3dsmax minimized down in the task bar. It should have the title 'vraydummy.max'. If 3ds Max stays there alive without closing then you have the Render Server part working. If you see the a 3ds Max window flashing on the taskbar and then disappearing, right-click on the V-Ray DR spawner icon in the taskbar tray, select exit to close the DR spawner, and try running a regular Backburner job with this machine as the server. After that, try to start the V-Ray DR spawner again.

Now test the render client: Open your 3ds Max as you normally would. Open a scene you would like to render (preferably a simple one for this test).

Choose V-Ray as your current renderer and make sure you have checked Distributed Rendering ON in the V-Ray System section. Press the Settings button in the Distributed Rendering section. Add the machines used for rendering – either with their IP address or their network name and close the dialog. Render the scene as you normally would. You should see the buckets rendered by the different servers. If Something Fails Practically every action taken by V-Ray DR is logged. You can find all the log files in the C: directory and find out what has failed.

If you do not understand the problem, you can compress and send the files to us to analyze them and eventually try to help - If any of the servers fails, you should get a notification and the render client will try to reassign the buckets to another server. Distributed Rendering Settings The Distributed rendering settings dialog is accessible from the rollout of the renderer settings.

The settings themselves are stored in a text file called vraydr.cfg, which is located in the 3ds Max plugcfg folder (normally, this is located in the local application data folder for the current Windows user). Add server – Allows the user to manually add a server by entering its IP address or network name.

Edit server – Allows the user to change the data about a render server. Remove server – This button deletes the currently selected server(s) from the list. Resolve servers – This button resolves the IP addresses of all servers. Restart slaves on render end – Enabling this option will cause the 3ds Max copy on the render slaves to be restarted once a DR rendering is finished. This may help to make distributed rendering more stable. Save servers in scene – This option causes V-Ray to store the list of render servers into the 3ds Max scene. This is useful if the scene is later sent to backburner for distributed rendering.

In that case, instead of taking the DR servers list from the vraydr.cfg file on the machine where the backburner server is running, the list will be taken from the 3ds Max scene. Max servers – Allows the user to limit the maximum number of servers from the list to be included in distributed rendering. When set to 0, all listed servers will be used. Use local host – When enabled, the client machine (the one from which the user initiates the DR render) will also take part in the rendering calculations. If disabled, the client machine only organizes the DR process, sends rendering tasks to the render servers and displays the final result.

Transfer missing assets – Allows render servers to automatically download missing rendering assets from the client machine. This includes textures, V-Ray proxy files, IES profiles, GI solution caches (irradiance map, light cache), X-Ref scenes etc. Use cached assets – This option tells the render servers to keep the downloaded rendering assets between different DR sessions. If disabled, the render assets are automatically deleted once the render server disconnects from the client machine at the end of the rendering. When enabled, assets are kept in a folder on disk. By default it is named vrayassetscache located in the temporary folder for the user that runs the V-Ray DR spawner.

The location of the assets cache can be modified with the environment variable VRAYASSETSCACHEPATH. Modified assets are generally detected and re-transferred to the render servers even though they may already exist in the render servers' caches.

Cache limit type – Allows the user to specify under what conditions the assets cache is cleaned up. The possible values are: None – Assets are never deleted from the render servers' cache. Age (hours) – Assets are kept for the specified amount of time. At the end of the rendering, the render servers will delete assets that have been transferred before the specified time limit. Size (GB) – When the size of the assets on a render server exceeds the specified amount, least recently used assets are automatically deleted at the end of each render until the folder size is less than the limit. Cache limit value – The specific value of the limit for the asset cache. This is either hours or GB, depending on the value of Cache limit type.

V-Ray DR Spawner command line options You can add command line options to the VRaySpawner. You can specify Numa command line options to VRaySpawner.exe to better utilize processor nodes with Numa architecture: -numa=N - select the number of slave processes to start.

If N is not given, N=0 or N=M, one process per NUMA node will be created. Here 'M' is the number of selected nodes using '-node', or the number of all available NUMA nodes if no '-node' is used. select NUMA nodes that will be used for the slave process(es). Default - use all available NUMA nodes. select listening ports for the slave process(es).

If the number of processes is greate than the number of ports given, the last port is auto incremented. The default listening port is 20204 for 3ds max. The render client should be set to use the corresponding port range. Every render server must have all the plugins and texture maps in their proper directories loaded so that the scene you are sending will not cause them to abort.

3ds Max Vray Tutorial Pdf

For example having a PHOENIX plugin used in the scene will cause a server failure in any of the servers that do not have the PHOENIX plugin installed. If you have mapped your object with a file named JUNGLEMAP.JPG and you do not have that map in the BITMAPS directories of the render server installation - you will get bucket rendered at that machine as if the map was turned off, unless you also turned on the Check for missing files option in the V-Ray rollout, in which case the render server will refuse to render the scene. When you cancel a DR rendering, it may take some time for the render servers to finish working and they may not be immediately available for another render.

Default lights are not supported in DR mode and will not render. If you need any lighting in the scene, you should add it explicitly. The default system temp folder, usually C: Users AppData Local Temp on Windows (%TEMP%), is used for copying the assets if the VRAYASSETSCACHEPATH environment variable is not set. V-Ray supports DR. It divides the frame into regions and spreads them across the participants in the distributed rendering.

This is done completely through TCP/IP protocol which is the standard protocol of the Internet and thus the most common protocol that is supported by the hardware. V-Ray itself does not need additional file or directory sharing (note that you may actually need some file/directory sharing for the bitmaps or other additional files used during rendering). The distribution management is divided into Render Clients and Render Servers. Render Clients The render client is the computer that the user is currently using and from which the rendering is started. It divides the frame into rendering regions and spreads it across the Render Servers. It distributes data to the render servers for processing and collects the results. Render Servers A render server is a computer that is part of the so-called render farm - it requests render data from the render client, processes it and sends the result back.

Add server - this button allows you to manually add a server by entering its IP address or network name. Remove server - this button deletes the currently selected server(s) from the list. Resolve servers - this button resolves the IP addresses of all servers. Local Machine Only 1.

Enable Distributed Rendering by making sure 'On' is enabled from the rollout. Enable 'Don't use local machine'. One limitation with this feature is that Light Cache calculations are NOT visible in the the V-Ray frame buffer. Open the Distributed Rendering Settings and choose add server and input the IP address of 127.0.0.1 and chose OK. Render the scene as you normally would. You should now see the rendering buckets labeled with the name of your local machine.

In the task manager your will see that XMLDRSpawner CPU usage is high, at around 90%, and the SketchUp process should be using very little CPU. To render using distributed rendering the XMLDRSpawner must be running. By default on your local machine V-Ray will try to identify if your machine is running a 64-bit opertating system and it will automatically start the 64-bit version of the XMLDRSpawner.

However, you can start or restart the 64-bit render server manually as follows:. Start the XMLDRSpawner.exe program from the Start menu ( Start menu Programs Chaos Group V-Ray for SketchUp Distributed rendering 64-bit Launch the distributed rendering spawner). It will automatically open a command prompt window. Rendering Servers Only 1. Start the 64-bit render server on your rendering servers manually as follows:.

Start the XMLDRSpawner.exe program from the Start menu ( Start menu Programs Chaos Group V-Ray for SketchUp Distributed rendering 64-bit Launch the distributed rendering spawner). It will automatically open a command prompt window. Enable Distributed Rendering on your local machine by making sure 'On' is enabled from the rollout. Enable 'Don't use local machine'.

Open the Distributed Rendering Settings and choose add server and input the IP address of each of your rendering servers. Render the scene as you normally would. You should see the buckets rendered by the Server Name. In the task manager of your local machine your will see that XMLDRSpawner has no CPU usage and the SketchUp process should be using very little CPU.

By » Thu Nov 15, 2012 6:42 pm I'm trying to run a DR render on two mac. Unfortunately, during the rendering, it is used only computer's master processor. By » Thu Feb 13, 2014 12:50 pm Hi, I'm working on a PC, with skp8 & vray 1.49.01 installed, but I also have 3 imacs available.

I'd like to set distributed renders on the 3 macs, from my PC. (all machines are working on the same gigabit network, whit a storage nas) SO I installed vray DRspawner on the iMacs, but I'd like to know if that's possible to set a DR between mac & PC?

All the materials, textures & ies are stored on the same nas, accessible from all machines. My main issue is that on my PC, materials path is something like Z:/FOLDERS/Material.jpg Although the macs are using this kind of path: /Volumes/FOLDERS/Material.jpg So, if I let the Z:/, the macs can't find materials. That's surprising, but when I set the 'mac style path' (starting by /Volumes.) in vray (on the PC), the PC can find the textures, and of course, the imacs can find the texture too. So, no problem for the materials, since I rewrite the paths, by replacing Z:/ by Volumes/ But it's not working for IES.

When I set a /volumes/ path to ies lights. The PC can't find them, and I get dark renders:/ Any idea? Is it there an other way to set DR between mac & PC? What is Distributed Rendering (DR) Spawner? Distributed Rendering is the capability to render a single image across multiple computers.

This has the possibility of utilizing multiple computers which can greatly increase rendering speed. VRay can use up to ten computers with just one license. An expert in the field of Distributed rendering is Edgar 'rodrigonotor' Navas. I asked him if I could share in this blog his tutorial and he gave me a permission to post this excellent tutorial here. Tutorial: How to set up the DR Spawner by Edgar Navas Firs of all, you have to connect yours PCs in a LAN (Local Area Network) and know each IP address.

By default, Windows OS come with activated, which is the hub that assigns the IP addresses of each pc. In my case, for practical reason I made my LAN with static IPs. The default IP address is 192.168.xx.xx. I use another because I manually assign IP address to a specific PC. I use 172.16.25.xx Ok, going back to IPs issue, to know what is the IP address of each PC, in the windows star menu, choose run and then CMD.

A window like this should appear. Inside the DOS windows, you have to type ipconfig and then key enter o intro and the screen will look like this. In my case, my IP address is 172.16.25.7 this can be done in each PC that you want to connect whit DR Spawner. Second an important thing to know, probably you have installed V-ray without Distributed Rendering Spawner, again run the installer an choose only the DR Spawner option. Don`t close that window. The third important thing to know is the Window Firewall. You need to set up permissions to the Windows Firewall.

Ok, almost done, to make sure that the Master is connecting to other PCs run CMD again and type (in my LAN is) ping 172.16.25.xx -t where xx is the number or numbers assign to each PCs Now the LAN is ready to make a Distributed render In V-ray Options-System check box ON and then click to the button with 3 points Here is for config the hosts (slaves) add server write the IP address and OK Enter all hosts or servers, click on the button resolve servers and check the IP addresses that we have entered. Check the box for each server And done, Distributed Rendering Spawner it's configured. Distributed Rendering Spawner Off Distributed Rendering Spawner On. Starting Distributed Rendering Spawner On.

Distributed Rendering Spawner On. Almost finished Best Regards (Saludos), Edgar Navas Our cinematics are packed with action – huge environments, crowds of characters with hair and SSS, fire, explosions, and debris – all with 3D motion blur and render passes. It’s a lot to work with, but V-Ray makes it easy to get the job done. Kevin Margo, Director & VFX Supervisor, Blur. This page provides information on the Distributed Rendering rollout in the Render Settings.

Page Contents Overview Distributed rendering is a technique for distributing a single render job within a single frame across many computers in a network. For more information, please see the page in the section of this documentation. UI Path: Render Settings window Settings tab Distributed rendering rollout Parameters Use distributed rendering – Enables additional parameters and settings needed to distribute the rendering across additional computers. Use local machine – The client/local machine will function as a render server along with the other computers used to complete the rendering task. Disabling will mean all rendering will be done on other machines apart of the DR set up. Ignore in batch mode – Distributed rendering will not be utilized when rendering is set to Batch Mode. Transfer missing assets – A llows render servers to automatically download missing rendering assets from the client machine, including textures, V-Ray proxy files, IES profiles, GI solution caches (irradiance maps, light caches), etc.

Used cached assets – Tells the render servers to keep the downloaded rendering assets between different DR sessions. If disabled, the render assets are automatically deleted once the render server disconnects from the client machine at the end of the rendering. When enabled, assets are kept in a folder on disk.

By default, it is named vrayassetscache located in the temporary folder for the user that runs the V-Ray DR spawner. The location of the assets cache can be modified with the environment variable VRAYASSETSCACHEPATH. Modified assets are generally detected and re-transferred to the render servers even though they may already exist in the render servers' caches.

Cache limit type – Allows you to specify under what conditions the assets cache is cleaned up. The possible values are: None – Assets are never deleted from the render servers' cache Age (hours) – Assets are kept for the specified amount of time. At the end of the rendering, the render servers will delete assets that have been transferred before the specified time limit. Size (GB) – When the size of the assets on a render server exceeds the specified amount, least recently used assets are automatically deleted at the end of each render until the folder size is less than the limit. Cache limit value – The specific value of the limit for the asset cache. This is either hours or GB, depending on the value of Cache limit type. Overwrite local cache settings – Available when Transfer missing assets and Use Cached Assetsis enabled.

Enabling will make the render nodes ignore their local settings for how long they'll keep a transferred asset if any such settings have been placed. Instead, the nodes will use the settings from the host's Maya render settings. Distributed Rendering Settings This window is opened by clicking the Settings. button.

These options set the machines V-Ray will use for Distributed Rendering. When using CPU Rendering, changes can be updated during rendering. Server name or IP address – A text field to enter the name or IP address of the machine to use as a DR server(slave) Port number – Specifies the port number at which the DR server operates.

Server alias/description – A text field to place notes about the particular DR server. Add server – Allows a manual way to add a server by entering its IP address or network name. Remove server –Deletes the currently selected server(s) from the list. Toggle status – Toggles the state of the selected server(s) between enabled and disabled Edit – Modifies the information for the selected entry in the list. Limit used DR servers – When several DR servers are available, sets an upper limit to the number of servers used for rendering.

Sort list by – Organizes the server list by Server name / IP address, Port number, Status or Server alias / description. Resolve servers – Refreshes the list of server names to IP addresses. Close – Closes the Distributed Rendering settings window. Step-by-Step DR Set Up 1. Set-up the Render Servers. You can do that in two different ways. 1.1 Start the render servers as specified in the.

1.2 Start the V-Ray Stand Alone and enter the 'vray -server' command in the command prompt. Set-up the Render Client.

In the Maya interface, open the Render Settings window, in the Settings tab under the roll out click on the Settings button in the Distributed Rendering group. Add all the Render Servers by inputting their IP's in the Add Server name or IP field and click on the Add Server button. You can include or exclude the servers in the list in the current rendering by selecting them from the list and toggling the Toggle Status button.

When you cancel a DR rendering, it may take some time for the render servers to finish working and they may not be immediately available for another render. Servers can be added, removed, enabled, and disabled while running a CPU distributed render. For GPU rendering, DR settings can not be changed during the render. When using progressive rendering, nodes can only be added or enabled while rendering. While rendering, some of the options will be disabled Stop the render to make adjustments. Distributed rendering on MacOS X via Autodesk© Backburner©: since Backburner© gets started as root user (hence V-Ray is started as a root user as well), V-Ray would not find some files needed to properly setup distributed rendering. The solution to this problem is to copy the files: serverlist.tmp, serverstatus.tmp, serverports.tmp, serveralias.tmp and vraydrlimit.tmp from the desired user's settings (/Users/.username./.Library/Preferences/Autodesk/maya) to /Applications/ChaosGroup/V-Ray/.mayaversion.

Additionaly, one more file needs to be edited in order for vray to funtion properly under Backburner environment: add the string 'export VRAYAUTHCLIENTFILEPATH=/Users/.user./.ChaosGroup/vrlclient.xml' to '/etc/profile' — this ensures V-Ray will know where to load its license from!

The crack for 1.5sp2X32 bit works, it slows a bit the things which is not that bad, however, the main problem is that there are watermarks all over the rendered picture. So, Andy, when you install vray, and then run the crack, you will see 3 buttons, click on the first one and navigate to the the autodesk, 3dmax2009 folder, and there you will see the 2009.dll. Select it and click Open, and there you have it. You can work with Vray settings. But as I said, it has watermarks allover the pic.

Hope someone can find something that has no watermarks and it’s faster. Vray evermotion toturials http://rapidshare.com/files/117181912/51materialvelvet.avi.html. How to do install vray 3dsmax 2009 without watermarker mirror: vray maya 2008 for mac x86 vray maya 2008 for linux x64 http://rapidshare.com/files/121952741/vrayAdv08523maya2008linuxx64.zip.html.