You are viewing the documentation for Deformable v0.2.1, an older version. Read the latest, v0.9.0
Maya Plugin
Troubleshooting
Where the Maya plugin shows its messages, what each message and node error means, and the Maya steps that fix them, with Maya's own history commands, the bake and the size of scene files.
On this page
Most problems show a message: on the Command Line after an action or while you play, or in the Status section of a node’s Attribute Editor. Start there. This page lists the Maya plugin’s messages and the Maya steps that fix them. What to check for each symptom, such as objects that pass through each other or a simulation that is slow, is on Troubleshooting.
Where the messages show
Every message of the plugin starts with Deformable:. It shows in three places:
- The Command Line at the bottom of Maya’s window shows the last one, a warning in yellow and an error in red.
- The Script Editor (Windows > General Editors > Script Editor) keeps them all, in order. Open it when a message went by too fast.
- The Attribute Editor shows a node’s own error or warning in its Status section, and a Deformable Scene’s message in its Status Message, for as long as it holds.
A node’s message names the object and the node, such as
Deformable: pSphere1: Deformable Tetrahedralize: INVALID_CAGE: …, and a scene’s message names the scene, such as
Deformable: deformableScene1: Play from the start frame. Each new message shows once, and a playback that loops
shows it once. mayapy and a batch render print them as they happen, so a render log on another computer shows them
too.
Nothing moves when I play
Look at the Command Line, or the Deformable Scene’s Status Message, at the start frame:
| Message | Fix |
|---|---|
| Deformable: No Deformable Scene: choose Deformable Scene > Create Scene | Nothing simulates without a Deformable Scene. Choose Deformable Scene > Create Scene. |
| Deformable: Add to a Deformable Scene to simulate: pCube1 | The named objects, five at most, are in no Deformable Scene. Select them and a scene, and choose Edit Deformable > Move to Scene. See More than one Deformable Scene. |
| Deformable: deformableScene1: Play from the start frame | Press Alt+Shift+V, then Alt+V. |
| Deformable: deformableScene1: Set Playback speed to Play every frame: a dropped frame is never simulated | Playback skips frames to keep up, and a skipped frame is not simulated. In Windows > Settings/Preferences > Preferences > Time Slider, set Playback speed to Play every frame. Then play again from the start frame. A scene that plays its bake does not ask. |
| Deformable: deformableScene1: Return to the start frame to apply changes | A setting changed during play. Go to the start frame and play again. |
| Deformable: deformableScene1: A substep would be longer than 0.04 s: raise Substeps | Raise Substeps on the Deformable Scene: 2 or more at 24 frames per second. |
Then check these:
- Is a tool still running? The progress bar at the bottom of Maya’s window lists the running tools and how long each has run, such as Deformable: Tetrahedralize (pSphere1) 0:42. Wait for them, or press Esc to cancel them. A tool whose Compute State shows Waiting has Run set to Wait, and one that shows Cancelled waits for a change: choose Edit Deformable > Update Now.
- Is the object held? In its deformableObject’s Attribute Editor, Type must be Dynamic and Disabled off. Check Disable on the Deformable Scene, and its keys.
- Does the Command Line say Left out of the simulation? See An object stays still at Play. An object whose deformableObject has any other error is left out too. See A node shows an error.
- Is it in the trial and too big? Playing stops with a dialog that says Trial limit: the scene simulates 3,120 tetrahedrons; the trial allows 2,500. The objects that do not fit stay still. See The trial.
- Does a script step the time? In
mayapy, nothing asks Maya for the scene, so a script must read the scene’ssimulatedFrameon every frame. See Read the simulation from a script. - Was the scene copied with Maya’s Duplicate? A copy of a Deformable Scene made with Edit > Duplicate is not on Maya’s time and never steps. Delete it, and make a second scene with Deformable Scene > Create New Scene. See More than one Deformable Scene.
An object stays still at Play
At Play the plugin names each object left out, from every Deformable Scene, and says why, such as Deformable: deformableScene1: Left out of the simulation: Bolt (its tetrahedrons are too small). See Troubleshooting., and its deformableObject shows the fix in its Error Message. Each reason and its fix are on An object stays still at Play. In Maya:
- its scale is negative or zero: set the scale positive in the Channel Box. To freeze it, undo the create action first, freeze with Modify > Freeze Transformations, and create the object again.
- it has inside-out tetrahedrons: lower Thickness on the object’s Deformable Extrude.
- its Deformable Object node says why: see A node shows an error.
For tetrahedrons that are too small:
- Use an autocage with fewer faces. Choose the option box of Create Object with Autocage, and lower Target Face Count, such as to 50 or 20. On an object that has an autocage already, lower Target Face Count on its Deformable Autocage. Then play from the start frame.
- Simplify the mesh. Choose Mesh > Reduce, in the Modeling menu set, such as with Percentage 90, which removes 90 % of the faces, and create the object from the reduced mesh.
The create action refuses my mesh
A create action checks each mesh first and names its problems:
| Warning | Fix |
|---|---|
Not verified: <mesh>: non closed boundary (12) |
The mesh has holes. Fill them with Mesh > Fill Hole, or use Create Object with Autocage with the preference off. |
Not verified: <mesh>: co located vertices (2) |
Vertices sit on top of each other. Select the mesh and choose Edit Mesh > Merge. |
Not verified: <mesh>: non planar (104) |
Some polygons are bent. Choose Mesh > Triangulate. |
Not verified: <mesh>: the world matrix is mirrored or flat (determinant ≤ 0) |
The object has a negative or zero scale. Set the scale positive. |
| Select one or more meshes that are no deformable objects | Select a polygon mesh. A mesh that is a deformable object already, a region or a splinter cage is skipped. |
| Span Layers needs triangles: triangulate the mesh (Mesh > Triangulate) before you copy it | A layer has a face that is not a triangle. Triangulate the first mesh, delete the copy, copy the first mesh again and redo your change to the copy. |
| Span Layers needs two meshes with the same vertices and faces, such as a mesh and a moved copy of it | The second mesh is not a copy of the first. Triangulate the first mesh, delete the second, copy the first again and redo your change to the copy. |
| Span Layers needs exactly two selected meshes: the first one selected holds the object | Select two meshes, the one that holds the object first. |
To see every problem selected in component mode, run Deformable Object > Verify Mesh. See Verify Mesh.
For a model that is not meant to be closed, such as a character with separate eyes, wrap it in an autocage and turn off Verify Meshes Before Creating Objects. See Preferences.
A node shows an error
A node with an error shows it in the Status section of its Attribute Editor, and its output is empty, so the object may show nothing. Nodes after it may show an error too: fix the first one in the chain. The errors of the tools themselves are on A tool shows an error. The errors that come from the network:
| Message | Node | Fix |
|---|---|---|
| Freeze Transformations does not apply to a deformable object: undo it, and freeze before Create Object | deformableObject | Modify > Freeze Transformations ran after the object was made. Undo it with Ctrl+Z. |
| Deformable Prepare and Deformable Object take different tetrahedrons | deformableObject | Feed the tetrahedralMesh of both nodes from the same node, as the create actions do. |
| Prepared Surface Mesh must come from Deformable Prepare | deformableObject | Connect its preparedSurfaceMesh from a Deformable Prepare, or break the connection for a bare object. |
| The object already has a Deformable Object node; this one is ignored | deformableObject | Keep one deformableObject per transform. Delete the second one. |
| The Tetrahedral Mesh input must be a tetrahedral mesh | deformableObject | The mesh is not 4 triangles per tetrahedron. Use From Tetrahedral Mesh only on an _ mesh. |
| Tetrahedrons too small for the simulation: …, Flat tetrahedrons, …, Inside-out tetrahedrons, …, Three tetrahedrons share one face, …, No tetrahedrons to simulate: … | deformableObject | Play left the object out. The message names the fix. See An object stays still at Play. |
| Span Layers needs triangle meshes | Deformable Span Layers | A layer has a face that is not a triangle. Triangulate the first mesh, delete the copy and copy the first mesh again. |
| Image Library is Custom and no Image File is set | Deformable Splinter | Pick a file in Image File, or a bundled pattern in Image Library. |
A field whose force is not a finite number makes its scene say A field gives a force that is not a finite number, so it pushes nothing, with the field’s name, and that field pushes no vertex on that frame. Check the field’s values and keys. See Apply Field to Object.
A tool refused by the license computes again by itself once Check Now or Activate succeeds. See License status.
Maya’s history commands broke an object
Maya’s own history commands reach into the network of a deformable object:
- Edit > Delete by Type > History on the object deletes the mesh it was made from and freezes its surface where it stands. Undo it, and use Edit Deformable > Delete History.
- Modify > Freeze Transformations after the object was made gives the error above. Undo it.
- Edit > Duplicate copies the shapes, not the network that moves them. Delete the copy, and use Edit Deformable > Duplicate Object.
- Edit > Delete on the Deformable Scene says Cannot delete locked node ‘deformableScene1’: the scene is locked so these commands cannot reach it. Use Deformable Scene > Delete Scene.
See History and the locked scene.
Raise the floor
To hide the small overlap of a resting object of about 10 cm and more, which rests 2 cm in, move the Kinematic floor up 0.02 units, turn off Primary Visibility in the Render Stats of its surface shape, and add a plain plane with Create > Polygon Primitives > Plane where its top was, as the floor you render. See An object rests a little into the floor.
The bake does not play
A baked scene that simulates again says why, once: Deformable: deformableScene1: The bake no longer matches the scene: bake again or free it. The scene, or something it reads, changed after the bake, or the bake folder is not where the file expects it:
- Undo the change, and the bake plays again from the next time you play or go to the start frame.
- Or bake again, with Deformable Scene > Bake Simulation.
- When you moved the file, move its
deformable_cache_<file>folder with it, beside it. - When another file sets the same Bake Directory and baked after this file, the bake there is that file’s: give this file’s Deformable Scene a Bake Directory of its own and bake again.
See Bake Simulation.
The render shows the rest shape or the wrong frame
A render that starts where the simulation cannot reach says so in the Script Editor, and in the render log on the command line, such as Deformable: deformableScene1: Frame 10 renders pCube1 without the simulation: render from frame 1, or bake first. Past the end of the playback range, an object baked or simulated up to the end holds that frame, so it is not named. See Render.
A render with motion blur needs a bake: see Motion blur.
The scene file is large
The plugin stores the output of every tool in the scene file, so a file grows with its tetrahedrons. A Maya ASCII file
(.ma) takes about 260 bytes per tetrahedron of an object made with Create Object from Polygon Mesh: 100,000
tetrahedrons make a file of about 25 MB. A Maya Binary file (.mb) of the same scene is about a third smaller, so for
a very large scene you can save it as Maya Binary, with File > Save Scene As and Maya Binary as the file type.
Both work the same. The Maya Binary copy plays the bake of the file it was saved from, which stays that file’s: see
Bake Simulation.
An object made with Create Object with Autocage stores much less, as its cage is light. The bake is not in the file: it is in the folder beside it.
Get help
If you are stuck, email support@tangerina.io. To report a bug, include what Report a Maya plugin bug lists: the versions, your steps, the Script Editor’s output and a small scene file.
Deformable Help > Copy Support Info copies the versions and the license status for you: paste them at the top of your email. See Help.