OTOY Forums

J.C wrote:

aoktar wrote:

J.C wrote:I've sent it last time with the video. Here it is again If you missed it.

We haven't see this behavior in our systems or heard from others. Reset your C4D prefs to let our preferences are default and try again. Defaults are well, be sure you don't have something else to bug us.

Still happens after resetting settings, both on my system and my friend's system too. I've checked also with Cinema S24 and 2023.1 and 2023.2

As I said try to test it with default layout. For example, Texture UV dialog is setting dirty flags when it is open.

Hi,
in the 2022.1.1-R5 (Cinema4D 2023) I'm not able to save render pass anymore.
I had to switch back to 2022.1.

cirasa wrote:Hi,
in the 2022.1.1-R5 (Cinema4D 2023) I'm not able to save render pass anymore.
I had to switch back to 2022.1.

I encountered the same issue, and I changed the "Plugins" directory to lowercase "plugins" as prompted. Then I deleted all the xdl64 files except for "c4dOctane-R2023.xdl64". After that, I was able to perform multi-channel rendering normally.

PS: There is a hotfix version for 2022.1.1-R5, which you can download from the website.

Hi,

not shure if I'm doing something wrong, but when rendering Octane-EXR-AOVs
(of course I checked "safe beauty" and "denoised beauty") in AE with "Extractor"
all passes are there except the "Denoised Beauty"

I'm on C4D 2023.2 and Octane 2022.1.1R4

thanks
Mike

btw the same with R5.
When I disable "multilayer" and render in separate folders the
"denoised beauty" gets rendered.
Also in LV the "Object Color Pass" is correct, but when rendered as EXR it is completely black

Fixed! Sorry for the trouble!

It seams, that my C4D Scenefile was completely messed up.
Don't know why, but good old "copy files in a new blanc scene" fixed the Render Issues!

Thanks anyway
Mike

aoktar wrote: As I said try to test it with default layout. For example, Texture UV dialog is setting dirty flags when it is open.

I've tried default layout and it stops restarting itself, but the reason for this is a Timeline (Dope Sheet) window. I had it docked in my layout. When the window is opened, weather with custom or with default layout, it causes restarts.
It would be great if you solved this issue weather on your side or with Maxon.

J.C wrote:

aoktar wrote: As I said try to test it with default layout. For example, Texture UV dialog is setting dirty flags when it is open.

I've tried default layout and it stops restarting itself, but the reason for this is a Timeline (Dope Sheet) window. I had it docked in my layout. When the window is opened, weather with custom or with default layout, it causes restarts.
It would be great if you solved this issue weather on your side or with Maxon.

Just because I read your comment and had a project open: I can confirm this bug. Custom layout with a docked timeline causes the problem. If the timeline is not active (I have it docked beneath the node editor and aov manager), the LV doesn't refresh.

I noticed (and mentioned) it ages ago that octane has problems with custom layouts. Switching to a different layout causes the node editor or the settings window not to load properly and either beeing blank or it opens in a separate, undocked, window. It only fixes this by loading a single monitor layout and than switch back. Pretty annoying doing it 10 times a day...

I think it was introduced around S25 or so.

edit: the LV refreshes as well when changing the in and out points of the timeline. Another thing were an update shouldn't occure.

Hello, I've also encountered the update issue. I'm using the latest Cinema 4D 2023 and Octane versions, when I move the camera around the scene force to update every time.

I've tryed settin up a simple scene, just a cube with an HDRI, but the problem still occur, with the live-viewer active when I move the camera the scene continuosly update.

Never seen this issue, only with the latest octane version R5.

Thank you

KeeWe wrote: Just because I read your comment and had a project open: I can confirm this bug. Custom layout with a docked timeline causes the problem. If the timeline is not active (I have it docked beneath the node editor and aov manager), the LV doesn't refresh.

I noticed (and mentioned) it ages ago that octane has problems with custom layouts. Switching to a different layout causes the node editor or the settings window not to load properly and either beeing blank or it opens in a separate, undocked, window. It only fixes this by loading a single monitor layout and than switch back. Pretty annoying doing it 10 times a day...

I think it was introduced around S25 or so.

edit: the LV refreshes as well when changing the in and out points of the timeline. Another thing were an update shouldn't occure.

There are not a BUG on my side, C4D is having a strange design to give problems for developers. No clues to understand the user operations to know for example layouts are switched, or objects are unchanged. Switching a layout that causes to close and open the windows. We don't know it will open after a close, and we treat as they are closed. It requires to resend the scene. Otherwise stability issues will appear.
It's my not mistake if we see strange issues after a C4D update. It means Maxon silently changed something and giving problems. We/you should first talk to Maxon not to Otoy.
What you should do here so:
Stop to making a bug report party here and show me the problem. Then I'll talk to Maxon if it's caused by their changes. But most of time they will not change anything and will give advices without real solutions.

aoktar wrote: What you should do here so:
Stop to making a bug report party here and show me the problem. Then I'll talk to Maxon if it's caused by their changes. But most of time they will not change anything and will give advices without real solutions.

We are not making bug party here but trying to solve issues. The bug was confirmed by my friends and other user and we now know what is causing it.
I think it's better you communicated with Maxon, as you as the developer of popular plugin may have more influence to make them fix the issue we encounter.

J.C wrote:

aoktar wrote: What you should do here so:
Stop to making a bug report party here and show me the problem. Then I'll talk to Maxon if it's caused by their changes. But most of time they will not change anything and will give advices without real solutions.

We are not making bug party here but trying to solve issues. The bug was confirmed by my friends and other user and we now know what is causing it.
I think it's better you communicated with Maxon, as you as the developer of popular plugin may have more influence to make them fix the issue we encounter.

Well, good to know but it's not helping much. Give me more solid and specific examples by PM. Also as I said some are special cases and no way to workaround or solve it without loosing some performance or stability on our side.
Record some videos and send me by PM, not forum.