Some questions about the difference between plugin and stand

[gordonrobb]

I just wanted to discuss a few differences between standalone and plugin, that I wanted to know if it was possible to fix.

To be honest they are all the same thing.

Almost everything that you change in Standalone updates directly. This is especially useful when adjusting colours. Is there anyway, that the plugin can change to have this behaviour?

Also, a while ago, I asked about the differnece (in gamma I think) between the colour you see in the picker, and the colour that you end up with in the render. There is definitly a difference between the two. In standalone, what you pick, is what is shown. Not so in plugin. This is particulary difficult with dark colours, I have to get down to the difference between r,g,b, 1,1,1, and 2,2,2 to get it right.

What do you think?

[juanjgon]

I just wanted to discuss a few differences between standalone and plugin, that I wanted to know if it was possible to fix.

To be honest they are all the same thing.

Almost everything that you change in Standalone updates directly. This is especially useful when adjusting colours. Is there anyway, that the plugin can change to have this behaviour?

Also, a while ago, I asked about the differnece (in gamma I think) between the colour you see in the picker, and the colour that you end up with in the render. There is definitly a difference between the two. In standalone, what you pick, is what is shown. Not so in plugin. This is particulary difficult with dark colours, I have to get down to the difference between r,g,b, 1,1,1, and 2,2,2 to get it right.

What do you think?

Color pickers in Lightwave are not dynamic, so I can't change the colors without select a color and close them ... but you can change in real time the color parameteres if you click and drag over the numeric values of all the color widgets, and even change them to HSV if you right+click over them.

About color corrected color picker, the problem is that Lightwave can't correct the color picked using the Octane response curves of it's tone mapper. I am not sure about how standalone works, but in the plugin when I pick a color a get a linear value, if you select a (.1,.1,.1) gray, I get this values an this are the values that I put in the Octane parameter, later Octane applies the gamma and tonemmaping you have in your settings, and it could becomes lighter ... but I can't convert this color using the Octane response curves or other tone mapper parameters.

I am going to see if could be possible at least correct the gamma of the picked color ... this could help.

-Juanjo

[FrankPooleFloating]

That reminds me.. in LW Options > CS, should we have it set with Color Correct OpenGL off and Affect Color Picker on?

In other words, I have it set to full linear on everything and only Affect Color Picker checked... this correct?

(seems to work good like this - but can't hurt to double-check)

[gordonrobb]

When I do that, there is less of an issue between colour picker and what Octane renders. But AFAIK, this was NOT what you were supposed to do.

[gordonrobb]

.. but you can change in real time the color parameteres if you click and drag over the numeric values of all the color widgets, and even change them to HSV if you right+click over them.
-Juanjo

Not sure I understand this bit. Can you tell me what you mean?

[juanjgon]

You can left+click and drag over the color numeric values to change them in real time. If you right+click over them, you can change from RGB to HSV parameters.

-Juanjo

[gordonrobb]

Woh! Going to try that right now