size = parent.parmTuple('size').eval() This should return a vector 3. Great Python series! Would like to see some advanced tutorials on the subject. Even a paid series. Automation to Ue4 and Unity like your Race Track course. How to properly setup VSCode without the annoying linter problems with the hou module perhaps?
I want to watch all your houdini+python video, seems like this is not in that playlist, could you please put all the hou+py vidoes in that playlist kindly?
In python we access the attrs through the geometry...so like this: geo.findAttribValue('attr name'). Theres a couple ways. I have a few videos I need to post this week on that very topic.
These tutorials have been immensely useful. I've seen you use both KWARGS and hou.pwd() as function args in HDA python modules - is there a difference?
Kwargs, comes with a bunch of data about the HDA. If you go here: www.sidefx.com/docs/houdini/hom/locations.html then scroll down to "Parameter callback scripts " you'll see all the other data in the Kwargs dictionary. For instance you can get the parameter that called the function by using kwargs['parm']. Theres some other useful stuff in there as well. :-)
I mostly write out to json these days if I need to save state or need to get data in and out from unreal or houdini....text files are just quick and dirty...json is more object oriented so makes it easier to find data in the json file. Every so often we will use csv files too.
if you don't need the values as string you can write sizex, sizey, sizez = parent.evalParmTuple("size") and if you need them as string this is cleaner than my previous example sizex, sizey, sizez = [str(v) for v in parent.evalParmTuple("size")]
size = parent.parmTuple('size').eval()
This should return a vector 3.
Great Python series! Would like to see some advanced tutorials on the subject. Even a paid series. Automation to Ue4 and Unity like your Race Track course. How to properly setup VSCode without the annoying linter problems with the hou module perhaps?
I really enjoy your super easy-going vibe when you make a video.
It's so cool, perfect timing with my need thanks
Thanks for your videos , they are very useful!
I want to watch all your houdini+python video, seems like this is not in that playlist, could you please put all the hou+py vidoes in that playlist kindly?
Thank you for your tutorial video! This is exactly what I needed!
Big fan of your work. Quick question how to access the attributes? I cannot seem to understand the SideFX documentation.
In python we access the attrs through the geometry...so like this: geo.findAttribValue('attr name'). Theres a couple ways. I have a few videos I need to post this week on that very topic.
@@IndiePixel3D You are the man!
These tutorials have been immensely useful. I've seen you use both KWARGS and hou.pwd() as function args in HDA python modules - is there a difference?
Kwargs, comes with a bunch of data about the HDA. If you go here: www.sidefx.com/docs/houdini/hom/locations.html then scroll down to "Parameter callback scripts " you'll see all the other data in the Kwargs dictionary. For instance you can get the parameter that called the function by using kwargs['parm']. Theres some other useful stuff in there as well. :-)
@@IndiePixel3D Awesome thank you!
Is this a common way to make data persistent across Houdini sessions?
I mostly write out to json these days if I need to save state or need to get data in and out from unreal or houdini....text files are just quick and dirty...json is more object oriented so makes it easier to find data in the json file. Every so often we will use csv files too.
9:55 actually you can do it in one line
sizex,sizey,sizez = map(lambda v: str(v.eval()), n.parmTuple("size"))
That is pretty fancy fo sho!
if you don't need the values as string you can write
sizex, sizey, sizez = parent.evalParmTuple("size")
and if you need them as string this is cleaner than my previous example
sizex, sizey, sizez = [str(v) for v in parent.evalParmTuple("size")]
Hi, I ran into some problems when accessing string parameters.
Unity car phy6 tutz??????
Yes, I know...hang in there...im getting there.