New Maya 2010 Debian/Ubuntu based Install Guide?

I’ll try not to get to get off-beat or totally far-out, but I’m in the creative writer mode. You’re hereby WARNED.

I read a comment at my Madman blog today, that made me feel all warm and cozy on the inside.

That might be slight an exaggeration, but, anyway it was nice to get positive feedback. It went something like this:
(Hope you don’t sue me for quoting you, PaulN!)

“We really appreciate your helpful guides for getting Maya to work with Ubuntu around here – any chance you can document how you got 2010 working? We are quite stumped by this version. Specifically Autodesk seem to have invented the most ass-backwards license setup _ever_ for this release.”

Second, don’t expect this post to include a new guide for Maya 2010, this time + licensing tips for the Version 2010, that’s part of the Autodesk Entertainment Bundle 2010, I use This! that includes:

Maya 2010
Mudbox 2010 *MS/Mac OS 10
Softimage 2010 *MS
3DS Max 2010 *MS
MotionBuilder 2010 *MS

+ a bonus application. I got “Sketch book Pro 2010″ without cost, that runs on my Mac Book Pro. No Linux guide on this one either, as it is a Intel Mac + OS 10 and MS  only app. I don’t care much about virtualization or emulation of operating systems, so for me it’s “native or I don’t”…

Moving on… The thing I was topic-flamer for, this post. I know there are many out there that would go far to get a real, no fuzz .pdf to print and follow with pictures and all, while GETTING MAYA TO RUN on their GNU/Linux machine calculating and crunching ones and zeros with a Q7 64-bits QuadCore CPU, mounted on a motherboard with 3K*Mhz FSB, dual CPU slots, so you’ve decided to buy two, giving you 8 Cores for lightening fast bit-crunching while rendering  the latest reel. Topped with the latest NVIDIA® Quadro® Plex 2200 S4 dedicated visual computing system (VCS) humming in the closet.

The thing is, Maya 2010 isn’t 1 application anymore, it’s three separate packages, semi-crossed and stress-developed (by underpaid programmers, working in polluted office environments) to work seamlessly.

So, naturally, the conversion from .rpm, involves some knowledge about how to read the package descriptors in the .rpm’s, and possibly creating a specialized script for creating the .deb installers using Alien as the back-end, so that they wil place and link the package correctly. Things might seem to work until you try rendering in MR with a new option, causing the application to SEGFAULT.

I think I know why Autodesk decided to merge Maya (Unlimited) Toxic, and Matchmover into one package:

It’s not the correct use of the words “Complete” or the word “Unlimited”, as a way to describe escalating possibilities between two products.

Here, it is used to “Identify feature levels” with words, cleverly hatched out from the sub-department in R&D, set out to form a naming convention for their flagship line of (hijacked) products…

If a thing is “complete”, it has (according to a trustworthy dictionary/thesaurus) the following qualities:

“A state of being, often used as descriptors of either a psychological achievement as in: “Fulfilled”, meaning there is nothing more to strive for. Products, where it’s meaning often is synonymous with “Accomplished” and indicating from the stem word “complete” that concludes something, there is nothing more to add.”

I suspect this naming convention to be the problem here.

Boss says: “Hey!, I’ve looked up the word “complete” and “unlimited” in a thesaurus this weekend. We need to re-brand, and we need to do it fast!!
The words actually summons the same in all but the slightest context digressions! The word “complete” means, like, “nothing more to add”, “finito”, nothing more to add.
But we’ve made an “Unlimited” version as well as “Complete”, and it adds stuff. A lot!
This is insane! I’ll fire the 200 people employed with marketing, and the rest of you: think fast! We need ONE version of Maya, and this time, we’ll prefer the safe way. Let’s just call it “Maya”, plus maybe, hey, 2010 is coming up right? Let’s call it Maya 2010, and release it in 2009! That’s more like it! Nobody is going to make us look like illiterate fools!

The thing is, there is actually, besides from some statically linked lib files that needs to be updated to newer versions, not much keeping you from installing the Binary, closed source software, using a package scheme converter like Alien.

These days, the developers of new software rides on the widespread wave that have done the switch to either a new version of the GNU C[your language here] Compiler suite, a different multi-threading framework, or they’ve jumped on the “Let’s do OpenCL and Cuda development” wagon. Possibly a “Nokia/QT path” for cross platform development as well…

This doesn’t directly touch the users of the software, because, as in the case with Autodesk, the software is delivered in installable packages, that places statically linked lib files along with the binary ones (so they know that the client will be using the right version when upgrading their operating systems, something that makes relying on native language and library support impossible.

But, these are just packed with different package format schemes, and those are not binary. The content is.

If you find a way to extract the files from a .rpm package and then into a .deb package that in turn does the same thing, placing files where they belong, and creating different links, etc (also known as “Installing”). I wouldn’t consider myself a deep level hacker to make use of tools that are readily available for these tasks. But, then there is a problem. You need to do all this “by hand”!
A roll-your-own-spliff software installation, and it needs to be punced in as “commands” in a shell environment!

Hmm… (scratches head). “Lets search Google!”

What I’m trying to say is that with a LPI level 1 GNU/Linux knowledge under your belt, you should be able to decipher this task at hand.
BUT.

If you try to follow exact step-by-step instructions, without having a clue what or why you’re issuing these cryptic looking commands, you’re most likely to fail. There is no such thing as an identical system. You might get a kernel panic, after you ruthlessly renamed or moved an actual system-file, (“Hey, the name was ALMOST the same!”) as in the guide! But the file wasn’t statically linked, but the actual code containing instructions for reading the instructions to operate your graphics card.

So, a Guide, could mean success or failure, or the difference between a stable system and a kernel panic…
I must say that most of the problems I’ve seen reported and tried to answer on this post, is a result from, and belongs to the mentioned kind of “misbehavior” against your darling computer.

So, if I’m going to write a complete hands-on guide for installing Maya 2010, it will take plenty of time and effort, not to mention installing the thing on different versions of GNU/Linux distributions.
So, I will not make a guide for free, covering the ins and outs of this process.

There are three applications involved, and a slight error in one install, might corrupt another.

BUT, If there are enough people out there willing to pay me $5 each for doing this, I’d consider doing it. Then it would be a labor, and the quality of the guide would be accordingly.

So. If that is something you would like to purchase, please send me a Gmail containing the words MAYA PDF as subject in the message. Then, I’ll get to it.

Madman

Why do I call myself “The Madman”?

Well, obviously because I believe I am mad. I think there is more mad people in this world then there are sane people.

Most people I see around me are wearing masks. These masks is bought in the “house of artificial happiness”, and it was purchased in a unconscious state of mind, by someone unknown, while they grew up.

If you look at the world we live in, it would be a strange thing if one could live happily.

Sure, I have pleasures in life, but is that the same as happiness? As a whole, it’s really more too it then just momentary states of enlightenment. When I meditate (yes, I do Vipassana meditation), I see things clearly. All the work that must be done.

I try to to live as if there was no tomorrow, but that has side effects. Like two weeks ago, I purchased a Mac Book Pro, which I really couldn’t afford. So my mortgage payment is now overdue. But that was a materialistic, and selfish example.

This might have to do with my bipolar depression, I don’t know.

Anyway, try not to inhale dry cheese crackers. It will not do you good.

Network Licensing Maya 2010 on the Linux client

I recently received a question about licensing via a network server running Windows on the network.

I’m definitely no licensing expert, but this MIGHT give you a push in the right direction. (Or get you totally far out) ;-)

So, the guy that contacted me had a problem regarding the license utility not showing up when starting Maya.

Autodesk support had turned him down, as the platform (or rather the distribution) used was not “supported” by the giant.
This should not be a barrier, and I seriously think that Autodesk should be able to offer SOME sort of support to paying network licensees that pay $$$ an mas for their overpriced products, no matter what Linux distribution they choose to use. (hopeless).

So here it goes:

Well, the license utility usually pops up on the first launch of Maya.

The error:

Tried Maya Unlimited 2010 (657B1 2010.0.0.F), error 41

The F (657B1 2010.0.0.F) in the error stands for floating license I think.
The FlexLM errorcode 41 stands for “Feature was never checked out”

You obviously should have access to the license file and that this is registered with AD and in order, as the
licensing works on the Windows clients. This is done using the LMTOOLS on the
Windows licensing server.
So, on the client side:

First find out where the lmutil executable is installed on your local machine.
I think what you need to do is to first locate the licensing server with:

./lmutil lmhostid -hostname

This should show the servername.

Then you need the License server ID, to get this:

./lmutil lmhostid

The twelve-character host ID should show up.

So with this information you should be able to get the same interface to licensing
on the Linux box with the license tool “lmutil” located somewhere in /opt/Autodesk/Adlm/ path.
(if this is where you installed).

Do a search for the file if you dont find it.
This is the executable license utility that looks the same on all platforms.

But, if you cant get by with this, I must wave the white flag, as I’m no licensing expert!
;-)

When Lightwave comes with a “Hard Core”…

If you, like me, have been following the evolution around the next version of Lightwave, you also know that the details around the project, that the users (members) of the “Hard Core” community has been privileged to get insight in, is really promising.

I will not expose any of these materials in my blog, as they are “community only”.

Most of it will probably leek through via the wire elsewhere, but I don’t want to be the one to blame. One thing I must site from todays news update is not something that could be considered “exposure”, but maybe as a bait, or seed to grow confidence in a society that has kinda been an “underdog” in the sense of presence, at least for the last couple of years.

When I quote the words: “The Future is really bright for Lightwave”, and when these words comes from “the high order” of developers at Newtek, it should suffice.

As you see when visiting Newtek’s Lightwave web page, it’s Core we’re talkin’ here. A new way for developers and artists alike to build upon and take advantage of a product that has been tested by real users, flamed upon and beloved, constantly debated in a enthusiastic sub forum for registered users. Bugz have been corrected and through frequent “test releases”, the members have been able to actually use the upcoming product, from its infantile beginnings, all the way to the final release.

That’s pretty unique, if you think about it. I don’t know any other company (that does not operate with open source), that has enough guts to do a thing like this. But on second thought it makes perfect sense. It cuts development time and testing cycles, as most bugs and annoyances has already been seen and reported by loyal followers.

I must say, I look forward to the “New Standard”, that will actually change the possibilities in magnitudes, compared with todays work flow.

Thumbs Up, and good luck!

May the forces be with you.

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… ;-)

 

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

About the Maya on Linux Guide

Sorry to say, that I can not provide you more support than I’ve already done in preparing this, (still the best I’ve found to date), guide for installing Maya 2009 or 2010 on any version of Linux, listing all the required libraries, and a step-by-step, working (if you read the comments) recipe for success.

It has taken me quite some time and effort to troubleshoot, log, and prepare the existing guide, and it works for me, if followed unchanged and in correct order.

GC

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