Page 1 of 1
OSL Texture Sliders Have Unbound Min/Max
Posted: Tue Dec 01, 2020 5:32 pm
by blastframe
A. Windows 10
B. 2 x NVIDIA Titan Black
C. 64 GB Memory
D. Driver 457.30
E. OctaneRender Enterprise 2020.1.5
F. 2020.1.5-R4
G. Cinema 4D R23.110
H.
Hello,
Currently most of the .osl scripts included with Octane do not specify min & max for their sliders, making them extremely difficult to use. I realize that this is because of the OSL Script's developers omission of code such as
, but there should be a better fallback for this as it is very common and I assume most users would not know OSL scripting. Currently, just a small tweak of the float slider goes from 0.1 to 3136242826161580685133037700330291200 (screenshots attached).
- Before
- After
Re: OSL Texture Sliders Have Unbound Min/Max
Posted: Tue Dec 01, 2020 6:28 pm
by aoktar
How it can be a bug? I added these for making help and you report as bug. Not fair, sorry! You can easily add a few parameters to define limits, they are script for users
Re: OSL Texture Sliders Have Unbound Min/Max
Posted: Tue Dec 01, 2020 6:35 pm
by blastframe
Hi Ahmet,
I have worked for major software companies before and this is something that would be filed as a User Experience bug. The software does not operate in accordance with user expectations, particularly if they are new to OSL and are looking to these scripts as examples. It is part of the software you distribute and, if the scripts had proper quality control (and if it's so easy to do), they would have sliders that were set up correctly.
Please have more respect for your customers.
Re: OSL Texture Sliders Have Unbound Min/Max
Posted: Tue Dec 01, 2020 8:20 pm
by aoktar
I can happily remove wrong scripts if it frustrated you. I don't have resources to fix every scripts or send me corrected versions to put in to library.
Re: OSL Texture Sliders Have Unbound Min/Max
Posted: Tue Dec 01, 2020 9:03 pm
by Goldorak
blastframe wrote:Hi Ahmet,
I have worked for major software companies before and this is something that would be filed as a User Experience bug. The software does not operate in accordance with user expectations, particularly if they are new to OSL and are looking to these scripts as examples. It is part of the software you distribute and, if the scripts had proper quality control (and if it's so easy to do), they would have sliders that were set up correctly.
Please have more respect for your customers.
I will personally work out the included OSL issues being non-obvious to users with the team. We are working hard to make most useful OSL shaders baked into 2020.2 across core/plug-ins shortly to minimize confusion.