If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Exciting News: Chaos acquires EvolveLAB = AI-Powered Design.
To learn more, please visit this page!
New! You can now log in to the forums with your chaos.com account as well as your forum account.
when using DR each machine calcs its own IR map, or you can have them all use the same premade IR map in a place accessable by all machines.
-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 ■
i am doing much architectural stuff, so i am taking advantage of vrays light distribution capabilities and do not so much heavy raytracing. therefore irradiance map is the fastest way for me because irradiance map calculation takes most of the rendering time.
i getting two more machines today and wonder how to use DR for my work.
do you mean, irradiancemap calculation cannot be speeded up by distribution on more than one machine?
so, is direct computation the better choice for DR?
what you do is calculate your irradiance map on your local machine. Copy that irradiance map to a common local folder or network drive. you need to modify your ini file to point to these locations on all slave rendering machines, this is similar for textures. Then select DR from render box under system tab, after you have selected this make sure you chose render "from irradiance map".
Each machine will now use your precalculated map to render.
You dont have to edit the *.ini file. Just create the IR map on the local machine then put the file in to a folder accessable by all the render slaves. In "Advanced irradiance parameters" enter the path and file name of the saved IR map. As long as the DR is setup on all machines then it should work without a hitch.
-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 ■
True you do not have to modify the ini. But that only works if all renderslaves are mapped(direct connection) to your distributing machine, by way of UNC paths.
But if they are not mapped and you only have one license of viz and you have 10 machines to use dr.; you have to edit the ini file. This is to say that you do not want to use default max/viz folders. The problem with one license is that you cant open Viz on the render slaves. It asks you to authorize or if past 30 days, dialog box says expired. Therefore if you do not place all your files in default max locations you have to edit the ini file... suchs as; DIR30=C:\maps. Every new project I just cut/paste my textures and vrmps to it.
I have found to much traffic on the server causes errors in rendering using mapped computers. Therefore I am copying my textures and vrmps to each local rendering slave HD.
Its been working flawless. I simply created a batch file to open the connection to each machine, copy files from my MAPS folder locally to each render slaves MAPS folder and then close connection. That way I am not affecting other co-workers using the server.
Hope I am helping, I struggled with this for a couple of weeks at my office to come up with the best solution and I am extremely happy with the results.
Comment