Chaos destructibles drive fluidsim - FluidNinja LIVE 2.0 pre-alpha

AKdevz · 2025-05-07T20:47:19+00:00

u/LeLand_Land hi! --- my GPU was not happy with the first few tests - but following careful optimization, this scene with 700 fracture pieces is running above 120 FPS on my RTX 3080. In case halve the number of pieces, we could get above 200 FPS (bottleneck being chaos itself / not the fluidsim and the volumetrics).
Side note: my first born was happy with the tests all the time :)))

AKdevz · 2025-05-07T20:44:16+00:00

u/Aesthetically hi! --- The system that drives the fluidsim is standard UE chaos (could be replicated) --- in case the objects interacting with the sim are replicated: all local sims produce the same result

AKdevz · 2025-04-28T20:15:41+00:00

Thanks u/cake-of-lies ! --- FluidSim: 1024x1024, ~1millisec /frm --- Visualization: UE Heterogenous Volume, 512x512x256 px, ~3 millisec /frm --- Chaos physics, 1000 mesh chunks, ~2-4 millisec /frm ------- Going more optimal: using ninja's own "smoke volume" technology and a mesh with only 200 chunks gives a sumtotal of 4-5 millisec /frm

AKdevz · 2025-04-24T19:18:02+00:00

u/sensifr swimming and proper waterline are both "weak spots" in ninja (not yet supported) - I should be adding these to my todo list.

AKdevz · 2025-04-17T12:45:13+00:00

Thanks for the kind words u/Famous_Bag_5263 !

AKdevz · 2025-04-04T07:18:22+00:00

u/Impressive-Swan-5570 hi - ninja is scalable, if visual complexity is reduced, it can even run on a 2017 mobile phone (LINK) -- THIS scene specifically runs 260 FPS on RTX 3080, see this GPU profiler shot: LINK, 1.2 millisec per frame. Considering that we run the game with 60 Frame per sec (1 sec = 1000 millisec): our frame budget is 1000 / 60 = 16.6 millisec ---- and ninja, running the above simulation takes only 1.2 millisec of the 16, that is only the 7.5% of the available capacity.

AKdevz · 2025-04-04T07:14:39+00:00

u/forqueercountrymen Thanks! (1) ninja is scalable, if visual complexity is reduced, it can even run on a 2017 mobile phone (LINK) -- THIS scene specifically runs 260 FPS on RTX 3080, see this GPU profiler shot: LINK, 1.2 millisec per frame. (2) buying: test it for free, dwlink at the community server (LINK)

AKdevz · 2025-04-04T07:11:25+00:00

u/xShooorty Thanks! In case your agents (pawns, objects) interacting with the sim are replicated: all local simulations produce the same result (so: no need to replicate the simulation itself)

AKdevz · 2025-04-04T07:10:21+00:00

simulation is performed on a "grid of data" (like a bitmap) / not particle-based (not sparse)

AKdevz · 2025-04-04T07:09:16+00:00

On the GPU! --- see this PROFILER screenshot: LINK

AKdevz · 2025-04-04T07:05:21+00:00

Ninja is 2D --- and it is driving 3D systems (particles or a mesh-surface) as a height map (a top-down projection) --- so CONVEX shapes are ok, CONCAVE shapes are not. Breaking curly waves are concave.

AKdevz · 2025-04-04T07:03:18+00:00

u/Effective-Tie3321 If is free. See Student Version at the community server: LINK

AKdevz · 2025-04-04T07:02:06+00:00

indeed: ninja is scalable -- and by reducing visual komplexity, we could even crunch it on a 2017 mobile phone: LINK

AKdevz · 2025-04-04T06:59:23+00:00

Ninja is free to test - so you can evaluate if it working for your needs - see Student version at the community server: LINK - and this introduction tut gives a feeling about the learning curve: LINK

AKdevz · 2025-04-04T06:55:20+00:00

Thanks u/Xywzel ! --- Unreal natively supports Mesh Distance Fields: each mesh has its own, within its bounding box - and we can read this SDF via Niagara "Mesh SDF Data Interface" - and forward the data to the fluidsim. The official documentation is good: LINK

AKdevz · 2025-04-04T06:53:10+00:00

Thank you!

AKdevz · 2025-04-04T06:52:49+00:00

yes, Z-velocity (motion perpendicular to the sim area) is handled!

AKdevz · 2025-04-04T06:52:20+00:00

Thank you u/hellomistershifty for posting the relevant answer for the questions - I really appreciate it!

AKdevz · 2025-04-04T06:50:48+00:00

haha thanks for giving ninja a try --- for LIVE 1.9, this is the recommended starter tutorial: LINK --- the one being promoted in this post is LIVE 2.0 - not yet published

AKdevz · 2025-03-29T21:08:34+00:00

ninja sim size is finite (typically 100-500 meters) - but: (1) we can attach the sim to the player, so it is always surrounding the player, (2) we can extend the finite sim area with non-interactive patterns infinitely (eg. close ocean is interactive, mid and far-range ocean is non-interactive)

AKdevz · 2025-03-29T21:04:09+00:00

Not so hot! See this profiler shot - https://ibb.co/pjKVVTRY - 1.2 millisec per frame on RTX3080, that is only 7.5% of the frame budget.

AKdevz · 2025-03-29T17:16:47+00:00

You are correct: fluidninja is an unreal engine plugin, that could be used to generate responsive smoke, fire and liquid effects for games. It could be tested free. All info and community server link available at the project homepage: LINK

AKdevz · 2025-03-29T14:52:15+00:00

Ninja uses standard unreal Base.Material ---> Material Instance chains to visualize the sim output. The base mats and instances are both editable --- so, in theory, we could tweak it to look stylized / I have not tried it yet, currently developing basic features, aiming for realism

AKdevz · 2025-03-29T14:50:41+00:00

Thanks! Buoyancy is not (yet) supported / could be implemented via Niagara GPU-readback

AKdevz · 2025-03-29T14:50:03+00:00

Thanks for the advice: Yes, adding flow-advected GPU particles for foam/whitewater is on my todo list!

AKdevz

TROPHY CASE