So it’s been a while since I updated anything on here. Part of that is because I don’t have the time anymore. The reason I don’t have the time is because I am now gainfully employed as a Technical Director at Reel FX. It’s pretty awesome and rewarding. Now all I do is write tools all day for the artists. Onwards. So Python is an amazingly awesome language. One of the reasons it’s so awesome is because you can do really hard things really easily in it. One of those things are list comprehensions. A list comprehension is basically a way of creating a new list based off of another list and a subset of qualities you’re looking for. Here’s an example:
my_list = [1, 2, 3, 4, 5]
new_list = [num for num in my_list if num > 3]
>> [4, 5]
So this post has been sitting in my queue for over 2 months now. Why? Well, because it was a lot of trial and error and a lot of failure. I happen to like having clean installs and refuse to have redundancy when I can avoid it. So I thought that I’d do an install of PyQt for OSX to the default Python and symlink it to Maya that way I only have one install that I have to update when I need to update it – among other reasons. Unfortunately, Maya hates that idea. Loathes it even. The errors it spits out are ugly and are basically kill errors that make it so you can’t use PyQt either from bash or from Maya. Loads of fun, eh? To top it off, even if you do get PyQt to work with Maya, there’s no point – in my opinion – in putting PyQt into your default Python install so you can run it from the CLI. Why? Because this bug from ’09 still hasn’t been resolved and you’ll get the following error: “Qt internal error: qt_menu.nib could not be loaded.” Note that the bug I reference is actually for when you choose no-framework, however, even without choosing no-framework as a compile option you’ll still get that error. PyQt on OSX is like trying to set environment variables permanently in XP with a .bat file (pre-SP2 and without using the registry). There is hope though and after a little read on why I’m doing this, we’ll get there. Continue Reading…
So in my last post on Houdini George had asked about whether or not I’d be getting more into Houdini. I really want to get into the rigging and skinning with it, but unless I can figure out why Houdini is constantly crashing I don’t know how effective I’m going to be. I also noticed that there are a fair bit of threads regarding Houdini crashing and I had a few folks tell me they stopped learning it because it was so crash prone (most had Mac’s as well so I’m wondering if it’s OSX specific), so I’m not the only one.
Alright. Let’s get to what this post really is about. I decided to jump on how to make a basic (and craptacular I might add) model in Houdini, layout uv’s and add a texture to it. I decided to see if a video tutorial would work and I gotta be honest, it’s a lot harder to tweak it out when your After Effects render takes 3 hours or if you screw something up or if it crashes or your kids are going to sleep, etc. I enjoyed doing it and I think it went well, but there are some addendums that need to be pointed out. Also, if you’re short on time, sorry. The video is about 45 minutes long. (The completed files can be found at the bottom.) So before you delve into it here’s what it is, isn’t and some extra notes. Continue Reading…