the file posted above actually failed due to human error -
Julien Depredurand was so kind to show me how to use the gas linear combination DOP properly, I attached the fixed file - and it's working.
Learned something new …
cheers!
Found 433 posts.
Search results Show results as topic list.
Technical Discussion » fluid from attributes
-
- asnowcappedromance
- 512 posts
- Offline
Technical Discussion » fluid from attributes
-
- asnowcappedromance
- 512 posts
- Offline
yes Jeff, I totally agree with you that artists shouldn't need to dive into the big solvers to manipulate them on a much lower level and instead just press some buttons on a nice interface.
I actually have a question to the usage of the gas linear combination DOP.
I set up a quick network that uses the technique of the Source Volume DOP to import the SOP velocity and ran into a problem.
I attached a hipfile, the dopnet right now is using Gas Calculate DOPs (red colored nodes) which work fine but as soon as I replace them with gas linear combination DOPs the setups stops working. (red nodes next to the gas calculate nodes, not connected right now).
what's going on there? Btw the Source Volume DOP doesn't use gas linear combination either …
I actually have a question to the usage of the gas linear combination DOP.
I set up a quick network that uses the technique of the Source Volume DOP to import the SOP velocity and ran into a problem.
I attached a hipfile, the dopnet right now is using Gas Calculate DOPs (red colored nodes) which work fine but as soon as I replace them with gas linear combination DOPs the setups stops working. (red nodes next to the gas calculate nodes, not connected right now).
what's going on there? Btw the Source Volume DOP doesn't use gas linear combination either …
Technical Discussion » fluid from attributes
-
- asnowcappedromance
- 512 posts
- Offline
hi Jeff, thanks for clarifying things, appreciated!
The only thing that keeps me from using those shelf tools is that they create all those extra bunch of nodes that one usually doesn't need and I experienced that it slows the simulation down quite a bit.
Anyway, I like how the source volume DOP works, I will try to adapt this workflow where one creates a tempfield first using the gas match field microsolver, loads the SOP velocity field with a SOP solver and then uses a couple of gas calculate DOPs to pre-multiply the velocity mask and copy the tempvel field onto the vel field.
I learned a lot looking through your file,
best,
Manu
The only thing that keeps me from using those shelf tools is that they create all those extra bunch of nodes that one usually doesn't need and I experienced that it slows the simulation down quite a bit.
Anyway, I like how the source volume DOP works, I will try to adapt this workflow where one creates a tempfield first using the gas match field microsolver, loads the SOP velocity field with a SOP solver and then uses a couple of gas calculate DOPs to pre-multiply the velocity mask and copy the tempvel field onto the vel field.
I learned a lot looking through your file,
best,
Manu
Technical Discussion » vop not compile when file open?
-
- asnowcappedromance
- 512 posts
- Offline
I recently had the same problem, a vex node that worked perfectly fine suddenly gave me all those warnings, try to rebuild the shader, you could use the opscript hscript command to give you the code to rebuild the whole thing and then copy/paste it in the textport after you renamed the old broken node, that rebuilds the whole vex network on the fly!
command would be something like this:
opscript -r /shop/myShader
maybe that could fix the problem. I can't tell you what causes Houdini to behave that way though :?
~ Manu
command would be something like this:
opscript -r /shop/myShader
maybe that could fix the problem. I can't tell you what causes Houdini to behave that way though :?
~ Manu
Technical Discussion » fluid from attributes
-
- asnowcappedromance
- 512 posts
- Offline
you could either use the gas calculate dop to manipulate the velocity field or try gas advect to get the right motion.
I set up a basic scene that shows how to use both methods,
maybe Alejandro can contribute more to your question, he did a really nice smoke path follow test a while ago:
http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=21558 [sidefx.com]
anyway, check out my scene file,
regards,
Manu
I set up a basic scene that shows how to use both methods,
maybe Alejandro can contribute more to your question, he did a really nice smoke path follow test a while ago:
http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=21558 [sidefx.com]
anyway, check out my scene file,
regards,
Manu
Houdini Lounge » new geometry within foreach loop
-
- asnowcappedromance
- 512 posts
- Offline
Technical Discussion » how to timeshift per-primitive?
-
- asnowcappedromance
- 512 posts
- Offline
Houdini Lounge » group based on primitiv attributes
-
- asnowcappedromance
- 512 posts
- Offline
that was some previous version of houdini where grouping wasn't possible, with Houdini 12 you can definitely do it.
http://www.sidefx.com/docs/houdini12.0/hom/hou/PrimGroup [sidefx.com]
http://www.sidefx.com/docs/houdini12.0/hom/hou/PrimGroup [sidefx.com]
Houdini Lounge » group based on primitiv attributes
-
- asnowcappedromance
- 512 posts
- Offline
Hi,
Why don't you do the grouping in that python SOP that is plugged
into the group node? If you're looking for a node based approach,
put the group SOP into a foreach SOP, loop N times over your primitives
and stamp the loop iteration onto the group name parameter, use the
stamp() expression in the group's expression field as well!
Best,
Manu
Why don't you do the grouping in that python SOP that is plugged
into the group node? If you're looking for a node based approach,
put the group SOP into a foreach SOP, loop N times over your primitives
and stamp the loop iteration onto the group name parameter, use the
stamp() expression in the group's expression field as well!
Best,
Manu
Houdini Lounge » SpaceShip Engine Glow
-
- asnowcappedromance
- 512 posts
- Offline
have a look at this thread:
http://forums.odforce.net/index.php?/topic/14865-engine-test/ [forums.odforce.net]
cheers,
Manuel
http://forums.odforce.net/index.php?/topic/14865-engine-test/ [forums.odforce.net]
cheers,
Manuel
Technical Discussion » fuse SOP distance
-
- asnowcappedromance
- 512 posts
- Offline
good question, can't really explain it,
I tend to snap the points together (you can use average position) based on a dist threshold, which gives way better results and then have another fuse SOP consolidate them (or facet SOP).
I tend to snap the points together (you can use average position) based on a dist threshold, which gives way better results and then have another fuse SOP consolidate them (or facet SOP).
Technical Discussion » VOP SOPs
-
- asnowcappedromance
- 512 posts
- Offline
Houdini Lounge » Voronoi fracturing: Choseing the shape of the fractures
-
- asnowcappedromance
- 512 posts
- Offline
well with Voronoi that's not going to be possible,
the nature of the algorithm itself doesn't allow anything like that,
feel free to read about it in detail:
http://en.wikipedia.org/wiki/Voronoi_diagram [en.wikipedia.org]
of course you could always instance any shape onto the cubes after they've been simulated and fake the crumble - reveal in comp!?
the nature of the algorithm itself doesn't allow anything like that,
feel free to read about it in detail:
http://en.wikipedia.org/wiki/Voronoi_diagram [en.wikipedia.org]
of course you could always instance any shape onto the cubes after they've been simulated and fake the crumble - reveal in comp!?
Technical Discussion » Determine multiparm add/remove button #
-
- asnowcappedromance
- 512 posts
- Offline
I'm pretty sure there's no way of accessing the plus or minus buttons with python, what you could do - add an integer parm to your node and have the have the multiparmfolder relative reference it, that way you can create a callback script on the integer parm and just hide the multiparm plus minus button in the ui.
callback script is something easy like this:
def evalParms():
node = hou.pwd()
parmNum = node.parm(“integerParm”).eval()
print parmNum
callback script is something easy like this:
def evalParms():
node = hou.pwd()
parmNum = node.parm(“integerParm”).eval()
print parmNum
Technical Discussion » how to timeshift per-primitive?
-
- asnowcappedromance
- 512 posts
- Offline
Technical Discussion » VOP SOPs
-
- asnowcappedromance
- 512 posts
- Offline
you're use of npt as an end condition looks correct to me, no infinite looping here. You can test that by printing i inside of the forloop!
best,
Manu
best,
Manu
Technical Discussion » how to create interactive fracture
-
- asnowcappedromance
- 512 posts
- Offline
I'm sure if you look through the forums there's plenty of example files in how to do that kind of stuff, however, I put an example file together that encompasses a couple of techniques on how to achieve such an effect using the solver SOP and VOP SOPs.
This is just one way to do it and I kept it simple (feel free to enhance the effect), there's a couple of other ways to do it as well.
have fun,
Manu
This is just one way to do it and I kept it simple (feel free to enhance the effect), there's a couple of other ways to do it as well.
have fun,
Manu
Technical Discussion » volume not moving
-
- asnowcappedromance
- 512 posts
- Offline
you had set the scalar object (density) to default operation “always” which overwrote the density at every new substep. Also, if you do a volume from attribute operation don't forget to specify which attribute you want to base it on, in your case you were missing a “v”.
best,
Manuel
best,
Manuel
Houdini Lounge » Voronoi fracturing: Choseing the shape of the fractures
-
- asnowcappedromance
- 512 posts
- Offline
Technical Discussion » Custom Variable mapping
-
- asnowcappedromance
- 512 posts
- Offline
what Martin means is when you create an attribute with the “add attribute” VOP there is a parameter “Local Variable Name” where you can set the variable mapping :wink:
-
- Quick Links