Found 183 posts.
Search results Show results as topic list.
Technical Discussion » Command-Line Python Scripting from Windows
- NFX
- 183 posts
- Offline
I'm having this exact issue as well. I think the conflict is coming from my system's python. Perhaps there is a way to swap to using houdini's included python when the hou module is imported?
Technical Discussion » Trying to use command line but getting a .dll error.
- NFX
- 183 posts
- Offline
Having this issue with H16 on windows. Tried using the dlopen_flags from the documentation and still no luck. Anyone figure this out?
Technical Discussion » PySide2 not found on Windows
- NFX
- 183 posts
- Offline
I'm using Houdini 16 and for some reason whenever I try to import anything from PySide2 (for pypanels or in shelf tools) it says that the module does not exist. However, I am able to import my system's PySide module just fine.
I tried hunting down where the PySide2 modules are stored in Houdini's installation files and can't find them for the life of me. Any idea where these reside?
I tried hunting down where the PySide2 modules are stored in Houdini's installation files and can't find them for the life of me. Any idea where these reside?
Technical Discussion » Subdivision Flickering in Render
- NFX
- 183 posts
- Offline
So I am trying to render a geometry with “render geometry as subdivision” turned on and am noticing weird flicking in the textures. Not noise really, but small groups of pixels changing how the texture looks in random locations. I can also see what looks like fine black concentric lines on the model, kind of like a weird displacement issue. If I turn off subdivision then the effect goes away.
I'm only using a diffuse and roughness map with the principled shader. The objects is pretty matte with low specularity, high roughness, and no fancy features like SSS turned on. My super-sampling is cranked up to 8 in mantra and for troubleshooting I've turned off secondary bounces.
Looking on the forum, it seems that Houdini's had trouble with subdivision in the past. Is this still an issue?
I'm only using a diffuse and roughness map with the principled shader. The objects is pretty matte with low specularity, high roughness, and no fancy features like SSS turned on. My super-sampling is cranked up to 8 in mantra and for troubleshooting I've turned off secondary bounces.
Looking on the forum, it seems that Houdini's had trouble with subdivision in the past. Is this still an issue?
Technical Discussion » Stylesheets and HDA's
- NFX
- 183 posts
- Offline
I thought the documentation said that applying stylesheets as a primitive attribute would lead to slow renders. Or does that only apply to unpacked geo since the attribute would be replicated for every single prim?
Also, while I know of the material sop's “save as stylesheet” option, this doesn't seem to work for packed disk primitives. Am I wrong about this? Are there any good tools for editing geometry level stylesheets? Like a way to set target depth?
Another issue I ran into with the material sop method is that it seems to force absolute shop paths, even if you set them to be relative. Is this a bug?
Also as a side note, setting the stylesheet on the “shop_materialstylesheet” only works if you keep the geo inside of that node. Any external referencing and the sheet will no longer be able to effect it.
So far it seems for HDA's, storing it on the geometry is the most robust way (fewer ways for a user to misuse it and complain that it's broken), however the provided methods for creating,editing, or merging geometry sheets are both sparse and buggy.
Also, while I know of the material sop's “save as stylesheet” option, this doesn't seem to work for packed disk primitives. Am I wrong about this? Are there any good tools for editing geometry level stylesheets? Like a way to set target depth?
Another issue I ran into with the material sop method is that it seems to force absolute shop paths, even if you set them to be relative. Is this a bug?
Also as a side note, setting the stylesheet on the “shop_materialstylesheet” only works if you keep the geo inside of that node. Any external referencing and the sheet will no longer be able to effect it.
So far it seems for HDA's, storing it on the geometry is the most robust way (fewer ways for a user to misuse it and complain that it's broken), however the provided methods for creating,editing, or merging geometry sheets are both sparse and buggy.
Edited by NFX - Feb. 27, 2018 13:19:32
Technical Discussion » Stylesheets and HDA's
- NFX
- 183 posts
- Offline
I am also interested in hearing people's HDA workflows with stylesheets. It seems to me that as they are currently designed, while they are super useful for setting materials on packed disk prims and such, they just don't fit into the HDA paradigm.
Hopefully someone can prove me wrong though.
Hopefully someone can prove me wrong though.
Technical Discussion » Hou module not picking up HOUDINI_PATH
- NFX
- 183 posts
- Offline
Using hou.putenv() to set the ‘HOUDINI_PATH’ before loading the file seems to do the trick. Thanks for the suggestion Zephmann!
The odd thing is that hou.houdiniPath() still returns the wrong values, even though everything else works. Either way files are loading now without complaining and that is what I needed.
Also yes this was running from python with me handling initialization of the env vars and importing the hou module.
The odd thing is that hou.houdiniPath() still returns the wrong values, even though everything else works. Either way files are loading now without complaining and that is what I needed.
Also yes this was running from python with me handling initialization of the env vars and importing the hou module.
Edited by NFX - Feb. 9, 2018 20:05:13
Technical Discussion » Promoting multiparm breaks Python menu scripts
- NFX
- 183 posts
- Offline
So after some more research on the topic of why this is happening, it seems jsmack's comments are incorrect according to the documentation.
hou.pwd() documentation [www.sidefx.com]
It seems that the parameter containing the call to .pwd is returned rather than the parameter of the node that references the original parameter in order to maintain relative referencing. Seems this might be an issue with multiparms after all.
The only solution I have found is to duplicate the code on the referencing parameter to point to the HOM of the node it is referencing. Ugly, but functional-ish.
hou.pwd() documentation [www.sidefx.com]
It seems that the parameter containing the call to .pwd is returned rather than the parameter of the node that references the original parameter in order to maintain relative referencing. Seems this might be an issue with multiparms after all.
The only solution I have found is to duplicate the code on the referencing parameter to point to the HOM of the node it is referencing. Ugly, but functional-ish.
Edited by NFX - Feb. 6, 2018 14:26:43
Technical Discussion » Hou module not picking up HOUDINI_PATH
- NFX
- 183 posts
- Offline
I'm using the hou module in a custom python script. The process I am using is that I set the needed environment variables inside the python script via os.environ and add Houdini's python2.7libs folder to the sys.path before finally importing the hou module as per the documentation.
However when I load a hip file via hou.hipFile.load I get errors saying that houdini can't find some of the custom HDA's it contains. I keep these HDA's in a special folder for asset management purposes and made sure that it was included in the ‘HOUDINI_PATH’ environment variable that I set before importing hou. However, running hou.houdiniPath reveals that houdini sees the variable as set to what appears to be default values. If I then os.getenv the variable by name it does show it as being set and containing the proper folder that contains the hda/ and otl/ folders where I keep the missing assets. Confusing…
Is this a bug? Am I doing something wrong?
However when I load a hip file via hou.hipFile.load I get errors saying that houdini can't find some of the custom HDA's it contains. I keep these HDA's in a special folder for asset management purposes and made sure that it was included in the ‘HOUDINI_PATH’ environment variable that I set before importing hou. However, running hou.houdiniPath reveals that houdini sees the variable as set to what appears to be default values. If I then os.getenv the variable by name it does show it as being set and containing the proper folder that contains the hda/ and otl/ folders where I keep the missing assets. Confusing…
Is this a bug? Am I doing something wrong?
Technical Discussion » Promoting multiparm breaks Python menu scripts
- NFX
- 183 posts
- Offline
Okay, well for now I'll just have to rewrite the paths to point to the correct node after promoting the parameters I guess.
Technical Discussion » mantra: [VRAY_ProcGT] procedural warning: Optimization not run on geometry (this may be ok)
- NFX
- 183 posts
- Offline
I am interested in hearing what this means as well. I am rendering files that consist of packed prims and noticed that a large portion of render time happens just after this warning is raised. Coincidence?
Technical Discussion » Promoting multiparm breaks Python menu scripts
- NFX
- 183 posts
- Offline
Is there a way to make sure that the code points to the asset with the python module whether or not the parameter has been promoted?
Also your reasoning doesn't seem to explain why only parameters in a multiparm would have this issue.
Also your reasoning doesn't seem to explain why only parameters in a multiparm would have this issue.
Technical Discussion » Promoting multiparm breaks Python menu scripts
- NFX
- 183 posts
- Offline
So I have a multiparm on an asset that contains menus that are generated via python with a script like this…
However if I put the asset inside a subnet and then try to promote the multiparm by using the ‘from nodes’ tab, I get an error saying that no method called ‘generateContextMenu’ is found in the python module. Now if I try the same thing with an identical parameter on the asset that is not inside a multiparm everything works like a charm.
Is there a way around this issue? Am I doing something wrong.
hou.pwd().hm().generateContextMenu(kwargs['parm'], hou.pwd())
However if I put the asset inside a subnet and then try to promote the multiparm by using the ‘from nodes’ tab, I get an error saying that no method called ‘generateContextMenu’ is found in the python module. Now if I try the same thing with an identical parameter on the asset that is not inside a multiparm everything works like a charm.
Is there a way around this issue? Am I doing something wrong.
Technical Discussion » Copy/Paste Hotkeys Not Working in Python Panel
- NFX
- 183 posts
- Offline
Yep. I'm on a Mac.
So this is a bug then? Oh well. I guess I still have the option of copy pasting from the context menu.
So this is a bug then? Oh well. I guess I still have the option of copy pasting from the context menu.
Technical Discussion » Copy/Paste Hotkeys Not Working in Python Panel
- NFX
- 183 posts
- Offline
So I am still trying to figure out this issue. I've tried forcing the QLineEdit to be in focus, but Houdini is still intercepting my keyboard's clipboard commands.
Below is the simple program I am running. Basically it is just a text field that I expect to be able to copy and paste from. Any idea what I am doing wrong?
from PySide2 import QtCore, QtWidgets
Below is the simple program I am running. Basically it is just a text field that I expect to be able to copy and paste from. Any idea what I am doing wrong?
from PySide2 import QtCore, QtWidgets
from PySide2 import QtCore, QtWidgets class TextField(QtWidgets.QLineEdit): def __init__(self, parent): super(TextField, self).__init__(parent) self.setPlaceholderText('Hello World') self.setFocusPolicy(QtCore.Qt.StrongFocus) class Example(QtWidgets.QWidget): def __init__(self): super(Example, self).__init__() tf = TextField(self) tf.move(30, 65) tf.setFocus()
Edited by NFX - Jan. 22, 2018 15:08:50
Technical Discussion » Event Trigger for python callback on drag and drop
- NFX
- 183 posts
- Offline
The ability to drag in arbitrary text or even binary data and handle it would be amazing. Just to verify, would this work with python panels? So far I haven't been able to figure out a good way drag and drop data from a custom panel into a parameter field. Seems like an important feature to have to support common studio tasks like wanting to drag an asset from a python asset manager into the viewport or network view. Perhaps there is already a way to do this that I have missed?
Technical Discussion » "Rolling Back" HDA definition versions with python
- NFX
- 183 posts
- Offline
Thanks for the useful answer zephmann. Yeah this mirror's what I have been finding so far. I was hoping that it would be possible to change the nodeType and somehow set that as the default definition to use. Guess I will have to possibly rethink how I was going to use this feature.
Technical Discussion » Drag from pypanel and drop value onto parameter
- NFX
- 183 posts
- Offline
So I have a custom pyside panel I have been making and am trying to figure out how to drag items from a QTableWidget and drop them into a parameter on a node, with the result being that the node parameter gets filled in with a value relating to the dropped element.
I have been searching the documentation for ideas on how to do this and found the drag and drop section of the hou.ui class. However I'm not sure how to relate this to my panel or how to get the parameter that I mouse over and drop into.
Any tips?
I have been searching the documentation for ideas on how to do this and found the drag and drop section of the hou.ui class. However I'm not sure how to relate this to my panel or how to get the parameter that I mouse over and drop into.
Any tips?
Technical Discussion » Set up HDA so that a single inner subnet is unlocked for editing
- NFX
- 183 posts
- Offline
Does anyone know if there is a way to set the dive target with hython? I'm checking the documentation and do see anything.
Technical Discussion » Set up HDA so that a single inner subnet is unlocked for editing
- NFX
- 183 posts
- Offline
-
- Quick Links