Hello,
I was hoping someone might be able to shed light on why I get an error message in my trying to use hou.HDAModule.
In case the file needs to be looked at I've included it also.
I've tried to make the file as small as possible that still replicates the problem I am having with a larger version.
Any help is appreicated.
Thank you
Found 2040 posts.
Search results Show results as topic list.
Houdini Indie and Apprentice » Using hou.HDAModule
- BabaJ
- 2042 posts
- Offline
Houdini Indie and Apprentice » Relative or Absolute paths still create warning message
- BabaJ
- 2042 posts
- Offline
Thank you very much arctor,
In addition to helping in this matter, you've indirectly helped show me what areas to look into further that will help me structure my code in a way I was hoping to be able to do.
e.g. your code example and the link to hou.HDAModule
Thanks again.
In addition to helping in this matter, you've indirectly helped show me what areas to look into further that will help me structure my code in a way I was hoping to be able to do.
e.g. your code example and the link to hou.HDAModule
Thanks again.
Houdini Indie and Apprentice » Relative or Absolute paths still create warning message
- BabaJ
- 2042 posts
- Offline
Hi arctor,
So here's the attached file.
It actually is a simpler version of what I am doing elsewhere.
Maybe it could be more simple, I don't know.
I was trying to keep all the ‘elements’ of what I planned on doing with my more complex version.
Thanks again for taking the time to look at this.
So here's the attached file.
It actually is a simpler version of what I am doing elsewhere.
Maybe it could be more simple, I don't know.
I was trying to keep all the ‘elements’ of what I planned on doing with my more complex version.
Thanks again for taking the time to look at this.
Houdini Indie and Apprentice » Relative or Absolute paths still create warning message
- BabaJ
- 2042 posts
- Offline
Hi arctor,
Thanks for the reply, hopefuly your still on and might be able to answer again.
Even if I do what you said I still get an error message, although it just seems like a shorter version of the orginal.
The first screenshot is of this “new” error message.
I only have 2 nodes in my chop and in both I eliminated anything in the Export Prefix parameter.
Just to be sure I looked in all my other nodes as well to make sure everything is set as relative paths and I've included screenshots of everything that has any parameter reference to another parameter.
I was thinking, in one of my parameter references I am using a function that is in my Python Source Editor.
And even though the function is using relative paths for it's arguments I thought I may have read somewhere saying we can't use code that is stored in Python Source Editor when we are going to make a digital asset?
Is this true? It would make sense as that code does lie outside the subnet and maybe that's why I get the error message?
Maybe I need to take that Python Source Code and put it in Python Nodes within the subnet?
Thanks to anyone who can shed light on this.
Thanks for the reply, hopefuly your still on and might be able to answer again.
Even if I do what you said I still get an error message, although it just seems like a shorter version of the orginal.
The first screenshot is of this “new” error message.
I only have 2 nodes in my chop and in both I eliminated anything in the Export Prefix parameter.
Just to be sure I looked in all my other nodes as well to make sure everything is set as relative paths and I've included screenshots of everything that has any parameter reference to another parameter.
I was thinking, in one of my parameter references I am using a function that is in my Python Source Editor.
And even though the function is using relative paths for it's arguments I thought I may have read somewhere saying we can't use code that is stored in Python Source Editor when we are going to make a digital asset?
Is this true? It would make sense as that code does lie outside the subnet and maybe that's why I get the error message?
Maybe I need to take that Python Source Code and put it in Python Nodes within the subnet?
Thanks to anyone who can shed light on this.
Houdini Indie and Apprentice » Relative or Absolute paths still create warning message
- BabaJ
- 2042 posts
- Offline
Hello,
I was hope someone might be able to help me understand the warning/error messages I am getting when creating a subnet to make a digital asset.
I've watched the 6 video tutorials but none of the content seems to shed a light on the “problem” I am looking at.
I have a Chop network that has a wave and export node.
I also have 2 pathcv nodes that are driven by the Chop.
In screenshot “A” below I get that error message shown when I go to create the digital asset ( right clicking the subnet > create digital asset ).
So it's telling me that I am using nodes outside the subnet or that I am using absolute paths.
What I am using is as in screenshot “B” ( the export node of the Chop network )
These are relative paths.
So I tried shortening them going from using: “../../pathcv1 ../../pathcv2”
to using: “../pathcv1 ../pathcv2”
But this doesn't work because now the pathcvs' no longer work ( they don't become moved, driven by the code )
The reason I tried shortening it like this is because the absolute path is:
“/obj/SUBNET/pathcv1 /obj/SUBNET/pathcv2”
So going by what the warning message is saying I am assuming the “/obj” is the part that is outside the subnet and if I remove that then it should not be considered outside the network.
But again, the code fails to work if I “shorten” it like that.
So I've tried variations of these two paths, but these 2 are the only ones that allow my code to work but both give the same warning message:
“../../pathcv1 ../../pathcv2”
“/obj/SUBNET/pathcv1 /obj/SUBNET/pathcv2”
I don't know what to do to eliminate the warning message and it seems that I should because I get other error messages for when after I create the digital asset and want to make changes ( modify ) the asset and the original warning message comes up again, along side other warning/error messages.
I'm just trying to clear up what I may be doing wrong or not understanding.
any help is appreciated.
Thank you
I was hope someone might be able to help me understand the warning/error messages I am getting when creating a subnet to make a digital asset.
I've watched the 6 video tutorials but none of the content seems to shed a light on the “problem” I am looking at.
I have a Chop network that has a wave and export node.
I also have 2 pathcv nodes that are driven by the Chop.
In screenshot “A” below I get that error message shown when I go to create the digital asset ( right clicking the subnet > create digital asset ).
So it's telling me that I am using nodes outside the subnet or that I am using absolute paths.
What I am using is as in screenshot “B” ( the export node of the Chop network )
These are relative paths.
So I tried shortening them going from using: “../../pathcv1 ../../pathcv2”
to using: “../pathcv1 ../pathcv2”
But this doesn't work because now the pathcvs' no longer work ( they don't become moved, driven by the code )
The reason I tried shortening it like this is because the absolute path is:
“/obj/SUBNET/pathcv1 /obj/SUBNET/pathcv2”
So going by what the warning message is saying I am assuming the “/obj” is the part that is outside the subnet and if I remove that then it should not be considered outside the network.
But again, the code fails to work if I “shorten” it like that.
So I've tried variations of these two paths, but these 2 are the only ones that allow my code to work but both give the same warning message:
“../../pathcv1 ../../pathcv2”
“/obj/SUBNET/pathcv1 /obj/SUBNET/pathcv2”
I don't know what to do to eliminate the warning message and it seems that I should because I get other error messages for when after I create the digital asset and want to make changes ( modify ) the asset and the original warning message comes up again, along side other warning/error messages.
I'm just trying to clear up what I may be doing wrong or not understanding.
any help is appreciated.
Thank you
Houdini Indie and Apprentice » Nodes using Python Source Editor in subnetwork
- BabaJ
- 2042 posts
- Offline
Hi graham:
No I wasn't using relative paths, only “channel reference” option as opposed to “Relative channel reference”
I'm including a few screenshots…one of the error messages and the others that refer to the error message. There are more references in the “chain” of channel referencing but they all refer in the same manner with “channel reference” and the functions are all prefixed with hou.session.
Thanks
No I wasn't using relative paths, only “channel reference” option as opposed to “Relative channel reference”
I'm including a few screenshots…one of the error messages and the others that refer to the error message. There are more references in the “chain” of channel referencing but they all refer in the same manner with “channel reference” and the functions are all prefixed with hou.session.
Thanks
Houdini Indie and Apprentice » Nodes using Python Source Editor in subnetwork
- BabaJ
- 2042 posts
- Offline
Hi,
I have a couple nodes that work with a CHOP network and they in turn use functions I have defined in the Python Source Editor.
All works fine, but once I put those nodes and CHOP network together in a subnetwork they no longer are able to work.
Is there a way to change this, or is it a ‘normal’ limitation?
Thanks for any feedback
I have a couple nodes that work with a CHOP network and they in turn use functions I have defined in the Python Source Editor.
All works fine, but once I put those nodes and CHOP network together in a subnetwork they no longer are able to work.
Is there a way to change this, or is it a ‘normal’ limitation?
Thanks for any feedback
Houdini Indie and Apprentice » Lingering Warning Messege
- BabaJ
- 2042 posts
- Offline
Hello,
I was hoping someone might help me eliminate a lingering warning message.
I can't remember at what point this message got created but I did some copy and pasting of paramters that included some typo mistakes I made for the new parameters. On top of that I had copied the whole CHOP network to be used for other objects but forgot to temporarily delete the export nodes references - so this also created a conflict in the copy process.
All in all I sorted all those mistakes out and the code works just fine as intended. But everytime I open the file this warning message pops up and also a very similar warning ( referencing the same parameter ) comes up everytime I do a copy of my template CHOP.
Like I said my code works fine but this warning message is annoying and I am concerned at some point it might bite me in the butt if I don't take care of it now. As I am going to make many copies of this CHOP network I don't want to be in a situation where I have to go through the code and make many correcrtions.
I've included 3 screenshots because I wanted to show all the places that the parameter being stated in the warning message is being used and the editor for expression can only show one parameter at a time.
Any help is appreciated.
Thank you
I was hoping someone might help me eliminate a lingering warning message.
I can't remember at what point this message got created but I did some copy and pasting of paramters that included some typo mistakes I made for the new parameters. On top of that I had copied the whole CHOP network to be used for other objects but forgot to temporarily delete the export nodes references - so this also created a conflict in the copy process.
All in all I sorted all those mistakes out and the code works just fine as intended. But everytime I open the file this warning message pops up and also a very similar warning ( referencing the same parameter ) comes up everytime I do a copy of my template CHOP.
Like I said my code works fine but this warning message is annoying and I am concerned at some point it might bite me in the butt if I don't take care of it now. As I am going to make many copies of this CHOP network I don't want to be in a situation where I have to go through the code and make many correcrtions.
I've included 3 screenshots because I wanted to show all the places that the parameter being stated in the warning message is being used and the editor for expression can only show one parameter at a time.
Any help is appreciated.
Thank you
Houdini Indie and Apprentice » Changing even with Window Pinned
- BabaJ
- 2042 posts
- Offline
Houdini Indie and Apprentice » Changing even with Window Pinned
- BabaJ
- 2042 posts
- Offline
Hi,
I'm not sure if this is something I'm not doing right with a setting, if it's a bug, or maybe not just a feature and might be a feature request.
So far when I work with pinned windows I can do stuff like go into nodes and look more closely while another window that is pinned stays unchanged.
But in this case when both windows are looking at the same parameter window, changing the folder tab in one also changes the folder tab in the other pinned window as well.
In my case of the screen shots I have two folders “Tx” and “Ty” and as I am working through one folder like say “Tx” I was hoping to be able to keep “Ty” open as well to compare as I went along.
Of course the easy work around for me is to have the edit parameter interface open and just look through the two folders…
but my question is, out of curiosity…
Is the pinned window feature working as intended and to the extent is was designed too?
My screenshot includes 3 windows from the left - a floating window, regular window set to parameters, and third a network window with keyboard key “p” bringing up a parameter sub-window. ( changing folder tab in any one changes folder tab in the other 2 )
Thanks for any comments or reply
I'm not sure if this is something I'm not doing right with a setting, if it's a bug, or maybe not just a feature and might be a feature request.
So far when I work with pinned windows I can do stuff like go into nodes and look more closely while another window that is pinned stays unchanged.
But in this case when both windows are looking at the same parameter window, changing the folder tab in one also changes the folder tab in the other pinned window as well.
In my case of the screen shots I have two folders “Tx” and “Ty” and as I am working through one folder like say “Tx” I was hoping to be able to keep “Ty” open as well to compare as I went along.
Of course the easy work around for me is to have the edit parameter interface open and just look through the two folders…
but my question is, out of curiosity…
Is the pinned window feature working as intended and to the extent is was designed too?
My screenshot includes 3 windows from the left - a floating window, regular window set to parameters, and third a network window with keyboard key “p” bringing up a parameter sub-window. ( changing folder tab in any one changes folder tab in the other 2 )
Thanks for any comments or reply
Houdini Indie and Apprentice » Chop Export is dropping output of referenced nodes
- BabaJ
- 2042 posts
- Offline
Ok awng,
Thank you again…I'm going to take your points and play around with them for a while.
Think that will keep me busy for a while.
Thank you again…I'm going to take your points and play around with them for a while.
Think that will keep me busy for a while.
Houdini Indie and Apprentice » Chop Export is dropping output of referenced nodes
- BabaJ
- 2042 posts
- Offline
I'm starting to think there is something going on with my computer.
Later on in the day I worked on another new file and for the wave node I used a sine function I had defined in the python source editor in that wave nodes expression option.
It doesn't give the same wave I was aiming for with my other file like in the screen shot in my first post here, but….
The thing is that for the export node in this new file I named 4 obj pathcv points the same way and they all responded to the function like they should. And yes btw I checked the nodes names and they are all good ( in the first file )
So I suspect if I created a new file and played with the same nodes to get the type of sine wave I aiming for it might just work.
It's not the first time I do/create something in one file and some “glitch” comes up…
..only to do the same/similar set up in another new file and find it works.
And I'm not talking “complicated” things…just today I had a file where it wouldn't let me press the “accept” button on the python source editor and close the window. I could only use the “x” dialogue button to close it.
So it's these little things that are making me think it's my computer.
But if you happen to read this reply awong, do you think I went about it the “right” way to get the sine wave I was aiming for…meaning the use of clamp and shift then putting in merge then resample?
Another more efficient? way I might want to try?
Thanks
Later on in the day I worked on another new file and for the wave node I used a sine function I had defined in the python source editor in that wave nodes expression option.
It doesn't give the same wave I was aiming for with my other file like in the screen shot in my first post here, but….
The thing is that for the export node in this new file I named 4 obj pathcv points the same way and they all responded to the function like they should. And yes btw I checked the nodes names and they are all good ( in the first file )
So I suspect if I created a new file and played with the same nodes to get the type of sine wave I aiming for it might just work.
It's not the first time I do/create something in one file and some “glitch” comes up…
..only to do the same/similar set up in another new file and find it works.
And I'm not talking “complicated” things…just today I had a file where it wouldn't let me press the “accept” button on the python source editor and close the window. I could only use the “x” dialogue button to close it.
So it's these little things that are making me think it's my computer.
But if you happen to read this reply awong, do you think I went about it the “right” way to get the sine wave I was aiming for…meaning the use of clamp and shift then putting in merge then resample?
Another more efficient? way I might want to try?
Thanks
Houdini Indie and Apprentice » There is a Box inside my Sphere
- BabaJ
- 2042 posts
- Offline
There is a bounding box option on the group node and it also has a sub-option for points only.
I tried playing around with it…along with add and resample nodes ( to try and work with points only ) and didn't have any luck.
I suspect it would be a combination of those nodes along with some of the nodes in the modily shelf like “copy to points” , “combine”, etc.
sorry…couldn't help.
I tried playing around with it…along with add and resample nodes ( to try and work with points only ) and didn't have any luck.
I suspect it would be a combination of those nodes along with some of the nodes in the modily shelf like “copy to points” , “combine”, etc.
sorry…couldn't help.
Houdini Indie and Apprentice » There is a Box inside my Sphere
- BabaJ
- 2042 posts
- Offline
Houdini Indie and Apprentice » There is a Box inside my Sphere
- BabaJ
- 2042 posts
- Offline
Instead of deleting it…maybe do something like create a group node between merge and sphere and one between merge and cylinder….then whatever you do after merge only use( select ) the names of the two groups…whatever may be “loose geo” won't be included…effectively deleting it.
If you have a complex process in which you not sure where the “loose geo” is coming from, maybe retrace your steps back to the beginning and for each node have a look at the spreedsheet to see what it getting generated…then maybe you can figure out a way to sort your process with the use of other nodes like maybe the group node for example.
If you have a complex process in which you not sure where the “loose geo” is coming from, maybe retrace your steps back to the beginning and for each node have a look at the spreedsheet to see what it getting generated…then maybe you can figure out a way to sort your process with the use of other nodes like maybe the group node for example.
Houdini Indie and Apprentice » There is a Box inside my Sphere
- BabaJ
- 2042 posts
- Offline
You can click on the boxes bypass flag ( it's the furthest flag on the left of the box object - bypass flag turns yellow when it is on )
Houdini Indie and Apprentice » Chop Export is dropping output of referenced nodes
- BabaJ
- 2042 posts
- Offline
Hello,
In the screenshot I've included I have 4 pathcv points that I am wanting to translate along their ty axis in unison.
I've managed to work and set up with some of the nodes available in the CHOP network to get a continuous up and down movement of my points related to the first half only of a sine wave. ( no delay between the “top” half of the sine wave accomplished with the shift of half a cycle then merged and resampled)
But in the export I have the 4 nodes listed but only 2 of the nodes respond to the waveform ( /obj/pathcv8 and obj/pathcv11 ).
The other two nodes ( /obj/pathcv1 and /obj/pathcv10 ) remain still while keyframes are run even though their parameter boxes are shaded orange to indicate they have been over ridden by the Chop network.
The odd thing is that if I wire straight from limit ( clamped ) or shift node to the export node, all 4 pathcv object ty points move in unison. Of course I want to be able to include the merge and resample so that there is no delay in time of movement.
Any suggestions of what I may be doing wrong?
Thank you
In the screenshot I've included I have 4 pathcv points that I am wanting to translate along their ty axis in unison.
I've managed to work and set up with some of the nodes available in the CHOP network to get a continuous up and down movement of my points related to the first half only of a sine wave. ( no delay between the “top” half of the sine wave accomplished with the shift of half a cycle then merged and resampled)
But in the export I have the 4 nodes listed but only 2 of the nodes respond to the waveform ( /obj/pathcv8 and obj/pathcv11 ).
The other two nodes ( /obj/pathcv1 and /obj/pathcv10 ) remain still while keyframes are run even though their parameter boxes are shaded orange to indicate they have been over ridden by the Chop network.
The odd thing is that if I wire straight from limit ( clamped ) or shift node to the export node, all 4 pathcv object ty points move in unison. Of course I want to be able to include the merge and resample so that there is no delay in time of movement.
Any suggestions of what I may be doing wrong?
Thank you
Houdini Indie and Apprentice » Accessing Python Node from Another Python Node
- BabaJ
- 2042 posts
- Offline
Ok, thanks graham:
Good to know, now I can let that avenue go.
Actually, originaly I was using Python Source Editor but it was starting to get to the point where I had too much stored in one place.
So I was looking for a way to break things up into parts.
I was working with storing things in script *.py files and doing things like
“ from ‘scriptfile’ import * ”
for the Python Source Editor but it seems I can only import down into one level.
The “variables” stored in the script file were able to be accessed directly from the python node with the same,
“from ‘scriptfile’ import * ” notation,
but a function within the Python Source Editor that uses one of those “variables” as an argument when used in the python node doesn't seem to be able to access that variable.
It's like it can only be passed/referenced down one level. No “nesting” type behaviour seems to be allowed.
I think I am going to look into the HDK and play with some C++.
Thanks for your feedback.
Good to know, now I can let that avenue go.
Actually, originaly I was using Python Source Editor but it was starting to get to the point where I had too much stored in one place.
So I was looking for a way to break things up into parts.
I was working with storing things in script *.py files and doing things like
“ from ‘scriptfile’ import * ”
for the Python Source Editor but it seems I can only import down into one level.
The “variables” stored in the script file were able to be accessed directly from the python node with the same,
“from ‘scriptfile’ import * ” notation,
but a function within the Python Source Editor that uses one of those “variables” as an argument when used in the python node doesn't seem to be able to access that variable.
It's like it can only be passed/referenced down one level. No “nesting” type behaviour seems to be allowed.
I think I am going to look into the HDK and play with some C++.
Thanks for your feedback.
Houdini Indie and Apprentice » Accessing Python Node from Another Python Node
- BabaJ
- 2042 posts
- Offline
Hello,
I'm trying to figure out how I can access code written in one python node like definitions and “variables” “declared”/“set” and access it from another python node.
This is more of a continuing exercise for me to see how much I can and cannot do with Python in Houdini.
The screenshot I'm attaching should be able to illustrate the principal I am trying to do.
I have tried many versions of this like using “import” and different wiring of the nodes as well but still am unable to make any reference and use code that is in one python node in another.
Any help is appreciated, thank you.
I'm trying to figure out how I can access code written in one python node like definitions and “variables” “declared”/“set” and access it from another python node.
This is more of a continuing exercise for me to see how much I can and cannot do with Python in Houdini.
The screenshot I'm attaching should be able to illustrate the principal I am trying to do.
I have tried many versions of this like using “import” and different wiring of the nodes as well but still am unable to make any reference and use code that is in one python node in another.
Any help is appreciated, thank you.
Houdini Indie and Apprentice » How to Determine what sub-frames Python code will see
- BabaJ
- 2042 posts
- Offline
Hi awong,
Thanks again,
Yeah because not only do I want the oscillating motion but the ability to change direction anywhere along its motion and expand or contract its range of motion with slider controls.
Although I haven't yet studied how to use chops, I was aware of them and did view to some degreee a couple ‘tutorial’ videos on them, although I didn't see a way to accomplish what I wanted with them.
That's not to say I can't; I did see the potential in using them.
I'm glad you mentioned Chops to me.
I think I will revisit them and study them a bit more closer.
Thank you very much, you've helped me along here towards learning how to get more out of Houdini - much appreciated.
Thanks again,
Yeah because not only do I want the oscillating motion but the ability to change direction anywhere along its motion and expand or contract its range of motion with slider controls.
Although I haven't yet studied how to use chops, I was aware of them and did view to some degreee a couple ‘tutorial’ videos on them, although I didn't see a way to accomplish what I wanted with them.
That's not to say I can't; I did see the potential in using them.
I'm glad you mentioned Chops to me.
I think I will revisit them and study them a bit more closer.
Thank you very much, you've helped me along here towards learning how to get more out of Houdini - much appreciated.
-
- Quick Links