Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tigger

  • Rank

Personal Information

  • Name
  • Location
  1. CGWorkshops: VEX in Houdini - ask me anything!

    Thanks for the reply Shawn! It's encouraging to hear that I fit the target audience. Sounds like I should be pretty well equipped to learn a bunch from the course. I'm really looking forward to getting started! I like your definition of a TD. It gave me a better understanding of who a TD is. I knew generally what was meant by the term with respect to tools and responsibilities. I'm super interested in visual effects, and TD is the role that most interests me, so I've searched around a bit to learn about it. But it is great to hear an explanation from someone who lives it. I just met Andrew a couple weeks ago. Super great, super smart guy! And Robert's work is so inspiring. His early Processing stuff is what lead me into "creative coding". I've heard cinderdome stories from Steve; sounds like a fun time!
  2. CGWorkshops: VEX in Houdini - ask me anything!

    Hi Shawn, I'm signed up for the course and I'm really stoked for it! So much so that I'd love to start prepping for the course. I sent you a private message on CGWorkshop's site with a couple questions, but the message system over there isn't very user friendly. So I'm posting here in hopes that you or someone who's familiar with the course content can help me out. I am a self-taught programmer currently working as a so-called "Creative Technologist". I rarely use Houdini in my day job (though I'm hoping to change this!), therefore I am not as deeply familiar with Houdini as I'd like to be. I have been playing around with Houdini for a couple of years now, watching tutorials and quietly reading through the wealth of knowledge on the forums here, but I definitely still feel like a novice. All that said, can you clarify what is important to know Houdini-wise before starting the course? The "Student requirements" section of the course description states "you must be comfortable working in Houdini in a TD capacity". Could you explain what that entails exactly? I'd like to get as up to speed as possible before the course so I can get the most out of it. Thanks much! PS - I love that you mentioned Cinder earlier in this thread. Cinder is great! It is my tool of choice for most of my "creative coding" needs. I actually sit next to one of the core team members at work. If anyone is interested in C++ "creative coding" with modern opengl, the Cinder team has recently made the shiny, new, modern opengl based render engine branch public on github.
  3. The computer I built in 2007 (the one I'm replacing) has G.Skill RAM and I never had any problems. I actually specifically chose G.Skill this time because of price but also because I have had a good experience with them so far. Thanks for the advice though. I will look into some other RAM manufacturers for comparison.
  4. Thank you Mark for the really great info. Exactly what I was looking to hear.
  5. Hello All, I am new to these forums and this is my first post. I am almost as new to Houdini as I am to these forums, so I am just learning Houdini using Apprentice. Houdini works just fine on my current computer, but it is pretty outdated at this point. It was built back in 2007! So I'm looking at upgrading with a completely new build. I've done a good amount of research related to a computer build that would work pretty well with Houdini and based on that I've put together a build. I would like to get some thoughts as to how this build looks and any suggestions and/or recommendations for what to change. The build is linked here: http://pcpartpicker.com/p/lhI9 I do have some questions related to some of the info that I've found in my research: - Is 64 GB of RAM overkill for someone just starting to learn Houdini? I'm thinking of dropping the extra set of 32 GB to save some money. Although $30 off seems like it is a good deal... - I am most likely going to remove the second GTX 680 from the build to save money. How valueable is it to have that second GPU? If I keep (or add later) the second GPU, should the two GPUs be connected via their multi-GPU connector (SLI for nVidia)? Or should the 2 cards be left unconnected? I've never used a multi-GPU setup so I'm not 100% how to configure them. - I've read about different combinations of SSDs and HDDs. What is a recommended setup? In the build you'll see that I've included 1 SSD. Is it worthwhile (value wise) to get a second SSD and have them in Raid 0? I already have 2 1TB 7200 rpm drives in my current computer that I can use. How should I utilize those in this new build? I read a mention of setting up the SSD as a local cache and using regular HDDs for files. Does Houdini use the OS disk as a default local cache, or does that need to be configured? Any suggestions and insight here is very helpful! - This is kind of a random question...I've read that nVidia cards are better for the viewport while AMD cards perform better with OpenCL. What about installing an nVidia card as the main GPU for viewport and installing an AMD card as a second GPU. Then set Houdini to use the AMD card as the OpenCL card? Does this even make sense or is it just a silly idea? What would the advantages and disadvantages be? - I am very much in need of a new mouse and keyboard. You'll see the ones I selected in the build. What input devices do you guys use? Which mouse and keyboard? - Displays. I currently own a BenQ 241W and use a very old Dell 2005FPW as a second monitor. I'd like to upgrade my displays, though I'm not sure what to do yet: get a second 24" or upgrade to a 27"? Which displays and display setups are suggested for Houdini work? Many thanks for your time and suggestions. I look forward to learning much about Houdini from all the awesome info and people in this forum. Hopefully I'll be able to give back one day. Cheers.