4k texture model loading is way to slow.

[HyeokSuLee]

It took over 1 minute as gltf extension.
Is there some solution for pre load?
Or command to load and check when loading is complete.

[alice-i-cecile]

See #1307 for your last request :)

[DJMcNab]

Have you tried running in release mode? The image crate is very slow in debug mode

You can also set up your project so that cargo builds your dependencies in release mode. I'm on mobile, so it's hard to check, but I think it's in Cargo.toml:

[profile.dev.package.*]
opt-level = 3

[HyeokSuLee]

Have you tried running in release mode? The image crate is very slow in debug mode

You can also set up your project so that cargo builds your dependencies in release mode. I'm on mobile, so it's hard to check, but I think it's in Cargo.toml:

[profile.dev.package.*]
opt-level = 3

yeah, you are right. in release mode it is fast enough.

1. Can you tell me more detail about build dependencies in release mode ?
   I've tried with below but it doesn't seem to work.

[dependencies]
bevy = "0.5.0"
[profile.dev.package.bevy]
opt-level = 3

2. And after build, assets folder doesn't copy to target/debug(or release).
   I know it can be done by build scripts, but bevy examples look like not use build script.
   Is there a way to automatically copy assets to target folder?

[DJMcNab]

Dependencies are built with whatever profile applies to them. In this case, you have asked exactly the bevy crate to be built in release mode, which will have no effect, because the bevy crate itself is only a wrapper crate. I personally use exactly the code snippet I advised you use (the one using using [profile.dev.package.*]) in my Cargo.toml. There is more documentation in the cargo book.

Bevy locates assets based on the cargo workspace root, environment environment variable with a fallback to the current executable location. This is implemented here:

bevy/crates/bevy_asset/src/io/file_asset_io.rs

Lines 29 to 41 in 20673db

	pub fn get_root_path() -> PathBuf {
	if let Ok(manifest_dir) = env::var("CARGO_MANIFEST_DIR") {
	PathBuf::from(manifest_dir)
	} else {
	env::current_exe()
	.map(|path| {
	path.parent()
	.map(|exe_parent_path| exe_parent_path.to_owned())
	.unwrap()
	})
	.unwrap()
	}
	}

To use a bevy program in a different folder, you should set the CARGO_MANIFEST_DIR environment variable, or you can move the executable manually. There are plans for further integration with Distill, which might improve this situation. This work is tracked in #708

[alice-i-cecile]

I'm going to close this for now, but feel free to ask for any more assistance that you need, either here, in the Discussions or on Discord @HyeokSuLee <3

Asset loading speed will continue to be improved, but I think the issue is resolved for now thanks to release mode.