Display range for Octane node parameters ...

[adkkda]

Hi folks,

Not sure if this has been asked before. I searched and came up blank so here it goes.
I'm sure some of you noticed that on the stand alone (C4D also has these, not sure about the rest) all parameters have defined ranges. Some of those are obvious while some are not so obvious. It would be really great if we had something similar, tho I'm not sure if LW allows for this functionality? Thanks.

[UnCommonGrafx]

I'm betting you won't get many +1s for this: discussions have revealed some users want that and that others often go outside those numbers, as it is allowed.

As a question that's been asked on the discussion, "Why do you need the software to tell you the limit, outside of it stopping at a set number?"

For conversation sake...

[atnreg]

In LW the sliders have some ranges but you can type in any value. And in my opinion that is exactly great, that way you can adjust the values for very different cases, not only those that the parameter is meant for. I really hope this will not change in LW nor Octgane plugin

[adkkda]

Hey guys,

Perhaps my question was a bit vague/misleading, I wasn't asking for hard coded limits I simply suggested that it might be handy if the OCTANE ranges were somehow available/displayed. Might be handy to know what the OCTANE ballpark is and when you're beyond it. I'm well aware of LW sliders and driving the values above and beyond, and as you I like them just as they are , in OCTANE tho most of that is mute when you are not in the ballpark so to speak, so a roughness of 200% (in LW) or 2.0 (in standalone if you could go that high) would have zero effect.

[hdace]

Hey guys,

Perhaps my question was a bit vague/misleading, I wasn't asking for hard coded limits I simply suggested that it might be handy if the OCTANE ranges were somehow available/displayed. Might be handy to know what the OCTANE ballpark is and when you're beyond it. I'm well aware of LW sliders and driving the values above and beyond, and as you I like them just as they are , in OCTANE tho most of that is mute when you are not in the ballpark so to speak, so a roughness of 200% (in LW) or 2.0 (in standalone if you could go that high) would have zero effect.

Sounds reasonable to me.

[atnreg]

Hey guys,

Perhaps my question was a bit vague/misleading, I wasn't asking for hard coded limits I simply suggested that it might be handy if the OCTANE ranges were somehow available/displayed. Might be handy to know what the OCTANE ballpark is and when you're beyond it. I'm well aware of LW sliders and driving the values above and beyond, and as you I like them just as they are , in OCTANE tho most of that is mute when you are not in the ballpark so to speak, so a roughness of 200% (in LW) or 2.0 (in standalone if you could go that high) would have zero effect.

Yes and I meant that those slider values could be limited to 'official' value range but as you can type any value, it would not limit the usage

[juanjgon]

There is an important problem in the LightWave SDK: it doesn't have floating sliders. I can add sliders with limited ranges, but only for integer values.

Anyway I think that there is a way to set a limit for the floating value if you scrub the <> button. I will see if this feature can be useful in our plugin.

-Juanjo

[adkkda]

There is an important problem in the LightWave SDK: it doesn't have floating sliders. I can add sliders with limited ranges, but only for integer values.

Anyway I think that there is a way to set a limit for the floating value if you scrub the <> button. I will see if this feature can be useful in our plugin.

-Juanjo

Thanks Juanjo,

I had an inkling that this is a LW SDK issue, and yes, only if you feel it would ultimately be useful.

[adkkda]

Yes and I meant that those slider values could be limited to 'official' value range but as you can type any value, it would not limit the usage

Precisely Antti Ideally LW should provide some sort of mechanism for seeing those ranges as well.

A good example might be the scattering direction (-1 to 1) VS scattering scale (0.0001 - 10,000) as indicated by the octane stand alone.
Some might miss the fact that scattering direction can be reversed (negative dial) while for scattering scale you wouldn't really want to explore those extreme precision limits via a slider.

Anyway ... I just thought it might be a nice to have, plus it might make life easier for folks using Juanjo's other render integrations which I'm sure would have their own unique ranges.