OctaneRender™ Standalone 1.33 Tweet

[pixelrush]

Why did I know you would disagree...
Why don't you just listen to the users for a change?
To be blunt I don't like your attitude.
I wont be a customer after 1.x

[abstrax]

Ok, so please help me out a bit: How are sliders of a very wide range better than the new input methods using the scroll wheel or the mouse sliding? I was never able to enter any useful position this way. In the end I always had to type in the coordinate in older versions.

Of course, we can bring the sliders back, that's easy. But does it make things better or worse? To give you an example what I mean with a cluttered interface, here are two screenshots of a camera in CINEMA 4D and in OctaneRender:

Although the C4D camera has lots more options, the user isn't immediately overwhelmed and you can quickly find the parameters you are looking for. The version in Octane looks more like a dashboard of Battlestar Galactica or something. Granted, the sliders are only part of the problem, but they are certainly not improving the readability. At least in my opinion.

[xxdanbrowne]

My 2c:

I personally like the sliders but I get the point about the cluttered interface too.

Might I make a suggestion by way of asking a question to the Octane team?

How hard would it be to do the sliders and have like a tiny minimize button at the edge to make the sliders vanish?

[manalokos]

Sliders are good for shader values, and stuff like angles, values that have a defined range.

The "holding the mouse button down and moving the mouse up and down" using the tiny arrows was one of the best upgrades in Octane's UI, works perfectly in all kinds of variables, and for translation it is the best way to interact for sure!

[abstrax]

My 2c:

I personally like the sliders but I get the point about the cluttered interface too.

Might I make a suggestion by way of asking a question to the Octane team?

How hard would it be to do the sliders and have like a tiny minimize button at the edge to make the sliders vanish?

I think, that's possible and something we have been pondering with for quite some time. It also has been proposed multiple times in the past. The reason why we haven't done it yet is, because it takes quite some effort to do it right and we just didn't have the time for it yet. But yes, I hope eventually we will implement a better way to display node values in the future.

[Zay]

Isn't it possible to collaps/uncollaps the values and have Octane remembering it and even save it to .ocs files?

[abstrax]

Isn't it possible to collaps/uncollaps the values and have Octane remembering it and even save it to .ocs files?

You mean the current collapse / uncollapse state? Yes that shouldn't be too much work so we may squeeze it in.

[Zay]

You mean the current collapse / uncollapse state? Yes that shouldn't be too much work so we may squeeze it in.

Yes, that's it. It would give a better overview and faster workflow if you could hide (collaps) the values you hardly ever use or have already set and don't want to touch again, when moving back and forward between the materials.

[smicha]

You can increase the speed with the SHIFT modifier 10x and with the CTRL modifier 100x.

That is what I said. For me this solution is perfect.

BTW. What if there was a slider with custom min and max values, so that a user could input them manually and then use a slider?

[LudovicRouy]

I like the idea of a more compact UI with mouse use and shift ctrl !