Legacy MPxNode plug-ins defaulting to parallel evaluation: what are the actual limits and risks?

Answer

The default‑to‑parallel behavior for legacy MPxNode plug‑ins that do not implement MPxNode::evaluationMethod() is consistent across Maya 2019 through Maya 2026; there is no per‑node way to force serial evaluation without recompiling the node. To attribute a race condition to a specific node, enable Maya’s Thread Safety Checking (or Evaluation‑log) and inspect the warnings/logs for the offending node.

Likely explanation

Maya’s Evaluation Manager treats any node that lacks an explicit evaluationMethod() declaration as fully parallel (kParallel). This fallback has not been altered by later conservative heuristics, so the behavior is uniform in the stated version range.

Confirmed facts

• Legacy nodes without evaluationMethod() are scheduled as kParallel in Maya 2019‑2026 (research finding).
• No built‑in attribute, plug‑in metadata, or Evaluation Manager override can force a single legacy node into serial mode without recompiling (research finding).
• Enabling Evaluation → Enable Thread Safety Checking (or Debug → Evaluation → Log Node Execution) causes Maya to log warnings when a node accesses non‑thread‑safe state while running in parallel (research finding).
• If Thread Safety Checking is unavailable, the only reliable workaround is to run the entire scene in serial evaluation mode via the Evaluation Manager UI (research finding).

Steps to diagnose and mitigate

1. Open the scene in Maya with parallel evaluation enabled (default).
2. Activate Thread Safety Checking: Evaluation → Enable Thread Safety Checking.
3. Play the animation or evaluate the graph a few frames.
4. Open the Script Editor / Output window and look for warnings of the form "Node <nodeName> accessed non‑thread‑safe static data".
5. Identify the offending node from the warning; that node is the source of the race condition.
6. If Thread Safety Checking is not available (older Maya build), switch the Evaluation Manager to Serial mode globally and observe whether the intermittent issue disappears; this confirms the node’s unsafety but incurs a performance cost.
7. For a permanent fix, recompile the node to implement MPxNode::evaluationMethod() returning kSerial or kDefer, or make the compute method thread‑safe (e.g., remove static caches, protect I/O with mutexes, or use thread‑local storage).

Missing diagnostic detail that could change the recommendation: Are you using a Maya version that includes Thread Safety Checking (introduced in Maya 2020)? If not, the only viable approach is global serial evaluation until you can rebuild the nodes.