AMZN-stankowi

Why are the MaterialType files referencing the Shader files via path and not via source asset UUID? Also, let me know if there's anything you need the asset pipeline team...

I've been working on documentation updates for the asset pipeline, I've added that page to my list to go back over.

I've put an update to the documentation to address issues with assets referencing other files, here https://github.com/o3de/o3de.org/pull/1882

the workflow I was trying to cover was: You drag and drop the source FBX asset, and the FBX's only product assets do not have a logical instantiation target. The...

I think it would make sense to resolve this, and create new tickets for any other requested changes.

> format gltf fixed too? This should fix this scale bug for all non-FBX format files.

This is a bug in the Asset Browser: > EditorLib.dll!AzToolsFramework::AssetBrowser::AssetBrowserTreeView::GetSelectedAssets(bool includeProducts) Line 143 C++ EditorLib.dll!AzToolsFramework::AssetBrowser::AssetBrowserTreeView::AfterRename(QString newVal) Line 641 C++

I'm really wanting to find time to dig into the overall interface of the Asset Processor, I think there's a lot we can do to improve information presentation in the...

I've split https://github.com/o3de/o3de/issues/12618 off into its own ticket, it's a different error than the rest of the files https://github.com/o3de/o3de/issues/12618 For the other files, can you give additional details, the scan...

Do you get these errors with those files with AutomatedTesting, or just your new project? I'm wondering if maybe a Gem wasn't activated or something.