Version 4.0-RC4-R2 (obsolete release candidate) 22.09.201

[AlvaroLetelier]

it’s a know error.

Happy to help a little.

Thanks for the reply.

[aoktar]

it’s a know error.

Happy to help a little.

Thanks for the reply.

In R20 build can be more problems. It needs to be tested and gathered feedbacks from users.

[divasoft]

Thank you for the scene. Ahmet and I have been trying to reproduce the issue. He could reproduce the render failure, I could not (i.e. here it renders fine on a 1080 and a TitanV). I gave him a build with more logging so we can investigate. One thing Ahmet found was that could actually render after he disabled the shader cache in the C4D OpenGL preferences. Maybe that might help in the meantime.

Thank you for your feedback, Abstrax. But disabling OpenGL cache was not helpful for me (octane still crashing).
And yes, i have 2x gtx 1080ti

[FxDesign]

Hello Aoktar,
In this release, the motion blur is crashing C4D with X-particles.
(I'm on R19.068)

Have you planned to fix that ?

Thank you

[aoktar]

Hello Aoktar,
In this release, the motion blur is crashing C4D with X-particles.
(I'm on R19.068)

Have you planned to fix that ?

Thank you

Fixing how? Did you sent any sample scene?

[abstrax]

Thank you for the scene. Ahmet and I have been trying to reproduce the issue. He could reproduce the render failure, I could not (i.e. here it renders fine on a 1080 and a TitanV). I gave him a build with more logging so we can investigate. One thing Ahmet found was that could actually render after he disabled the shader cache in the C4D OpenGL preferences. Maybe that might help in the meantime.

Thank you for your feedback, Abstrax. But disabling OpenGL cache was not helpful for me (octane still crashing).
And yes, i have 2x gtx 1080ti

Just a quick update: We haven't found the culprit yet, but at least I can now reproduce the issue on my machine.

I can reproduce the it the Standalone if (and only if) C4D is open. I don't have to load anything into the Standalone. Just have to have C4D open - even without the plugin being installed. Looks most likely like some driver issue. Let's see if we can work around it.

Which NVIDIA graphics driver version do you use and which OS / Windows?

EDIT: When I disable "Hardware OpenGL" in the C4D preferences it also renders fine in the Standalone. -> There seems to be some conflict or some lack of resources between the C4D graphics pipeline and Octane CUDA.

[AlvaroLetelier]

On RC4-R3 Motion blur is working like charm!

Thanks!

[Pleaseluggage]

I'm very frustrated with OTOY at the moment.

I love the product. It's been awesome and you all have been very supportive.

However...

I feel I've fallen for a bait and switch. I have to essentially buy the plugin AGAIN (the 2018 subscription) instead of the plugin I already bought because the cryptomatte is witheld in 4.04.x

The client demands this and I wish my previous plugin wasn't made obsolete. Is there an "upgrade" subscription price for the 2018/2019 Octane versions or do I have to pay full price?

Thank you for hearing me out.

[frankmci]

I feel I've fallen for a bait and switch. I have to essentially buy the plugin AGAIN (the 2018 subscription) instead of the plugin I already bought because the cryptomatte is witheld in 4.04.x
.

As far as I can recall, Cryptomatte was never specifically promoted as a feature for 4.x, although it was part of Otoys "development roadmap" that stretched out for several years. Do you have any links to Otoy publicly saying otherwise? The first official statement I've found was Goldorak, almost exactly a year ago today, saying that it wouldn't be implemented until V 2018.1.

viewtopic.php?f=33&t=55253&hilit=crypto ... 20#p343524

[Pleaseluggage]

I'm an idiot. Thank you for all of your patient replies. I was just complaining to make myself feel better I suppose. Frustrated. This is amazing technology. I should (and do) feel more fortunate that the team included this in the first place.

Thank you all.