flutter3d_particles

A pool, an emitter, and one draw call.

final particles = ParticleSystem();
renderer.addContributor(ParticleContributor(particles));

particles.burst(effect, at, direction: normal);
particles.advance(loop.lastFrame);

Every live particle in a scene is drawn in a single instanced call, on any backend the engine has. The pool is fixed and reused. A system that allocated per particle would spend a frame's budget in the garbage collector at exactly the moment something exploded.

The system is advanced with the frame the simulation accepted, GameLoop.lastFrame, and not with the raw delta. Otherwise the smoke drifts away from the world it is attached to on any machine that drops a frame.

There is no Flutter in it. The contributors draw through flutter3d_core's PassContributor, so the package runs under dart test, and flutter3d_model_core bakes a system into a SimulationCache on the Dart VM. The same seed and the same sequence of advance calls give byte-identical particles. The bake relies on that; it does not add it.

Part of flutter3d, an independent implementation of a 3D engine for Flutter. It is not a fork or a binding of another engine, and it is not affiliated with the Flutter team. It has four switchable rendering backends: Impeller via Flutter GPU, WebGL2, WebGPU and a software rasteriser. It loads glTF, OBJ and .f3d, and has six lighting models, shadows, bloom, skinning, animation, BVH culling and picking, plus a deterministic fixed-step game layer with collision, navigation, positional audio, and gamepad and touch input. Four example games (shooter, platformer, racing, strategy) are each built on a genre package: flutter3d_game_shooter, flutter3d_game_platformer, flutter3d_game_racing, flutter3d_game_strategy. A new game starts from the editor's scaffold, which writes one from a template: flutter3d.pleion.dev/first-project/. Documentation: flutter3d.pleion.dev.