Jump to content


  • Posts

  • Joined

  • Last visited

About cristobalvila

  • Birthday 07/07/1966

Contact Methods

  • Website URL

Personal Information

  • Name
  • Location
    Zaragoza, Spain

cristobalvila's Achievements


Newbie (1/14)



  1. Hi Dany, I'm doing my first steps with Apprentice. Going to Orbolt and trying to install your shader, it gives me the option to “Launch in Houdini”, but this doesn't work in my machine: a floating window with a big Orbolt logo appears and nothing occurs… Other assets offers the possibility to manually download a OTL, but this option is not present here… It's possible to access to the OTL and install manually? Maybe sending an email to you? (I don't want to spam your email, for that reason prefer to ask here before). A big thanks in advance!
  2. Yeah! Thanks Goldleaf! I will save alias to all those directories, since they are really useful! Big thanks
  3. Thank you so much, Rayman! Just to be sure that I didn't broke something… I placed both files here: /Library/Frameworks/Houdini.framework/13.0.582/Resources/houdini/dso/sop_pathdeform.dylib /Library/Frameworks/Houdini.framework/13.0.582/Resources/houdini/config/Icons/SOP_path_deform.svg It's that right? THANKS!
  4. Thanks Alexey! Please, excuse my complete ignorance (doing my first steps with Apprentice), but where I should place these files for Houdini-Mac? I'm searching for some “plugin” directory, or similar, inside my Houdini folder without success… In fact, it intrigues me were really is installed the main application and related files?, since the files I have inside /Applications/Houdini 13.0.582 are so lightweight… THANKS!
  5. Here is the scene with the imported Alembic boy. It works like a charm! Thanks again for your help, Petz slicedBoyFromUVs.zip
  6. Thank you so much for your input, Petz! The scene you provide works perfectly fine. Now I need to study it to completely understand the procedure, specially that VEXpression on Attribute Wrangle SOPs. I will investigate also how to use PolyCut SOP to slice poly-surfaces. I never used that SOP. Well, in fact I never used the 95% of SOPs in Houdini, since I'm a complete novice!
  7. Yes, that is exactly the conclusion I have arrived :-) Well, I did some tests on an imported polygonal torus and tube (as Alembic, from Modo) and it works fine. I should add a Convert to “Mesh” SOP, however. The curious thing is that UVs were NOT necessary there. This is a clue for me about the use of some kind of inner point order for Carving these imported objects… And the help says: “The Carve op works with any face or surface type, be that polygon, Bezier, or NURBS” Yeah, I suppose Houdini could do something like this (I'm pretty sure, in fact, being the power of this tool), but maybe it's something not no obvious and to much intricate for my poor knowledge… Using the UV map to “slice” geometry (animating results) is something that I have used frequently, but with simple Texture Maps, or gradients, using the Stencil or Transparency channel. But using a real geometry slice derived from UV would be a useful feature for some situations, certainly. Well, I will continue… So much to learn, so little time! :-D Thanks for your feedback, guys.
  8. Hi guys, Doing with my first steps learning this marvelous software :-) I was under the impression that CARVE SOP will slice/cut our meshes (even imported ones) following the information derived from UVs. But now I see that this assumption was wrong… I understood what Carve does when using on Sweeps, Lofts, Birails… stuff created inside Houdini. On a next step, I decided to do some tests using Alembic geometry imported from Modo. My first results were great, because I imported some basic figures, like a thorus or a tube (and at these stage I will continue thinking that slice operation should be derived from imported UVs). But now, using a more complex imported geometry/UVs, I get unexpected results… Now I suspect that Carve Slice operation is derived from internal point order structure and not UV map. My question: is there some SOP or (relatively simple) procedure to apply a slice operation, like the ones produced by Carve, but derived from UVs information? I would like to get something like this mockup, slicing geometry through green and red lines that would be pairs of U and V coords, like the Carve SOP: Unfortunately, this is what I really get: Thanks for your help! :-)
  9. Thanks again for your clarifications, Netvudu! Really appreciate your help
  10. Damm! Thank you so much for this alternate version, Netvudu! I think that I follow the net (more or less), although that green operators… ufff, I need to learn some more basic things before completely understand. Specially that expression in the Atribute VOP: vcc -q $VOP_INCLUDEPATH -o $VOP_OBJECTFILE -e $VOP_ERRORFILE $VOP_SOURCEFILE Of course, I will save your example as gold for further reference and study! Step by step… ----- A different issue: trying to open your file in Houdini 13 I received lot of warnings, and then I saw I can open in 14… Is there some way to save this 14 scene to open with 13? (it occurs that even if I instaled the new 14, it doesn't run fine on my system… and I plan to continue learning for some months on 13, until I acquire a brand new machine…) Thanks again for your great help, guys!
  11. Aha! Yes, you are right, it gives a nice result once you resample the NURBS! However it seems a “curious” thing to me that, even without resampling, it works fine in one direction ($PCT) and “not so fine” in the opposite (1-$PCT). Something related with NURBS interpolation or something… I suppose… In the other hand, without resampling, it works fine using $PT*(1/($NPT-1)) and 1-($PT*(1/($NPT-1))) Big thanks for your help, Pradeep!
  12. It occurs both with 13.0.582 and Attached is the scene corresponding to screenshot (v13). sweep_invert_PCT.hipnc.zip
  13. Hi guys, We can use $PCT in the Sweep Scale parameter and will get a linear scale from 0-1 along the backbone. That is great and fast! But, why using 1-$PCT does not give us a precise result? As you can see on attached image, both extremes on right sweep are bigger than on left one. It's obvious on the thin end, but also occurs on thicker one… $PCT gives us an 0.0 ... 0.25 ... 0.75 ... 1.0 scale 1-$PCT should give 1.0 ... 0.75 ... 0.25 ... 0.0 scale, right? The same problem occurs when using a ramp: chramp("profile", $PCT, 0) It works perfectly fine at first stage, but if you change your first ramp point control from 0 to 1 and last one from 1 to 0 it clearly appears that the thin extreme is NOT zero size… (?) Maybe I'm misunderstanding something obvious? THANKS for your feedback! NOTE: these alternatives works perfect… $PT*(1/($NPT-1)) 1 - ($PT*(1/($NPT-1))) chramp("profile", $PT / ($NPT - 1), 0) …but it really intrigues me that the more simple $PCT has this problem.
  14. It's an iMac 27" - 2.66 GHz - i5 (+4 years) with Mavericks 10.9.5 I'm running Houdini 13 Apprentice on same machine and works pretty well… My goal is to learn the basis of this app along 2015, and then I will probably acquire a MacPro or at least a “high-end” iMac… and go to the Houdini Indie route. Of course I can stay with 13, but just installed the new 14 (more a curiosity than a need…) and found these strange behaviors with handles. Other parts seems fine…
  15. Thanks for your input, Elena. I have deleted my prefs and nothing changed on handles visualization… :-/ Just in case, I deleted this entire directory: /Users/cristobal/Library/Preferences/houdini/14.0
  • Create New...