It seems like the Invoke Node isn't limited by the Local Scheduler, no matter how many CPU counts I set in the Local Scheduler Node, the Invoke Node will use more CPU. And in my case, I run some OpenCL code in Invoke Node, and it created 15 workitems parallelly and cause the GPU crashing. And then my computer just restarts by itself.
So is there any way to limit the CPU use for Invoke Node? Or how can I run the Invoke node not parallelly? Thanks.
Found 159 posts.
Search results Show results as topic list.
PDG/TOPs » How to limit the CPU counts for Invoke Node
- EricSheng
- 159 posts
- Offline
PDG/TOPs » force PDG network to run completely in-process?
- EricSheng
- 159 posts
- Offline
Yeah, but as far as I know, there's no way to run ROP Fetch/HDA Processor/Hython in-process, so I write a lot in-process node with Python Processor and saved as TOP node hda on my own. like import image as HeightField geometry/output HeightField as Image, split geometry to workitem by attribute, etc. With Python Geometry class and Python SOP Verb I guess you can write many PDG version SOP easily, although I think it's should've done by SESI but sadly not. And what's more, with Invoke TOP node you can use some compiled compatibility SOP to run in-process, you can check the Partition by Bounds TOP node to see how to work with the Invoke Node.
Still, a lot of things can't run in-process easily or I just can't figure it out, like export geometry as fbx, or work with non-compiled compatibility SOP.
I think a lot of these functions really should offer by SESI but overall it's still very early stage for PDG. I hope the upcoming Solaris won't like these.
Still, a lot of things can't run in-process easily or I just can't figure it out, like export geometry as fbx, or work with non-compiled compatibility SOP.
I think a lot of these functions really should offer by SESI but overall it's still very early stage for PDG. I hope the upcoming Solaris won't like these.
Edited by EricSheng - 2019年9月7日 02:44:09
Technical Discussion » Why is Houdini constantly making decisions for me?
- EricSheng
- 159 posts
- Offline
pickledBabaJDoes anyone have to be overly presumptuous to think that no one likes to press T (or E/R) twice in order for the tool to switch to the new selection? Do you personally like the results you get with the PolyBevel? I could go on with many others.
The only problem is some artists make too many assumptions about other artists. Which is really what the implied original point of my post in this thread was.
There are (basic) things in Houdini that are broken and have not been addressed, even after reporting them, which I think makes the preferences discussion kinda moot at this moment. That is, unless someone's prepared to state that they prefer things that are demonstrably broken.
I agree with you Pickled, does anyone enjoy the Curve SOP in Houdini? It's so hard to use compared to Cinema4D's Curve tool.
Technical Discussion » Why is Houdini constantly making decisions for me?
- EricSheng
- 159 posts
- Offline
Yeah, Houdini really lacks of basics functions, e.g. can't select/edit multiple points in Curve SOP. Can't select SOP node in viewport which will cause merge multiple parts to one node and select a single part becoming such a hell.
SideFX is good to make cool things, but unfortunately, these won't change soon.
SideFX is good to make cool things, but unfortunately, these won't change soon.
Technical Discussion » Can't assign some parameter to volumeresize SOP Verb in python
- EricSheng
- 159 posts
- Offline
PDG/TOPs » How to distinguish between these two workitem states, light green and deep green?
- EricSheng
- 159 posts
- Offline
The left light green checked nodes have fully cooked, and the right deep green checked nodes have cooked and changed some parameter on the top node. If I recook the end node, the left nodes will not get recooked except for the end node, but the right nodes will get recooked for all the nodes.
So how can I tell these two states of the nodes? If I check the workitem state with Python, these two will all return “CookedSuccess”.
Technical Discussion » Can't assign some parameter to volumeresize SOP Verb in python
- EricSheng
- 159 posts
- Offline
fuatHi, fuat:
Not in Front of houdini, but maybe two ideas :
- are you working on a volume or on a vdb?
- did you try setting the same tilecount on a SOP rather than calling the Verb from Python? With the exact same values. Does that work ?
Thanks for your reply, I'm working on a volume(actually a HeightField), It works well from SOP node, but no luck with Python verb I've attached a simple test file if you want to have a look.
Image Not Found
Technical Discussion » Can't assign some parameter to volumeresize SOP Verb in python
- EricSheng
- 159 posts
- Offline
>>> volumeResizeVerb <hou.SopVerb volumeresize> >>> volumeResizeVerb.parms()["tilecount"] <hou.Vector3 [5.84866e-315, 1.21908e-315, 2.06823e-314]> >>> volumeResizeVerb.setParms({"tilecount":hou.Vector3(2,2,2)}) >>> volumeResizeVerb.parms()["tilecount"] <hou.Vector3 [5.84866e-315, 1.21908e-315, 2.06823e-314]> >>> volumeResizeVerb.parms()["voxelpad"] <hou.Vector3 [6, 6, 6]> >>> volumeResizeVerb.setParms({"voxelpad":hou.Vector3(12,12,12)}) >>> volumeResizeVerb.parms()["voxelpad"] <hou.Vector3 [12, 12, 12]>
This is the result from Houdini Python shell, as you can see, the tilecount parameter is not assigned properly, while the voxelpad is assigned properly. is it a bug?
PDG/TOPs » Python partitioner bug when save to Digital Asset
- EricSheng
- 159 posts
- Offline
Every time press the button “Save to Digital Asset”, the error pops up, and the saved hda is unusable. The problem has existed since long ago to recent daily build.
Technical Discussion » Select several points on a CURVE, how?
- EricSheng
- 159 posts
- Offline
It's an old topic, but I just wonder will this function be added in H18? I mean Solaris is awesome, but Houdini really lacks in some basic functions, like the “ugly” Curve tool. Curve tool can be the base input for many custom hdas, if the input tool sucks, the experience of the whole procedural generation system will be destroyed.
Is this a joke? cause I can find someone asked for this since 2007, and now 2020 is coming. If the new LOPs can offer us a greater curve tool, it will be so much fun than some useless new node like the Poly Draw.
Is this a joke? cause I can find someone asked for this since 2007, and now 2020 is coming. If the new LOPs can offer us a greater curve tool, it will be so much fun than some useless new node like the Poly Draw.
Edited by EricSheng - 2019年8月7日 10:58:56
PDG/TOPs » Cook TOPS from python or HScript, verbose
- EricSheng
- 159 posts
- Offline
So I find a way to cook a TOP node with python code in the Houdini menu file:
# you can check the nodegraphtopui.py file in the Houdini installation folder import nodegraphtopui as topui node = hou.node("YOUR TOP NODE PATH") # do cook topui.dirtyCookNode(node)
Edited by EricSheng - 2019年8月6日 22:59:21
PDG/TOPs » PDG output multiple objects to a FBX file , help !
- EricSheng
- 159 posts
- Offline
I want to know, too. besides, the ROP Geometry Output node is slow to cook, is there any in-process way to output FBX? I meant we can export geometry with python hou.Geometry.saveToFile() which is in-process and very fast to cook but sadly not work with FBX.
Technical Discussion » Is there any way to add a primitive to a geometry through python?
- EricSheng
- 159 posts
- Offline
I find there's no such hou.Geometry().addprim() method, and only hou.Geometry().merge(geometry), which can merge two geometry, but what if I want to merge a primitive to a geometry or construct a geometry with a primitive, is there any way to do that?
Thanks.
Thanks.
PDG/TOPs » Get inputResultData file path in Python
- EricSheng
- 159 posts
- Offline
Say I want to load the upstream output file, I use an python processor node with , but the returned path is begin with “__PDG_DIR__”(sometimes is the full path).
I've tried to use expandString() but with no luck.
Now I just replace the “__PDG_DIR__” with the absolute path, is there a better way to get the input result file? am I doing something wrong here?
Thank you.
upstream_item.inputResultData[0][0]
__PDG_DIR__/geo/xxx.bgeo.sc
Now I just replace the “__PDG_DIR__” with the absolute path, is there a better way to get the input result file? am I doing something wrong here?
Thank you.
Houdini Engine for Unreal » (Solved) HF Scatter issue
- EricSheng
- 159 posts
- Offline
HF_Scatter node is poorly written, you can dive in that node and check which one is reporting this error.
Houdini Indie and Apprentice » Hi, I have a question about UV of Houdini.
- EricSheng
- 159 posts
- Offline
you can use Houdini Engine to export the mesh directly to Unity, which supports up to 4 channels per uv.
PDG/TOPs » PDG Master class posted
- EricSheng
- 159 posts
- Offline
Thanks, Ken,
Great to know the HDA Processor Pole is available in the local scheduler node, also I notice in the daily build 17.5.322, there's a checker named “Use HDA Pole” in the local scheduler node, and every time I turn on the checker and cook the graph, the error info pops up
So shall I turn on the “Use HDA Pole” if I want to use the HDA Processor Pole feature?
Thank you.
Great to know the HDA Processor Pole is available in the local scheduler node, also I notice in the daily build 17.5.322, there's a checker named “Use HDA Pole” in the local scheduler node, and every time I turn on the checker and cook the graph, the error info pops up
TPipe:: open ::CreateFile errored GLE=errno = 2
Thank you.
Edited by EricSheng - 2019年7月21日 02:01:51
PDG/TOPs » few more questions [updated]
- EricSheng
- 159 posts
- Offline
Hi Ken,
Thank you for pointing out the Invoke node, and it looks interesting. But after playing it for several hours, I still can't figure it out, a simple question which has stuck me for a long time, how to create a HieghtField Import/Export TOP node runs as fast as the Geometry Import TOP node and does the job just like the HF_Import/Export SOP node?
Thank you for pointing out the Invoke node, and it looks interesting. But after playing it for several hours, I still can't figure it out, a simple question which has stuck me for a long time, how to create a HieghtField Import/Export TOP node runs as fast as the Geometry Import TOP node and does the job just like the HF_Import/Export SOP node?
Edited by EricSheng - 2019年7月17日 02:40:26
PDG/TOPs » few more questions [updated]
- EricSheng
- 159 posts
- Offline
Hi, Ken:
Can we create our own In Process TOP nodes? I can see the Python Script TOP node is somehow running in process, but what if I want to manipulate the geometry a little bit, I need to use an HDA Processor or the ROP Geometry Output node which is not “in process” and slow to cook.
Thanks!
Can we create our own In Process TOP nodes? I can see the Python Script TOP node is somehow running in process, but what if I want to manipulate the geometry a little bit, I need to use an HDA Processor or the ROP Geometry Output node which is not “in process” and slow to cook.
Thanks!
Edited by EricSheng - 2019年7月16日 02:36:53
PDG/TOPs » Is there any way to create custom lightweight geometry processor TOP node?
- EricSheng
- 159 posts
- Offline
For example, the Geometry Import node is very fast to cook, but what if I want to import height maps as height fields, I have to create an hda to make the import function, then drop down an HDA Processor node in TOP net and cook it. But the HDA Processor node is fairly slow to cook compared to the Built-in Geometry Import node. As far as I understand, the HDA Processor node need to run individual Houdini thread for every workitem in the background, while the Geometry Import node functions like “Evaluating In Process” as how the Python Script node works.
Is there any way to create such lightweight TOP node like the Geometry Import node?
Is there any way to create such lightweight TOP node like the Geometry Import node?
-
- Quick Links