OTOY Forums

aoktar wrote:

marshalartist wrote:We have attempted to send a link via direct message for a scene file, please can you comfirm if you have received it.
If not please can you send us an appropriate email address. We can not post the file publicaly

You can use PM system of forum

PM sent

aoktar wrote:

Kalua wrote:Thanks, Aoktar!
Overall working great here.
One question: I see Universal Camera now has a "Keep up-right" function, which is very nice. However I see it behaves differently than Thinlens Perspective control in regards to the camera vertical movement which seems to be inverted.
Please refer to .gif
Is it supposed to be like his?
Regards,

Hi Kalua! I don't write the Core, so I don't know what's supposed to be.

Thanks, Aoktar.
I thought this could be an implementation issue!
Regards,

EDIT: Actually now I realise, I think I mistaken "keep-upright" with perspective correction. I guess the right way to make perspective correction with Univrsal Camera is with C4D's camera "Film offset X and Y".

Hi,

trying to render an older project with new 2022.1.1R2 (c4d 2023.2) with some passes.
At "Displaying Post processing pass" Octane never finishes rendering.

And I cannot stop the rendering. Have to quit C4D with the task manager.

Any help on this?

Thanks
Mike

miohn wrote:Hi,

trying to render an older project with new 2022.1.1R2 (c4d 2023.2) with some passes.
At "Displaying Post processing pass" Octane never finishes rendering.

And I cannot stop the rendering. Have to quit C4D with the task manager.

Any help on this?

Thanks
Mike

Test it on a new project by copy content to define the issue. Send the scene if you cannot still solve it

I got the same issue. No matter which pass I remove it's displaying the same message. I tried moving everything to a new document and it's the same thing. Got the newest octane/c4d plugin versions.

UPDATE: the issue was some non-octane materials. After converting them I had no problems.

kasperrubin wrote:I got the same issue. No matter which pass I remove it's displaying the same message. I tried moving everything to a new document and it's the same thing. Got the newest octane/c4d plugin versions.

UPDATE: the issue was some non-octane materials. After converting them I had no problems.

Rather than materials, C4D textures will be a reason of issues. Thanks for info

Hello,

I don't understand why changing the Color Space of an Instance Color Node works well... but is then ignored if I render the scene again (or navigate in the timeline).
Is this normal? (I'm not use to change color space)
Thank you.

Toche wrote:Hello,

I don't understand why changing the Color Space of an Instance Color Node works well... but is then ignored if I render the scene again (or navigate in the timeline).
Is this normal? (I'm not use to change color space)
Thank you.

Not normal, there are two functions one is changing the colorspace to sRGB here. It's a kind of bug, I'll fix it for next build.

We are having the issue with not being able to save render passes after updating to C4D 2023.2.0

We have tried making sure we are only using Octane materials and textures, not using any C4D shaders or textures. Also created new .c4d files from 2023.2.0 but we still have the issue on a couple of computers. Even upgrading to the latest Octane Standalone + plugin version did not help fix the issue. One of our slower render boxes with 3x 2080ti will render the passes but our render box with 2x 4090 will not save the passes

lightborne wrote:We are having the issue with not being able to save render passes after updating to C4D 2023.2.0

We have tried making sure we are only using Octane materials and textures, not using any C4D shaders or textures. Also created new .c4d files from 2023.2.0 but we still have the issue on a couple of computers. Even upgrading to the latest Octane Standalone + plugin version did not help fix the issue. One of our slower render boxes with 3x 2080ti will render the passes but our render box with 2x 4090 will not save the passes

I haven't change anything to cause this on plugin side, but I'm suspecting about C4D and their SDK. What's the version numbers of C4D in computers with issues? It should be fine with latest update of C4D and this R3 build. At least we cannot get the issue here.
https://render.otoy.com/customerdownloa ... R3_win.rar