Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Release date: July 12, 2018

Please take a close look at RealFlow | Maya's list of limitations and known bugs. It is a valuable resource when you encounter problems, crashes, or difficulties:

System requirements

  • Autodesk Maya® 2017 or Autodesk Maya® 2018 (64 bit only)
  • Windows 7 (or higher) or macOS 10.10 (or higher) operating system
  • Red Hat® Enterprise Linux 6.5 or CentOS 6.5 and 7.2 Linux operating system. (Same requirements as Autodesk Maya)
  • CPU 64-bit Intel® or AMD® multi-core processor
  • 8 GB RAM
  • 100 MB disk space for installation
  • Network adapter and internet access for license activation.
  • RealFlow | Maya supports GPU-based simulations and multi-core/multi-processor systems.
Note:

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 storage device.

Fixed bugs

Colliders
  • RFMAYA-449 - Collider node may lead to memory leaks when removed.
  • RFMAYA-464 - Volume of objects in Solid Outside mode is not properly computed sometimes.
  • RFMAYA-468 - Collider interaction textures are not properly applied when the object is transformed by translation or rotation.
Daemons
  • RFMAYA-470 - Magic daemon crashes if selected object does not contain any vertices/faces.
Emitters
  • RFMAYA-448 - Fill Emitter usage may lead to memory leaks.
  • RFMAYA-466 - Maya crashes when resetting the simulation if an emitter has no fluid linked.
General
  • RFMAYA-452 - Cache loading does not work when Maya evaluation mode is set to DG instead of Serial or Parallel.
  • RFMAYA-467 - A resolution of 512 pixels is used for texture sampling instead of the RealFlow preferences value.
  • RFMAYA-471 - Scenes with nodes with references to objects like Fill emitter or Magic daemon sometimes fail to initialize the object when imported as references or loaded as Maya ASCII.
  • RFMAYA-476 - Some node links like mesher fluids or fluid-fluid interaction may not be working after loading a scene depending on the order.
Maya UI
  • RFMAYA-371 - Crown daemon manipulator doesn't work properly.
  • RFMAYA-451 - Crown shape is not is not recreated on scene opening.
  • RFMAYA-473 - Some RealFlow nodes are not highlighted when selected.
Meshes
  • RFMAYA-439 - Sometimes the amount of UV sets generated for the mesher emitter weights is bigger than the actual count.
  • RFMAYA-472 - Meshing a big amount of particles leaks memory.
Parameters
  • RFMAYA-460 - "Stiffness" parameter does not have any effect for Rigids.
Visualization
  • RFMAYA-266 - Meshes can't be selected in viewport if they are in the same position as the fluid.
WetMaps
  • RFMAYA-469 - Maya crashes if WetMap resolution is 0 or 1.

Limitations

Daemons
  • RFMAYA-463 - Setting keys on crown shape parameters crashes Maya on simulation reset.
Maya UI
  • RFMAYA-310 - Legacy viewport is not supported.
  • RFMAYA-419 - Transformation tools may lead to unexpected results when used in a mode different than Object on RealFlow nodes.
  • RFMAYA-461 - Undo of Manipulator controllers does not work.
Fluids
  • RFMAYA-328 - Fluids lack "Compute Vorticity" option yet.
Meshes
  • RFMAYA-145 - Motion blur only works for cached meshes yet.

Known bugs

Emitters
  • RFMAYA-391 - Simulating frame by frame always creates new particles, no matter what is the resolution of the fluid.
  • RFMAYA-431 - Maya crashes when using a subdiv animated by vertex for the Object Emitter.
Maya UI
  • RFMAYA-440 - Undoing the deletion of a RealFlow node may not recover the previously existing links.
Meshes
  • RFMAYA-144 - Motion blur for cached meshes looks distorted when the samples are taken from frames with different number of vertices.
  • RFMAYA-313 - Maya 2017 crashes sometimes the first time a Mesher node loads a mesh with more than ~25k triangles.
nParticles
  • RFMAYA-137 - Maya crashes sometimes in Cache Mode with nParticles.
  • RFMAYA-324 - Particles synchronization between Fluid and nParticles is not working properly.
Simulation
  • RFMAYA-420 - Maya crashes sometimes when a Rigid simulation stops if GPU is enabled. Caching the simulation works.
  • No labels