Martin Krol
Martin Krol
About Me
EXPERTISE
VFX Artist
INDUSTRY
Film/TV
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Python: set attribute type Oct. 24, 2023, 3:24 p.m.
Hey there guys.
For whatever reason trying to set the attribute type 1 in the paint node keeps giving me errors.
I can change the attribname1 with no problem but trying to change the attribtype1 to use Color by setting it to a value of "0" always gives an error.
here's an example of code
Anyone of you have this error show up for ya?
EDIT: Nevermind. I was being dumb. "" turns it into a string. needed to remove the quotations.
For whatever reason trying to set the attribute type 1 in the paint node keeps giving me errors.
I can change the attribname1 with no problem but trying to change the attribtype1 to use Color by setting it to a value of "0" always gives an error.
here's an example of code
attribNodeAttribNameParm = attribNode.parm("attribname1") attribNodeAttribNameParm.set("Cd") attribNodeAttribTypeParm = attribNode.parm("attribtype1") attribNodeAttribTypeParm.set("0")
Anyone of you have this error show up for ya?
EDIT: Nevermind. I was being dumb. "" turns it into a string. needed to remove the quotations.
Resample Sop Node Default settings. Oct. 26, 2022, 4:38 p.m.
Hey there.
I hope this post doesn't sound like I am angry. Just a little frustrated after having had 2 hangups today due to unwanted behaviour.
I haven't made any form of RFE in years now so I am not sure of the process, but would it be possible to change the default behaviour from having it set to maximum segment length to max segments instead? The reason I say this is that it is not always the case that people work on small scenes. It always gets me hit in the but when I place it in a large scene and it cooks forever because by default it's set to 0.1 When working with units as large as 100000 or more, this behaviour often crashes the scene, or takes absolutely forever to cook. I would rather have a safe mode for this node that shows what it does regardless of scene scale ( even if the max segments are set to a higher value like 100 or 1000 and then adapt to my needs.
No node should ever crash/ or break houdini because the user is not working at an expected scale. This has bugged me for years now. It's just that today it hit me in the butt twice, and it is getting annoying.
I know I can set defaults, but that doesn't fix the issue at it's core. Every time I update workstations, change studios, get a new houdini version rolled out, etc. I don't want to have to keep track of this issue.
hopefully others agree.
I hope this post doesn't sound like I am angry. Just a little frustrated after having had 2 hangups today due to unwanted behaviour.
I haven't made any form of RFE in years now so I am not sure of the process, but would it be possible to change the default behaviour from having it set to maximum segment length to max segments instead? The reason I say this is that it is not always the case that people work on small scenes. It always gets me hit in the but when I place it in a large scene and it cooks forever because by default it's set to 0.1 When working with units as large as 100000 or more, this behaviour often crashes the scene, or takes absolutely forever to cook. I would rather have a safe mode for this node that shows what it does regardless of scene scale ( even if the max segments are set to a higher value like 100 or 1000 and then adapt to my needs.
No node should ever crash/ or break houdini because the user is not working at an expected scale. This has bugged me for years now. It's just that today it hit me in the butt twice, and it is getting annoying.
I know I can set defaults, but that doesn't fix the issue at it's core. Every time I update workstations, change studios, get a new houdini version rolled out, etc. I don't want to have to keep track of this issue.
hopefully others agree.
Point attrib to Node name set. ( Python) June 1, 2022, 9:57 p.m.
Thanks guys.
So, for whatever reason using node.setName(str(someDeclaredVariable))
was giving me the following error:
hou.NetworkMovableItem_setName(self, name, unique_name)
OperationFailed:the attempted operation failed.
However, I did as hinsunlee suggested. I wrote str(someDeclaredVariable)) into the name section when creating the node and not as a separate line, and it worked out
.
so what worked was changing this line
createGeoNode = createWorkArea.createNode("geo", "geoNode")
into this
createGeoNode = createWorkArea.createNode("geo", str(fullPathAttrib))
Cheers.
So, for whatever reason using node.setName(str(someDeclaredVariable))
was giving me the following error:
hou.NetworkMovableItem_setName(self, name, unique_name)
OperationFailed:the attempted operation failed.
However, I did as hinsunlee suggested. I wrote str(someDeclaredVariable)) into the name section when creating the node and not as a separate line, and it worked out
.so what worked was changing this line
createGeoNode = createWorkArea.createNode("geo", "geoNode")
into this
createGeoNode = createWorkArea.createNode("geo", str(fullPathAttrib))
Cheers.