KawaiiPhysics: one AnimGraph node and no physics engine
KawaiiPhysics : Simple Bone Physics for UnrealEngine 4 & 5
At a glance
- What is it?
- An Unreal Engine plugin that makes hair, skirts, and other bones sway from animation and movement, using a deliberately simple simulation rather than the engine's physics. The design constraints it advertises, fixed bone lengths and viewport-editable colliders, explain most of its behaviour.
- Who is it for?
- This plugin suits an Unreal project that needs secondary motion on cloth and hair and does not want to pay the cost or the unpredictability of the full physics solver for it. Two things to check before you commit.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- pafuhana1213/KawaiiPhysics3,413 ★ · +99
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| pafuhana1213/KawaiiPhysics | 3.3k | 3.4k |
99 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Pseudo-physics on purpose, with no engine underneath
The plugin describes itself as pseudo-physics rather than physics, and the feature list makes the trade explicit. It uses a simple algorithm with no dependency on the engine's physics system, and the stated reason is that it stays light at runtime. Two properties follow from choosing your own small simulation. Forces are yours to compose, so wind and gravity are joined by custom forces that exist purely for artistic effect. And the failure modes are contained, because bone lengths are kept fixed, so bones never stretch or collapse even when the simulation breaks down. That second guarantee is the one that matters for hair and skirts: a solver that explodes usually produces stretching, and stretching on a skirt is the artefact players notice first. The bones are driven from the character's animation and movement, which is why the result follows a running animation without any extra authoring.
One node in the animation graph is the whole integration
The integration cost is stated as a single sentence: drop one node into the animation graph and you are set. There is no component to place, no collision setup ritual, and no per-bone configuration, because everything is a parameter on that node. Where those parameters are documented matters, and the answer is the project's documentation portal rather than the readme, with a page per parameter set. Two escape hatches exist for anything the node cannot express: parameters and external forces can be driven at runtime from either Blueprint or C++, so a project can animate the wind rather than hard-coding it. Recent additions are not in the feature list at all but in a changelog hosted on the same portal, which is a reasonable arrangement for a plugin that ships new capabilities between releases.
Colliders are spheres, capsules, and planes, edited in the viewport
Collision handling is deliberately narrow, and the three shapes are named: spheres, capsules, and planes. All three are adjustable directly in the viewport, which is the design decision worth noting. Putting collider editing in the editor rather than in a data file means that tuning a skirt against a character's legs is a dragging exercise rather than a data authoring exercise, and that feedback loop is what makes a physics-adjacent tool usable by someone who does not write physics code. Settings are then saved and reused through two asset types, a data asset and a physics asset, so the tuned values travel with the character rather than living in a level. For a project with many similar characters that reuse is the difference between tuning once and tuning per instance.
Two constraints stand in for what a solver would do
The last two named features are the ones that address the classic failure of secondary motion, and they are worth reading together because they operate on opposite sides of the simulation. A bone constraint keeps a defined distance between two bones, and its stated purpose is keeping skirts from clipping through the legs, which is a contact problem that a small custom solver has no way to detect on its own. The sync feature goes the other way: it takes bones that animation already drives, such as legs, and feeds them into the simulation, so cloth reacts to the body rather than passing through it. Between them, they are an admission that a bespoke integrator needs help with contact, supplied from the animation data that already exists. Neither is a general collision response, and both are named as narrow fixes.
Three download channels, and only one tells you about updates
Prebuilt downloads are offered through three channels, and the choice matters more than it looks. They exist for people who do not have a C++ build environment, which is a real constraint for a plugin that compiles native code into the engine. The engine marketplace listing is described as carrying the same content as the release page, so it is a mirror rather than a variant. The third channel is a storefront that runs on a different platform again, and its distinguishing feature is that following the store gets you update notifications. Everything after the download is the same: create a Plugins folder at the root of your project and copy the plugin folder into it. That is the entire installation procedure, and it is worth noting that there is no build step at all for someone who downloads rather than compiles.
Engine support ends at 5.8, and the 4.x line is a fixed tag
Supported engine versions are stated as a range from version 5.3 through 5.8. Support for an older generation is not carried in the current branch: the 4.27 line is pinned to one specific earlier tag, so a project on that engine is choosing a frozen version rather than tracking updates. That arrangement is common for a plugin whose simulation code touches engine internals, and it puts the maintenance burden on whoever needs that combination. The tag naming makes the same point from another angle, since every release is prefixed with its date and a version, so a tag tells you both when it was cut and which minor it belongs to. The current release line is at the version after the one before it, cut in the first half of the year, and the most recent commit to the branch is a few months newer than that release.
Three documentation sources, one of them machine-written
The documentation strategy is unusual enough to describe precisely. There is a portal, which is the official and current location. There is a wiki, explicitly labelled legacy because the latest information has moved to the portal, which is the arrangement you inherit if you follow an older tutorial. And there is a third source described as generated documentation produced by a machine, useful for orientation but not authoritative. Issues and discussions sit alongside them for questions and bug reports. The sample project is unusually thorough for a plugin of this size: it has a main level, plus one level per feature topic, plus a combined level that loads every topic side by side. Inside play mode you move between exhibits and topics with two pairs of keys, open the documentation page for the current exhibit with one, and open the animation blueprint with another, and the same two actions are available as buttons on the signs in the level.
Editorial conclusion
This plugin suits an Unreal project that needs secondary motion on cloth and hair and does not want to pay the cost or the unpredictability of the full physics solver for it. Two things to check before you commit. Confirm your engine version is inside the supported range, since older engine generations live on separate old tags rather than on the current branch. And if your project is Blueprint-only, read the packaging note first, because the documentation warns of an error when packaging such a project and the fix is to convert it.
Frequently asked questions
what is kawaii physics
A pseudo-physics plugin for Unreal Engine that animates things that sway, such as hair and skirts. It drives bones from the character's animation and movement using a simple algorithm with no physics engine dependency, keeps bone lengths fixed so nothing stretches when the simulation breaks, and lets you add wind, gravity, and custom forces.
how to install kawaii physics
If you have no C++ build environment, download the plugin from the release page, an engine marketplace listing with the same content, or a storefront that sends update notifications. Then create a Plugins folder in your project root and copy the KawaiiPhysics folder into it.
how to use kawaii physics
Add the KawaiiPhysics node to the animation graph of your animation blueprint, then set its parameters using the documentation portal. Colliders come in sphere, capsule, and plane shapes and are adjustable in the viewport, settings are saved through data and physics assets, and parameters and forces can be driven at runtime from Blueprint or C++.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pafuhana1213-kawaiiphysics)Star history chart for your README
[](https://hysenlabs.com/projects/pafuhana1213-kawaiiphysics)Was this useful?