You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Chris Santora 66f7fa2f42 Fixed a bug where a new entity using a mesh that was already loaded would not be able to correctly initialize a material component. ... Repro steps: - Create two entities. - Entity 1 - Add a mesh component and assign a model with multiple sub-meshes - Add a material component. The material component looks correct. - Entity 2 - Add a mesh component and assign the same model as the other entity - Add a material component. The material component shows "<unknown>" for all material slot names The problem was that ReflectedPropertyEditor creates a new Asset<> reference with the correct ID but does not load it. This asset is passed to EditorMaterialComponent, MaterialComponentController, and MeshFeatureProcessor and none of these tell the Asset to load. The MeshFeatureProcessor was not loading the Asset or connecting to the AssetBus because the instance already existed in the InstanceDatabse so from the FP's perspecive there was no need. But for the FP's GetModelAsset() API to function correctly it needs to have the asset initialized to the available AssetData pointer. So we updated the MeshFeatureProcessor to always connect to the AssetBus so it will find the available AssetData via the OnAssetReady callback. Signed-off-by: santorac <55155825+santorac@users.noreply.github.com>		4 years ago
..
MeshFeatureProcessor.cpp	Fixed a bug where a new entity using a mesh that was already loaded would not be able to correctly initialize a material component.	4 years ago