Try setting the environment variable "TF_DEBUG=PLUG_*" to produce a bunch of output about USD's plugin loading when you run husk. This might help figure out why the Arnold plugin isn't being found (which is the first reason I would suspect for causing this issue). Assuming you can run the Arnold delegate in Houdini's viewport, try comparing the output of running husk vs Houdini with that TF_DEBUG setting to see if/where they differ.
tas3d I am not, at least not intentionally. Seems like PowerShell is. I will keep this in mind if I need to run it on different shell. Not sure what Deadline will do once I start sending husk to deadline.
FYI, im on Win10.
Normally to use any Houdini tools on the command line, a lot of env vars have to be set. This is done automatically when using the 'houdini command line tools' cmd prompt. Alternatively, sourcing houdini_setup ensures the shell has been prepared.
hello Michal, how did You setup the environment variables for Your cmd? I tried to do it the same way as I start Houdini to use Arnold. I use a batch to set $PATH and $HOUDINI_PATH and start Houdini, but this does not work with Husk for me, either Arnold is not found by Husk or the $HOUDINI_PATH seems to be not correct, as some other tools are not loaded correctly. Would be great if You could tell me more about how You set up the environment to get Arnold with Husk in a cmd
# htoa config startPATH=$PATH;C:/Users/Tas/htoa/htoa-18.104.22.168_r8825678_houdini-19.0.589.py3/htoa-22.214.171.124_r8825678_houdini-19.0.589.py3/scripts/bin
HOUDINI_PATH= C:/Users/Tas/htoa/htoa-126.96.36.199_r8825678_houdini-19.0.589.py3/htoa-188.8.131.52_r8825678_houdini-19.0.589.py3;&# htoa config end
be careful not to "mess" it up with other plugin paths that might come after/before loading Arnold. It was very finicky to setup. Especially when loading Redshift, Renderman and others all at the same time.