Release date: August, 21st 2017
Please take a close look at RealFlow | Cinema 4D's list of limitations and known bugs. It is a valuable resource when you encounter problems, crashes, or difficulties:
- Cinema 4D R15, R16, R17, R18 or R19 (when available) (64 bit only)
- Windows 7 (or higher) or OS X 10.9 (or higher) operation systems Intel® or comparable main processor
- 8 GB RAM
- 100 MB disk space for installation
- Network adapter and internet access for license activation
- RealFlow | Cinema 4D supports GPU-based simulations and multi-core/multi-processor systems.
Since fluid simulations are computationally expensive and allocate large amounts of disk space we recommend Intel® i7 or Xeon systems (or comparable), 16 GB RAM (or more) and a 512 GB hard disk drive/SDD.
- RFCFD-549 - Better behavior when fluids with different surface tension coefficients interact.
- RFCFD-543 - New 'Compute Vorticity' parameter for fluids to compute it only on demand.
- RFCFD-536 - From now on it is possible to use Team Render without installing a RealFlow | Cinema 4D license in the render nodes/clients.
- RFCFD-351 - Array Tool: Parameters can't be animated for meshes.
- RFCFD-517 - Initial State files created in RealFlow | Cinema 4D 1.0 are not compatible with 2.0 version due to the switch from RPC to Alembic.
- RFCFD-356 - When using a multi-segment spline with the spline emitter node the "Prev" and "Next" buttons only iterate through the control points on the current segment.
- RFCFD-358 - File paths can't have unicode characters on Mac OS X.
- RFCFD-519 - Simulation steps configuration from RealFlow | Cinema 4D 1.0 scenes is reset to Auto mode when opened in 2.0 version.
- RFCFD-469 - Simulation look on render may differ between multiple simulation/renders unless caching is enabled.
- RFCFD-486 - Objects deformed with Rigid, Elastic and Particle Skinner only support motion blur when using the Point Cache tag.
- RFCFD-499 - Particle render instances are not rendered/recognized by NVIDIA's Iray.
- RFCFD-500 - Motion blur with meshes doesn't work with NVIDIA's Iray.
- RFCFD-501 - Motion blur with meshes doesn't work with Maxwell Render.
- RFCFD-530 - Particle render instances original objects remain visible during render.
- RFCFD-531 - GPU simulation crashes if TurbulenceFD plugin is installed and user has multiple NVIDIA graphic cards.
- RFCFD-548 - Plugin crashes when two SPH fluids with and without surface tension interact when GPU is enabled.
- RFCFD-538 - Surface Offset parameter of Fill Emitter sometimes is ignored if previous value was smaller.
- RFCFD-524 - Surface Offset parameter of Volume tag is ignored for Fill Emitter.
- RFCFD-547 - Duplicating and linking a Magic daemon to a Fluid and then removing the link to the Fluid crashes when simulating afterwards.
- RFCFD-544 - Surface tension in the Crown daemon is not working when the GPU is enabled.
- RFCFD-550 - Linking a second k Isolated daemon to a fluid and then removing the connection makes the other k Isolated daemon stop working.
- RFCFD-528 - Creating Thinking Particles groups for Fluids with the same name may lead to unexpected behaviour.
- RFCFD-534 - Sending a job to Render Queue crashes Cinema 4D.
- RFCFD-552 - Cinema 4D crashes if you try to render with Octane a cached scene that contains a Gravity with some parameter animated.
- RFCFD-542 - It is possible to enable GPU simulation even if it is not supported for the current computer.
- RFCFD-522 - Emitter ID value is not preserved on scene reopening.
- RFCFD-349 - If two different Fluid nodes are linked to the same Emitter node particles get created continuously only in the first linked Fluid.
- RFCFD-354 - If a segment is removed the configuration of the circles of the other segments is reset.
- RFCFD-353 - Undo/Redo is not working when a control point is added.
- RFCFD-200 - Split parameter does not work for k Age and k Speed daemons.
- RFCFD-551 - Having two or more k Isolated daemons linked to the same fluid makes the isolation value grow as many times as the number of k Isolated linked daemons.