missing operators / missing parameters

   13416   8   3
User Avatar
Member
345 posts
Joined:
Offline
Hi all,

I don't know why is that happening but every time I start houdini I get following warnings.

$ Can't open dophints.cmd
Warning: Bad operator type when binding handles: Object/path
Warning: Bad operator type when binding handles: Object/path
Warning: Bad operator type when binding handles: Cop2/emboss

I am on XP 64, dophints.cmd is in the right place. It looks like it is machine related problem, I reinstalled houdini a couple of times and still get the same thing. Any ideas?

Thanks
kuba

PS. The most annoying thing is that camera node is created with transform and render tab only, the rest parameters I have to add manually. Also I miss some cop operators… anyway any suggestions will be very helpful.
User Avatar
Member
1769 posts
Joined: Dec. 2006
Offline
Had similar problem when i set houdini otl scan path variable, and the factory otls were not found at startup
daniel bukovec | senior fx td | weta digital
qLib -- http://qlab.github.io/qLib/ [qlab.github.io]
User Avatar
Member
345 posts
Joined:
Offline
Thanks Daniel,

Just installed again cop2 asset and in fact I can access all of the missing cops. But is it related in anyway with dophints.cmd…?
User Avatar
Member
1769 posts
Joined: Dec. 2006
Offline
I cannot answer that since i'm not that experienced with technical side of this
daniel bukovec | senior fx td | weta digital
qLib -- http://qlab.github.io/qLib/ [qlab.github.io]
User Avatar
Member
7709 posts
Joined: July 2005
Online
Try moving aside your $HOME/houdini9.X directory?
User Avatar
Staff
4435 posts
Joined: July 2005
Offline
The dophints error is not related to the binding handles error. I strongly suspect that both are the result of a badly set path. I would suspect the HOUDINI_PATH given that you are getting these two unrelated errors. What is your HOUDINI_PATH set to? If you are not explicitly setting this value, try running “hconfig -ap” from the Houdini Command Line Tools. This will print out all the paths used by the Houdini environment. You should make sure that the HOUDINI_PATH entry includes “$HFS/houdini” as one of the search directories.

And you can definitely create an Emboss COP? The “bad operator type” message means that Houdini has no idea what the Emboss COP is… So I can't think of any reason you would be getting this message _and_ be able to create an Emboss COP…

Mark
User Avatar
Member
509 posts
Joined: July 2005
Offline
weird to respawn such thread but I'm bumping into the same issue.

I'm trying to add a site-wise directory containing my custom otl I want to be accessible from my workstations .. and if I set the HOUDINI_OTL_SCAN_PATH in my shell (is that the right place?) I loose all the default olts and get the “binding handles” error in my shell …
I went through the whole help but I'm confused, and I'd like not to go with the old opLibrary method as it seems now deprecated…

any help would be appreciated

thanks!
JcN
VisualCortexLab Ltd :: www.visualcortexlab.com
User Avatar
Member
1769 posts
Joined: Dec. 2006
Offline
hi!

your otl_scan_path should be set in the houdini.env file and it has to end with $HFS otls, otherwise it cant pickup the factory otls:

my env file looks like this:

HOUDINI_OTLSCAN_PATH = $HOME/houdini12.1/otls;some other otls path;$HFS/houdini/otls
daniel bukovec | senior fx td | weta digital
qLib -- http://qlab.github.io/qLib/ [qlab.github.io]
User Avatar
Member
614 posts
Joined: Aug. 2008
Offline
8)
  • Quick Links