For the record: Any 64-bit Cinema 4D on MacOS X?

[GruvDOne]

Based on what has been said, I believe that it will happen, but it won't be anytime real soon.

Maxon will have to re-code the program in XCode, which isn't quite as capable an environment as what they currently use (codewarrior, I think). Since C4D runs on Carbon API's, a simple 64-bit recompile of the existing code won't cut it, since Apple decided to push developers to Cocoa to take advantage of Leopard's 64-bit goodness.

Not to mention the fact that, I am sure Maxon's Mac developers are more likely than not busy enough with making 10.5 fully compatible with.. well 10.5.

[macsupremacist]

I would much rather have Cinema fully support Mac OS 10.5 rather than be 64bit. I don't know about you guys but I don't have more than 4 gigs of ram, so it really wouldn't do me a ton.

[Simon Wicker]

maxon are already using xcode (you can't make a universal binary in any other way), we are just waiting for them to move away from using carbon to cocoa.

cheers, simon w.

[lllab]

you cant blame maxon for that, they had all ready for 64bit but apple changed their plans in last minute and doesnt support carbon 64 apps anymore suddnely.

so all developer has worked for nothing....(thats the part of apple policy i dont like)

cheers
stefan

[Srek]

The changed development plans of Apple messed up the schedule at MAXON too, again i'm glad that we don't announce stuff prematurely :)

Cheers
Björn

[Kuroyume0161]

The reason that this request was made 'for the record' is that that little Apple schtick (as I term it) linked in my op has some Mac Cinema 4D users thinking that there is indeed a 64-bit version for Mac or that they are already using it! There isn't much to counter this except what is mentioned in the R10 C++ SDK documentation (which logically deconstructs the premise as false) and in threads like this.

Just trying to verify that something didn't slipped by me somehow. :)

[GruvDOne]

you cant blame maxon for that, they had all ready for 64bit but apple changed their plans in last minute and doesnt support carbon 64 apps anymore suddnely.

so all developer has worked for nothing....(thats the part of apple policy i dont like)

cheers
stefan


Well, the more I look into it, the more I understand Apple's decision on this. Carbon was essentially provided to give developers back in the OS9 days with an easy way to port their legacy code over to the new OSX. Since that time, Apple has been encouraging developers to switch over to Cocoa, and many have. In fact, among Major software programs, the only ones still using Carbon API's are those who existed well before OSX (and even many of them have switched over).

Apple, like anyone else, has a right to advance their software, and just didn't want to spend the resources necessary to keep dragging along antiquated frameworks. I would expect that eventually, there will be no Carbon support in OSX at any level, and this forcing of the hand is the first step in that direction.

Now, I do think that Apple's timing in making that announcement to developers was very, very poor. If they were even contemplating such a move, they needed to tell developers way sooner, to give them the option of making adjustments.

But, what's done is done. Maxon has always worked harder than anyone at staying pace with current OS capabilities (being the first major 3rd party program to release a UB compile for example), and I suspect that we will see a 64 bit OSX C4D in the near future.

[TBoxman]

Personally, I DO want Maxon to make Cinema 4D 64 bit. Just last week I was working on a project involving hair on an animal's body and to make it very realistic I needed to up the counts. But I couldn't render it without running out of memory.

I backed the numbers down and relied on the underneath texture maps to help the hair look convincing. Project looked great. And learning more about hair will probably lead to better, more optimized usage. But running out of RAM to render the project is a very convincing reason to want C4D 64 bit - and not just because it sounds better than 32 bit.

Go Maxon! I hope that this means you are working on it and Apple's reversal to include 64 bit Carbon in Leopard didn't mean it's not gonna happen.

[Per-Anders]

Personally, I DO want Maxon to make Cinema 4D 64 bit. Just last week I was working on a project involving hair on an animal's body and to make it very realistic I needed to up the counts. But I couldn't render it without running out of memory.

I backed the numbers down and relied on the underneath texture maps to help the hair look convincing. Project looked great. And learning more about hair will probably lead to better, more optimized usage. But running out of RAM to render the project is a very convincing reason to want C4D 64 bit - and not just because it sounds better than 32 bit.

Go Maxon! I hope that this means you are working on it and Apple's reversal to include 64 bit Carbon in Leopard didn't mean it's not gonna happen.

Go to the HAIR post effect, change the render type to RayTrace and then set the Tracing Memory down to Low (and be prepared to wait) or whatever value you want. This will allow you to render virtually unlimited hair counts on little memory but at the price of speed.

[stew]

Carbon was essentially provided to give developers back in the OS9 days with an easy way to port their legacy code over to the new OSX.
In 2001 and OS X 10.0, yes. But in later releases Apple added many new features and APIs to Carbon that have never been supported in OS 9. Even 10.5 contains substantial new additions to the Carbon framework (see http://developer.apple.com/releasenotes/Carbon/%20HIToolbox.html). And Apple uses all those themselves, with applications like Finder, iTunes and Final Cut.

For us polygon addicts who actually need a 64bit address space, this is worth nothing, but the rest of the world who isn't even close to using the 32bits they have can stay in Carbon land without a worry.

[lllab]

" Well, the more I look into it, the more I understand Apple's decision on this."

we sure, but then they shoukd have said from beginning and not telling the developers first there is a 64carbon, giving them betas that have full working 64 carbon and 2 weeks before release they juts change mind and skip it...

thats not nice , that i do not undertsand....

cheers
stefan

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.