bevyengine / bevyengine/bevy

write the actual meta data into meta files with `asset_processor` feature enabled

Open
#24,466 0 comments 0 reactions 0 assignees View on GitHub
A-Assets C-Feature S-Needs-Design
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## What problem does this solve or what need does it fill?

My initial idea was to find the equal functionality of `load_builder().with_settings(...)` in BSN. which is really a hard thing.

Then I remembered the meta file, it looks like a good alternative, and discovered the `asset_processor` feature. But it only writes a default meta files. Migrating from `with_settings` to meta files is not very smooth.

## What solution would you like?

`asset_server.load_builder().load()` can write actual meta files with `asset_processor` feature enabled.

## Additional context

Origin #24415.

Contributor guide

Open the contributing guide

Research direction

Start at asset_server.load_builder().load() and trace how the asset_processor feature currently writes default meta files. Compare that behavior with the settings supplied through load_builder().with_settings(...); done means loading with asset_processor enabled writes the actual metadata needed for migration to meta files.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.