It is thinking like that that is responsible for mediocre software. You are just plain stupid, to put it in words you might understand. With the way OS X manages memory I am very very interested in seeing some benchmarks when it happens.Īnd if you think the type of work that you produce has ANYTHING to do with the OS you are using you should take a huge step back and really look at what you are doing. Autodesk could have had a 64bit capable version of Maya for the Mac quite a long time ago (Apple didn’t make it any huge mystery that the Carbon framework would not be 64bit capable) and I am sure they will not long from now. I would say the amount of time I save using Quicklook alone is well worth any price I pay when it comes to rendering on a single workstation. I promise you, any time you may make up running a 64bit version of Maya, you lose when it comes to actually working with the files you are producing. Render setup is all about compromise and optimization. I would imagine this is a limitation or issue with the scene itself more than anything. This problem has absolutely nothing to do with running Maya on the Mac operating system. I am not really sure what you are saying, but I think beige covered it in his post after this one. The beauty is that you can work in maya on your mac in OSX and then boot it into windows or linux to render. The idea of having to split up my scenes is nauseating. People clearly are doing good work on macs but I don’t miss the days of 32bit. I know studios who’s range is more like 16gb to 32gb. We are going to need to upgrade the whole thing to 8gb because more and more of our jobs require it. We have a segment of the farm that has 4gb of ram and one that has 8gb of ram. Macs are great to a point, but I have renders that go way past 2gb of ram all the time. For some 64 bit isn’t worth the battle at the moment. Thank Apple for this cluster****.ĭevelopers pick and chose their battles. So, developers weigh the pros and cons, “Do I spend a lot of development hours making a port right away which won’t net me any more profit? Or, do I work on the next version and put it out as a 32 bit version and kind of work on the 64 bit version on the side?”. A lot of developers figure there is better things to do with their money as, believe it or not, people will still buy a 32bit OSX version. It takes development hours and people to make the conversion happen. There’s no happy iWizard with candy coated buttons from Apple which automagically converts your favorite app over to 64bit. There’s a horrible misnomer surrounding how easy it is to covert an app over. There are a lot of apps that aren’t 64 bit and probably never will end up being ported to 64 bit on OSX, including beloved Apple apps. Who cares if Autodesk is on the top of your list on your machine. Hint - it starts with Auto and ends with desk. It’s just that 10.6 makes all the included apps 64-bit and sorts out Cocoa 64-bit, which some vendors rely on. Like I mentioned before, there is nothing stopping you from running 64-bit apps on OS X 10.5. Maxwell, Houdini, Cinema 4D, VRay for C4D have been 64-bit for as long as a two years. “Macs” have nothing to do with it - it’s software vendors who are slow to get their 64-bit software out that are the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |