-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add OSL-node support #12
Comments
First, .osl files that are on disk that are present during startup work right? SItoA asks Arnold what shaders are available and generates shader nodes/UIs, correct? Second, is this about a generic osl code shader? If so, then I would use the Text Editor widget (can it be used in shader nodes, I don't know). |
I wasn't aware of this but reading the docs now and yes that should already work. So what we need is a text editor and the PPG to update after a change. So... Text Widget or Edit in script editor? |
So since this is the first time I read about how osl works in Arnold I didn't really know what we needed until now.
This node can take osl code directly as a string and in that case it need to use the Text Widget in the PPG. |
'shadername' is a path to an osl file? that is a very odd parameter name... @sjannuz , is there any details about what shadername is/does? |
See Manually Loading Shaders here: https://support.solidangle.com/display/A5ARP/OSL+Shaders |
I see... not sure how best to use that. |
How could / should this be done?
The text was updated successfully, but these errors were encountered: