SteveNi
-
Content count
65 -
Donations
0.00 CAD -
Joined
-
Last visited
Recent Profile Visitors
1,192 profile views
-
Location of nodes presets in File System
SteveNi replied to SteveNi's topic in General Houdini Questions
I cannot rewrite them because I dont fully remember them and I cannot recover them because they are not in the H15.0 vexpression file. To be honest I don't really immediately need them, but I'd like to port everything I had on the H15.0 installation on my current H15.5, I've done it with otls and I wanted to do it with presets too. -
Location of nodes presets in File System
SteveNi replied to SteveNi's topic in General Houdini Questions
Yes I can surely create a file where I store all of my presets and personal settings manually, but the point here is that I used to use H15.0, and I can no longer acces it because they don't give Apprentice licenses anymore for that version (I asked via email to SideFx), and I had like 3 vex presets, 2 of which I no longer fully remember, and they aren't stored in the Vexpression.txt file of my H15.0 installation, so... are they lost? -
Location of nodes presets in File System
SteveNi replied to SteveNi's topic in General Houdini Questions
Thanks! My compute_path_length should be in the point wrangle section of the file but I cant find it. I tried to create several others presets and it seems like Houdini doesn't even touch that file, the file last modification date is still the same indeed. VEXpressions.txt -
I need to port the nodes presets of my H15.0 installation to the H15.5 one, where are the presets file located in the file systems? I cant find them even without a search using the present name... Sorry for the n00b question. Thanks
-
Yea you are right, the problem here is that I need to load the attribute for a specific primitive, thats why I used the primitive() function. Guess I'll have to use another method.
-
Oooooh thats true, thanks! EDIT: Is there anyway to load the current status of the attributes, apart from keep track of the changes in variables?? I tried to use geoself, just to be sure, but it doesn't work either.
-
So I was writing some vex code for a scene Im working on, and while I was debugging the code to correct an issue I placed various printf() functions in the code to check the state of the attributes right after I made some changes to them, and I noticed that if I load an attribute in a variable and print it, modify the attribute, reload it in the same variable and then print the variable out again, it wont show the newer value if the loading&printing process is done in the same wrangle node of where the attribute was modified. Here's an example scene wich exactly recreates my scenario. Am I missing something stupid here? Test_attribute.hipnc
-
I can finally reply after the maintenance on this site. So yea, if you import the "group type" menu it will work, but not without it. Ill report this to SideFx by also refer to this topic Thanks
-
Please watch this video where I create the OTL from scratch, you can also read the error message. https://vimeo.com/213274634 Password: 101
-
I added group to that script but gives the same error I dont think this matters but Im still working in H15.5...
-
Ops sorry I forgot to upload the .hda file, here it is. casdaf.hdanc
-
Ehy no problem I just saw in the video you published on your vimeo that you added the bend controls
-
1)Yes absolutely add resolutions parameters. 2)It looks like you have already added the right parameters for noise in the OTL window. 3)Yes maybe add some fit range nodes, so you can modulate the noise from a simple range to read like (-1,1), but always leave these locks off (see screen shot), this way, if wanted, it will be possible to go over the range predefined. Another thing you could add is a deformer to bend the overall mushroom: As you can see from the image not every mushroom is completely straight.
-
Yea sure! HDA_test.hipnc
-
So I'm making a HDA wich has a color sop inside of it, of wich Im using the group field, thats why I need to acces this field at the upper level (the HDA interface). So to to do this, when building the HDA interface I dragged that field directly from the color sop to the HDA interface, (pic1/3)but when I try to use it from the HDA it throws this error (pic2), wich I guess is referencing this code inside the group's script (pic4). I've never messed around with this kind of stuff, how can I solve this?
