Björn Marl
Forum Replies Created
-
Thinking Particles can do all of this, but it takes a good deal of work on your own. To the best of my knowledge there is no tutorial that covers this.
However the basic setup isn’t that hard, the explosion can be done with PFragment, just define the part you want left as a hole as a particle and let the debris spread outwards. PRepulse & Bounce will take care of the impact of debris in other objects, just make sure to use the particle mass to define the influence.
Hope this helps
Bj -
Hi,
this sounds like a problem with the chipset drivers or similar. CINEMA 4D is running very fine on 2003 Server here. You won’t need the 8 GB swapfile, 2 is way eough since no 32 bit app can use more then about 2.7 GB and the absolute maximum for OS and app together is 4 GB.
Cheers
Bj -
Hi,
to the best of my knowledge e-books were never available for CINEMA.
Since R7 isn’t available any more for some years now, you should take a look at the current version R9. You can find the PDF documentation to R9 on the Maxon website.
Cheers
Bj -
It’s not that different. Posemixer became a tag so now you can use it independent from the hierarchy. Take a look at the addendum PDF for more info.
Cheers
Bj -
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).
Cheers
Bj -
Again, tell me how Motion does it.
This is what Apple tells on this
> Got boatloads of RAM installed in your system? Motion 2 can use it.
> With Mac OS X -
Yes
-
>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. -
>Reading that developer guide, it’s pretty obvious that the Cinema 4D could be
>ported to 64 bit. Cinema 4D is exactly the kind of application that would work
>well under the 32-bit GUI/64-bit processing model.Fact is the modeller can’t be ported to 64 bit with 10.4, therefore it would be impossible for mac user to create scenes where the scene size demands more then 4 GB.
>Also unless Maxon creates the ability of it’s 64-bit apps to work with 32-bit
>plugins, plugin developers will have to create both a 32-bit and a 64-bit version.The ability to link 32 bit libraries in a 64 bit apps is something none of the major players on the OS market were able to pull off, why should Maxon be able to do it? It’s like trying to put the hood of a VW bug on a lincoln continental. Either it won’t work or it won’t be the hood of a VW bug anymore.
Cheers
Bj -
The codebase of CINEMA is the same for OS X and Windows 32/64 bit. If we were to support a 64 bit non GUI renderer to make use of the 64 bit parts of OS X this would need a seperate codebase, thereby increasing workload in programming and quality assurance immensly.
Cheers
Bj