Migration should be significantly easier than the 0.9 -> 0.11 jump. The main breaking change will be the Asset v2 which will require major changes to our site_asset_io, as well as loaders and asset events parsing.
Luckily the new asset pipeline introduced some interesting features, such as "multiple asset sources distinguished on the prefix".
I believe we can refactor the current bundled site_asset_io into a rmf_server_reader that parses rmf-server:// assets, a package_asset_reader that parses package:// assets etc.
We might also be able to use external crates to avoid having to write our own platform agnostic http client logic and fix #128, such as https://github.com/johanhelsing/bevy_web_asset.
Apart from the new asset system, there are nice features here and there, but one of the most interesting ones (to me) is batched GPU rendering that increases performance when rendering multiple instances of objects with the same mesh / material, which is a pattern we use extensively.
Crates wise, current status:
[x] bevy_egui: 0.21 -> 0.23.
[x] bevy_mod_raycast: 0.13 -> 0.16.
[ ] bevy_infinite_grid: Currently 0.8, not released yet but merged to main.
[x] bevy_mod_outline: 0.5 -> 0.6.
[ ] bevy_polyline: Currently 0.7, not released yet but merged to main.
Bevy 0.12 has been recently released.
Migration should be significantly easier than the 0.9 -> 0.11 jump. The main breaking change will be the Asset v2 which will require major changes to our
site_asset_io, as well as loaders and asset events parsing. Luckily the new asset pipeline introduced some interesting features, such as "multiple asset sources distinguished on the prefix". I believe we can refactor the current bundledsite_asset_iointo armf_server_readerthat parsesrmf-server://assets, apackage_asset_readerthat parsespackage://assets etc. We might also be able to use external crates to avoid having to write our own platform agnostic http client logic and fix #128, such as https://github.com/johanhelsing/bevy_web_asset.Apart from the new asset system, there are nice features here and there, but one of the most interesting ones (to me) is batched GPU rendering that increases performance when rendering multiple instances of objects with the same mesh / material, which is a pattern we use extensively.
Crates wise, current status:
bevy_egui:0.21->0.23.bevy_mod_raycast:0.13->0.16.bevy_infinite_grid: Currently0.8, not released yet but merged to main.bevy_mod_outline:0.5->0.6.bevy_polyline: Currently0.7, not released yet but merged to main.bevy_stl:0.11->0,12..bevy_obj:0.11->0.12.