How to work with Cryptomatte?
I get different results in LV and Picture-Manager. And how can I "Mask" specific objects?
Cinema 4D version 2018.1-RC6.1 (Test version)
Moderators: ChrisHekman, aoktar
- Silverwing
- Posts: 287
- Joined: Wed Jun 15, 2011 8:36 pm
- Location: Ludwigsburg Germany
- Contact:
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 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.
WIN 10 PRO 64 | ASUS X99-E WS | 3 X GTX 1080Ti | i7 5960X 8X 3,33GHz | 64GB RAM
I have the exact same problem which i explained on page 1Silverwing 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.
i7 10700k | Win 10 64 bit | RTX 3090
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.anklove wrote:I have the exact same problem which i explained on page 1Silverwing 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.
C4D 2025.1.1 Octane 2025.2.1 v1.5.1, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
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?
Hi,
c4doctane 2018.1-RC6 Studio already supports 2x GPUs: ciao Beppe
c4doctane 2018.1-RC6 Studio already supports 2x GPUs: ciao Beppe
This version not work with cinema Volume builder. I start render and nothing happens. VDB Volume object does not work same.
No, you don't understand me. Why did you use Volime mesher? I talked about Volume Builder only and vdb loader. Try itVVG wrote:all okdivasoft wrote:This version not work with cinema Volume builder. I start render and nothing happens. VDB Volume object does not work same.