- Plugin PushCPs , does in general the same as puzh V2 (but Marcel Brinkmann is lost in space ....
can started from a model or group
possible actions
modifiy the model self
create pose from 0% -> 100% (2 keys)
create pose from -100% -> 100% (3 keys)
create a action (upto 10 keys, checkbox must be check for keying the frame)
moving the cp's inside a existing action or choreographie
demonstration video http://www.sgross.com/am_test/amforum/push_demo.mp4
- shadows for particle systems are not rendered , if
"Use settings from the camera" is active, the camera has "Render Hair/Particles" on ,but in the viewsettings "Render Hair/Particles" is off
- When starting "Bake Particle" while holding the Shift key down, A:M won't update the viewports for each calculation/baking step (for speedup and prevents an "Application not responsible bug" from happening, when large/many systems are calculated and updated)
- "Bake Particle" always switches the viewmode to wireframe, after finishing changing back to the last used viewmode
- fluid systems no longer build their fluidprop (representation for the fluids in finalrender), if the system is outside the viewport (reducing memory consum, speedup)
- Largeadressaware enabled
This only has an effect when A:M is running on 64 bit Windows/OSX
If installed memory is
> 3GB the internally memory limit is set to 2,5GB
> 4GB the internally memory limit is set to 3,5GB
otherwise the internal memory limit is at the default 1,7GB
This makes it possible to render in higher resolution and work with large particle systems (in special hair and fluids, they are very memory intensive)
About the internally memory limit:
A:M is checking at some points (in special in the rendering process) if the internally memory limit is reached. If this is true , then A:M tries to release some memory (to avoid swapping to harddisk), but in some circumstances this causes the needed time for the actual operation to grow greatly.
(cause: if limit reached -> free memory , but if things stored in this memory are needed -> realloc the memory and rebuild these things again ...)
