Page 1 of 1

OSL shader input issues compared to other DCCs, Standalone

Posted: Sat Sep 27, 2025 10:31 am
by tombyrom
Hello neonZorglub
In 3dsmax when using an OSL texture, the OSL texture map does not show all possible input pins?

It looks like it only shows input pins for color and texture inputs... There are no input pins for floats, vectors etc

This also means that I cannot input a Sun Direction map into a vector input because there is no input pin being shown.

I compared this to the 3dsmax built in OSL shader map, as well as comparing against Octane Blender and Octane Standalone

They expose all input pins as standard, allowing you to plug whatever you need.

I am reporting as a bug as I don't believe the 3ds Max implementation is correct.

Attaching scene and screenshots

Thanks
Tom

Re: OSL shader input issues compared to other DCCs, Standalone

Posted: Sun Oct 05, 2025 10:00 pm
by neonZorglub
Hi tombyrom,

Thanks for the sample.
Those extra pins are hidden by default, because it currently affects all materials and textures and can make the UI a bit heavy..

You can enable those in Octane Preferences / Material / 'Activate Value Texmaps', and then by restarting 3dsMax.

See the related post :
"New Octane Value Textures"
viewtopic.php?t=82743

I checked you scene, and seems to work:
osl_tex_with_ValueTexmaps.png

[EDIT] : in fact, there are some issues with some OSL textures when activating Value Texmaps ..
Some of the other osl parameters are not sent correctly to the Octane renderer.
Sorry about that. This should be fixed in the next releases.

Thanks

Re: OSL shader input issues compared to other DCCs, Standalone

Posted: Tue Oct 07, 2025 4:48 pm
by tombyrom
Thanks neonZorglub, I did look in preferences for a setting but completely overlooked that one, I will turn it on.

I am not sure if you spotted but when I turn this on to get all input pins. The moon tint value no longer works properly? It seemed locked to a red colour unless I switched it back to a value.
However, changing the value or changing the built in colour did not update the tint. I wasn't even using an input.

Turning off this preference, removing all inputs, and the tint starts to work properly again. Maybe you spotted this already?

Edit: In fact this is the same for all colour inputs, any colour input no longer functions correctly when I turn that preference on (even when nothing is plugged into the pin)