Page 2 of 4

Cryptomatte

Posted: Mon Mar 11, 2019 10:58 am
by moebius
How to work with Cryptomatte?

I get different results in LV and Picture-Manager. And how can I "Mask" specific objects?

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Mon Mar 11, 2019 11:52 am
by Silverwing
Hi Ahmet.

I have a weird issue with materials in this built whenever I work with bigger scenes that have a lot of materials.

Problem:
When I create or copy a octane material and assign it to an object some other objects randomly switch to another materials.

Example:
I have a white cube a red sphere and a green pyramid.
I create a new blue material and assign it to the white cube.
Now the cube is blue. But the green pyramid suddenly becomes red (or any other available material)
The tag of the pyramid is still the green material. But in the rendering the pyramid is rendered red. Also after I reassign the material, after reload the render to the GPU or even restart C4D.

It probably does not work with simple scenes with 3 objects like above.
Usually I have a lot of instances in the scenes.

The material assignment is showing up correctly in C4D. And even when I reload the problem persists.
The only way to fix this is to cut and paste the material that should be signed to the object and then reassign it.

Sorry that I do not have a simple test scene...

I can send you a scene via Skype if you want as I can´t share it publicly.
I will make a video of the behaviour when I have the time.

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Tue Mar 12, 2019 9:19 am
by anklove
Silverwing wrote:Hi Ahmet.

I have a weird issue with materials in this built whenever I work with bigger scenes that have a lot of materials.

Problem:
When I create or copy a octane material and assign it to an object some other objects randomly switch to another materials.

Example:
I have a white cube a red sphere and a green pyramid.
I create a new blue material and assign it to the white cube.
Now the cube is blue. But the green pyramid suddenly becomes red (or any other available material)
The tag of the pyramid is still the green material. But in the rendering the pyramid is rendered red. Also after I reassign the material, after reload the render to the GPU or even restart C4D.

It probably does not work with simple scenes with 3 objects like above.
Usually I have a lot of instances in the scenes.

The material assignment is showing up correctly in C4D. And even when I reload the problem persists.
The only way to fix this is to cut and paste the material that should be signed to the object and then reassign it.

Sorry that I do not have a simple test scene...

I can send you a scene via Skype if you want as I can´t share it publicly.
I will make a video of the behaviour when I have the time.
I have the exact same problem which i explained on page 1

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Wed Mar 13, 2019 2:12 am
by Kalua
anklove wrote:
Silverwing wrote:Hi Ahmet.

I have a weird issue with materials in this built whenever I work with bigger scenes that have a lot of materials.

Problem:
When I create or copy a octane material and assign it to an object some other objects randomly switch to another materials.

Example:
I have a white cube a red sphere and a green pyramid.
I create a new blue material and assign it to the white cube.
Now the cube is blue. But the green pyramid suddenly becomes red (or any other available material)
The tag of the pyramid is still the green material. But in the rendering the pyramid is rendered red. Also after I reassign the material, after reload the render to the GPU or even restart C4D.

It probably does not work with simple scenes with 3 objects like above.
Usually I have a lot of instances in the scenes.

The material assignment is showing up correctly in C4D. And even when I reload the problem persists.
The only way to fix this is to cut and paste the material that should be signed to the object and then reassign it.

Sorry that I do not have a simple test scene...

I can send you a scene via Skype if you want as I can´t share it publicly.
I will make a video of the behaviour when I have the time.
I have the exact same problem which i explained on page 1
I had this problema as well in recently removed V4 R5. Aoktar already found a way of fixing it. Probably will know how to do it as well for V2018.1.

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Wed Mar 13, 2019 2:22 pm
by bagel
So since Standalone RC6 and presumably final version is back to 2 GPU rendering, is RC6 plugin allowing more than a single GPU? I can't enable my second GPU, no errors, I can set it, but then it just unselects itself. Any idea on when final version is coming and will it support 2 gpus?

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Fri Mar 15, 2019 4:10 pm
by bepeg4d
Hi,
c4doctane 2018.1-RC6 Studio already supports 2x GPUs:
F1AAAA26-F766-463B-861A-6CDD8EC97137.jpeg
ciao Beppe

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Fri Mar 15, 2019 4:20 pm
by bagel
bepeg4d wrote:Hi,
c4doctane 2018.1-RC6 Studio already supports 2x GPUs:
F1AAAA26-F766-463B-861A-6CDD8EC97137.jpeg
ciao Beppe
*sigh*

Don't mind me. I'll go be dumb somewhere else. I made a mistake in which plugin I currently had installed. Thanks!

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Fri Mar 15, 2019 6:35 pm
by divasoft
This version not work with cinema Volume builder. I start render and nothing happens. VDB Volume object does not work same.

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Fri Mar 15, 2019 9:50 pm
by VVG
divasoft wrote:This version not work with cinema Volume builder. I start render and nothing happens. VDB Volume object does not work same.
all ok

Re: Cinema 4D version 2018.1-RC6.1 (Test version)

Posted: Sat Mar 16, 2019 1:17 am
by divasoft
VVG wrote:
divasoft wrote:This version not work with cinema Volume builder. I start render and nothing happens. VDB Volume object does not work same.
all ok
No, you don't understand me. Why did you use Volime mesher? I talked about Volume Builder only and vdb loader. Try it