Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bevy_asset_loader doesn't work with bevy/asset_processor feature (0.14 Crates Release) #225

Open
Braymatter opened this issue Jul 6, 2024 · 4 comments

Comments

@Braymatter
Copy link

Braymatter commented Jul 6, 2024

Our game has several asset collections, and we use preprocessing to convert our textures to BASIS-LZ

Whenever we run our app with the preprocessing flag the AssetCollections never seem to get loaded, and we're stuck with a black screen.

According to the logs, bevy_asset_loader is trying to load, but it looks like it somehow never completes.

It just logs these repeated 'Check loading' logs in debug

image

By contrast invoking the program without the pre-process flag does these 'check' logs for less than a second then loads normally. Both invocations appear to preprocess the assets correctly.

@Braymatter Braymatter changed the title Bevy_asset_loader doesn't work with preprocessing flag Bevy_asset_loader doesn't work with preprocessing flag (0.14 Crates Release) Jul 6, 2024
@Braymatter Braymatter changed the title Bevy_asset_loader doesn't work with preprocessing flag (0.14 Crates Release) Bevy_asset_loader doesn't work with bevy/asset_processor feature (0.14 Crates Release) Jul 6, 2024
@NiklasEi
Copy link
Owner

NiklasEi commented Jul 6, 2024

The same worked in Bevy 0.13? Do you have a reproduction that I can access?

@Seldom-SE
Copy link

(I also work on this project)

The same worked in Bevy 0.13?

Yes

@Braymatter
Copy link
Author

Update from our side, bevy doesn't appear to be copying the .bin files from gltf's over to the ImportedAssets directory which is causing this issue. We've created an issue on bevy: bevyengine/bevy#14190

Ideally we'd get an informative log or something from bevy_asset_loader, but the cause of this appears to be bevy.

We're able to work around it by switching it to a .glb

@NiklasEi
Copy link
Owner

NiklasEi commented Jul 6, 2024

Good to know, thank you. Imo the warning should be coming from Bevy here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants