You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since SimplexNoise is now deprecated we want to deprecate NoiseEffectController and move it into a bridge package that bridges to fast_noise. Then the NoiseEffectController can use different types of noise and I'm sure there will also be more applications for where we want to use noise which we can put in that package.
Why should this be improved
To avoid putting in another dependency in the core of Flame, but also open up the possibility for more applications within Flame using noises.
What could be improved
Since
SimplexNoise
is now deprecated we want to deprecateNoiseEffectController
and move it into a bridge package that bridges to fast_noise. Then theNoiseEffectController
can use different types of noise and I'm sure there will also be more applications for where we want to use noise which we can put in that package.Why should this be improved
To avoid putting in another dependency in the core of Flame, but also open up the possibility for more applications within Flame using noises.
Any risks?
It will be a breaking change.
More information
https://github.com/frankpepermans/fast_noise
google/vector_math.dart#270
The text was updated successfully, but these errors were encountered: