Error codes

Cloth neXt error codes

79 documented codes. Find the code shown in the Bake window for its cause and the first recovery step.

Scene validation

CodeCauseFirst step
CNX-E100Unclassified scene validation failureCorrect the highlighted scene setting and retry.
CNX-E101No enabled deformable objectEnable Cloth neXt on at least one Cloth, Cable / Rope, Soft Body, or Rigid Body object.
CNX-E102Invalid or inconsistent Bake rangeUse a valid common Bake range on all deformables.
CNX-E103Unsupported or changing topology during preparationApply topology-changing modifiers or keep evaluated topology constant.
CNX-E104Invalid material, rest-shape, or solver-quality valuesCorrect the highlighted value. Shrink cannot be combined with an enabled non-zero Stretch Limit.
CNX-E105Invalid Pinning or constraint setupCheck Pin Groups, Advanced Pin Motion targets, Soft Constraints, target topology, and overlapping Pin Groups.
CNX-E106Incompatible multi-object settingsGive all deformables a compatible range and supported configuration.
CNX-E107Object disappeared during preparationRestore the named object and do not delete it while Bake is starting.
CNX-E108Invalid Force configurationUse a supported Force on an Empty and verify that its animated values and transform are finite.
CNX-E109Non-finite or malformed geometryRepair NaN/Inf coordinates, degenerate geometry, or invalid transforms.

Companion startup

CodeCauseFirst step
CNX-E110Unclassified Companion startup failureClose stale Bake windows and retry.
CNX-E111Companion bundle missing or failed integrity validationRepair or reinstall the Cloth neXt extension.
CNX-E112Local Companion transport could not startClose stale Bake windows and retry; check local security software.
CNX-E113Companion process launch failedCheck Windows execution permissions, then repair or reinstall the extension.
CNX-E114Companion readiness handshake timed outClose the existing Bake window and retry.
CNX-E115Companion window was not visible or topmostRestore normal desktop/window access and retry.
CNX-E116Companion authentication or protocol mismatchClose all Bake windows and reinstall the matching extension build.

Bake preparation

CodeCauseFirst step
CNX-E120Unclassified preparation or export failureCheck evaluated geometry and the cache folder, then retry.
CNX-E121Cache/work directory is missing or not writableChoose a writable cache location and check free disk space.
CNX-E122Evaluated geometry export failedCheck modifiers, transforms, and evaluated object geometry.
CNX-E123Simulation scene or parameter encoding failedCheck geometry, materials, Pins, Constraints, Forces, and finite numeric values.
CNX-E124Animated Pin target capture failedCheck each animated Pin target, keep evaluated topology stable, and keep target objects available throughout the Bake range.
CNX-E125Insufficient disk spaceFree disk space or move the cache to a larger writable volume.
CNX-E126Bake worker could not startRetry after other heavy jobs finish; restart Blender if thread creation keeps failing.
CNX-E127Interrupted or stale partial Bake stateClear the partial result or Rebake; the last complete cache remains safe.
CNX-E128Animated Collider capture failedKeep the Collider's evaluated topology stable and check the reported frame, transform, and active simulation proxy.
CNX-E129Recovery checkpoint is missing, corrupt, or incompatibleChoose a compatible verified checkpoint, or use Start Fresh after preserving needed files.

Solver startup

CodeCauseFirst step
CNX-E130Unclassified solver startup failureRun the solver health check, then repair the selected managed installation or choose another compatible solver.
CNX-E131Solver executable, native worker, or runtime dependency missingRestore or repair the verified solver; if security software quarantined it, allow the solver folder.
CNX-E132Solver protocol, schema, or package is incompatibleInstall the solver version required by this Cloth neXt release.
CNX-E133Solver health or readiness check failedRepair the managed solver and inspect its startup diagnostics.
CNX-E134Solver process exited during startupInspect the solver stderr tail; update GPU drivers or repair dependencies.
CNX-E135Solver execution permission deniedAllow the signed solver executable and retry.
CNX-E136Configured local solver port is occupied by another serviceClose the conflicting service or choose another port; Cloth neXt will not stop foreign processes.

Scene upload

CodeCauseFirst step
CNX-E140Unclassified scene upload failureCheck the local solver connection and retry.
CNX-E141Solver connection or response timed outRetry and check whether security software blocks localhost traffic.
CNX-E142Solver connection closed or brokeRetry after the solver health check succeeds.
CNX-E143Solver rejected or did not acknowledge uploadInspect the diagnostic log and verify the matching solver version.
CNX-E144Uploaded payload hash or identity mismatchRepair the solver installation and retry with a fresh Bake.
CNX-E145Malformed or oversized solver responseRepair or update the solver to the supported protocol version.

Solver connection

CodeCauseFirst step
CNX-E146solver control server exited while an owned solver descendant remained activeKeep the diagnostic log and retry after Cloth neXt confirms owned-process cleanup.

Water Flow

CodeCauseFirst step
CNX-E147Water Flow grid or sequence exceeds its memory budgetCheck the reported grid and memory estimate. Shorten the Bake duration or choose a smaller field. Preparing a .gaia cache alone is frame-wise.

Project build

CodeCauseFirst step
CNX-E150Unclassified solver project build failureInspect scene geometry and the solver diagnostic log.
CNX-E151Solver rejected project buildInspect geometry, materials, Pins, Constraints, Friction Regions, and Forces in the diagnostic log.
CNX-E152Project build timed outSimplify the scene or increase stability/performance headroom, then retry.
CNX-E153Contact or geometry initialization failedRepair intersections, degenerate faces, and invalid collision geometry.
CNX-E154Solver project was unexpectedly busyWait for the owned solver to stop, then retry.

Simulation

CodeCauseFirst step
CNX-E160Unclassified simulation failureInspect the failing frame and solver diagnostic log.
CNX-E161Constraint solver did not convergeLower Friction first. If it still fails, reduce Pressure and Collision Gap, increase animated Collider sampling, then try a smaller Time Step.
CNX-E162Intersection blocked the simulation from advancingUse Intersection Diagnostics and Auto Fix Intersections for mapped initial self-intersections. Otherwise separate the geometry; for inflation or self-contact, lower Pressure, add clearance, or use a smaller Time Step.
CNX-E163Simulation stalled or timed outInspect the last frame, reduce scene complexity, and retry.
CNX-E164Solver process crashed or exitedInspect the solver stderr tail for the underlying cause (intersection, non-finite, or convergence) before checking GPU/driver stability.
CNX-E165Non-finite simulation resultReduce Time Step and extreme Force, material, constraint, or Motion Override values; repair invalid input geometry.
CNX-E166RAM safety limit or solver memory exhaustionLower scene complexity; raise the Auto-Cancel on High RAM threshold only when sufficient system memory is available.
CNX-E167Solver completed without every requested frameKeep the diagnostic log and retry after a solver health check.
CNX-E168Force or parameter instabilityReduce animated Force magnitude and extreme material parameters.
CNX-E169Unexpected solver stateStop other solver work, run the solver health check, and start a fresh Bake.

Result transfer

CodeCauseFirst step
CNX-E170Unclassified result transfer failureCheck disk space and the local solver connection.
CNX-E171Result transfer timed outCheck disk performance and localhost security software, then retry.
CNX-E172Connection broke during result transferRetry after a successful solver health check.
CNX-E173Invalid or missing solver output mapKeep the diagnostic log and repair/update the solver.
CNX-E174Requested result frame is missingRetry; report the diagnostic log if the same frame is missing again.
CNX-E175Result frame is corrupt or cannot be decodedCheck disk integrity and repair/update the solver.
CNX-E176Result size or vertex count mismatchRestore the original topology and Rebake.

Playback cache

CodeCauseFirst step
CNX-E180Unclassified playback-cache failureCheck cache access and target topology.
CNX-E181Playback cache could not be writtenChoose a writable cache folder with sufficient free space.
CNX-E182PC2 finalization failedCheck disk space and filesystem reliability, then Rebake.
CNX-E183Object topology changed before importRestore the topology used when the Bake began and Rebake.
CNX-E184Target object no longer existsRestore the target object and Rebake.
CNX-E185Playback attachment failedRemove conflicting cache modifiers or animation and retry.
CNX-E186Cache integrity validation failedDo not use the partial cache; Rebake to create a verified result.
CNX-E187Multi-object cache set is incomplete or inconsistentKeep every target object unchanged and Rebake the full set.
CNX-E188Cable / Rope Curve playback could not be appliedRestore the original Cable / Rope Curve topology and remove conflicting Curve animation.

Cleanup

CodeCauseFirst step
CNX-E190Unclassified cancellation cleanup failureWait for cleanup; restart Blender only if the owned process remains stuck.
CNX-E191Cancellation did not complete in timeWait briefly, then restart Blender if the owned solver remains active.
CNX-E192Owned solver process could not be stoppedClose Blender after preserving diagnostics, then retry.
CNX-E193Temporary or partial files could not be removedClose programs using the cache folder and clear the partial result.

Internal

CodeCauseFirst step
CNX-E198Bake worker stopped without a terminal resultPreserve diagnostics and restart Blender before retrying.
CNX-E199Unexpected internal failurePreserve the diagnostic log and report the code and full Blender error.