Cinema4D version 2020.1-R7 (Obsolete stable)05.06.2020

[FractalMotion]

Yes i'm using 2020.1-R2 , i downloaded the latest version in the first post of this thread . but also had this bug with the previous versions of the plugin unfortunatly.

[aoktar]

Yes i'm using 2020.1-R2 , i downloaded the latest version in the first post of this thread . but also had this bug with the previous versions of the plugin unfortunatly.

This is not a bug, but maybe a wrong install or another software that blocks it

[bepeg4d]

Hi FractalMotion,
please, navigare to `C:\programs\Maxon\Cinema 4D R20\corelibs` directory, and check to have not the following files in it:


If yes, remove them, and restart C4D.

ciao Beppe

[FractalMotion]

Wow it worked !!! Grazie mille Bepe i had little hope for this Thanks for the hard work on the plugin Aoktar , it works like a charm !
Have a great day everybody

[BCres]

Just want to say 'thank you' Ahmet and everyone who worked on the core release. It really is an amazing renderer. I'm using the ACES profile exclusively now when I render.

I have one small issues that hasn't kept me from working, but thought I'd ask if anyone had any ideas. I'm using 2020.1-R2 and Studio driver 442.92 on a 2080ti. I actually wonder if this isn't C4D S22 related.

A scene which loads and renders fine, suddenly won't open next time I go into C4D. This happens a lot if I open and close C4D and have to return to the scene. There is nothing (C4D wise) left active in the Task Manager. But I can fix the problem by rebooting the system. That works everytime.

I am sure this is just an early version bug (whther Octane or C4D) that needs to be ironed out. Using two first versions of anything together is always a bit problematic.

Any ideas would be appreciated, but if not I can still work. Thanks again.

**edit** I had an issue about a sluggish interface but I believe it was due to using the "LV multicore" and "Octane for Open GL" features in the Octane setting. Turning them off seems to have fixed it.

[aoktar]

Just want to say 'thank you' Ahmet and everyone who worked on the core release. It really is an amazing renderer. I'm using the ACES profile exclusively now when I render.

I have two small issues that haven't kept me from working, but thought I'd ask if anyone had any ideas. I'm using 2020.1-R2 and Studio driver 442.92 on a 2080ti. I actually wonder if a lot of this isn't C4D S22 related.

1) I've noticed 2020.1 is a lot more sluggish (compared to 2019.1.5) when moving objects in the scene and when the LV updates. In fact, I can hear system noise everytime the LV updates. And it seems Octane is constantly reloading textures or something when I do this. Even if my mouse moves over the C4D Viewport, it re-renders.

2) A scene which loads and renders fine, suddenly won't open next time I go into C4D. This happens a lot if I open and close C4D and have to return to the scene. There is nothing (C4D wise) left active in the Task Manager. But I can fix the problem by rebooting the system. That works everytime.

I am sure these are just early version bugs that need to be ironed out. Using two first versions of anything together is always a bit problematic.

Any ideas would be appreciated, but if not I can still work. Thanks again.

Thanks for kind words!
I haven't exclusively tested it in S22 and didn't compile a special build over S22 SDK. It may be a reason. Other than this, it sounds like you're working without priority selected and or high activated. Also do you see any material messages at bottom info line of C4D while move somethings? Did you tested on R21?

[BCres]

Yes, Ahmet, I did see tons of material messages when all of the disk activity was going on. You're right, "priority" was unchecked. I'll turn it on. I also edited my post to say turning off "LV Multicore" and "Octane for Open GL" helped a lot. It's a lot more usuable now.

Okay checked in C4D R21 and it behaves fast even with those features turned on and priority turned off, so must be an S22 issue. But I can live with it.

The "having to reboot issue" to reopen a scene is more problematic, but honestly I think it's a C4D issue as well.

Thank you for your help. I know you're busy.

[kermelin]

Thank you for the release, it is by far the most stable version I tried and I love the color management toggle at the top. If I understand correctly, RGB textures do not need to be linearised separately when working in ACES, right? I've done some render tests according to an older page below but the renders turned out to be better without touching the textures gammas.

http://www.aoktar.com/octane/OCTANE%20H ... KFLOW.html

[franchais]

Hi I'm having trouble getting the random colors to work?

Any idea on whats happening?

[bepeg4d]

Hi franchais,
have you enabled the render Instance, or Multi Instance option of the MoGraph cloner?
ciao Beppe