OTOY Forums

iDani wrote:Hi there,
i have a problem with Octane Cinema 4D on OSX. This problem has existed on OSX from the very beginning. When rendering, no matter which scene of an animation, Octane usually breaks off around 600 frames. The Octane log shows that the memory is full. But the memory is not full. I have a MacBook Pro with M3 chip and 64Gb Ram. Enclosed is the error message from the log.

cheers Daniel

Hi Daniel,
sorry but I cannot reproduce the issue here, I've just rendered a 900 frames animation on M4 without issues: Could you share a scene that shows the issue for you?
You can share a link via Private Message.

ciao,
Beppe

bepeg4d wrote:

iDani wrote:Hi there,
i have a problem with Octane Cinema 4D on OSX. This problem has existed on OSX from the very beginning. When rendering, no matter which scene of an animation, Octane usually breaks off around 600 frames. The Octane log shows that the memory is full. But the memory is not full. I have a MacBook Pro with M3 chip and 64Gb Ram. Enclosed is the error message from the log.

cheers Daniel

Hi Daniel,
sorry but I cannot reproduce the issue here, I've just rendered a 900 frames animation on M4 without issues:

IMG_4460.jpeg

Could you share a scene that shows the issue for you?
You can share a link via Private Message.

ciao,
Beppe

Hi Beppe,

Thanks for your feedback. Unfortunately I can't share the file, but I will finish something in the next few days that I can send and then send it to you here.
On my PC with 4090 and 380ti these crashes are not. Somehow something seems to fill the memory on the Mac but I'll see if I can send you a file in the next few days.

UON.Visuals wrote:New bug in R4: I can confirm that compare image/store render buffer doesn't work anymore:

We can not reproduce your issue.
Here it works for me.

Can you give us more details and exact steps how to reproduce?

Also system specs, software versions and if you are using a Custom Layout in C4D.
You should definitely try it with the default layouts first.

Thanks

ChrisHekman wrote:

augdalmo wrote:Hi,

I have encountered a problem with Chaos texture. I have created a material with Chaos texture and saved it on LiveDB manager.
As I try to use this material from Live DB, on Octane Node Editor the Chaos texture node is changed in appearance, it losed input pin .
There is also a problem in preview Octane Material node, it appear white, this is a problem that occur for some time.
Regards

Yes, chaos nodes from LiveDB/ORBX still use the old chaos node for now. This is because LiveDB stores materials as octane OCS, and not as plugin nodes.
We are currently working on supporting conversion from LiveDB/ORBX to the new node system. But for now it will generate the older nodes.
Ill see if i can fix the whiteness

Hi Chris,
there is also another problem on node editor, as I create a Displacement node atomatically Normal node create two links on Displacement node, even if I broke the links as I reopen material in node editor the links reappear.
It also cause sometime a sudden crash of C4D as I tray to adjust the effect wiht the cursors.
Regards

Hmmm, speaking of the Node Editor - is the "Save as preset" option in the right-click context menu working, currently?

It sounds extremely useful (e.g. creating a noise library with specific settings, configuring the "comments" node once and then reusing it,...), but I'm not sure where the presets would show up if they are in fact created? I don't see them in the Asset Browser, but maybe I'm misunderstanding the entire feature. : )

I can use "Save Selected as Preset" from the C4D context menu if I right-click on a parameter within the node and not the node itself, which will then create a preset in the Asset Browser, BUT, clicking on this preset in the AB then leads to an error message (illegal state, condition not fulfilled).

For this second option, I assume that C4Ds preset system simply doesn't yet interact with Octane nodes. But does Octane have its own preset system? (So what does right-click on a node, "save as preset" do?)

If I use Octane area light with take system area light rectangle shapes goes crazy.
1) add area light
2) activate both "auto take" and "lock overrides" mode active
3) change area light size/s (position changes do not create any problems, just size modifications do)
4) add another take, change area light size again
5) go back and activate first take

Keep repeat take activations.
Area light size additively changes.

Since we are in the middle of a project and will get a new workstation with a 5090 soon, will there be a production ready build of 2024? I really don't wanna switch to a beta build with a deadline coming up...

bepeg4d wrote:

iDani wrote:Hi there,
i have a problem with Octane Cinema 4D on OSX. This problem has existed on OSX from the very beginning. When rendering, no matter which scene of an animation, Octane usually breaks off around 600 frames. The Octane log shows that the memory is full. But the memory is not full. I have a MacBook Pro with M3 chip and 64Gb Ram. Enclosed is the error message from the log.

cheers Daniel

Hi Daniel,
sorry but I cannot reproduce the issue here, I've just rendered a 900 frames animation on M4 without issues:

IMG_4460.jpeg

Could you share a scene that shows the issue for you?
You can share a link via Private Message.

ciao,
Beppe

Hi Beppe,

I now have a scene that I can send you. I will send you a link to the download including the bugrepoerts of Octane/OSX/ and cinema 4D via private mail. I hope you can do something with it. The scene crashed at frame 618.
Otherwise everything is going very well and you are doing a good job.
cheers Daniel

Delizade wrote:If I use Octane area light with take system area light rectangle shapes goes crazy.
1) add area light
2) activate both "auto take" and "lock overrides" mode active
3) change area light size/s (position changes do not create any problems, just size modifications do)
4) add another take, change area light size again
5) go back and activate first take

Keep repeat take activations.
Area light size additively changes.

Hi,
please try to do the same with a C4D Area Light, it seems that the issue is in Maxon C4D, not in c4doctane plugin.

ciao,
Beppe

KeeWe wrote:Since we are in the middle of a project and will get a new workstation with a 5090 soon, will there be a production ready build of 2024? I really don't wanna switch to a beta build with a deadline coming up...

Nope, sorry, it is not possible, at least, not before 2025.1 will be stable.

ciao,
Beppe