This document surveys where MPM appears in products and game-adjacent work, as distinct from explaining the algorithm itself. It asks:
- Which industries and tools use MPM?
- Which games, middleware products, playable sandboxes and prototypes have a documented connection to it?
- What methods do games commonly use instead, and why?
The entries are organized by type of use and strength of evidence. Dates provide a useful chronology, but being earliest is not treated as a measure of technical importance.
MPM is well-established in offline film visual effects (VFX) and engineering simulation, increasingly seen in real-time tech demos and research, and present in games through fluid middleware, sandbox projects, playable demonstrations and prototypes. The amount of public technical detail varies sharply among those uses, so the survey distinguishes confirmed methods from product statements and visual evidence.
1. Adoption landscape
MPM is production-proven, with adoption strongest in film and engineering and narrower roles in games. The landscape breaks into five areas, ordered by how battle-tested each is. Commercial DCC adoption dates from Houdini 20.5 in July 2024:
- Offline film VFX — the most mature use. MPM’s graphics debut was Disney’s 2013 snow paper, and its in-house engine Matterhorn powered the snow in Frozen and is integrated into the production pipeline for Big Hero 6 and Zootopia (stated in the SIGGRAPH 2016 course abstract). This is offline, render-farm simulation — minutes-to-hours per frame — not real-time.
- Engineering simulation — mature, decades deep. MPM’s original home (Sulsky et al. 1994) is computational mechanics: geotechnical engineering (landslides, slope stability, soil–structure interaction), high-velocity impact, and granular/large-strain problems. Commercial and open-source engineering solvers exist (CB-Geo MPM, Anura3D). Again: accuracy-first, not real-time.
- Commercial DCC tooling — new since 2024, and it moves the baseline. SideFX Houdini 20.5 (July 2024) ships a GPU-accelerated MPM solver as a stock feature — written in OpenCL, presented to artists as the FLIP solver extended to solid mechanics, with snow, mud, soil, concrete, metal, jello, rubber, honey and sand presets, multi-material interaction, and rigid coupling. It is offline VFX, not real-time. But it means MPM is no longer “a method a studio implements”: it is a checkbox in the tool most VFX shops already own. cebas thinkingParticles exposes MPM as artist-facing operators too. So MPM is no longer exotic in commercial software, even though it remains rare in games — the two statements are about different products. Links in References §3.
- Research & tech demos — active, real-time emerging. Graphics research keeps extending MPM (CD-MPM dynamic fracture, AnisoMPM, CRESSim-MPM for surgical soft-body). Real-time MPM tech demos in Unity and WebGPU are now common — but a demo is not a shipped product.
- Commercial games and middleware — small and heterogeneous. Zibra Liquids puts confirmed MLS-MPM into an undisclosed number of shipped games as fluid middleware. Space Simulation Toolkit has a developer-confirmed MPM demonstration tied to its commercial sandbox, while Liquid Crystal and several Zibra-based projects provide playable or prototype examples. See §2 for their differing evidence boundaries.
2. Commercial games, middleware and prototypes
The public record includes commercial middleware used in shipped games, products with an MPM demonstration or subsystem, playable sandbox projects, research prototypes, and patents. These are different kinds of adoption, so the entries below state both the source class and the scope that the source actually establishes.
Selected timeline
The dates mark public demonstrations, releases or disclosures; they do not rank the work or imply that every implementation remained unchanged afterward.
| Date | Work | What the public record establishes |
|---|---|---|
| 2020 | Space Simulation Toolkit | A developer-confirmed MPM demonstration tied to a paid 2D sandbox; the released and current solver scope is undocumented. |
| ~2021–2022 onward | Zibra Liquids | Commercial MLS-MPM fluid middleware used in an undisclosed number of shipped Unity and Unreal games. |
| 2023 | Echoes of Somewhere demo and AR sculpting experiments | A public game demo built around Zibra-driven liquid control, plus hand-tracked liquid-sculpting interaction studies. |
| 2024 | Liquid Crystal, Hydrolab and PB-MPM | Playable all-continuum sandbox builds, an AR/VR liquid-puzzle prototype, and EA SEED’s BSD-licensed real-time research solver. |
Nearby methods often confused with MPM
A granular or fluid appearance does not identify the underlying solver. These examples use other methods or have no supporting MPM evidence:
| Game | What it actually uses |
|---|---|
| Noita | Custom cellular-automata engine (“Falling Everything”) |
| Teardown | Voxel-based physics |
| Falling-sand sandboxes (e.g. The Powder Toy, Sandspiel) | Cellular automata |
| Fluidity (2010) and similar water-puzzle games | Other methods; predate the relevant MPM graphics work |
| Black Myth: Wukong (2024), whose sand and snow clips are widely shared | Unreal Engine 5 Chaos / Niagara. No MPM claim from the developer or supporting technical evidence. Listed because “the sand physics are wild” clips circulate widely |
No public MPM method claim accompanies NetEase’s Where Winds Meet or Naraka: Bladepoint, and the GDC vault carries no production MPM talk for either title.
The shared lesson is that granular or fluid appearance does not identify an MPM method. Cellular automata, voxels and engine-native effects can produce similar imagery at much lower cost.
Documented uses and projects
The cases below cover standalone products, middleware, applications built on middleware, experiments, and corporate research activity.
Evidence-class rule. Each case below identifies the kind of source supporting it. A storefront or promotional video proves what was marketed and when; a developer statement proves what that developer said; a technical manual can establish exposed controls; a patent establishes claims and ownership; and none silently substitutes for source code, an independent benchmark, or a solver-boundary diagram.
Source class: mixed — commercial storefront and first-party marketing/demo, developer statement, and community documentation. Space Simulation Toolkit (Pavel Kudinov) — a proprietary 2D GPU particle sandbox released commercially through Steam Early Access on 5 June 2020. Three facts have to be kept together:
- First-party product demo and developer statement, March 2020. A product post links the official four-minute demonstration; when asked “MPM?”, the developer answers “yes.” The video description links the same Steam application, so this is not an unrelated experiment.
- Commercial storefront and current marketing record. The product did ship commercially, remains on sale, and receives updates. The directly tied MPM demonstration establishes product-level MPM evidence while leaving the demonstrated solver’s release lineage unresolved.
- Later first-party promotion plus community technical documentation. The solver boundary is nevertheless unresolved. The current store description says only “particle simulator” and describes atoms joined by links; a later developer promotion calls the physics SPH; and the community material reference exposes direct node-repulsion, attraction and link-spring parameters rather than an MPM grid or constitutive model. There is no source release, solver paper, launch-build method inventory or current MPM claim.
Evidence summary: commercial-product MPM evidence, released implementation scope unverified. It does not prove that the launch or current build runs its whole world on MPM. The available sources do not identify which released mode used the demonstrated solver or whether that mode still exists.
Source class: first-party project pages, runnable demos, and author technical disclosures; no independent validation. Liquid Crystal (Grant Kot / kotsoft) — an in-development indie MPM sandbox game with publicly playable pre-alpha demos, built on Kot’s own MLS-MPM-lineage engine. It is not commercially shipped, its internals are unpublished, and the player character appears kinematic — but it is an announced, playable MPM-native game project.
- The design is all-continuum, not an effects layer. Per the author, “everything is simulated with particles,” including rigid-reading structures that fracture and shatter; the stated design is “a physics sandbox built around a unified particle-based physics model. Every material is configured from the same set of parameters.”
- What ships. A Temples level demo and a Materials sandbox, as DirectX 12 / Windows builds using mesh shaders for particle rendering and up to four split-screen views, in 0.5M- and 1M-particle variants with separate SSE2 and AVX2 CPU builds. Public performance reports span ~30 fps on an RTX 2070 SUPER down to single digits on weaker machines, so it is a demo rather than a tuned product.
- The configuration, from the author. Explicit time integration at a single step per frame, a 512×512×128 grid, particle resolution adaptive with about eight per cell at the surface, and per-material feature toggles so a liquid does not pay to track a deformation gradient it never reads. The physics runs on the CPU across all cores, leaving the GPU free for ray tracing — the exact inverse of the GPU-resident assumption most MPM literature makes. Three of those are work-elimination rather than throughput tuning, and they are what lets the domain reach that size at all.
- It has hit the multi-field problem. Kot has publicly described needing “to put solids on a separate velocity field from liquids so the particle velocities don’t blend together” — the same single-velocity-field limitation that multimaterial contact MPM (Theory §5) exists to solve.
- His two decades of MPM work, the port tree it seeded, and the part
of his catalog that is not MPM are in References §3. Demos: Liquid Crystal
Demo 2024 · Temples · Materials
· the web MPM demo
(
lc1)
Source class: vendor technical blog and product marketing. Zibra Liquids (ZibraAI) — commercial Unity/Unreal middleware for real-time fluids built on MLS-MPM (atomics + radix-sort P2G), shipping in games since ~2021–22. The method is confirmed by the vendor: Zibra’s Approaches to real-time fluid simulation in visual effects names MLS-MPM as the method “from which our tool, Zibra Liquid, was born,” and describes its APIC basis. Because it is an off-the-shelf asset, every title shipping Zibra Liquid ships MLS-MPM — so MPM in games is not one product but an unknown-sized tail of them, with no public customer list. It is a liquids effects layer rather than core physics. zibra.ai
Source class: first-party product page plus vendor case-study marketing. Echoes of Somewhere (Jussi-Petteri Kemppainen) — a 2.5D point-and-click adventure whose first episode’s story is about water, using Zibra Liquid — and therefore MLS-MPM — to build game mechanics based on liquid control rather than an effects layer. A free demo was published on itch.io in December 2023; the Steam page for Series 1 reads “Coming soon”, so a playable public build exists and the full game does not. site · Zibra case study
Source class: first-party engineering write-up and social-media demonstrations/comments. AR liquid-sculpting prototypes (Lee Vermeulen, 2023) — experiments preceding Hydrolab used Zibra Liquid with tracked hands, but they are instructive counterexamples to a physical clay interaction. Vermeulen's first-party write-up says the frozen-sculpt version removed material touched by the hand SDF and a later zero-gravity version reduced every particle's velocity by five percent each rendered frame. In the spinning-wheel experiment, he explains that the entire AR camera rig rotated rather than the simulated material. These are useful interaction prototypes, not validation of a clay constitutive model, mass-conserving sculpting, or physical rotation.
Source class: vendor case-study marketing corroborated by creator statements. Hydrolab (Lee Vermeulen, co-founder of Alientrap Games) — an AR/VR liquid-puzzle game on Zibra Liquid where the puzzles are the liquid. It was a 2024 prototype and was abandoned in favor of voxel projects, so it never shipped. Zibra case study
Source class: patent/legal records plus public corporate disclosure. Tencent — holds two MPM patents through Tencent America LLC, both naming authors it employed at its Game AI Research Center:
US11966999B2, Real-time simulation using material point method on GPUs, whose independent claims all require multiple GPUs; andUS11373353B1, the counterpart of ASFLIP (Fei et al. 2021). Both are rows in Patents §3. Its disclosed shipped work is AI systems (QQ Speed Mobile, PUBG Mobile) rather than MPM, and Chinese-language sources are thinly covered in English indexes, so a Tencent MPM shipment can be neither confirmed nor ruled out from the public record.
3. Evidence limits and terminology
The survey covers what is publicly documented, which is not the same as everything that exists. Three limits govern how its entries should be read:
- Studios rarely publish solver internals. A small or mid-sized studio could have shipped MPM-based effects without documenting or marketing the method, and nothing in the public record would show it.
- A product-level MPM statement is not a solver-boundary diagram. Space Simulation Toolkit is a real commercial-product connection, but the available sources do not say whether one mode, every material, the launch build, or the current build uses MPM. “Core physics” and “an MPM mode” are different claims.
- Deployment scope matters. A localized MPM effect, a fluid-middleware subsystem, and a world built around one multi-material solve are all uses of MPM, but they have different engineering costs and product roles. The survey identifies the scope instead of ranking one as the more important use.
4. Why game use remains selective
MPM appears in narrower game roles than in film, engineering and DCC tools. Several structural reasons explain that distribution:
- There is no general-purpose off-the-shelf MPM tool. Unlike rigid-body physics (PhysX, Havok, Box2D), MPM has no drop-in general engine middleware — the one commercial offering (Zibra Liquids, §2) is fluids-only, an effects layer. A studio wanting MPM as core physics must build the solver itself.
- Unity does not ship MPM. Unity’s built-in physics is rigid-body (PhysX in 3D, Box2D in 2D). Any MPM in Unity is custom code a developer writes on top of the engine — there is no “Unity offers MPM but nobody uses it” paradox; the engine never offered it. (Same for Unreal, Godot, etc.)
- The real-time barrier is real. A studio building its own solver inherits MPM’s limitations (see Theory §7): the small-timestep stability limit (the Courant–Friedrichs–Lewy, or CFL, condition), high memory cost, and the particle-to-grid (P2G) scatter parallelization bottleneck. Hitting interactive frame rates on consumer hardware was, until recently, very hard.
- The risk/reward hasn’t favored it. Cellular automata and voxels deliver “destructible/granular” feel at a fraction of the cost and complexity, so the commercial incentive to take on MPM’s R&D burden has been weak.
- GPU residency moves the systems burden; it does not remove it. The developer of the in-development voxel sandbox BFS says its physics and gameplay run on the GPU and describes an input-only deterministic multiplayer design: the server orders and rebroadcasts inputs, every client simulates the world, and frame hashes detect divergence. The disclosed envelope is eight players, no late join, no rollback or prediction, and an expectation that a lagging peer would have to be removed. That is a useful adjacent architecture, but the reveal does not name MPM, publish the simulation method, or establish bit-exact behavior across GPU families. It demonstrates the product bargain rather than a general solution: eliminating bulk state replication transfers risk to determinism, resynchronization, latency policy and hardware support. Its later terrain-editor disclosure adds the other side of the GPU-first bargain: a 2048×2048×1024 global voxel domain and whole-world recomputation after edits, alongside memory pressure and temporal antialiasing ghosting because regenerated voxels lack motion vectors. The first-party reveal and comment links are cataloged in References §3.
4.1 What ships instead — the incumbent water & snow stack
The last bullet deserves specifics, because “what a studio would use instead” is the actual competition, and it is very good and very cheap. Two techniques own the water and snow space, and neither is a continuum solver; a third, a 2D grid fluid built for smoke and fire, is routinely stretched to cover water and mud as well:
Water → 2D shallow-water height fields. Not cellular automata — a real physics solver, just a 2.5D one (full method in Related Methods §1.5). The reference implementation is Chentanez & Müller’s Real-time Simulation of Large Bodies of Water with Small Scale Details (SCA 2010): shallow water equations on a height field, with particles spawned where the height field cannot cope (breaking waves, waterfalls, splashes) and reabsorbed on landing. The cost is startling — complete scenes at ~4–18 ms/frame on a 2010-era GTX 480.
That paper is not merely academic: Fluid Flux (Imaginary Blend / Krystian Komisarek), a commercial Unreal Engine water system released April 2022, is a direct implementation of it — the developer said so explicitly when asked, linking the paper. Its shipped envelope is a useful benchmark for what “good enough water” costs today:
| Fluid Flux (UE4.26–UE5.5+) | |
|---|---|
| Method | 2D SWE height field + Niagara particles |
| Simulation cost | ~0.5–0.7 ms/frame (dev’s figure, RTX 2060 @ 120 fps) |
| Max sim resolution | 1024×1024, ~1 m/pixel → ~1 km² (coastline 2048², ~20 km²) |
| Features | Wet–dry shorelines, waterfalls, advected foam, caustics, wetness, underwater, buoyancy/boats, wave breaks, ocean blending |
| Hard limits | Heightfield projection only — no caves, no planets; domains can’t move or rotate at runtime; console builds lose precision to 16-bit floats |
| Effort | Developer states 15 months to first release, 3+ years R&D total |
It is also externally validated as physics, not just as an effect: a 2025 peer-reviewed digital twin of a river-experiment facility used Fluid Flux as its solver and compared the results against a real-scale flow experiment. A game engine’s water plugin standing up to hydraulic-engineering scrutiny is a fair measure of how mature this incumbent is.
Smoke, fire and fog → a 2D Eulerian grid, stretched to cover water. The other widely licensed real-time fluid for the same engine is FluidNinja LIVE (Andras Ketzer; first listed in December 2020, rebuilt as LIVE-2 for UE 5.6 and later in September 2026). Its own manual settles the method question: it is a grid Navier–Stokes solver — density and velocity advected through a fixed 2D grid, with pressure and divergence buffers, run as GPU simulation stages — and one model serves gases and liquids alike. It is not MPM and not a particle method: particles enter only as interaction sources and leave only as decoration pushed by the grid’s velocity. Three design choices define the product:
One 2D sheet, drawn as 3D. The simulation is a single plane, either turned toward the camera (flames, smoke, explosions) or laid along the terrain (water, low fog). Depth is the renderer’s job: volumes extruded from the density buffer, pressure displacing a water mesh, parallax and 2D ray marching. A finite simulated patch follows the player, and everything beyond it is a passive animated pattern.
Approximation over convergence. According to the parameter reference, pressure is not solved to convergence each frame: it is a weighted average over fixed convolution kernels (5–15 texels) accumulated through a feedback loop across frames, with a cruder option for low-end hardware. The simulation advances one cycle per rendered frame with no substeps; its speed control widens the neighbor-sampling distance instead, which the documentation itself calls a faux method.
Liquids, mud and sand are exploits or paint. Free-flowing water is the same model overdriven: density accumulates past saturation, is thresholded into wet and dry, and is pushed downhill by a velocity taken from the terrain gradient, with corrections that keep it from creeping up rims. The documented limits follow from that — only a layer about a meter deep accumulates, so pools and rooms cannot fill to depth; a filled hollow can leak and act as a source; there is no buoyancy. Viscous mud and blood come from misusing the fluid parameters rather than from a viscosity model, and sand and snow footprints use a painter mode that skips the fluid solve entirely — the displacement-mask technique described below.
What that buys is cost. The vendor reports 0.2 ms per frame for a 512×512 smoke grid and 1.2 ms for a 2048×2048 creek on an RTX 3080, with rendering (2–3 ms) rather than simulation dominating the frame. The manual also lists more than a dozen commercial releases said to use it, while noting that most such usage is under non-disclosure and is inferred from screenshots. Measured against MPM, it makes the height field’s trade more sharply still: a 2D field carries no material identity, no conserved volume and no constitutive response, so the sand, mud and snow on its feature list are appearances rather than granular or viscoplastic behavior — and for a smoke plume or a footprint trail, that is exactly the right engineering choice.
Layered simulation is the shipped pattern. An indie voxel engine handling oceans will typically run a bulk voxel fluid sim for the water body, wave and tide motion applied as oscillating “target height” masks, a connectivity flag marking which water is joined to the ocean (so rock pools disconnect as the tide drops and keep their water), and a separate, higher-resolution, surface-only 2D ripple simulation running near the player for wakes and interaction. Nobody runs one solver at one resolution — the budget goes where the camera is. That is the same demote/promote logic the height-field papers use, arrived at independently.
BFS makes the same representation split explicit for snow: a thin height-map layer for broad coverage, VFX snow squares for weather, and physical particles for interaction. The developer identifies the physical path as modified PBD, not MPM, and describes a future transition in which frozen particles align to and become cellular-automata voxels. The conversion remains a plan rather than a published result, but the three-level presentation is already useful product evidence: persistent cover, airborne weather and interactive bulk snow do not have to share one representation.
Snow, sand and mud → displacement textures + parallax occlusion mapping. Deformable ground in shipped games is overwhelmingly not simulated at all (full method in Related Methods §2.3): a mask written by simple analytic primitives at the feet, a diffusion pass to soften it, and a parallax shader that marches the view ray through a height texture so the surface reads as displaced without any geometry. Indie implementations of exactly this run comfortably in real time on laptop hardware, and are genuinely convincing to look at.
The critique of them is the more useful artifact, because it is a public catalog of where the illusion breaks, written by players rather than researchers: no compaction (a repeatedly-walked path never packs down into a faster route), no cohesion (the thin pillar of undisturbed snow that survives between a walker’s legs cannot exist), no conserved volume (displaced material doesn’t have to go anywhere), no bulk failure (no post-holing, no collapse), and — most tellingly — deep examples read as sand, flour, or mud rather than snow, with repeated objection to bodies moving through waist-deep material unimpeded.
Where the two approaches actually differ. For shallow decorative deformation or a plain river, the incumbents look excellent at a fraction of the cost, and remain the sensible engineering choice. What they do not produce is the list above: compaction, cohesion, conserved volume, bulk failure, depth-correct resistance, material mixing, and phase change. Those are consequences of a constitutive model rather than features that can be bolted onto a height field or a displacement texture, so refining the incumbent stack does not converge on them. The trade is straightforward: MPM produces those behaviors and costs considerably more per frame.
5. Real-time enablers
Three developments expand the range of MPM workloads that can run interactively (all detailed in Theory and Implementation):
- MLS-MPM (Moving Least Squares MPM, 2018) makes each step ~2× cheaper and drops the shape-function gradient — modern real-time work starts here.
- PB-MPM (position-based MPM, 2024), from EA’s research lab SEED, makes MPM stable at any timestep, explicitly framed for “real-time applications where the hardest requirement is stability under autonomous, potentially violent player input” — i.e. a game.
- GPU optimization (fixed-point atomics, sparse grids, spatial sorting) brings the particle counts and frame rates into interactive range.
These techniques support several product shapes: specialized middleware, localized effects, interactive sandboxes, and unified multi-material simulations. The appropriate scope depends on platform, particle count, material model and frame budget. A permissive reference license governs copying that source and nothing more — the underlying techniques carry their own patents, which is a separate question with its own document (Patents).
The frontier keeps moving (2024–2026): XPBI (SIGGRAPH Asia 2024 — real-time continuum inelasticity in a PBD pipeline), CK-MPM (SIGGRAPH 2025 — compact-kernel performance), convex MPM↔︎rigid coupling pushed to interactive rates on GPU (Zong et al. 2024; Yu et al. 2025, the Drake/robotics line), and PB-MPM derivatives (e.g. an affine-projection stabilizer, The Visual Computer 2025). Most remain research or demonstrations, while commercial use is concentrated in the narrower roles cataloged above. Full citations in References.
6. EA SEED and PB-MPM
SEED (Search for Extraordinary Experiences Division) is EA’s internal applied-research lab, and the group that published PB-MPM:
- Launched at E3 2017; sits inside EA Worldwide Studios (offices in Stockholm and Los Angeles); led by Colin Barré-Brisebois.
- SEED does not ship games itself — it turns experimental ideas into techniques used across EA titles, and publishes openly so others can build on the work.
- That open-publication model is why PB-MPM is public, demo-only and BSD-licensed rather than an internal technique.
- Its other work gives the measure of the lab: Project PICA PICA (real-time ray tracing), Swish (neural-network cloth simulation in Madden NFL 21), Voice2Face (audio-driven facial animation), reinforcement-learning goalkeepers in EA SPORTS FC 26, collusion detection in team-based multiplayer, and Vaporwave, a scalable real-time smoke solver. The full list is on SEED’s publications page.
Sources for this document
- Games context: assembled from general web search, GDC/SIGGRAPH talk records, Steam, devlog channels, vendor case studies and the EA SEED repository.
- Space Simulation Toolkit: Steam product and Early Access record · March 2020 developer post and MPM confirmation · linked official video · later developer SPH description · community material-parameter reference. The last source documents the visible product interface, not the underlying solver; together the sources establish a product connection while leaving implementation scope unresolved.
- Shipped-destruction context (how games actually do it — falling-sand, voxel, heightfield baking): Purho, Exploring the Tech and Design of Noita, GDC 2019 — gdcvault.com/play/1025695; Brown, How Games Do Destruction, GMTK, 2025 — gmtk.substack.com; From Dust (2011) as the shipped sim-material→static-terrain precedent (lava hardening into walkable terrain).
- BFS adjacent GPU architecture: June 2026 developer reveal · input-relay lockstep description · eight-player and late-join boundary · rollback/prediction status · engine-shell description · GPU terrain editor · layered snow system and modified-PBD method boundary. All technical details are developer statements, not an independently evaluated implementation disclosure.
- §4.1 incumbent stack: Chentanez, N. & Müller, M. Real-time Simulation of Large Bodies of Water with Small Scale Details, SCA 2010 — PDF (source of the method and the GTX 480 timings). Fluid Flux — product page & documentation (feature set, resolution/coverage limits, GPU benchmarks, engine support), demo build; the developer’s attribution of the algorithm to the 2010 paper and the ~0.5–0.7 ms / RTX 2060 figure are the developer’s own, stated at the 2022 reveal. External validation: A Digital Twin of River Experiment Infrastructure Based on a 3D Game Engine and Validation of Water Flow with a Real-Scale Experiment, Applied Sciences 15(23):12507, 2025 (flow reproduction validated at the Andong River Experiment Center) — mdpi.com/2076-3417/15/23/12507 · DOI: 10.3390/app152312507. FluidNinja LIVE — storefront listing (publication date, engine range, license tiers), the LIVE-2 manual (method, data pipeline, renderers, performance figures, water and buoyancy limits, shipped-title list) and parameter reference (pressure kernels and feedback, frame-locked stepping, the water-model note), and CG Channel’s LIVE-2 release report. Every method and performance statement is the vendor’s own; none has been independently benchmarked. The displacement-snow technique notes (mask primitives, diffusion, normal smoothing, POM) and the list of what players say it cannot do are drawn from indie devlogs and their reaction threads rather than from published work.
- Disney production use: SIGGRAPH 2016 MPM course notes (abstract names Frozen, Big Hero 6, Zootopia) — PDF; Stomakhin et al. 2013 snow paper — Disney Research.
- EA SEED / PB-MPM: github.com/electronicarts/pbmpm · SEED · SEED 10-year anniversary.
- Real-time enablers (MLS-MPM, PB-MPM, GPU): see Theory and Implementation; full citations in References.
- Engineering MPM solvers: CB-Geo mpm, Anura3D.