Problems using latest ADN GitHub OSL pack with 3dsmax2020

[MysticLtd]

Hi!

I loaded the the actual OSL Shader Package from ADN GitHub space (https://github.com/ADN-DevTech/3dsMax-OSL-Shaders) and added them, following the steps in the documentation (http://help.autodesk.com/view/3DSMAX/2020/ENU/?guid=GUID-9DD7702C-31B0-47F2-965F-460FE2E42522).

Now for some shaders the UI seems to be incomplete f.e. the "Curves (color)" .

Here two screenshots: One from my 3dsmax2020 with the OSL package added afterwards and one screen**** from the 3dsmax2021 new features video, which shows how the shader UI should look like.

You can see what is missed are the control curves, unfortunately the main feature of the shader 😞 .

Now my question is: Is there a way to make these new OSL shaders work in 3dsmax 2020 somehow?

Thanks in advance! Greetings!

[MysticLtd]

Hi!

I loaded the the actual OSL Shader Package from ADN GitHub space (https://github.com/ADN-DevTech/3dsMax-OSL-Shaders) and added them, following the steps in the documentation (http://help.autodesk.com/view/3DSMAX/2020/ENU/?guid=GUID-9DD7702C-31B0-47F2-965F-460FE2E42522).

Now for some shaders the UI seems to be incomplete f.e. the "Curves (color)" .

Here two screenshots: One from my 3dsmax2020 with the OSL package added afterwards and one screen**** from the 3dsmax2021 new features video, which shows how the shader UI should look like.

You can see what is missed are the control curves, unfortunately the main feature of the shader 😞 .

Now my question is: Is there a way to make these new OSL shaders work in 3dsmax 2020 somehow?

Thanks in advance! Greetings!

[madsd · Accepted solution]

No.

The reason is that additional UI functionalities are build around the OSL intitiative which is not backward portable.
The new UI route started in 2021.

QT ui, we can write the UI in qt designer as .ui files, bring in qt widgets and so on, rearrange and design the ui, we can only go "so far" when building ui directly in the OSL code.

What you get in 2020 should be a working shader, but with an auto generated UI, some features may go missing, you need to clean up the code if it glitches for you, but its not a bug, so yeah, up to you.

Im also doing for example the OSL Triplanar with qt UI, it would be impossible to do this kind of ui interactivity in 2020. I actually dynamically reformat the UI if certain checkboxes are touched, as an example --->

[madsd · Accepted solution]

No.

The reason is that additional UI functionalities are build around the OSL intitiative which is not backward portable.
The new UI route started in 2021.

QT ui, we can write the UI in qt designer as .ui files, bring in qt widgets and so on, rearrange and design the ui, we can only go "so far" when building ui directly in the OSL code.

What you get in 2020 should be a working shader, but with an auto generated UI, some features may go missing, you need to clean up the code if it glitches for you, but its not a bug, so yeah, up to you.

Im also doing for example the OSL Triplanar with qt UI, it would be impossible to do this kind of ui interactivity in 2020. I actually dynamically reformat the UI if certain checkboxes are touched, as an example --->

[MysticLtd]

Thanks for your detailed replay! I understand.

Sadly this is not what I hoped for, but it answers the question. I honestly feared something like that.

Unfortunately I am not familiar with coding and programming so writing the UI by myself direct in the OSL code as you suggested is not an option to me.

Maybe I should force to upgrade to 2021.

[MysticLtd]

Thanks for your detailed replay! I understand.

Sadly this is not what I hoped for, but it answers the question. I honestly feared something like that.

Unfortunately I am not familiar with coding and programming so writing the UI by myself direct in the OSL code as you suggested is not an option to me.

Maybe I should force to upgrade to 2021.

[madsd]

If you ask me, I find plenty of reasons that justify the upgrade.

[madsd]

If you ask me, I find plenty of reasons that justify the upgrade.