Limitations and Workarounds¶
Many simulation parameters should only be changed on the start frame.
Many parameters can only be changed on the start frame because it is technically difficult to change them on the fly (e.g. tet mesh resolution). To indicate this, these attributes are not keyable. However, changes to these attributes made on other frames should take effect once the solver is put back to the start frame. If they do not, this may indicate a bug in the software. To workaround it, go to the start frame, change the value to something else, and change it back again. Alternatively, run ‘ziva -refresh’ to rebuild the entire solver. If all else fails, try saving and reloading the scene. If you encounter this, please file a bug report letting us know how to reproduce the failure by emailing firstname.lastname@example.org.
Quasi-static solves are not always stable.
If there are insufficient constraints (attachments to bones) in the system, a quasi-static step can explode because the physical quasistatic problem is not well-posed. To solve this, add more attachments. In other cases, instabilities are a weakness of our current implementation and taking more substeps should resolve the issue.
Selecting Ziva nodes in the viewport doesn’t work in Viewport 2.0.
Selecting Ziva DG nodes (eg: zAttachment, zTet, etc.) by clicking in the viewport doesn’t work with Viewport 2.0 in Maya 2016.5 and 2017. Switching to the legacy viewport is the current workaround.
Ziva VFX writes a log file that can be consulted for additional information should Maya crash. The log file’s location is printed in the Maya script editor as soon as the plugin is loaded, so look there to learn where your log files are going. On Windows, a typical log filepath is:
On Linux, a typical log filepath is: