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
As more features get added in, I should put more consideration into how things are organized. Sky models, for instance, can be organized into an enum and the variants can be feature-gated. In that case, the enum should be marked non-exhaustive, so changing the variant features won't cause a compile error. Besides that, it allows for adding new sky models in the future.
On that note, I should probably see if current features can receive the same treatment (allow for changing behavior at compile time and run time) to make them more flexible.
The text was updated successfully, but these errors were encountered:
Things to do when Bevy 0.9 is released.
QOL changes:
Remove(Bevy 0.9 now requiresAtmosphereSkyBoxMaterial
(unnecessary newtype) or make it an aliasimpl Resource
, so theHandle
can't be used directly)procedural
feature (controls whether theAtmospherePlugin
adds theAtmospherePipelinePlugin
) (Fixes Custom skybox texture? #29)detection
featureRemove dithering (Bevy 0.9 now adds dithering by default)(dithering is still necessary, it seems banding still occurs)Potential Features:
Gradient
model)Night sky model (Fixes Starry starry night #27)Compile time vs run time discrepancy
As more features get added in, I should put more consideration into how things are organized. Sky models, for instance, can be organized into an enum and the variants can be feature-gated. In that case, the enum should be marked non-exhaustive, so changing the variant features won't cause a compile error. Besides that, it allows for adding new sky models in the future.
On that note, I should probably see if current features can receive the same treatment (allow for changing behavior at compile time and run time) to make them more flexible.
The text was updated successfully, but these errors were encountered: