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

Fix False Reports of Using Legacy Assets #17934

Merged

Conversation

AMZN-Gene
Copy link
Contributor

@AMZN-Gene AMZN-Gene commented May 17, 2024

Removing 2 of 3 legacy asset id warnings. When an asset is reprocessed, asset processor triggers a OnCatalogAssetChanged event. It triggers the event for both the normal asset id, and the legacy asset id equivalent even if the legacy asset id isn't ultimately used.

The legacy asset warning still exists, but only inside the AssetProcessor's GetProductAssetInfo(); this appears to only be called when a legacy asset is actually being processed.

How was this PR tested?

  1. Build assets from scratch and see no false warnings about legacy asset ids
  2. Leave editor open and reprocess a prefab and see no false warnings about legacy asset ids

Fixes #17933

…e assetprocessor will trigger the OnCatalogAssetChanged event for using the legacy id any time it processes an asset. The legacy asset warning still exists in AssetProcessor code as GetProductAssetInfo doesn't get called for legacy asset unless a legacy asset is actually being used https://github.com/o3de/o3de/blob/development/Code/Tools/AssetProcessor/native/AssetManager/AssetCatalog.cpp#L1715-L1728

Signed-off-by: AMZN-Gene <genewalt@amazon.com>
@AMZN-Gene AMZN-Gene requested review from a team as code owners May 17, 2024 21:12
@AMZN-Gene AMZN-Gene changed the title Fix Wrongly Reporting when Legacy Asset Is Being Used Fix False Reports of Using Legacy Assets May 17, 2024
Copy link
Contributor

@nick-l-o3de nick-l-o3de left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is happening in the stabilization branch too, consider cherry picking, please!

@AMZN-Gene AMZN-Gene merged commit d054b0c into o3de:development May 20, 2024
3 checks passed
@AMZN-Gene AMZN-Gene deleted the GHI_17933_LegacyAssetSpamFix branch May 20, 2024 16:18
AMZN-Gene added a commit to aws-lumberyard-dev/o3de that referenced this pull request May 20, 2024
…t look up becauseassetprocessor will trigger the OnCatalogAssetChanged event for using the legacy id any time it processes an asset. The legacy asset warning still exists in AssetProcessor code as GetProductAssetInfo doesn't get called for legacy asset unless a legacy asset is actually being used https://github.com/o3de/o3de/blob/development/Code/Tools/AssetProcessor/native/AssetManager/AssetCatalog.cpp#L1715-L1728 (o3de#17934)

Signed-off-by: AMZN-Gene <genewalt@amazon.com>
@AMZN-Gene
Copy link
Contributor Author

This is happening in the stabilization branch too, consider cherry picking, please!

Thankyou!
#17937

nick-l-o3de pushed a commit that referenced this pull request May 21, 2024
…t look up becauseassetprocessor will trigger the OnCatalogAssetChanged event for using the legacy id any time it processes an asset. The legacy asset warning still exists in AssetProcessor code as GetProductAssetInfo doesn't get called for legacy asset unless a legacy asset is actually being used https://github.com/o3de/o3de/blob/development/Code/Tools/AssetProcessor/native/AssetManager/AssetCatalog.cpp#L1715-L1728 (#17934) (#17937)

Signed-off-by: AMZN-Gene <genewalt@amazon.com>
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

Successfully merging this pull request may close these issues.

Legacy Asset Deprecation Notice is Spammed When Asset Reprocessed
5 participants