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.

Sign up for GitHub

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

Jump to bottom

Legacy Asset Deprecation Notice is Spammed When Asset Reprocessed #17933

Closed
AMZN-Gene opened this issue May 17, 2024 · 0 comments · Fixed by #17934
Closed

Legacy Asset Deprecation Notice is Spammed When Asset Reprocessed #17933

AMZN-Gene opened this issue May 17, 2024 · 0 comments · Fixed by #17934
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@AMZN-Gene
Copy link
Contributor

AMZN-Gene commented May 17, 2024 •
edited
Loading

The O3DE deprecation notice for using a legacy asset id is spammed if the asset processor reprocesses an asset.

Steps to reproduce

  1. Run Editor
  2. Open Asset Processor
  3. Rightclick a prefab and reprocess it

Expected behavior
Preprocessing a modern asset should succeed without warning

Actual behavior
The editor log gets a warning about deprecated asset id

Deprecated asset id warning! GetAssetInfoByIdInternal could not find the modern asset id for "<path_to_prefab>" and so fell back to using the legacy asset id. Please recreate the asset and update any other assets referencing this asset in order to generate a modern asset id"

Found in Branch
development

Relates to #17861
@AMZN-Gene AMZN-Gene added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 17, 2024
@AMZN-Gene AMZN-Gene mentioned this issue May 17, 2024
Merged
@AMZN-Gene AMZN-Gene mentioned this issue May 20, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix False Reports of Using Legacy Assets aws-lumberyard-dev/o3de
1 participant
@AMZN-Gene