OTOY Forums

I'm trying to compare a C4D render to Octane render. In order to do this I would like to light the scene the exact same way. I'm not really sure how Octane interprets an image when I load it into an OctaneSky.

Compared to a C4D sky, the differences seem to be:

1. Octane flips the HDR on X axis

2. OctaneSky image is a lot more washed out (I'm assuming its linear interpretation) and has a greenish tint

Anyone know of a way to have the OctaneSky look exactly the same in terms of gamma and color as a C4D Sky?

Thanks!

Hi,
what's the purpose of this? Octane have not to be same as c4d's sky. It has own algoritms to produce a sky. There is lot of parameters to change appearance of rendered image. How are you trying to put a image to sky?

Octane have a workflow for lighting the scenes.
A environment lighting and some geometry with emissive materials. Environments can be a Octane daylight or a hdri kind texture or a combination of both.
Also you can put any textures to environment to illuminate the scene. Even you can scale, rotate or tweak brightnes, etc. of this textures.

Hey Aoktar,

I'm basically just trying to get as close to a native Cinema render as possible so I can compare the render times for *almost* the same image. I'm aware Octane processes and sets up the scene differently.

I got pretty close results. I don't have a huge understanding of different color spaces, but the following seemed to get the renders pretty close in terms of gamma and color:

C4D Render:
1. Flip texture of HDRI sky and rotate to match
2. Enable Physical Render and GI
3. Set to linear in save options and sky texture

Octane Render:
1. In Cam Imager set gamma to 2.2 and response to linear.
2. In save settings set to sRGB (not sure why linear doesn't give me the results)

So I totally could be approaching this the wrong way, but the results are pretty close. If anyone has a better idea please say so!

interesting. You are comparing apples to bananas. Octane is a path tracer. Works similar to brute force method of GI. But calculates every pixels without doing some aproximation.

Haha yes, I'm aware its apples to bananas.