ICE logic to Houdini

   7788   18   3
User Avatar
Member
8 posts
Joined: March 2014
Offline
Hello.

Recently moved from Softimage to Houdini. I have relatively a little knowledge about ICE. At this time I'm trying to repeat this simple ICE tutorial in Houdini (http://www.youtube.com/watch?v=0c1i498va44 [youtube.com]). And I can't understand where do I start. Where nodes GetData and SetData, which are fundamental in ICE? Explain to me please, an example of this lesson, how to construct the logic in Houdini.

With respect, WotS.
User Avatar
Member
11 posts
Joined: Jan. 2014
Offline
Heh, I see we were having similar thoughts at almost the same time
User Avatar
Member
370 posts
Joined: Nov. 2008
Offline
http://www.sidefx.com/index.php?option=com_content&task=view&id=2186&Itemid=361 [sidefx.com]

and

http://www.sidefx.com/index.php?option=com_content&task=view&id=1744&Itemid=254 [sidefx.com]

First Steps Intro is good way how to get into Houdini workflow.
User Avatar
Member
302 posts
Joined: May 2006
Offline
I was in a good mood and created a Houdini file which very closely resembles every step taken in that ICE tutorial. It´s also full of notes so that you can go reading along while you see what I´ve done.

I will just say that from your questions (both Wots and Tom) I can tell you currently know very little of Houdini and that worries me. I mean, would you start a novice of Softimage on ICE for his first day with the software? Probably not. It looks like that´s what you´re trying in Houdini. Please, first understand the software and play around.

Anyway, here´s the file for your own pace of learning. This is “VOPs Concepts and Workflows Part 1”

Hope it helps.

Attachments:
IntroVOPsForSI_Users.hipnc (111.4 KB)

Javier Meroño
FX TD.
User Avatar
Member
11 posts
Joined: Jan. 2014
Offline
Thanks Javier, I should walk before I can run, I guess
User Avatar
Member
8 posts
Joined: March 2014
Offline
Thanks for quick help guys! Thank you very much for the links to tutorials. Especially, thank you for sending the project, Javier. But I have one question: in node called “importattrib1” we specify attribute called ‘dist’, but where we recorded it? As I understand it, we find it from the node ‘ray1’, but I not found a function that would write attributes. Or ‘dist’ is I system variable?
User Avatar
Member
4172 posts
Joined: June 2012
Offline
You can always middle mouse button click on the nodes to see when variables/attributes are created.
User Avatar
Member
75 posts
Joined: Feb. 2011
Offline
WotS
Thanks for quick help guys! Thank you very much for the links to tutorials. Especially, thank you for sending the project, Javier. But I have one question: in node called “importattrib1” we specify attribute called ‘dist’, but where we recorded it? As I understand it, we find it from the node ‘ray1’, but I not found a function that would write attributes. Or ‘dist’ is I system variable?

On the importattrib1 Node there is a parameter named OP Input Index. This is set to 1. This will inherit any attribute specified connected to the VOPSOP's 2nd input connector. 0 being first, etc. This input is connected to the Ray1 node, which if you middle mouse click on, will show a pop up with the created dist attribute.

Edit: To open up the Middle Mouse information into a new window, hit the “i” icon (Operator Info) on the node parameters. Next to help, which is pretty extensive with example files.
Edited by - March 9, 2014 15:26:05
User Avatar
Member
8 posts
Joined: March 2014
Offline
Argh! I forget about middle click!
User Avatar
Member
4172 posts
Joined: June 2012
Offline
WotS
Argh! I forget about middle click!

Rad! For those who are new, the middle mouse button click is the ‘stethoscope’ of Houdini. You can see and diagnose node by node. It will become your most used button!

Directions are:

1. Middle mouse click on node to see current info.

2. Enjoy!
User Avatar
Member
302 posts
Joined: May 2006
Offline
Indeed. The distance is calculated on the Ray Node. If you look its parameter, you will see there´s an option called “Point intersection distance” that is checked. That´s where we are calculating the distance.
And of course, as mentioned, with the middle mouse button you can tell all the attributes that there are at any given point in the network view.

You can also use the spreadsheet over any node to check the numeric values of an attribute at any moment during the node chain.
Javier Meroño
FX TD.
User Avatar
Member
8 posts
Joined: March 2014
Offline
Please give a link to the Houdini help .chm or .pdf
User Avatar
Member
302 posts
Joined: May 2006
Offline
uh? the help is inside the program. And it´s really good. You have a help card for every node with examples.

you can also check it online, of course.



http://lmgtfy.com/?q=houdini+13.0 [lmgtfy.com]
Javier Meroño
FX TD.
User Avatar
Member
8 posts
Joined: March 2014
Offline
Yes Javier. I know it. I just want to download it to my tablet for reading ‘Houdini help’ in places without access to the Internet.
User Avatar
Member
302 posts
Joined: May 2006
Offline
ah, I see.
I don´t think there´s a pdf version of the help.
I imagine you can copy your “help” folder from the Houdini installation into your tablet and read from the browser.

Houdini´s help system shouldn´t be underestimated. It´s a really interactive help with lots of examples. I recommend using it all the time while learning what nodes do.
Javier Meroño
FX TD.
User Avatar
Member
8 posts
Joined: March 2014
Offline
Big thanks for the great idea, Javier! It works!
User Avatar
Member
77 posts
Joined: May 2012
Offline
Hi WotS,
I was wondering, since you said yourself you had little knowledge about ICE, why are you trying to learn Houdini from ICE concepts? Wouldn´t it be better to follow VOPs or other Houdini tutorials for that purpose? There are tons of free and paid tutorials for that matter.

I would understand if you were already familiar with ICE workflow and were trying to replicate your knowledge in Houdini, but since that´s not the case I´m curious why you were doing it like that.
User Avatar
Member
57 posts
Joined: Dec. 2005
Offline
It would be fantastic to see Pooby on this forum soon. He's talked quite a bit about Houdini and fabric engine as alternatives to his beloved ICE. I think I'd expect to see him here soon. We should send him a warm welcome to this site.
User Avatar
Member
66 posts
Joined: Sept. 2008
Offline
I just wanted to remind people coming from other packages, especially XSI that are used to ICE nodes (also used it for a while) that in some senses the “VEX Builder” networks in Houdini might “look” more complicated, and let's face it, they are because of their general approach to doing things.

This is actually a good thing though. You can use the same brain cells in many more contexts without remembering all the node names for example.

If you want to ease the transition you can turn on the option to display full names for input and output connections in your network views.
You'll get the parameter default variable name by hoovering over a connection arrow anyway, so you can use that in your expressions etc.



Then they will look like this:
“If your life is not NOW, you're already dead…”
From Chrizto's book of truths
  • Quick Links