Skip to content

Asset loading on the Web produces many 404 errors for .meta files #10157

Closed
@coreh

Description

@coreh

Bevy version

5733d24

What you did

Ran any example that loads assets under WASM / WebGL with:

cargo run -p build-wasm-example -- $EXAMPLE_NAME_HERE && python3 -m http.server --directory examples
/wasm

What went wrong

Got barraged with 404 error messages in the web inspector with the page trying to load .meta files for every asset loaded.

Additional information

image
  • Looks like with Bevy Asset V2 #8624 we now look for .meta files for every asset that we load
  • On native this is a non issue, however on the web we do a bunch of requests, which both spam the console with 404 errors and also potentially slow down loading of the files that actually exist

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-AssetsLoad files from disk to use for things like images, models, and soundsC-BugAn unexpected or incorrect behaviorC-PerformanceA change motivated by improving speed, memory usage or compile timesO-WebSpecific to web (WASM) builds

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions