Long-standing basic problem: white balance

[AWOLism]

No problem, happy to help.

[elsksa]

Thankyou! truly, thankyou, this is what we were missing. Universally in c4d all the useful settings always start on the third tab of attribute settings, we were skimming over this 'main' tab the same way that you automatically skim past banner adverts on webpages, or cant find the butter in the fridge despite it being at the front of the middle shelf.

We were under the impression that octane being a spectral renderer meant that setting a white balance for the light was mandatory for all lights

This is exactly what I was showing in my first message:
viewtopic.php?f=30&t=78729#p406387
and my screenshot:
viewtopic.php?f=30&t=78729#p406419

What matters is that you have realized/found out what you were looking after.

[boxfx]

This is exactly what I was showing in my first message:

In a piece of software that we don't use.

If I ask where the fuel cap unlock button is on a Honda Civic in a Honda Civic forum, telling us where it is on your Ford Explorer, maybe not so helpful.

[elsksa]

As I did mention, the options are the same in both Octane Standalone and Octane for Cinema 4D. The GUI differs.

It is just a matter of "finding where is the brake pedal in both different cars from the same brand", so to speak.

I would not say that it was "may be" not helpful.

As long as you have found out by now, that is all that really does matter.

[elsksa]

There is a WB Option within the camera imager

Without deeply covering the rather advanced subject I have forgot to mention (and inform) that both "White Point" and "White Balance"/"Chromatic Adaptation" should not be mistaken.
Additionally, there is "white balance" on integer "display referred" rasterized image files and "white balance" on raw (not images) files. Different scenarios, different behaviors, different R'G'B' encoding context, mathematics, et cætera.