lucaspoffo
commented
1 year ago I usually wait for the bevy release version to update, they already have frequent enough release schedules that depending on master doesn't seem crucial. It might be interesting for others that use master thou, they could checkout this PR. Gonna take a look closer to their release.
raffaeleragni
Updates renet and bevy_renet to work with bevy main branch, currently 0.11.0-dev. Specifically bevy commit #8ec8149 though this can be updated as new commits are pushed.
Most of the changes are to bevy_renet and do not change any logic, merely adopts new syntax introduced by this version of bevy.
Only a few #[cfg_attr] changes had to be made in the renet crate to derive bevy resource / events.
Added the bevy git to the whitelist in deny.toml.
Had to remove "demo_bevy" from the workspace as it depends on other crates that depend on older bevy versions which causes conflicts. There might be a better way to fix this but I haven't got around to it yet.
Enabled the following bevy features to solve a rendering issue that resulted in all assets missing textures: ktx2, tonemapping_luts, zstd
Primarily made this for my own use but added documentation in case anyone else wants to use this. If you decide to merge this I would recommend a separate branch and some changes to the docs will need to be made.