Found 5 posts.
Search results Show results as topic list.
Houdini Lounge » Diagnosing errors
- kay.cloud
- 5 posts
- Offline
Well here it is a year later. There's been no response or suggestions on how to locate the offending source of the problem and I still have the same error message. How would one search a hip file for the parameter name if the parameter doesn't exist?
Technical Discussion » print vex node is not working inside material shader builder
- kay.cloud
- 5 posts
- Offline
FYI: others might be interested in the response I got from support:
Hi Kay,
This is because our new materials are multi-context (ie, displacement shader, surface shader, etc, all in one) so print vop doesn't know in what context you are evaluating.
This is what you need to do to get it working:
- add a Null VOP
- pipe one of the input wires to Surface_Output VOP through the Null VOP (so that the input node goes into the Null VOP and the Null VOP goes into the Output VOP)
- connect the Print Vop node to the second input of the Null VOP I made a quick example with the Wood material…
Cheers,
Silvina
Technical Discussion » print vex node is not working inside material shader builder
- kay.cloud
- 5 posts
- Offline
Is this a known but? We are using 11.0.692. This continues to work fine in our old style material networks.
For example, I take a distribution “Wood” material, add the print node and turn it on, but nothing shows up in my console.
For example, I take a distribution “Wood” material, add the print node and turn it on, but nothing shows up in my console.
Technical Discussion » catching python exceptions from _hou module
- kay.cloud
- 5 posts
- Offline
try:
node.matchCurrentDefinition()
if isLockedAsset(node):
if DEBUG: print “now locked again”
else:
if DEBUG: print “failed to lock previously locked node %s” % path
except Exception, e:
print(“relockParents failed with exception %s %s on %s” % (e, str(e), path))
This is not the first or only time that I have encountered this from the _hou plugin. I have only been doing python code in houdini for the last week, but have done a lot of other python programming. But I have seen this a number of times where something fails in the plugin but the try/except doesn't catch it. We are on 11.0.692.
node.matchCurrentDefinition()
if isLockedAsset(node):
if DEBUG: print “now locked again”
else:
if DEBUG: print “failed to lock previously locked node %s” % path
except Exception, e:
print(“relockParents failed with exception %s %s on %s” % (e, str(e), path))
This is not the first or only time that I have encountered this from the _hou plugin. I have only been doing python code in houdini for the last week, but have done a lot of other python programming. But I have seen this a number of times where something fails in the plugin but the try/except doesn't catch it. We are on 11.0.692.
Technical Discussion » catching python exceptions from _hou module
- kay.cloud
- 5 posts
- Offline
It seems as if something prevents catching exceptions generated from the _hou plugin. It's nice to at least see the traceback, but I would rather be able to generate that myself and to be able to catch the exceptions for handling more gracefully in my code. What's this about? Is there some special mode that I need to be in to be able to catch the exceptions?
e.g.,
The line that is throwing the exception is encapsulated in a try/except block.
Traceback (most recent call last):
File “<console>”, line 1, in <module>
File “<console>”, line 170, in otlImport
File “<console>”, line 12, in relockParents
File “/home/prisms/builder-new/Nightly11.0/dev/hfs/houdini/python2.5libs/hou.py”, line 5146, in matchCurrentDefinitio
n
return _hou.Node_matchCurrentDefinition(*args)
OperationFailed: The attempted operation failed.
e.g.,
The line that is throwing the exception is encapsulated in a try/except block.
Traceback (most recent call last):
File “<console>”, line 1, in <module>
File “<console>”, line 170, in otlImport
File “<console>”, line 12, in relockParents
File “/home/prisms/builder-new/Nightly11.0/dev/hfs/houdini/python2.5libs/hou.py”, line 5146, in matchCurrentDefinitio
n
return _hou.Node_matchCurrentDefinition(*args)
OperationFailed: The attempted operation failed.
-
- Quick Links