Ok, HDAs finished now, please check if you see any error or want me to add something else
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter4_HDA_4_WrappingAnHDA.pdf
I will be wrapping this today if there no messages an pass it to Side Effects so please let me know ASAP.
Softimage to Houdini guides
216712 335 9- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
- halfdan
- Member
- 599 posts
- Joined: May 2011
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
Friday surprise…
Data Management 1, 2 and 3 now online.
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
Enjoy
Data Management 1, 2 and 3 now online.
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
Enjoy
- stari
- Member
- 29 posts
- Joined: March 2014
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
Well, one more and I will be done, here is the Data Reconstruction section, hope it makes sense… would love to hear from Houdini artists to know if you guys use this technique or if there are better ways to do this.
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_6_DataReconstruction.pdf
Enjoy.
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_6_DataReconstruction.pdf
Enjoy.
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
And Data packaging is now done!!!
I bet some Houdini artists will find a few nice tricks in this one.
;-)
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_7_DataPackaging.pdf
I will be adding one more regarding modern approaches with Alembic files before I wrap this chapter.
Enjoy
I bet some Houdini artists will find a few nice tricks in this one.
;-)
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_7_DataPackaging.pdf
I will be adding one more regarding modern approaches with Alembic files before I wrap this chapter.
Enjoy
- Platon
- Member
- 99 posts
- Joined: July 2007
- Offline
Jordi,
great work as always!
when you set up all your cache nodes as $JOB/$HIP centric by default, you don't really need preflight that much, but yeah pre-flight is nice to have.
you might want to fix typo in:
page 432, last paragraph.
"I also tick the Alfred Stype progress
for visual reporting on the shell."
great work as always!
when you set up all your cache nodes as $JOB/$HIP centric by default, you don't really need preflight that much, but yeah pre-flight is nice to have.
you might want to fix typo in:
page 432, last paragraph.
"I also tick the Alfred Stype progress
for visual reporting on the shell."
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
Thanks a lot… will fix now.
Pre-Flight is not necessary as you mentioned but I love the fact that it crawls through the scene finding potential issues.. Ultimately I am not a slave of it given its limitations but still I find when developing assets specially it is a way to make sure the asset is as solid as possible.
cheers
FIXED
Pre-Flight is not necessary as you mentioned but I love the fact that it crawls through the scene finding potential issues.. Ultimately I am not a slave of it given its limitations but still I find when developing assets specially it is a way to make sure the asset is as solid as possible.
cheers
FIXED
- takita
- Member
- 207 posts
- Joined:
- Offline
- sanostol
- Member
- 575 posts
- Joined: Nov. 2005
- Offline
- Platon
- Member
- 99 posts
- Joined: July 2007
- Offline
- sanostol
- Member
- 575 posts
- Joined: Nov. 2005
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
I may have to develop further as it was not my intention to put anyone of using $JOB, but it is useful when you build a system around.
You could follow two routes;
1) The more pipelined route in which you use $JOB, this will require (for example) a shell based approach that updates those variables every time you move to another folder, etc… At Realise and pretty much every single place I know this is the method. This is very useful when you have to have concepts like show, episode, sequence and shot information.
An interesting thing that will happen is that once you start using it you will reinvent the concept by defining a set of variables you have full control and are direct pointers to abstract yourself from the directory structure as much as possible.
For example, your company is called Digital Donuts, you may want to build on your shell variables to have direct access like this.
$DDJOB
$DDGEO
$DDMAPS
$DDCACHES
etc…
So ultimately the idea of using just $JOB seems a bit futile, hence the comment.
2) On the other end of the spectrum, a very simple approach you could use would be to use $HIP and as I shown you can use it too in a more advanced way.
For example, let's imagine you have a directory structure like this
…/myshot/
————/hip
————/maps
————/geo
————/caches
and you could reference geo like this
$HIP:h/geo
so it is not difficult to build a simple workflow with $HIP but its true that it is very rudimental so only small facilities may want to follow this approach.
Hope it helps.
You could follow two routes;
1) The more pipelined route in which you use $JOB, this will require (for example) a shell based approach that updates those variables every time you move to another folder, etc… At Realise and pretty much every single place I know this is the method. This is very useful when you have to have concepts like show, episode, sequence and shot information.
An interesting thing that will happen is that once you start using it you will reinvent the concept by defining a set of variables you have full control and are direct pointers to abstract yourself from the directory structure as much as possible.
For example, your company is called Digital Donuts, you may want to build on your shell variables to have direct access like this.
$DDJOB
$DDGEO
$DDMAPS
$DDCACHES
etc…
So ultimately the idea of using just $JOB seems a bit futile, hence the comment.
2) On the other end of the spectrum, a very simple approach you could use would be to use $HIP and as I shown you can use it too in a more advanced way.
For example, let's imagine you have a directory structure like this
…/myshot/
————/hip
————/maps
————/geo
————/caches
and you could reference geo like this
$HIP:h/geo
so it is not difficult to build a simple workflow with $HIP but its true that it is very rudimental so only small facilities may want to follow this approach.
Hope it helps.
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
- sanostol
- Member
- 575 posts
- Joined: Nov. 2005
- Offline
- jordibares
- Member
- 655 posts
- Joined: Feb. 2006
- Offline
And finally the DataManagement chapter is finished… if anyone things I have missing anything of something should be expanded, drop me a line.
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_8_Alembic.pdf
And you have also the full chapter in one single PDF
HoudiniGuides_Chapter5_DataManagement.pdf
enjoy…
Next stop… Rigging
https://www.dropbox.com/sh/y0ti6tyf7o3435u/thsQH1Kf2o [dropbox.com]
HoudiniGuides_Chapter5_DataManagement_8_Alembic.pdf
And you have also the full chapter in one single PDF
HoudiniGuides_Chapter5_DataManagement.pdf
enjoy…
Next stop… Rigging
- halfdan
- Member
- 599 posts
- Joined: May 2011
- Offline
-
- Quick Links