OTOY Forums

Hello!

First post on the forums, so if I do something wrong, let me know!

I've been experiencing a weird issue, dunno if it's something with my setup, or if it's a setting somewhere, but I've been experiencing a noise block on my renders, even after rendering loads of samples. Saving the image after rendering, still has the noise block. Here's a reference image:



Any idea why this is happening? Is this because of my different models of cards? Any help would be wonderful!

My setup is:

2 machines

Both are connected via ethernet to each other, and both render fine, except for these noise blocks I see in the render

1st: Windows 10 Pro
2x GTX 1080
32GB DDR4 Memory
Nvidia Driver version: 368.81
Octane Render Standalone Version: 3.03.2
Octane Render Plugin Version: 3.03.2-R1
Maxon Cinema 4D R17.048

2nd: Mac OS X 10.11
2x GTX 980
16GB DDR3 Memory
CUDA Driver Version: 7.5.29
Octane Render Standalone Version: 3.03.2
Octane Render Plugin Version: 3.03.2-R1
Maxon Cinema 4D R17.048

Hi CrusaderArts,
I guess that you have the Minimize network traffic option active in the Kernel settings. At the end of the linked page you can find a brief description:
https://docs.otoy.com/manuals/products/ ... -lighting/
And here is a more detailed description about v3/v2 differences and about the overhauled work distribution in network rendering:
https://docs.otoy.com/manuals/products/ ... res-in-v3/

By the way, it would be very nice from you if you could share the rendering speed of your two machines on the same scene/frame. In this way we could have a rough estimation about the difference between 980 and 1080
ciao beppe

Hey,

I'll do some speed tests to see what the difference is between the 980s and 1080s I have.

As in terms of the issue, I already have the Minimize network traffic option active, but the issue seemingly still exists. I just did a test again on the same scene with network rendering disabled and the noise blocks are still there, My guess is that it has something to do with the experimental support of the 1080s. I also tested it with just my 980s, I didn't log the speed, but the noise box was gone.

I'm willing to provide the scene with the textures if it's needed for testing.

If there's anything else that needs to be done, then I'm willing to help out!

Thanks! Appreciate it!

David

Just did a speed test between the 2 machines on the same frame/same scene, here's the results:

1080s: Time to render 500 Samples: 6 Minutes, 39 seconds
980s: Time to render 500 Samples: 6 Minutes, 44 Seconds

Roughly around the same amount of time. 1080s still have that noise box, not sure what to do about that, if I can do anything about it.

CrusaderArts wrote:Just did a speed test between the 2 machines on the same frame/same scene, here's the results:

1080s: Time to render 500 Samples: 6 Minutes, 39 seconds
980s: Time to render 500 Samples: 6 Minutes, 44 Seconds

Roughly around the same amount of time. 1080s still have that noise box, not sure what to do about that, if I can do anything about it.

Could you send me the scene? Which of the computers is the master and which one is the slave?

Hey abstrax,

Here's the link to the scene via Dropbox: https://www.dropbox.com/s/5904neagj4a0v ... 1.zip?dl=0

The 1st machine, the one with the 1080s, is the Master, the one with the 980s is the slave.

Thanks! Hopefully we can find a fix for this.

David

Ok, it doesn't seem to be a net render issue but an issue with the GTX 1080 with this scene.

This is a render at 500s/px with only the GTX 1080 running: This the same render on a GTX 980 and a Titan Black: As you can see in the first image there is some invalid noise in the 1080 rendering, which seems to be worst in the top right tile. I don't know what the reason for that is, but it's not network rendering since I disabled it for the test.

Ah well, good to know that this isn't due to the network rendering.

Maybe we can investigate a little further into this, hopefully find the issue and fix it. You're free to use that scene for testing newer versions if needed to, It was just an everyday piece I was making for my everyday project.

Let me know if you manage to fix the issue.

Thanks abstrax,

David

CrusaderArts wrote:Ah well, good to know that this isn't due to the network rendering.

Maybe we can investigate a little further into this, hopefully find the issue and fix it. You're free to use that scene for testing newer versions if needed to, It was just an everyday piece I was making for my everyday project.

Let me know if you manage to fix the issue.

Thanks abstrax,

David

Yes, of course we will investigate and try to fix it. I will have a look at it in the coming days, just don't know yet what is going on therefor can't give an estimate when it will be fixed. It could be a CUDA issue or a bug in our code or something else.

I finally got around to properly investigate the issue and it's that same as this one: viewtopic.php?f=9&t=55380

Until the next Octane release is out, you could use either path tracing or direct lighting with mode diffuse GI. The problem affects Maxwell and Pascal GPUs.