Sliders - changed ranges and behaviour?

Fri Jul 22, 2016 11:25 am

I'm not sure what version it happened on but the slider behaviour and defaults changed to less useful ones on some parameters.

Eg
Mix material amount. Why is 0.5 not the middle of the slider but about 3/4 to the right?

Light intensity - Did this change, I don't know but the range is HUGE, 0 - 100000, I rarely need go above a few 100 and most of the time below that, dragging the slider therefore is way too coarse (the little arrows are a pain to use and it takes a second to get your mouse pointer located correctly on a big 5k display. I end up typing it in all the time. PIA. Where's the function to snap to the nearest 10 when holding option key and dragging?

Ditto many others (Glare, Bloom power, Gamma and Contrast many and various shader intensities) where the useful typical ranges are crammed down one tiny part of the slider range.

SSS Phase. What is going on with the behaviour of that slider? The mid point is -1 and the values go in reverse when you drag past it...

I haven't mentioned them before because they seemed such obvious problems I assumed they'd get fixed each update. When spending all your working day using sw there's nothing worse than a tool with frustrating core UI functionality IMO.

Fri Jul 22, 2016 12:22 pm

Can you be more specific? I don't see anything on mix slider,etc... as you said. Which version? Any images to show this problem?

Sat Jul 23, 2016 11:36 am

Octane 3.00-R1.1

Cinema 17.048

OSX 10.11.5

Sat Jul 23, 2016 12:47 pm

try with latest builds. I've added c4d slider type then removed because was not working well with ranges, etc...

Sun Jul 24, 2016 5:00 pm

aoktar wrote:try with latest builds. I've added c4d slider type then removed because was not working well with ranges, etc...

Seems to work better. Can we have snapping to whole (or x10) values when holding alt?

Mon Jul 25, 2016 10:32 am

And could we at least have the slider stop at its maximum value (eg 1.0) when moved all the way to the right?

Mon Jul 25, 2016 10:44 am

sdanaher wrote:And could we at least have the slider stop at its maximum value (eg 1.0) when moved all the way to the right?

They stop at maximum values if they have max=1 or max=10 or similar. Don't involve them with MAX and SLIDERMAX. Which sliders doesn't stop at max? Are you using "Octane default" or "Octane C4D like" with some recent builds like 3.03.2?

Also some sliders have logaritmic behaviour as in standalone. Nothing is different than STANDALONE for parameter ranges and behaviour if i haven't missed to syhnc someone.

Mon Jul 25, 2016 11:34 am

aoktar wrote:
sdanaher wrote:And could we at least have the slider stop at its maximum value (eg 1.0) when moved all the way to the right?
They stop at maximum values if they have max=1 or max=10 or similar. Don't involve them with MAX and SLIDERMAX. Which sliders doesn't stop at max? Are you using "Octane default" or "Octane C4D like" with some recent builds like 3.03.2?

Also some sliders have logaritmic behaviour as in standalone. Nothing is different than STANDALONE for parameter ranges and behaviour if i haven't missed to syhnc someone.

Brightness in Colour Correction node for example.

I have the same settings as in your pic.

Mon Jul 25, 2016 11:37 am

sdanaher wrote:
aoktar wrote:
sdanaher wrote:And could we at least have the slider stop at its maximum value (eg 1.0) when moved all the way to the right?
They stop at maximum values if they have max=1 or max=10 or similar. Don't involve them with MAX and SLIDERMAX. Which sliders doesn't stop at max? Are you using "Octane default" or "Octane C4D like" with some recent builds like 3.03.2?

Also some sliders have logaritmic behaviour as in standalone. Nothing is different than STANDALONE for parameter ranges and behaviour if i haven't missed to syhnc someone.
Brightness in Colour Correction node for example.

I have the same settings as in your pic.

It's float texture and MAXVALUE is not 1.0. Do you want that to be 1.0?

Mon Jul 25, 2016 11:52 am

aoktar wrote:
It's float texture and MAXVALUE is not 1.0. Do you want that to be 1.0?

The max value appears to be 1.0 as that's where the slider maxes out. The saturation slider is also float, but that stops at exactly 3.0 at the end of the slider range. Its all very inconsistent.

Alt seems to give fine control over the slider which is nice (though not in line with Cinema's interface standards for slider behaviour). I just discovered that changing the slider type to Float Slider gives the standard Cinema behaviour with integer alt-key snapping etc. Can this be done globally?