Cinema4D version 2020.2-RC6 (Release candicate) 29.12.2020

[aoktar]

Hi Ahmet, I have had a problem with the plugin for a long time and I didn't want to send anything until I was sure it wasn't a problem with my pc, but I did tests with 2 totally different computers and the problem keeps happening to such a degree that it makes me very difficult to work. I'm going to send him a compiled video and log files to see if you can determine what is happening. This is happening to me with almost all the scenes when I start to make them more complex. I hope this helps you and the problem can be solved. I had to postpone several jobs due to this error.

Note: This only happens if I use the octane render plugin, it does not happen with another engine.

I also tried an older version 2020.1.5-R4 and it is unstable

Thanks, Ahmet.

Windows 10 Pro x64 20H2
Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz 3.79 GHz
Motherboard Z490 Vision D
Nvidia 2080 ti 460.89 (Studio Drivers)

Interesting problem, haven't see it before! Could you close all other software and remove other plugins? Disable RTX and denoiser. Let me know if still happens.

[raulofs]

Thanks for your reply. Ok, I deleted the cinema preferences and left only the octane render plugin. Also close all the windows programs that were running in the background including adobe and stuff and the result is the same.

I send the files with the new tests

Thanks Ahmet.

[raulofs]

I did tests removing RTX and the denoiser, it's the same
Thanks Ahmet.

[karl]

Probably a stupid question, but how do you get "Use View Look(s)", shown in the picture below, to actually populate with something. The only other entry is none and nothing happens when I use either of them.

Is it referencing something else?

view looks.jpg

This config doesn't have any look to display.

Right, I get that much, so what I'm asking is—how do I get access to a configuration that allows me to use "Use View Look(s)"? None of the configurations offered make that selection usable.

Where do the "Looks" to come from? What file? What configuration? I don't have any idea how that pull down is even populated.

Sorry, but I can't find any documents for this. It'll be my last question. Thanks.

You're using the standard ACES OCIO config, which doesn't contain any looks. My understanding is that that config is intended as a starting point from which to build an ACES workflow - if you want to apply your own color grading, contrast adjustment, false color etc. you're supposed to design and add your own looks to the config.ocio file. Various software tools can export color transformation LUTs that can be used for OCIO looks. There are also various other OCIO configs available online you could try, although it's unlikely any pre-made config contains the exact look you want and fits in with the rest of your workflow (for example Filmic Blender contains a few looks but no ACES color spaces).

In an OCIO config that does have looks, each view can specify a default sequence of looks to apply when using that view. That's what "Use view look(s)" means in Octane - any other option will override the default view look(s) and apply the chosen look (or no look) instead.

It would probably be a good idea for Octane to not show the "Use view look(s)" option if the currently loaded OCIO config doesn't contain any views with default look(s). I'll look into making that change.

[aoktar]

I did tests removing RTX and the denoiser, it's the same
Thanks Ahmet.

Can you disable the all preview options for opengl/materials and nodes and try again? Also did you try with a clean install of C4D?

[BCres]

Where do the "Looks" to come from? What file? What configuration? I don't have any idea how that pull down is even populated.

Sorry, but I can't find any documents for this. It'll be my last question. Thanks.

You're using the standard ACES OCIO config, which doesn't contain any looks. My understanding is that that config is intended as a starting point from which to build an ACES workflow - if you want to apply your own color grading, contrast adjustment, false color etc. you're supposed to design and add your own looks to the config.ocio file. Various software tools can export color transformation LUTs that can be used for OCIO looks. There are also various other OCIO configs available online you could try, although it's unlikely any pre-made config contains the exact look you want and fits in with the rest of your workflow (for example Filmic Blender contains a few looks but no ACES color spaces).

In an OCIO config that does have looks, each view can specify a default sequence of looks to apply when using that view. That's what "Use view look(s)" means in Octane - any other option will override the default view look(s) and apply the chosen look (or no look) instead.

It would probably be a good idea for Octane to not show the "Use view look(s)" option if the currently loaded OCIO config doesn't contain any views with default look(s). I'll look into making that change.

Thank you, Karu. Yes, you're confirming what I had understood Ahmet to mean earlier, but the expanded explanation and especially the link you sent will take me much further and faster now.

I appreciate the whole team at OTOY. Everyone is always willing to help out.

[raulofs]

I did tests removing RTX and the denoiser, it's the same
Thanks Ahmet.

Can you disable the all preview options for opengl/materials and nodes and try again? Also did you try with a clean install of C4D?

Hello, completely uninstall cinema 4D and delete all the program folder, I reinstalled only Cinema and the plugin and deactivated all the preview options but it keeps happening, It has been difficult for me to advance in my work

Thanks Ahmet.

[aoktar]

I did tests removing RTX and the denoiser, it's the same
Thanks Ahmet.

Can you disable the all preview options for opengl/materials and nodes and try again? Also did you try with a clean install of C4D?

Hello, completely uninstall cinema 4D and delete all the program folder, I reinstalled only Cinema and the plugin and deactivated all the preview options but it keeps happening, It has been difficult for me to advance in my work

Thanks Ahmet.

It looks like a strange problem. Sent you a PM

[useruser]

Hey there;

Having render freeze when I have objects with keyed visibility attiributes. Tested with default cinema4d visibility property and octane tag visibility slider.

When the render reaches to the frame with the visibility key it stops calculation and hangs. This doesnt happen in the LiveViewer.

Im using HDR/sRGB output with no denioser. 2x RTX3080. having RTX on or off doesnt make a difference. I'm sending the sample scene file to aoktar.

same problem here: rendering hangs up in pictureviewer.( not in live viewer) with both options:animated visibility property in octane-objecttag or the c4d-standard visibility-tag.
so i switched back to octane 2019 because it was unable to render the project.

[aoktar]

Hey there;

Having render freeze when I have objects with keyed visibility attiributes. Tested with default cinema4d visibility property and octane tag visibility slider.

When the render reaches to the frame with the visibility key it stops calculation and hangs. This doesnt happen in the LiveViewer.

Im using HDR/sRGB output with no denioser. 2x RTX3080. having RTX on or off doesnt make a difference. I'm sending the sample scene file to aoktar.

same problem here: rendering hangs up in pictureviewer.( not in live viewer) with both options:animated visibility property in octane-objecttag or the c4d-standard visibility-tag.
so i switched back to octane 2019 because it was unable to render the project.

It was a problem from sdk, not plugin part