There is no significant boost in simulation speed with enabled GPU support. Why?
Dyverso is optimized for multi-core and many-core CPUs, but some GPU cards do not have enough computational power to outperform a modern 8 core or 12 core processor.
Gaming cards like the GeForce GTX 10 series are perfectly suited for Dyverso and perform very good. The typical speed boost is around 4x compared to CPU simulations.
For more information visit → "GPU-Acceleration" or "→ "Ask : GPU-Acceleration".
The mesh is not created where the particles are. Why is there is an offset between mesh and particles?
There are some cases where you will see an offset between mesh and particles:
- The "Scene" tree object has been shifted with the the parented "Mesher" node after the particle simulation. To fix this, detach the "Mesher" or reset the "Scene" object to its original position.
- With some MoGraph objects ("Cloner", "Array", and "Matrix"), RealFlow | Cinema 4D evaluates transformations and applies them to the "Scene" and "Mesher" nodes. This may result in an offset.
Particles are not influenced through daemons or other fluid containers. What's happening?
In many cases, the links are established automatically by RealFlow | Cinema 4D, but there are also occasions where you have to connect interacting nodes.
Take a look the "Scene" and "Links" fields of the nodes involved:
- If "Scene" and/or "Links" are empty the node will not be affected by other scene elements.
- Specify the interacting nodes and "Scene" through drag and drop.
I have applied an object to the "Object" emitter, but there is no emission. What's wrong?
When the body's polygons are very small it might happen that you will not get any particle emission. To fix this, increase the "Fluid" container's "Resolution" to create more particles. You may need very high settings (> 100 or more).
Isn't there a way to specify a default cache folder?
You can define a base path in Cinema 4D's preferences under "RealFlow". For the actual cache data we recommend specifying a separate folder for every scene, because otherwise existing data might be overwritten.
I have upgraded from RealFlow | Cinema 4D 1.0. Is it possible to use my scenes in 2.0?
Yes, this is possible, although a few fluid parameters have changed (e.g. PBD "Viscosity" is now "Damping", PBD "Ext Pressure" is now "Ext Pressure Scale"). We therefore recommend going through all fluid settings to see if they have been converted correctly.
- Cached particles files can no longer be used or imported, because in 1.0 the file format is RPC and in 2.0 we have switched to Alembic Ogawa.
- Initial state files from 1.0 are also saved in the former RPC format and therefore invalid.
- Mesh files, on the other hand, are still valid.
Why are the cache files so big?
RealFlow | Cinema 4D stores a lot of information for hundreds of thousands or even millions of particles – and every particle requires certain data for a correct simulation.
Meshes often consist of several millions of polygons. A single mesh can easily have 200-300 MB per file or even more, but with today's storage prices it should be problem to care for enough disk space.
Can I use SSD drives with RealFlow | Cinema 4D?
In terms of simulation and read/write speed it definitely is a good idea to have fast SSD, but these devices have a limited amount of bytes to be written – in many cases something between 250 and 500 TB. Beyond this limit data can only be read, but no longer be written.
If you consider a large simulation can produce several hundreds of gigabytes this lifespan is a serious thing to think about. We therefore recommend modern hard disk drives. They are slower, but much more reliable.