flutter3d_particles 0.7.1 copy "flutter3d_particles: ^0.7.1" to clipboard
flutter3d_particles: ^0.7.1 copied to clipboard

A pooled CPU particle simulation for flutter3d, and the contributor that draws it. Its particles can be a light source, which is the part no other engine on this platform has.

0.7.1 #

Released with the rest of the stack at 0.7.1. Nothing in this package changed. The release it resolves against builds from pub.dev again and no longer crashes Metal on the first unlit draw.

Its flutter3d_* dependencies ask for ^0.7.1, and it asks for vector_math ^2.4.3.

0.7.0 #

  • A burst can light something. ParticleSystem.burst takes an optional source, and a LightEmitter passed there has its glow fed by the burst's particles, then fades and leaves the measured set on its own. Before this a burst's particles were born belonging to nobody, so a muzzle flash or an explosion cast no light however bright its colour was, while the skill in this package said it did. Existing calls are unchanged.

  • flutter3d_particles_core is back inside, and Flutter is out. The simulation had been split off so a headless caller could bake a ParticleSystem; the two contributors stayed here because they imported Flutter, for a debugPrint inside an assert and for flutter3d's barrel. They import flutter3d_core now and report a missing shader stage through dart:developer's log, so the whole package is plain Dart and flutter3d_model_core depends on it directly. The public API is the same; an importer of package:flutter3d_particles_core names package:flutter3d_particles/flutter3d_particles.dart instead.

  • The pubspec follows. flutter: sdk and the dependency on flutter3d are gone, and the package depends on flutter3d_core ^0.7.0 and flutter3d_hardware ^0.7.0. An application that reached flutter3d only because this package brought it has to name it itself. The tests run under dart test. The archive carries skills/flutter3d-particles-one-draw-call/ for a coding agent, installed with dart run skills@ get.

0.6.0 #

  • Floors, and no code. One pool, one draw call, whatever is in it — byte for byte 0.5.0's. flutter3d and flutter3d_hardware are now floored at ^0.6.0, which is the pair this package's single batch was compiled against.

0.5.0 #

Breaking. An ease carries its curve.

  • KeyEase is a value class holding the shape it applies. Opening the list alone would have been useless — easeShape would have had no branch for a game's own ease. A game writes const KeyEase('bounce', _bounce) and every curve and gradient samples it without this package having heard of it.

0.4.0 #

  • No changes of its own; the version moves with the workspace, whose sibling constraints name a single release. The README's closing section now says what the engine around this package is.

0.3.0 #

  • No changes of its own. The workspace is released as a set, in the order ARCHITECTURE.md §16 gives, so this package's version moves with the rest and its constraints on its siblings move with it.

0.2.0 #

  • A pool, emitters, modifiers and a contributor that draws every live particle in one instanced call, on any backend the engine has.
  • A particle can be a light source and can carry a texture.
0
likes
150
points
436
downloads

Documentation

API reference

Publisher

verified publisherpleion.dev

Weekly Downloads

A pooled CPU particle simulation for flutter3d, and the contributor that draws it. Its particles can be a light source, which is the part no other engine on this platform has.

Homepage
Repository (GitHub)
View/report issues
Contributing

Topics

#particles #graphics #rendering #effects

License

MIT (license)

Dependencies

flutter3d_core, flutter3d_hardware, vector_math

More

Packages that depend on flutter3d_particles