OTOY Forums

Weirdpictures wrote:

bepeg4d wrote:Hi Weirdpictures,
after enabling the AB Comparison, you also need to use the Save Render Buffer command, since it is not stored automatically like before.
Then you will see the AB line, and use the Compare feature as before:

DC178A69-66A0-489A-9077-3B6A6AED8929.jpeg

ciao Beppe

Hi Beppe,

thanks for your reply. Yes, we know that we need to save the render buffer, but it wont show up or give us the red line to compare between two images.
Here is a screen recording to show the problem. Again, all works perfect with the R5 release, but R6 and R7 have this problem for us.

Same for me..

C4d R21 / win 10

It's a problem with "LDR 8-bit" tonemap type in LV. It works with other types.

R19.068 + 2020.1.R7

1. Enable A/B Comparison
2. Store Render Buffer

A/B Comparison Not Working.
Can't see Split line.
Stored Image List Not Working (same image. maybe not stored)

R6/R7 Not Working
R4/R5 Working

The delay added to viewport texture generation took care of a month long problem we were having with a project that used 7 different materials in a Composite material. C4d would always crash when trying to generate that material. It was hell trying to find a work around. This update could not have come at a better time! Thanks, Ahmet.

eyeonestudio wrote:R19.068 + 2020.1.R7

1. Enable A/B Comparison
2. Store Render Buffer

A/B Comparison Not Working.
Can't see Split line.
Stored Image List Not Working (same image. maybe not stored)

R6/R7 Not Working
R4/R5 Working

2020-06-09_003255.jpg

SWITCH to HDRxxxx tonemap type, RESTART render and try again!

aoktar wrote:

eyeonestudio wrote:R19.068 + 2020.1.R7

1. Enable A/B Comparison
2. Store Render Buffer

A/B Comparison Not Working.
Can't see Split line.
Stored Image List Not Working (same image. maybe not stored)

R6/R7 Not Working
R4/R5 Working

2020-06-09_003255.jpg

SWITCH to HDRxxxx tonemap type, RESTART render and try again![/quote

Working Here. Thanks.

Seun116_1 wrote:The delay added to viewport texture generation took care of a month long problem we were having with a project that used 7 different materials in a Composite material. C4d would always crash when trying to generate that material. It was hell trying to find a work around. This update could not have come at a better time! Thanks, Ahmet.

Glad that helped for this also.

aoktar wrote:

eyeonestudio wrote:R19.068 + 2020.1.R7

1. Enable A/B Comparison
2. Store Render Buffer

A/B Comparison Not Working.
Can't see Split line.
Stored Image List Not Working (same image. maybe not stored)

R6/R7 Not Working
R4/R5 Working

2020-06-09_003255.jpg

SWITCH to HDRxxxx tonemap type, RESTART render and try again!

Thanks Ahmet,

now it works perfect again. Love the look of the streamlined GUI by the way. Thanks for all the hard work.

I'm not sure if the following is exclusive to the latest plugin release, but I've been able to crash C4D R20 by dragging an XRef that contains an Octane Arealight into a Cloner, even if the Xref scene contains only the light.

Steps to reproduce:

• - create and save first scene with Octane Arealight
  - create second scene with Cloner and load first scene as XRef
  - drag Xref into Cloner

I've tested another scene with a standard Cinema 4D area light in a XRef and added the Octane LightTag afterwards without issue. It seems that as long as the tag is in the loaded XRef that it causes a problem.

I get this Log error, if i move a object in C4d:

Started logging on 13.06.20 20:11:01

OctaneRender Enterprise 2020.1 (8010000)

CUDA error 719 on device 0: unspecified launch failure
-> failed to wait for event
device 0: path tracing kernel failed
CUDA error 700 on device 1: an illegal memory access was encountered
-> failed to wait for event
device 1: path tracing kernel failed

----------------
Any solution?