No parameters at properties tab in renderman rop. Build 186, suse.
Is this a bug?
BUG?
4252 9 0- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
ok, copying of some libs from dsolib to bin helps me to start proto_install
Next troubles:
Would you like to test the driver now? y
The following render should appear in mplay.
/opt/hfs9.1.188/bin/imdisplay-bin: error while loading shared libraries: libHoudiniUT.so: cannot open shared object file: No such file or directory
R90007 {SEVERE} DisplayWindow failed to send display data (System Error: Broken pipe)
Next troubles:
Would you like to test the driver now? y
The following render should appear in mplay.
/opt/hfs9.1.188/bin/imdisplay-bin: error while loading shared libraries: libHoudiniUT.so: cannot open shared object file: No such file or directory
R90007 {SEVERE} DisplayWindow failed to send display data (System Error: Broken pipe)
Houdini is great! O'right?
- edward
- Member
- 7722 posts
- Joined: July 2005
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- edward
- Member
- 7722 posts
- Joined: July 2005
- Offline
- Wish
- Member
- 282 posts
- Joined: Jan. 2006
- Offline
- JColdrick
- Member
- 4140 posts
- Joined: July 2005
- Offline
You should not be running things this way, it sounds like you've been making some pretty big assumptions about shortcuts. Here's the way it should be done:
Install Houdini as root, accept default location.
Anytime you want to run houdini products, *go to the hfs install dir* and source the startup script. Do not do this as root.
Run houdini as your account(after renaming/deleting $HOME/houdini9.1 should it exist since it sounds like you've got a problematic one in there at the moment).
Run proto_install as your account, not root.
Now, that's not to say you couldn't copy and rewrite your own houdini startup script that mimics what the sesi one does and doesn't require you to go to a specific location to run it, but that's at least a mid if not advanced level admin task.
Cheers,
J.C.
Install Houdini as root, accept default location.
Anytime you want to run houdini products, *go to the hfs install dir* and source the startup script. Do not do this as root.
Run houdini as your account(after renaming/deleting $HOME/houdini9.1 should it exist since it sounds like you've got a problematic one in there at the moment).
Run proto_install as your account, not root.
Now, that's not to say you couldn't copy and rewrite your own houdini startup script that mimics what the sesi one does and doesn't require you to go to a specific location to run it, but that's at least a mid if not advanced level admin task.
Cheers,
J.C.
John Coldrick
-
- Quick Links