I’m Waving again…

As readers might conclude from the previous post, I hereby declare myself as an official “Waver” again.

I’ve recently purchased a new Mac Book Pro, with the Nvidia GT GPU option and some ekstra RAM and a faster hard drive. I installed the 32-bit (will it ever be 64) Maya 2010, and Lightwave 9.6.1 (64-bit beta).

I took both applications for a spin.

You have to feel it to believe the performance differences between these applications. Well, ok, I know that Maya is a “giant” package, with LOTS of (maybe too many) features, but, nevertheless, I think a brand new MBP should be adequate for any application that is supposed to run on a workstation.

My rendering is sent to my two stationary Quad Core machines anyway, so I need good response when working IN the application. I don’t see why I should need a $3000 workstation, and a $4500 piece of software that runs like crap on my Mac, when I get by with my current setup.

Plus, now I get 999 FREE NETWORKED RENDER NODES with Lightwave, just in case!

Did I mention that Cinema 4D requires an additional “Advanced Render” module ($400), to set up 3 render nodes???

So, now I use Modo 401 (Runs fairly well in 32-bit) for the more organic modeling, Lightwave for rigging, animation, special FX, Rendering, pretty much everything.

For detailing I use Mudbox 2009. This runs well on my MBP. And off course I use Photoshop CS3, because I’m addicted.

Just for clearing up my mind, I needed to write this down… 😉

 

Advertisements

Lightwave 3D 64-bit for Mac! (And why the others suck)

I’ve always been impressed by the folks at Newtek.
Listen. They’ve given out every god damned updates to their major releases for free, for as long as I can remember. Point release? 9.x to 9.5, no problem!
Download and be happy.

Lightwave has been (and still is) a choice for several 3D studios, in all sizes.
Reason? There are plenty, but the thing I’m focusing on now is:
The pricing is REASONABLE.

The product ships with batteries included.
Sure, it isn’t as intuitive as many other apps out there when you’re starting out, but most people usually hide as much of the UI elements when they get comfortable with any application. Screen real-estate and minimal distraction, right?

There is one thing that caught me by surprise the other day. This might be old news for many, but that’s irrelevant for this post anyway.
I was looking for a plugin at Flay, when I saw some forum post about the 9.6.1 beta. What? More 9.x. whatever releases? 9 was released in, like, I don’t remember. Years ago.
Yep. There it was. The Universal Binary RE-WRITTEN for the 64 BIT MAC COCOA framework.
Why do I shout? Autodesk is a big company, wouldn’t you say?

Maya is a pretty old lady, a workhorse, a friend, whatever, but not a 64-bit old woman.

Why? Because the thing is written in Carbon, and Apple has decided not to introduce 64 bit native applications using Carbon. Applications such as Photoshop, Maya and whatever needs to get a major overhaul to run as a native Cocoa application. Not a one week investment.

Now try placing Newtek and Autodesk in a side by side setup.
What’s that tiny thing doing in line?! Hey, they did it! They took the time, and listened to customers wish-lists, while at the same time working with the new Core foundation for the Next-Gen Newtek 3D application, named / codenamed “Core”.

Autodesk is too busy buying up companies these days, so maybe it just slipped.

Lightwave has Batteries included?
Yep. You get one of the best polygonal modeler apps around, see this extremity, if you have not done so: http://www.thegnomonworkshop.com/store/product/339/

You also get:
Really good texturing tools, a superb node-based material editor, great animation tools, easy and effective rigging tools, good “hair and fur” support, good dynamics (hard/soft body etc), motion graphs, particles, gravity, smoke, fire, hell, the whole enchilada!

So, I should be employed in NT Sales dep, but I’m not.
You don’t see all that much of this “propaganda”.
Wise people spend money on their products, then, in turn, the satisfied customers will act out all the commericumulus they need. (I know that word does not exist)

I surfed by Maxon’s Cinema 4D web shop the other day.

Price: Module based, from base module up to XL and Studio.
Base: about $1000,- (This is only the basic stuff, and BodyPaint)

Oh, you want hair and fur with that? $500 extra.

What? Dynamics? Really? $500 more, please.

It goes on like this.
Oh you want it ALL??? Particles, render-nodes, toon rendering, and the works?? You must be crazy, but ok, that’ll be $4.500,- please!

About the same price as Maya, and other packages.

So… What does Lightwave cost? I mean it has all those things as well, so maybe $3500,-?

Nope. Full package, years of updates for: $995,- Boxed with printed manuals.
Oh, why did I start this post. I’m getting emotional here.

I’ll stop right now.
Autodesk: Get a grip. The bigger you get, the harder you fall.

Newtek: This is business strategy.

Some wise words to end it all:

“Fortune favors the Prepared Mind”
L. Pasteur

Maya 2010 on Linux, and Mac, plus answer to 64 bit Mac question

Yep. New version. 2010. In the house, running happily on my Mac and Linux machines.

The procedures are nearly identical for installing the 2009 version, with the exception of the built in extra packages. I’ll Post a step-by-step instruction for installing 2010 soon, and answer the question about “Why is there no 64 bit version of Maya for OS X”, that pops up at about every g.d forum I visit.

Short answer: Maya is Carbon. Carbon is not 64 bit, because Apple decided that’s a waste of time and resources. So. If there will be a 64 bit version for Mac, the WHOLE application must be re-written in Objective-C in native 64bit Cocoa Framework (this is the only way to program native 64-bit applications on the Mac), vs. the 32 bit Carbon C++ API, that’s as mentioned is abandoned by Apple Inc.
Don’t think we’ll see that happen. Maya has some years on its back… But who knows?

Only the future will know.

Think that actually sums up part two of this post.

Happy living!

A list of required Maya 2009 dependancy packages in Linux

Many people out there, are doing great after following my tutorial, but those that does not run Ubuntu, often run into problems.

Before you post questions to this blog (post anywhere else if you want 😉 ) Make sure you install these packages either in .deb, .rpm or compile the shit from source. The names may differ slightly between distributions, so, search for something similar. The package manager and Google are good friends:

Shell Dependencies
• tcsh
General Dependencies
• glibc
• libpng
• libjpeg
• expat
• libICE
• libSM
• fontconfig
• freetype-
• e2fsprogs-libs
• zlib
• mesa-libGL

X/Motif Dependencies
• libX11
• libXext
• libXi
• libXt
• libXpm
• libXmu
• libXp
• libxcb
• libXdmcp
• libXau
• libXrender
• libXft
• libXinerama

Installer Dependencies
• glibc
• libstdc++
• libgcc
• expat
• libxcb
• libXdmcp
• libXau
• libXfixes
• libXrender
• libXrandr
• libXcursor
• libXinerama
• libXft
• freetype
• fontconfig
• libXext
• libX11
• libSM
• libICE

That should keep you busy for a while!

GC

Maya 2009 64bit Font install / missing fonts in Fedora et. al

Missing fonts in Maya on Fedora, and other Linux distros

A problem with missing font files in Fedora, prevents some text and labels from displaying
properly in the program windows. For example, texture names may
not appear as expected below the texture icons in the Hypershade window.
Also some other packages needs to be installed on some distributions, not on Ubuntu, as I know of, but I’ll writ it down anyway.
Download and install the following rpm or .deb files (names vary slightly so make a search for something similar:

1. xorg-x11-fonts-ISO8859-1-75dpi
2. xorg-x11-fonts-75dpi
3. Xinet.d
4. tcsh
5. libXp (for both .i386 .x86_64)
6. libXp-devel (for both .i386 .x86_64
7. mesa-libGLw mesa-libGLw-devel )
8. gamin-devel (for libfam.so)
9. Autofs