Cinema4D version 2024.1.2-R2 Build 0101

[J.C]

Thanks for new build!

The most important issue which is still there in the new build is the viewport update when objects or material changes. For example when I hide an object the change is not registered and only happens when something else changes in scene.
The crashes are less frequent but happen few times every day. The worst part is that they happen randomly and freeze whole Cinema app without the possibility to save the opened project. I've developed a common practice to save a project every time befre launching Octane window.

There is also small unfixed UI bug with displaying the amount of free vram:

stats.png (27.04 KiB) Viewed 9346 times

The other UI issue is the comparison feature. Left side A image is always the last rendered image and right B image is the old one. I think it should be opposite like for example in Lightroom where there is a Before (left side) and After (right) image, not the opposite.

[ChrisHekman]

Thanks for new build!

The most important issue which is still there in the new build is the viewport update when objects or material changes. For example when I hide an object the change is not registered and only happens when something else changes in scene.

we cannot seem to reproduce this issue. Could you give us steps to reproduce this, or a scene where this happens for you?

The crashes are less frequent but happen few times every day. The worst part is that they happen randomly and freeze whole Cinema app without the possibility to save the opened project. I've developed a common practice to save a project every time befre launching Octane window.

do you happen to have a scene you can share with me where this happens more often? I would like to check it out.

[Secretwoodsrl]

First of all thank you aoktar for your work, and I wish you good luck Chris!

I wanted to share a small issue with the live viewer update, that maybe could be fixed in the new releases.
I don't know if it's the same problem reported before.

When using the C4D viewport in "Geometry Only" mode (Filter -> Geometry Only), Octane Liveviewer doesn't update in real time anymore.
Furthermore updates like hiding/disabling objects are not visible till a render restart.
If I disable the "Geometry Only" flag then everything works good!

I've attached a simple video of this issue.

[DinoMuhic]

First of all thank you aoktar for your work, and I wish you good luck Chris!

I wanted to share a small issue with the live viewer update, that maybe could be fixed in the new releases.
I don't know if it's the same problem reported before.

When using the C4D viewport in "Geometry Only" mode (Filter -> Geometry Only), Octane Liveviewer doesn't update in real time anymore.
Furthermore updates like hiding/disabling objects are not visible till a render restart.
If I disable the "Geometry Only" flag then everything works good!

I've attached a simple video of this issue.

I can confirm this and have added it to our bug tracker, thanks

[J.C]

Thanks for new build!

The most important issue which is still there in the new build is the viewport update when objects or material changes. For example when I hide an object the change is not registered and only happens when something else changes in scene.

we cannot seem to reproduce this issue. Could you give us steps to reproduce this, or a scene where this happens for you?

The crashes are less frequent but happen few times every day. The worst part is that they happen randomly and freeze whole Cinema app without the possibility to save the opened project. I've developed a common practice to save a project every time befre launching Octane window.

do you happen to have a scene you can share with me where this happens more often? I would like to check it out.

Regaining the crashes I can't provide any of such scenes because they aren't public sources. I'll upload some bug reports that I could find in users folder.

As far as updating is concerned I'll share a screen capture showing such issues. It definitely happens with more complex scenes.

[cjadams]

welcome Chris and thank you for putting up with our craziness here!!!

One thing I would like to bump up the list is conversion of red shift materials and red shift textures etc.
The main reason for this is that Maxon is releasing a lot of new assets but none of them have obviously third-party or octane render compatibility

At this point however we know that almost everybody is moving towards the similar standard of interoperability eventually …but that time is not yet come.

[Kalua]

Build looks good so far, team!
Exciting new times ahead for c4d + Octane!
I have already requested this in other forums channels but wanted to bring it here too considering this is a very fresh topic.
Could we have a bar indicator for P2P Memory pool for those who use 2x3090 + Nvlink?
Just like the one Stand Alone has. I push memory usage to the limit and would love to know how C4D Octane is using my resources.
Regards,

[aoktar]

welcome Chris and thank you for putting up with our craziness here!!!

One thing I would like to bump up the list is conversion of red shift materials and red shift textures etc.
The main reason for this is that Maxon is releasing a lot of new assets but none of them have obviously third-party or octane render compatibility

At this point however we know that almost everybody is moving towards the similar standard of interoperability eventually …but that time is not yet come.

I have done some work to implement a Converter for RS materials. Team will use it soon. But every type of nodes are not supported well, it is a problem for assets in library. They will try to improve it

[UON.Visuals]

Can anyone tell my why I get this error? For the past few releases it pops up as soon as I hit render on the live viewer window even on a blank default project.

But I hit the render button again and then it works! On my render queue when one render finishes, the following renders all get errors because of this (until I manually open them and hit the render button twice, then hitting render in the render queue they work fine)
I suspect it has something to do with my OCIO environment but I tried both setting one and leaving it blank and it happens either way

[DinoMuhic]

Can anyone tell my why I get this error? For the past few releases it pops up as soon as I hit render on the live viewer window even on a blank default project.

But I hit the render button again and then it works! On my render queue when one render finishes, the following renders all get errors because of this (until I manually open them and hit the render button twice, then hitting render in the render queue they work fine)
I suspect it has something to do with my OCIO environment but I tried both setting one and leaving it blank and it happens either way

This usually happens when you have set your LiveViewer to OCIO<> but the look you want to use is not there (because you changed your ocio.config file or opened a scene file that needs a different OCIO View that is currently not present).