OTOY Forums

Joss wrote:If i understand correctly, V component of HSV is just a value, color itself coded just by Hue and Saturation, so if you changing just V, you basically having the same color shade with different brightness,

Yes, I did used the english term not the right way, not shade but brightness. But it does not change the sense.

Joss wrote:and that brightness can be perfectly used as a light power.

Yes, it can be used as light power, but not twice. But if you will use it to form the color, then set this RGB color to Octane environment texture, and then use the same parameter again to set the power of lighting of Octane environment that includes this RGB-texture (and that I think also has another scale of that value) - you will change the lighting power in the quadratic form. E.g. you have HSV:360,1,1 and you want to decrease the brightness twice. And you decrease the "V" to 0.5 (twice). Yes, you get the color twice less bright. But: after that you will get the power of Octane texture environment decreased from 1.0 to 0.5 too, so as result after decreasing the "V" just twice you will get the resulting brightness reduce of Octane environment squared: to four times - twice less bright RGB color will shine with twice less lighting power in Octane texture environment.

Technically - it is no problem, I can change it to such behaviour easily... But, I'm still doubting that it will be correct...
Maybe someone else will express his opinion too about it?

Here's a link to the crash logs for the IES files:

https://dl.dropbox.com/u/85554647/ies%20crash.zip

For some reason it seems like the octane light doesn't read the ies files.
The blackbody node works perfectly with ies files with a mesh, though.

Not sure it would be a good idea to have the value in the hsv diffuse linked to the material's power setting (even though it's a familiar workflow for me as well) if it doubles or quadruples the brightness or becomes redundant imho.

Slimshader
Thank you!

EDIT: Found the reason. Will be fixed in next version soon...

Got it. I wasn't used standalone much, and it was too much time ago, so i just don't remember it has a separate "power" control for env light.

Well, the possible solution could be to add 2 more attributes to camera octane attributes section, say, "envColor" and "envPower",
"where envColor" could be linked right to the camera's background color, and envPower set to default "Power" value.
And if user adding env node to scene, just use that node values over the camera ones.

But yes, would be nice to listen to some opinions.

*Update*:
Another option is just to use some default "Power" value and control env with color brightness.

Next version HERE.