Found 20 posts.
Search results Show results as topic list.
Houdini Indie and Apprentice » Houdini 13.0.198.21 does not show point\primitive number
- valshev
- 20 posts
- Offline
Why my Houdini 13.0.198.21 apprentice does not show point\primitive number and normals? I have tried out this on two different computers with the same result. Is it a bug?
Technical Discussion » help initiation failed
- valshev
- 20 posts
- Offline
Hi there,
I have a problem while initiating the help browser in H11 -
upon startup I get a message:
Could not initialize the help server:
Traceback (most recent call last):
File “<stdin>”, line 1, in <module>
File “C3D/Houdini/houdini/python2.6libs\houdinihelp\__init__.py”, line 36, in <module>
from lxml import etree
ImportError: DLL load failed: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Reinstalling does not solve this.
Anybody have an idea how to fix the matter?
I have a problem while initiating the help browser in H11 -
upon startup I get a message:
Could not initialize the help server:
Traceback (most recent call last):
File “<stdin>”, line 1, in <module>
File “C3D/Houdini/houdini/python2.6libs\houdinihelp\__init__.py”, line 36, in <module>
from lxml import etree
ImportError: DLL load failed: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
Reinstalling does not solve this.
Anybody have an idea how to fix the matter?
Technical Discussion » Flipping primitive normals
- valshev
- 20 posts
- Offline
Technical Discussion » Flipping primitive normals
- valshev
- 20 posts
- Offline
Imagine a box having primitive normals directed from inside toward outside of the box. How to flip them all opposite direction?
…or more precisely, how to flip a normal of an individual polygon?
…or more precisely, how to flip a normal of an individual polygon?
Technical Discussion » two polygons into one polygon
- valshev
- 20 posts
- Offline
Technical Discussion » two polygons into one polygon
- valshev
- 20 posts
- Offline
Hi there, I have a simple model which comprises two polygons like this:
I need to get rid of one of the two polygons like so:
So far I have not find any simple solution. Any suggestion? I am new to Houdini
I need to get rid of one of the two polygons like so:
So far I have not find any simple solution. Any suggestion? I am new to Houdini
Technical Discussion » hscript or python?
- valshev
- 20 posts
- Offline
I noticed that even experienced guys here still use hscript, not python.
I understand that python is a powerful language. But concerning Houdini, is
it worth to use it as it is for now with many features not implemented yet?
I understand that python is a powerful language. But concerning Houdini, is
it worth to use it as it is for now with many features not implemented yet?
Technical Discussion » Attribute name needs to be updated automatically problem
- valshev
- 20 posts
- Offline
Technical Discussion » Attribute name needs to be updated automatically problem
- valshev
- 20 posts
- Offline
Consider the following:
So we have one point, attribute ‘attribute1’ added to it,
and the Point surface node in which I put lvar('ATTRIBUTE1').
It is all right and works.But what if you want to change
the attribute name to different one, say ‘abc’.
Then you need also to type manually ‘ABC’ inside lvar(…): lvar('ABC')
in order to update the network. The question is what kind of expression
we need to put inside lvar(…) - lvar(some_expression) - so that there will be no need
to type every time the new name inside lvar(…) and the network
will get updated automatically?
So we have one point, attribute ‘attribute1’ added to it,
and the Point surface node in which I put lvar('ATTRIBUTE1').
It is all right and works.But what if you want to change
the attribute name to different one, say ‘abc’.
Then you need also to type manually ‘ABC’ inside lvar(…): lvar('ABC')
in order to update the network. The question is what kind of expression
we need to put inside lvar(…) - lvar(some_expression) - so that there will be no need
to type every time the new name inside lvar(…) and the network
will get updated automatically?
Technical Discussion » Indexing point attribute. Help needed
- valshev
- 20 posts
- Offline
It works! This is exactly what I need.
To Antoine Durr: It's just the way I learn Houdini and I'm trying to push it to the limits and see whether it can do what I want or cannot. Seems can.
Thank you guys!
To Antoine Durr: It's just the way I learn Houdini and I'm trying to push it to the limits and see whether it can do what I want or cannot. Seems can.
Thank you guys!
Technical Discussion » Indexing point attribute. Help needed
- valshev
- 20 posts
- Offline
hou.pwd().geometry().iterPoints().attribValue('attribute1') is definitely
what works in the python shell but not inside parameter field as expected.
Is it a bug?
what works in the python shell but not inside parameter field as expected.
Is it a bug?
Technical Discussion » Indexing point attribute. Help needed
- valshev
- 20 posts
- Offline
Technical Discussion » Indexing point attribute. Help needed
- valshev
- 20 posts
- Offline
This is what the Attrib Create surface node looks like
And the Transform surface node must look like
If you just use hou.pwd().curPoint().attribValue(“attribute1”)
it does'nt work because there is no point iteration. What I need is
to use direct access to the point#1 attribute1, 'some_expression',
which directly gives the integer value 1
And the Transform surface node must look like
If you just use hou.pwd().curPoint().attribValue(“attribute1”)
it does'nt work because there is no point iteration. What I need is
to use direct access to the point#1 attribute1, 'some_expression',
which directly gives the integer value 1
Technical Discussion » Indexing point attribute. Help needed
- valshev
- 20 posts
- Offline
Back here because of my previous topic.
Thank you guys who helped me before.
So I have 2 points created by the Add surface node.
Then I added an attribute ‘attribute1’ to each point by the Attrib Create surface node.
The ‘attribute1’ attrib has a class of ‘point’, type of ‘integer’,size of 1 and the ‘Value’ parameter equal to $PT (or lvar('PT') for python).
Another words the point#0 has the attribute1 = 0, and point#1 attribute1 = 1.
Then I subsequently added the Transform surface node in which I want the ‘ty’ parameter to be equal to the ‘Value’ parameter of the ‘attribute1 for point#1 ,i.e 1.
What I dug out from the help on HOM should look like the sequence
1. a = hou.node(’/obj/geo1/xform1')
2. g = a.geometry()
3. i = g.iterPoints() (where … stands for point #1)
4. x = i.attribValue('attribute1')
and voila you have x = 1 and put it into the ‘ty’ parameter!
That's okay but it only worked in the Python shell. I can't figure out what kind of expression I have to type in the ‘ty’
parameter field which resides inside the Transform surface node. Whatever I tried nothing worked yet
Please help cos I am new to HOM and expressions
Thank you guys who helped me before.
So I have 2 points created by the Add surface node.
Then I added an attribute ‘attribute1’ to each point by the Attrib Create surface node.
The ‘attribute1’ attrib has a class of ‘point’, type of ‘integer’,size of 1 and the ‘Value’ parameter equal to $PT (or lvar('PT') for python).
Another words the point#0 has the attribute1 = 0, and point#1 attribute1 = 1.
Then I subsequently added the Transform surface node in which I want the ‘ty’ parameter to be equal to the ‘Value’ parameter of the ‘attribute1 for point#1 ,i.e 1.
What I dug out from the help on HOM should look like the sequence
1. a = hou.node(’/obj/geo1/xform1')
2. g = a.geometry()
3. i = g.iterPoints() (where … stands for point #1)
4. x = i.attribValue('attribute1')
and voila you have x = 1 and put it into the ‘ty’ parameter!
That's okay but it only worked in the Python shell. I can't figure out what kind of expression I have to type in the ‘ty’
parameter field which resides inside the Transform surface node. Whatever I tried nothing worked yet
Please help cos I am new to HOM and expressions
Technical Discussion » How to independently edit point attribs?
- valshev
- 20 posts
- Offline
Okay, I agree, but for me it is still not clear how to implement this idea using the Null node as a control and what kind of field you add inside the Null interface and what expression you put then. I mean an expression that explicitly operates on one point and changes the attribute for only that point
Technical Discussion » How to independently edit point attribs?
- valshev
- 20 posts
- Offline
Imagine you have two points created by the Add surface node.
Then you add to each point an attribute say attrbute1 (class point, type integer, size 1) by means of the Attrib Create surface node. Then you want to change the integer value of the atribute just for one point independently say for point number 1. For example point 1 had the attribute1 integer value = 0 and you want to set it as 1. Okay, you may just go to Details View Tab and enter it. But this is done internally and not using some expression or extra node. The question is how to do this EXTERNALLY say using the Null surface node? Or maybe using some other sort of surface nodes?
Then you add to each point an attribute say attrbute1 (class point, type integer, size 1) by means of the Attrib Create surface node. Then you want to change the integer value of the atribute just for one point independently say for point number 1. For example point 1 had the attribute1 integer value = 0 and you want to set it as 1. Okay, you may just go to Details View Tab and enter it. But this is done internally and not using some expression or extra node. The question is how to do this EXTERNALLY say using the Null surface node? Or maybe using some other sort of surface nodes?
Technical Discussion » Python does not work
- valshev
- 20 posts
- Offline
Technical Discussion » Python does not work
- valshev
- 20 posts
- Offline
I was playing with python in the Houdini master 10.0.465 and found the following:
1. Create a grid ( or whatever) object
2. Add the Transform surface node to it
3. In the rotate ( transform, scale …) parameter field put
hscriptExpression(“$F”). The Python button is turned on
4. Try to animate
You will see that nothing is happening. Although the value of $F does show up in the field. Once you change the python expression back to hscript
( hscriptExpression(“$F”) -> $F ) everything is okay now.
Is this a bug?
1. Create a grid ( or whatever) object
2. Add the Transform surface node to it
3. In the rotate ( transform, scale …) parameter field put
hscriptExpression(“$F”). The Python button is turned on
4. Try to animate
You will see that nothing is happening. Although the value of $F does show up in the field. Once you change the python expression back to hscript
( hscriptExpression(“$F”) -> $F ) everything is okay now.
Is this a bug?
Technical Discussion » Attrib Reorient surface node tricky parameter
- valshev
- 20 posts
- Offline
Technical Discussion » Attrib Reorient surface node tricky parameter
- valshev
- 20 posts
- Offline
I was playing with the Attrib Reorient surface node and looked into
Houdini help on the subject:
I found that they use ‘orient’ parameter created in the Attrib Create surface node:
Everything is fine and ok. Unless you change the parameter name from orient to something different say ‘foo’ or whatever. Since that the teapots do not obey at all:
The question is whether the ‘orient’ is specific and something unique?
I did not find any reference on it throughout Houdini help
Houdini help on the subject:
I found that they use ‘orient’ parameter created in the Attrib Create surface node:
Everything is fine and ok. Unless you change the parameter name from orient to something different say ‘foo’ or whatever. Since that the teapots do not obey at all:
The question is whether the ‘orient’ is specific and something unique?
I did not find any reference on it throughout Houdini help
-
- Quick Links