JColdrick
I'm not sure what your point is - are you trying to convince SESI just how terribly they've misjudged the market?
No… in a polite tone, my point in a round about way was directed at the previous posters that said they don't want SESI spending time dealing with porting to OS X. They would rather have them add features to existing platforms. I was trying to make the point, that once they do the port, it will be MUCH MUCH easier to maintain because OS X is a turnkey solution with limited hardware, and OS configuration. This is compared to Linux and the array of PC configurations, that they deal with and still make a profit.
JColdrick
P.S. I don't think you understand the mechanics of things when you say “most professionals that use Houdini have already paid their $17K”. What has that got to do with it? You don't pay extra for another platform. What's relevant is how many *additional* sales(or how much pressure existing large customer companies make) are generated by investing in that port. it's a moving target, OSX. Remains to be seen whether or not it's worth the risk. SESI was the first to port to linux(well, except perhaps pixar/rman), before Maya, before XSI. They're hardly timid in this department.
I was responding to the previous poster that said that there are no professionals that use OS X willing to spend $17,000 on Houdini. I was making the point that they maybe they don't use OS X because they can't use OS X (since Houdini doesn't run on it) and thus they are already set up on Linux, and at this point are content. I realize how the license mechnism works, I had a Houdini license for 2 years from 2000-2002
Compiling kernels? Please, I have better things to do. Only diehard hobbyists do that. If you're going to spend time doing that for a production pipeline, you better have a lot of time on your hands.
OK…, I already admitted it's not that bad anymore… like it was years ago when everyone compiled their kernel.
Additional note…
Well for the Mac people out there, thinking of trying Linux on Virtual PC and then running Houdini on that. My attempt was on a Powerbook G4 1.25 GHz with 2 Gigs of Ram.
I installed Ubuntu 5.1 last night. It installed very cleanly, but took about 10 hours. After it booted, I had to go into recovery mode and make one X11 config change. But after all that, it works, but the performance issue made the install unusable… Takes like 5 seconds for windows to pop up. It is so slow, I'm not even going to try Houdini.
I find this strange, because I have a Windows 2000 Virtual PC install that I use to log my hours for work( the only Windows app I have to run ) The Windows 2000 install runs very well and fast. But Houdini 8.0 always crashes on it, so I gave up on that.
I find it very strange that a Linux distro would run so horribly slow compared to Windows 2000. I remember the days when Linux rocked on a 486. Have these consumer based Linux distros become that bloated on the road to user friendliness?
Maybe I'll try a stripped down Slackware and see if that makes a difference.
###
I would like to get Houdini up and running on Linux in Virtual PC.
After further testing, this may be doable, the slow response isn't as bad as I first thought… it seems that was more application start up time…, like a terminal window… still 5 seconds for a termina window… but it works.
Also talked to a friend who has been a Linux diehard since 1994, a computer science professional that does compile his own kernels… He says…
In general Linux distros still can rock. To a large extent, the greatest deterrminant of “speed” on a Linux machine is the choice of desktop. Run KDE and you'll be less impressed than if you run WindowMaker. Gnome desktops are somewhere in the middle.
Also, your stock kernel almost certainly does not come compiled fot the processor on your machine. While the differences between, say, a PII and PIII are nothing to get upset about, the same can't be said for a PII vs a Motorola chip. This can make a big difference.