Beta Release v0.1.8

Release Notes
Download Windows Installer
Installation Instructions

System Requirements

  • Windows 8.1 or later
  • Cinema 4D integration requires R20 or later
  • GPU simulation requires an Nvidia GPU with CUDA CC 3.5 or later (see
  • Redshift integration in standalone app requires Redshift v3.0.36.
    Redshift in C4D is unaffected by this requirement.


  • [Rake] Added constant module parameters for compile-time feature switches.
  • [Rake] Support static-if in struct/table declarations.
  • [Settings] Added Preferences/Show Viewport Framerate.
  • [Templates] Fixed broken Particles/Simple Fountain template.
  • [UI] Fixed occasional crash when closing secondary windows during playback.
  • [UI] Include origin and [1,1] when fitting curve to editor viewport.
  • [UI] Fixed crash if VolumeGrid stats UI was closed before defered update has completed.
  • [Viewport] Fixed stuttering viewport update during super real-time simulations.
  • [Voxelize] Ported particle voxelization from C++/CUDA to Rake
  • [Voxelize] Added separate intensity parameters for each object/channel pair.
  • [Voxelize] Support particle attributes as intensity inputs.


  1. It seems to be lacking vorticity in this release, isn’t it ?
  2. In C4D plugin, when I create poly mesh there is nothing parameter that I can an object mesh to it.
  3. In C4D plugin, when I create spline, C4D crash.
  4. In C4D plugin, when I click on Tfd container, nothing show up. Or I must use tfd v1 to load it ???
  1. Right, Vorticity is not implemented yet.

  2. Some parameters are not mapped to the C4D UI yet. You can access them in the Reactions Graph Editor until they are. Note that the Poly Mesh node is a simple Alembic importer at this point. It will eventually also allow bridging meshes from C4D. Meshes from C4D are bridged to Reactions when you add a Voxelize tag to them.

  3. Confirmed, thanks. Will take care of it.

  4. The TFD container that Reactions creates is only a proxy to allow 3rd party renderers to access Reactions volumes without supporting Reactions directly. As renderers start supporting Reactions directly, this proxy will become unnecessary. You can remove it, but then only use C4D’s builtin renderers to render Reactions volumes.