Matthew Duffy

another issue i noticed is say we have an OSL code i've manually copped to a Arnold:OSL node. if i have a #include "../common/ourfuncs.h" and even if i include the path to the "fullpath/" (which includes common etc) in the ARNOLD_PLUGIN_PATH it does not seem to resolve the relative path so im unsure of how this should work.

hello, so we have USD files, we are exporting from our gaffer lookdev into said USD file, so for example in out USD exported file we have in our materials a


now when we try to import these assets into houdini solaris when we then use the edit material to explode the matierals. it seems to just great 'generic shaders" with the outputs/inputs but not really the shader.
i've tried passing the OSL folder paths to the "ARNOLD_PLUGIN_PATH" but that does not seem to work. is thier a workflow thats built in to allow for osl shaders to be converted into the arnold:osl nodes? or find the names? etc.

hello, i'm taking a look at 456.py based on my logging. 456.py is called alot
the documetion is alittle unclear "Houdini runs this script whenever a scene file is loaded (including when Houdini starts up with a scene file)." the world "only" is missing. thus its unclear if this behavour is correct:

if i open without a scene file, 123 is called THEN 456 is called.
if i go click on "file:new": i get 456.py run NOT 123.py
if i click "file, open some scene" i get 123 and then 456.py.

thank you for any help. or clarfication.