Problems Loading Custom Vex Shaders

[lisux]

Hi all.

I have some custom shaders created in the VEX Builder.

I have created some new SHOPs from these VOPs and every time I open th escene I get a window with severeal warning messages telling that the parameters fo rthis SHOPs are not recognized.

and in the paramer pane I can't see the parameters of these shaders.

I have to manually Refresh Operator Type libraries to get the parametrs back again into the parameter pane, but I lost all my previous settings.

Why it happens?

[lisux]

Hi all.

I have some custom shaders created in the VEX Builder.

I have created some new SHOPs from these VOPs and every time I open th escene I get a window with severeal warning messages telling that the parameters fo rthis SHOPs are not recognized.

and in the paramer pane I can't see the parameters of these shaders.

I have to manually Refresh Operator Type libraries to get the parametrs back again into the parameter pane, but I lost all my previous settings.

Why it happens?

I have made some new tests and every of the shaders I made, coding in VEX and with vcc creating OTLs, I have to put the otl file in $HOME/houdini8.1/otls, otherwise, if I put the otl in other place, I get an error:

Unable to get VEX code from:
		opdef:/Shop/test

Anyone knows why I have to put all of my otl with shaders in my $HOME/houdini8.1 in order to work properly?

Thanks

[lisux]

I have found the error.

the problem is that mantra can't find the otl to load the shader.

I have my otl for this shader in $HIP/otls, the problem is that when I create an IFD the otl is loaded with the next statement:

ray_loadotl ./otls/test.otl

Because is a relative path the render can't find the path to the otl in run time.

But if I install the OTL from $HOME/houdini8.1/otls, the the load statement is:

ray_loadotl $HOME/houdini8.1/otls/test.otl

And then mantra can load th OTL wherever it has been launched.

So my problem now is how to force Houdini to use absolute paths when it creates the IFD, to ensure mantra can fins the otl.

Or even better using the $HIP variable instead of the ./ path.

Anyone having similar problems?

[edward]

Hmm ... Maybe you could try making an OPlibraries file from your $HIP that has absolute paths. See the one $HH for an example

[lisux]

Hmm ... Maybe you could try making an OPlibraries file from your $HIP that has absolute paths. See the one $HH for an example

Thanks edward.

The OPlibraries file seems to use relative paths to $HH.

So Houdini always look for the OPlibraries file installed in the $HIP fila in addition to $HH and $HIH?

Houdini always look to the $HIP variable in every scene opening to find stuff like in the $HIH variable?

At the moment I am using complitaly absolute paths, not the more elegant solution, but the most secure.

[edward]

Not sure. But here's the page that talks about OPlibraries in the online help:

hdox://houdini/content/base/net_otl_adv.html