Page 1 of 2

Multiple machines, different results(Deadline)

Posted: Sat Aug 25, 2018 12:13 am
by horizonmark
Here is our setup. Cinema 4D, Octane, Deadline, and a Mac server (ick)

We finally got everything working with all of these things. A few problem: Across 3 different machines, we are getting different results in Octane. Sometimes the textures and skyboxes pop in and out on different frames, sometimes the materials turn on and off on different frames. Our renders are looking like an ugly, ugly rave party.

Does anyone know what's up?

Re: Multiple machines, different results

Posted: Sat Aug 25, 2018 1:57 am
by niestudio
Are all of your standalone and plugin versions in sync?
What versions?

Have you checked the octane texture manager on each machine to make sure it can see all the textures etc?

Re: Multiple machines, different results

Posted: Sat Aug 25, 2018 10:57 am
by aoktar
Please figure it better by putting images and version info which is used in c4d and slaves.

Re: Multiple machines, different results

Posted: Sat Aug 25, 2018 12:19 pm
by horizonmark
When I head into work I will get that info to you. To the best of my knowledge, these are all fresh installs of both C4D and Octane. Latest versions.

Re: Multiple machines, different results

Posted: Sun Aug 26, 2018 11:12 am
by aoktar
Better to figure out by exact and visible information. Including numbers of versions. Not like saying "latest stables, etc.." please! Thanks for helping the development.

Re: Multiple machines, different results

Posted: Mon Aug 27, 2018 6:04 pm
by horizonmark
Hey aoktar,

It might be something with Deadline render.

(I created simple basic scene with cubes, saved, submitted, rendered, then deleted) then (added spheres, saved, submitted, rendered and only the cubes were rendered. So it may be a Deadline issue we are running into, which would be why the materials and stuff are popping on and off. I'll keep you in the loop if I get more info.

Re: Multiple machines, different results

Posted: Mon Aug 27, 2018 7:36 pm
by aoktar
horizonmark wrote:Hey aoktar,

It might be something with Deadline render.

(I created simple basic scene with cubes, saved, submitted, rendered, then deleted) then (added spheres, saved, submitted, rendered and only the cubes were rendered. So it may be a Deadline issue we are running into, which would be why the materials and stuff are popping on and off. I'll keep you in the loop if I get more info.
Sphere is a special case. You need to switch off "render perfect" option.

Re: Multiple machines, different results

Posted: Tue Aug 28, 2018 1:51 pm
by horizonmark
You are correct. That's all set.

But now, and I suspect this is related to all our other issues - if I have an Octane sky pointing to an HDR (and the HDR is inside the tex folder) - when rendering between different machines, the HDR will vanish on other machines - but it will appear on others. We just get the default Octane background color, as if the HDR isn't even there.

I'm wondering if this is related to our texture issue (flickering and sometimes the materials show as transparent)

I'm going to render you an example real quick here

I attached the images.

So one machine is rendering almost correctly (notice the one leaf is grey) and the other machines just does'nt know what's going on. If I render these locally, there are zero issues. Over the network however? Disaster.

Deadline Client Version: 10.0.17.7 Release (b00c030fe)
LATEST Octane 3 versions (and plug-in) for all machines
C4D R19 (latest version)

Re: Multiple machines, different results

Posted: Tue Aug 28, 2018 3:33 pm
by aoktar
Only reason which comes to mind that's not found the used textures in clients. Make a small test scene with a textured material and simple objects. Try on deadline if textures are visible or not.

Re: Multiple machines, different results

Posted: Tue Aug 28, 2018 6:07 pm
by horizonmark
Created a very simple scene, having the same issue.

We called the folks at Deadline to see what it could be - it could potentially be a permissions issue where the other render machines are not being allowed to access the textures in the repository. I'll keep you updated once we do some testing to see if this is indeed the issue.