Using asset_processor together with trace_tracy leads to an asset load error.

[samoylovfp]

Bevy version and features

tested with 0.18.0, features = ["trace_tracy", "asset_processor"]

What you did

Reproduction script

put any valid png file into `assets/test.png` and run this

#!/usr/bin/env -S cargo +nightly -Zscript
---
[dependencies]
bevy = { version = "0.18.0", features = ["trace_tracy", "asset_processor"] }
---

use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins.set(AssetPlugin {
            mode: AssetMode::Processed,
            ..default()
        }))
        .add_systems(
            Startup,
            |mut commands: Commands, asset_server: Res<AssetServer>| {
                commands.spawn(Camera2d);
                commands.spawn(Sprite {
                    image: asset_server.load("test.png"),
                    ..default()
                });
            },
        )
        .run();
}

What went wrong

I expected to see the png image displayed on screen, instead I got a runtime error

ERROR bevy_asset::server: no `AssetLoader` found with the name 'bevy_asset::server::loaders::InstrumentedAssetLoader<bevy_image::image_loader::ImageLoader>'

Disabling the tracy feature fixes the behavior.

[samoylovfp]

Found a workaround: if a .meta file is created first by running bevy with only asset_processor
feature then the correct loader is written into the meta file and it is loaded correctly on a subsequent run of bevy with trace_tracy feature

[samoylovfp]

#22213
This seems related

[andriyDev]

Yup, AFAIK this should be fixed on main. I don't think this PR made it into 0.18.0.