HI,
I am a new user to deadline and have what should hopefully be an easy question.
With render tiling, we are getting inconsistent tile stitching, even with maximum tile pixel padding
Other than per-calculating the GI solutions manually, is there a way to achieve cleaner results (via a script or option we are missing)?
Thanks in advance.
Hi,
You shouldn’t need to use pixel padding at all (normally). Could you post to this thread the log report and/or the error you are getting?
Do you mean the tiles are stitched into incorrect final positions or something like the lighting is incorrect on some of the tiles?
If the tiles are slightly different tones, then you need to ensure you cache any lighting calculation initially. Settings depend on renderer being used. Which renderer / lighting system are you using?
Sorry, yes the lighting is inconsistent between the tiles. We are using VRAY and would like to avoid manually pre-calculating the lighting as this adds an extra step to what is supposed to be streamlining.
Is there any script available to have one machine calculate the initial lighting solutions, and then all the machines to render the tiles?
Thanks for your response.
Hello,
So based on looking into this, that doesn’t seem to be something that Deadline is doing, and we don’t have anything built in to do it right. I am not sure if Mike would have some input to add, but the best answer I got was to check with Chaos group for more advice on how to work that.
Cheers,
Hello,
As Tile rendering is basically rendering a region of the overall image resolution on loads of machines, the only way to get consistent lighting is to pre-cache (pre-pass in VRay words) the 3D file first. No real need for any ‘special’ script, you can just submit the job to Deadline with the necessary settings in VRay set to calculate the lighting but NOT to render the actual frames out (you can use Machine Limit or whitelisting to control which machine is used) and then either submit the job a 2nd time to do the actual rendering but of course, without the MachineLimit/Whitelist limitation and then it will render on the whole farm OR in monitor, re-submit the job (suspended first), tweak the settings and then you can drag’n’drop it onto the first pre-pass job to make it dependent, so it won’t start until all the pre-pass frames have been calculated.
Different studios all like to do this workflow differently. 
Thanks very much mike. This is the workaround we have currently been using, so i suppose we will stick with that. Just wanted to see if perhaps there was a script to shortcut the 2 steps.
I will contact chaos group to see if they have any other options.
Thanks again.
Hi,
I’m just testing the 6.1 beta 5 with tiles render/Vray DR rednering, and multiregion rendering.
Am I right in thinking that you can only get tiles rendering to work correctly if you use the max frame buffer and save, not the Vfb and element save? If so can you tiles render and render elements? I’ll no in 10 minutes cos I’m testing!
Just trying to work out the best workflow for us going forward when rendering massive frames, with elements - tile or DR, and then use multiregion when making small changes.
Mark
Hi Mark,
Lots of options…
Let’s talk about this on the beta forum, once you have had a chance to test?
Hi Mike,
I have now tested, shall I start a new thread on the beta forum?
Mark