It seems we have been having some odd behavior with rendering on our network. Sometimes it seems like when we make a change, one of the computers we are hooked up to keeps some of the samples from before the change, and then applies it to the final. We get some ghosted images sometimes where the change took place.
In the attached image, I changed the resolution from 1k to 5k wide. I went to bed and this is what I woke up to. It looks like one of the computers still had samples at 1k and then tried to apply them to our 5k wide image.
Anyone have anything similar?
Error with network render
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
That's totally weird and I have absolutely no idea how that can happen. The results that get mixed together are matched against each other and for this to happen two checks (one including the image size) would have to fail. So our running theory is that the slave actually rendered this image in the proper resolution but somehow with incorrect camera parameters. If you could answer those questions we may get a better idea what's going on here:kavorka wrote:It seems we have been having some odd behavior with rendering on our network. Sometimes it seems like when we make a change, one of the computers we are hooked up to keeps some of the samples from before the change, and then applies it to the final. We get some ghosted images sometimes where the change took place.
In the attached image, I changed the resolution from 1k to 5k wide. I went to bed and this is what I woke up to. It looks like one of the computers still had samples at 1k and then tried to apply them to our 5k wide image.
Anyone have anything similar?
Did this problem occur in Standalone?
Which version?
Can you reproduce the issue?
What is your net render configuration (how many slaves and how many GPUs each)?
Thank you,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
We are using Octane 2.06 stand alone.
We had 3 machines hooked up when we did this image:
Master: 2x 780ti
Slave 1: 1x 780ti 1x GTX 690
Slave 2: 1x 780ti 1x GTX 690
We have seen something similar happen on other images. If we change something in the obj and refresh, sometimes the old image gets ghosted over the new one.
This has only happened a couple of times, doesn't seem to be common.
We had 3 machines hooked up when we did this image:
Master: 2x 780ti
Slave 1: 1x 780ti 1x GTX 690
Slave 2: 1x 780ti 1x GTX 690
We have seen something similar happen on other images. If we change something in the obj and refresh, sometimes the old image gets ghosted over the new one.
This has only happened a couple of times, doesn't seem to be common.
Intel quad core i5 @ 4.0 ghz | 8 gigs of Ram | Geforce GTX 470 - 1.25 gigs of Ram