I woke up this morning and powered my computer on blindly, then went to the kitchen to fix me a mug of strong coffee, like every other morning (well, if you can call 11am a morning that is ). To my surprise (and as it has always been with all of my computers), Windows booted up, but my keybard was dead, non-responsive. It was plugged in properly, it was illuminating, but I could press the keys as hard as I can, nothing happened. And so it started. My adrenaline levels risen tremendously, I started to feel really angry and I think if I could, I’d turn green and smashed everything in my way. However, that’s not the case and after I quickly gulped down the delicious, yet bitter, natures’ liquid miracle, I finally started to think. The only difference from yesterday was that I uninstalled VMWare (they released an updated version), but I didn’t install the update, because a phone call interrupted me and I had to quickly fix the last shot I was working on.
This is weird! Autodesk broke its unwritten rule by NOT including CAT with the standard installation of 3ds Max 2010. Why is that? Well, I admit it makes a bit of sense, however, this makes CAT hardly “main-stream” in the 3ds Max field, thus making it harder to count on when working on collaborative projects with freelancers or studios around the world.
CAT is available as a download to those who’re on the subscription program, which isn’t that cool! I personally don’t have subscription as I can hardly justify the cost vs. benefits, especially since the price for a single seat of 3ds Max 2010 is almost twice as expensive as in the US and I can’t buy a US license!
Quite frankly, it’s BS and I’m not very happy about how things turned out, really. I’d rather see Biped go and kept CAT as the core of character animation pipeline in 3ds Max.
I’m starting to seriously think about either reverting to Windows XP or radically switching to a different OS every day.
Gone are times when QuickTime actually meant you could watch movies on your Windows and Mac computers without trouble, when games, such as Myst, could provide richer, more entertaining, content to the consumers. Nowdays, QuickTime more and more means trouble and very unpleasant viewing experience. I’m not talking out of my ass here, I have, unfortunately, experience with QuickTime on both Mac and Windows and I must say that QuickTime is the worst media player you can ever install on your system!
People who’ve worked with me already know my attitude towards groups and why I always tell people who collaborate with me NOT to use them. But they never bother investigating why I tell them so. I agree that it is easy to condemn something right away, however, believe me, I have very good reasons for doing so.
The thing with groups in Max is that they are a special form of a hierarchy which isn’t transparent enough for a general user. They’re fast to create, but mainly, groups are a very convenient way for creating selection sets that are persistent (i.e. they get saved with the file) and you can return to them anytime you want and select a bunch of objects immediately just by clicking on any of the members in the group. These are all great advantages of gropus. The huge disadvantage is their transparency (by that I mean the way they work is hidden from the general user). A user can quickly and easily get carried away and make complex nested group assemblies which can become a REAL pain in the ass in the production pipeline if not taken care of properly. I personally don’t use groups at all (as you can easily substitute them for a different, pipeline friendly, workflow) and very strongly recommend anyone who shares files with me or any other member in our production environment, NOT using them as well.