nvidia driver: 344.16
gpu1: GTX 680
gpu2: GTX 760
OS: Windows 7 Pro x64
C4D: R15
octanePlugin: Version 2.12.1 - final (updated on 28.10.14)
p.s. added files:
after restart+new scene. DL kernel. + Difference Matte to see difference
+ one 4000x720 Difference Matte and pixels count
Version 2.12.2 - final (updated on 18.11.14)
Moderators: ChrisHekman, aoktar
Could you please send us a scene so we can reproduce this issue? Thanks.valters wrote:nvidia driver: 344.16
gpu1: GTX 680
gpu2: GTX 760
OS: Windows 7 Pro x64
C4D: R15
octanePlugin: Version 2.12.1 - final (updated on 28.10.14)
p.s. added files:
after restart+new scene. DL kernel. + Difference Matte to see difference
+ one 4000x720 Difference Matte and pixels count
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Hi,aoktar wrote:Understand this. But i have no idea why occurs. is it doing one time or repeately after changing again? Is this occuring on a spesific scene or any scene? This does not occurs on my trys
stil same problem whatever the scene...
Back to 2.11.1 RC2... and no problem of this kind with this version.
One of them already posted "by valters » Mon Nov 03, 2014 4:18 pm"abstrax wrote:Could you please send us a scene so we can reproduce this issue? Thanks.valters wrote:nvidia driver: 344.16
gpu1: GTX 680
gpu2: GTX 760
OS: Windows 7 Pro x64
C4D: R15
octanePlugin: Version 2.12.1 - final (updated on 28.10.14)
p.s. added files:
after restart+new scene. DL kernel. + Difference Matte to see difference
+ one 4000x720 Difference Matte and pixels count
and to see this issue you need to carefully look on image, as my previous post (images) is made in Adobe AfterEffects using Difference Matte with red background just to compare two images to clearly see that bug block. In usual render it looks just like I post on "by valters » Mon Nov 03, 2014 4:18 pm".
- Attachments
-
- New test & scene file
-
- new_day_test.zip
- c4D SCENE
- (110.35 KiB) Downloaded 248 times
valters wrote:One of them already posted "by valters » Mon Nov 03, 2014 4:18 pm"abstrax wrote:Could you please send us a scene so we can reproduce this issue? Thanks.valters wrote:nvidia driver: 344.16
gpu1: GTX 680
gpu2: GTX 760
OS: Windows 7 Pro x64
C4D: R15
octanePlugin: Version 2.12.1 - final (updated on 28.10.14)
p.s. added files:
after restart+new scene. DL kernel. + Difference Matte to see difference
+ one 4000x720 Difference Matte and pixels count
and to see this issue you need to carefully look on image, as my previous post (images) is made in Adobe AfterEffects using Difference Matte with red background just to compare two images to clearly see that bug block. In usual render it looks just like I post on "by valters » Mon Nov 03, 2014 4:18 pm".
New information:
I was render this scenes with different version and here is what i found:
Octane-for-C4D-2.06.0 - working fine. no this bug
Octane-for-C4D-2.06.1 - working fine. no this bug
Octane-for-C4D-2.10-test1 - working fine. no this bug
Octane-for-C4D-2.11.1-RC1 - not working fine. this block bug exists
Octane-for-C4D-2.11.1-RC2 - not working fine. this block bug exists
Octane-for-C4D-2.11.1 - not working fine. this block bug exists
Octane-for-C4D-2.11.2 - not working fine. this block bug exists
Octane-for-C4D-2.12.1 - not working fine. this block bug exists
so Octane-for-C4D-2.10-test1 for me was the last version without this bug.
nice determination. I'm not sure it's a bug or so. Marcus can answer bettervalters wrote:Last Update. Everything is working fine if on octane plugin/devices setting uncheck all boxes with priority. Turning on any Pri. check box making this "block" bug with two GPUs.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I opened your scene on 3 GPUs with priority enabled and neither in the live preview nor in the final rendering I can see any blocky artifacts. Is there anything else I have to do to reproduce the problem?valters wrote:Last Update. Everything is working fine if on octane plugin/devices setting uncheck all boxes with priority. Turning on any Pri. check box making this "block" bug with two GPUs.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
My steps was simple, I have just render two images, one with single gpu and second with both gpus. Both renders with the same amount of samples. After this just switching fast between two images I can see that block thing. Can you upload two rendered images, one with single card and second with two gpus and Pri. on?abstrax wrote:I opened your scene on 3 GPUs with priority enabled and neither in the live preview nor in the final rendering I can see any blocky artifacts. Is there anything else I have to do to reproduce the problem?valters wrote:Last Update. Everything is working fine if on octane plugin/devices setting uncheck all boxes with priority. Turning on any Pri. check box making this "block" bug with two GPUs.
and here is link to mp4. I have record process https://mega.co.nz/#!Odw0SKiT!24pCqywNL ... -6-IX61bUgvalters wrote:My steps was simple, I have just render two images, one with single gpu and second with both gpus. Both renders with the same amount of samples. After this just switching fast between two images I can see that block thing. Can you upload two rendered images, one with single card and second with two gpus and Pri. on?abstrax wrote:I opened your scene on 3 GPUs with priority enabled and neither in the live preview nor in the final rendering I can see any blocky artifacts. Is there anything else I have to do to reproduce the problem?valters wrote:Last Update. Everything is working fine if on octane plugin/devices setting uncheck all boxes with priority. Turning on any Pri. check box making this "block" bug with two GPUs.