Incompatible with bevy 0.17

[mpearson]

I may be doing something wrong but it seems like this library doesn't support Bevy 0.17 yet. I get a number of compile errors such as

note: there are multiple different versions of crate `bevy_app` in the dependency graph

and

the trait `bevy::bevy_app::plugin::sealed::Plugins<_>` is not implemented for `(iyes_perf_ui::PerfUiPlugin, FrameTimeDiagnosticsPlugin)`

For reference, here is the actual usage which worked fine before in bevy 0.15. I have a very simple wrapper plugin which configures iyes_perf_ui for my application:

use bevy::prelude::{default, App, Commands, Plugin, Startup};

use bevy::diagnostic::FrameTimeDiagnosticsPlugin;
use iyes_perf_ui::prelude::*;

pub struct FpsCounterPlugin;

impl Plugin for FpsCounterPlugin {
    fn build(&self, app: &mut App) {
        app.add_plugins((PerfUiPlugin, FrameTimeDiagnosticsPlugin::default()))
            .add_systems(Startup, setup_fps_counter);
    }
}

fn setup_fps_counter(mut commands: Commands) {
    commands.spawn((
        PerfUiRoot {
            display_labels: false,
            layout_horizontal: true,
            ..default()
        },
        PerfUiEntryFPS::default(),
    ));
}

[Wildos]

mgi388 made a pull request to support bevy 0.17, #35

If you don't want to wait for the maintainer to merge it, you can already use it by adding a patch to your Cargo.toml

[patch.crates-io]
iyes_perf_ui = { git = "https://github.com/mgi388/iyes_perf_ui", branch = "bevy-0.17" }

[naturedamends]

mgi388 made a pull request to support bevy 0.17, #35

If you don't want to wait for the maintainer to merge it, you can already use it by adding a patch to your Cargo.toml

[patch.crates-io]
iyes_perf_ui = { git = "https://github.com/mgi388/iyes_perf_ui", branch = "bevy-0.17" }

FYI: this is a terrible idea unless you understand exactly what your doing and the code, to download and execute this code, from a random repo, that you yourself don't own. The code does not even have to be version tracked and can be overwritten without being monitored by security software.

If you must do it: first fork the repo yourself, and then download from your own fork. And keep in in sync with the master repo.

[onx2]

mgi388 made a pull request to support bevy 0.17, #35
If you don't want to wait for the maintainer to merge it, you can already use it by adding a patch to your Cargo.toml

[patch.crates-io]
iyes_perf_ui = { git = "https://github.com/mgi388/iyes_perf_ui", branch = "bevy-0.17" }

FYI: this is a terrible idea unless you understand exactly what your doing and the code, to download and execute this code, from a random repo, that you yourself don't own. The code does not even have to be version tracked and can be overwritten without being monitored by security software.

If you must do it: first fork the repo yourself, and then download from your own fork. And keep in in sync with the master repo.

but I love malware! 🙉

[ArjixWasTaken]

If you must do it: first fork the repo yourself, and then download from your own fork. And keep in in sync with the master repo.

If you must do it, use a commit instead of a branch/tag.
A commit cannot be modified, it can only be deleted.

e.g. for bevy 0.18 #38 (comment)