OTOY Forums

I was just curious if anyone else has been having the color space issue? I can't seem to get it to work properly yet. It's like it's forcing the EXR file type into linear workspace when working in post.

Just FYI, I reverted back to 2020.1-R7 and the color space for the EXR file type is working normally again.

@aoktar

First i'm not your "Mate"!

I think you should be a little more friendly in reacting to my error messages. The fact is and remains, every time I check "Enable Camera Imager", I get a black render image.

It doesn't matter whether I'm doing a completely new scene or an old one!

The error comes from the plugin. The old plugin works without problems. Please fix the error and find out what the problem is.

And it makes no Difference if i dont use "Peers" oder "RTX on". I don't get full render image only a black image if i turn on "Enable Camera Imager" if i turn it off it works fine.

Today i tested and if i use "peers" i get this error:

Mismatching barriers, 5 and 1

But ony if i use "Mulitlayer file" if i don't use "Mulitlayer file" it renders in the "Picture Viewer".

But again if i turn on "Enable Camera Imager" i only get a black render image as finished end file output.

I get this errors:

Started logging on 07.07.20 14:51:28

OctaneRender Enterprise 2020.1.3 (8010300)

Mismatching barriers, 5 and 1
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
not all the passes requested for tonemapping are enabled
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
Mismatching barriers, 5 and 1


------------------------------

Started logging on 07.07.20 19:07:29

OctaneRender Enterprise 2020.1.3 (8010300)

could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
could not steal to daemon 192.168.178.43 because it has incorrect state: slave is authenticating
Mismatching barriers, 5 and 1
not all the passes requested for tonemapping are enabled

Best to submit this to help at otoy dot com so we can get this report into the system and assigned to the proper person. Thank you!

As said in a previous post, there are three issues under investigation by the core team:

• CPU and AVX support => not solved, go back to 2020.1-R7, or 2019.1.5-R3
• Displacement disappearing => already solved for 2020.1.4 next SDK
• Mismatching barriers error with NvLink => not solved, disable NvLink option in Nvidia control panel

ciao Beppe

Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

divasoft wrote:Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

It seems to render fine for me, even on an old GTX 1070 with 8 gigs of VRAM. Are you working with some tight memory limitations? The C4D UI does get a little sluggish with that many particles, but the rendering doesn't seem to be a problem. If you turn down you Parallel Samples you can get a bit more headroom, memory wise, with a small hit on render speed. Here's frame 20 of your example scene:

divasoft wrote:Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

There's not a limitation in plugin side. I cannot help for core or hardware related topics.

aoktar wrote:

divasoft wrote:Hi. I have a problems every time when i use huge particles amount. 10 millions and more. Octane just crush. I can't work.
Just simulate 20 frames and try to render. I will again have to switch to redshift. Can you already do something to make the octane work?
I wrote to you about this problem several times over the past 2 years.
Scene https://yadi.sk/d/0k090xST2uxJQA

There's not a limitation in plugin side. I cannot help for core or hardware related topics.

Can you explain what the problem is? Ask me for bug reports or something else. Yes, sometimes octane can render this scene, but in half the starts I get a crash. Once again, it’s not possible to work like that. Instead of excuses, can you help me with something? When I refer to redshift team, I always get accurate explanations of what the problem is, or they just fix it. From you, I usually hear that the problem is not in the plugin. What is the problem then, how to fix it?