Solver warnings
The solver reports when it had to clamp or drop something that would otherwise be invisible. Warnings appear in red in the main panel, and each kind is logged once per run. The Blaze Solver node shows them until the next run, with a Fix button where a setting can cure them.
| Warning | Meaning | Fix |
|---|---|---|
| gas bricks over the GPU pool | More 8³ bricks hold gas than the GPU pool can store. | Raise the Voxel Size (the Fix button multiplies it by 1.25), raise the Activity Threshold, or free GPU memory. |
| Live budget exceeded | A live frame takes longer than its time budget. | A larger Voxel Size gives about half the cells and a faster live frame. |
| timestep clamped by CFL | Live caps the substeps at 8 and the gas moved too far. A bake allows 32. | Lower Time Scale (Fix: times 0.75), or bake. |
| cells clipped by the density / fuel safety clamp | Smoke or fuel piled up past the limit. | Lower the emitter’s Smoke rate (Fix: times 0.7). |
| smoke left behind by the moving domain | With Move With Object, the box left gas behind. | Enlarge the domain box around the source (Fix: times 1.25). |
| non-finite gas cells reset | The solver hit NaN or infinite values and reset those cells. | Lower Time Scale (Fix: times 0.75). |
| force fields dropped | Too many force nodes. | Remove some, or join them. |
| colliders ignored by this engine | A collider is unsupported, has no geometry, or is over the limit. | Blaze takes sphere, box and mesh colliders with geometry. |
| collider points / triangles dropped | A collider mesh is too dense. | Decimate the collider meshes. |
| emitters dropped | Over the limit, or too large to voxelize. | Use fewer emitters or a smaller emitter volume. |
| emitter points dropped | A point source has too many points. | Use fewer points. |
| explosions dropped, curve forces dropped | Over the limit. | Use fewer explosion or curve force nodes. |
Particle solvers
Section titled “Particle solvers”| Warning | Meaning |
|---|---|
| NaN particles removed | The solver produced invalid particles and removed them. Lower the time scale or add substeps. |
| collider points dropped (buffer full) | A collider mesh sampled too many points. Simplify it. |
| contacts dropped (buffer full) | More contacts than the solver can store. |
| N of M requested particles | The solver runs a different particle count than you requested, for example because of a capacity limit or a stream. |
Impact
Section titled “Impact”| Warning | Meaning |
|---|---|
| particles not loaded | Over the solver capacity. |
| shards not loaded | Over the solver capacity. Use fewer chunks. |
| glue bonds not created | Over the solver capacity. |
| shard contact pairs dropped | The contact pair list is full. |
| stress-wave impact events dropped | Over the per-substep limit. |
| shard shatters skipped | The queue or shard capacity is full. |
Wrangles
Section titled “Wrangles”Wrangle ‘name’ is left out of the simulation: reason. The code of a wrangle failed to compile or is not valid for this solver. The reason says why, and the other wrangles and the simulation carry on. See Wrangles.
Other limits
Section titled “Other limits”For the Blaze Solver node, a warning without a fix button names its remedy in the message. See also Out of GPU memory.