>If that’s not separate code base, what is?
It’s a different compile of the same codebase, using a different compiler and a different target.
CINEMA has an own abstraction layer, very much like an own OS that allows for complete independence from the host OS.
>But if Maxon were to update Cinema for OS X Tiger, there would still only be the
>one version of Cinema for the Mac. Like Motion 2, the one Cinema 4D would work
>in Tiger on a G5 and give us more than 4 gigs of RAM, and it would also work in
>OS 10.3.9 on a G4. I also noticed that Motion 2 for OS X uses 32 bit plug-ins just fine.
If you can tell me how Motion as a 32 Bit app with a GUI can use more then 4 GB i might be able to give you an answer. In Apples own documents given on this it is clearly stated that it is not possible to have a 64 Bit app with a GUI on 10.4.
>BTW, why doesn’t Cinema use more than 2 gigs of RAM? Thanks!
It does, it’s just that Windows XP does not allow an application to use more then 2 GB by default. The /3GB option in the boot.ini changes this limit to 3 GB. On OS X this border does not exists and CINEMA can use the complete 4 GB that a 32 Bit OS allows.
In this case i have no idea why Apple utilizes a technique to do this for their own products without offering it to other parties. Either there are some still unknown facts on how Motion 2 does it without using 64 Bit in the Interface or the available options for developers outside of Apple are different to what they use internaly (which i doubt).