Skip to content

Commit 69a076d

Browse files
chore: release v0.1.0
2 parents 6448265 + b580972 commit 69a076d

File tree

2 files changed

+19
-0
lines changed

2 files changed

+19
-0
lines changed

CHANGELOG.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Changelog
2+
3+
All notable changes to this project will be documented in this file.
4+
5+
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6+
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7+
8+
## [Unreleased]
9+
10+
## [0.1.0](https://github.com/Vrixyz/bevy_fixed_update_task/releases/tag/v0.1.0) - 2025-01-13
11+
12+
### Features
13+
14+
- Custom timestep or substep count per frame.
15+
- Component approach, support multiple concurrent fixed "task" update.
16+
- Examples for minimal approach + interpolation integration.
17+
- Documentation to explain how this crate works on the [readme](README.md) and [docs](./docs/).

README.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,8 @@ so you can improve your time budget.
99

1010
## How it works
1111

12+
:warning: this crate makes most sense when using bevy's `multi_threaded` feature. Otherwise, this just adds unnecessary overhead.
13+
1214
It's quite similar to how bevy's fixed update works, but eagerly extracts ECS data into a background task, to synchronize it only when we exceed `Time<Fixed>` + its accumulated time.
1315

1416
The implementation doesn't use `Time<Fixed>` but a component approach `TimeStep`, `SubstepCount`, `TaskToRender`.

0 commit comments

Comments
 (0)