Cinema4D version 2020.1-RC2[R4](ReleaseCandidate) 06.04.2020

[bepeg4d]

Hi divasoft,
please, post the same double render, but with Solo mode enabled on the Gradient, or share a similar scene that shows the issue, thanks.
ciao Beppe

[divasoft]

Hi divasoft,
please, post the same double render, but with Solo mode enabled on the Gradient, or share a similar scene that shows the issue, thanks.
ciao Beppe

I tried to create an example in a new scene, but the problem could not be reproduced, everything works well. It was probably a glitch in that old scene, excuse for troubling.

[divasoft]

I have tested the latest update, the situation really got better, but from some point the render time still starts to grow, although the number of particles in each frame is almost constant (there is a particle killer modofoer under the fountain).

[aoktar]

I have tested the latest update, the situation really got better, but from some point the render time still starts to grow, although the number of particles in each frame is almost constant (there is a particle killer modofoer under the fountain).

send me your scene, I'll check if it can be better or not. No promises, having a lot of in cache that causes long search times. Probably I cannot do better without doing big revisions on the system.

[divasoft]

I have tested the latest update, the situation really got better, but from some point the render time still starts to grow, although the number of particles in each frame is almost constant (there is a particle killer modofoer under the fountain).

send me your scene, I'll check if it can be better or not. No promises, having a lot of in cache that causes long search times. Probably I cannot do better without doing big revisions on the system.

ok, check it please.
https://yadi.sk/d/kmYoMUzhHRXUsw

[bepeg4d]

Hi divasoft,
please, post the same double render, but with Solo mode enabled on the Gradient, or share a similar scene that shows the issue, thanks.
ciao Beppe

I tried to create an example in a new scene, but the problem could not be reproduced, everything works well. It was probably a glitch in that old scene, excuse for troubling.

Great, thanks for letting us know.
Happy GPU Rendering, and stay safe,
ciao Beppe

[pxlntwrk]

Hi,

In the "Displacement Node" settings would it be possible to have access to this parameter via xpresso?



thanks

[pxlntwrk]

hi,

There are some wizardery with the node editor at the moment.
Here is an example:
when I reopen a material setup done this morning, the display in node editor is completely incoherent compared to the settings made.
Some nodes appear detached and others are not connected correctly



even if the rendering is correct, the display of the nodes is erratic, and prevents any modification.
(freezing or pins do not react ...)

This is a bit annoying

Win 10 1909
C4D 21.207
Octane Cinema4D version 2020.1-RC2[R2]
NVIDIA 442.19 SD

[aoktar]

hi,

There are some wizardery with the node editor at the moment.
Here is an example:
when I reopen a material setup done this morning, the display in node editor is completely incoherent compared to the settings made.
Some nodes appear detached and others are not connected correctly



even if the rendering is correct, the display of the nodes is erratic, and prevents any modification.
(freezing or pins do not react ...)

This is a bit annoying

Win 10 1909
C4D 21.207
Octane Cinema4D version 2020.1-RC2[R2]
NVIDIA 442.19 SD

This is still a development version and I'm making some revisions on nodes to provide GROUP feature. ID system changed for nodes and this happens because of some conflict on node IDs. Did you created this material from the ground or downloaded it from LIVEDB?
Btw you setup is strange, I mean using mix material with composite material. You should just prefer to use composite material.

[pxlntwrk]

Hi,
thank you for the answer,
it is a material created from scratch.(for testing purposes)
Yes the composite material works well, but the mix material allows me to bring back a material "already created" into the setup