[LYN-3717] When pulling in an actor FBX, two entities are spawned & [ATOM-15258] Clicking and Dragging fbx file into viewport produces 2 entities (#1392)

* [LYN-3717] When pulling in an actor FBX, two entities are spawned & [ATOM-15258] Clicking and Dragging fbx file into viewport produces 2 entities * Added another operation to the CanSpawnEntityForProduct that checks the other products and can veto the creation process. * The model product will not create an entity in case there is already an actor exported, which prevents the issue reported by two different teams/users.
2021-06-22 05:12:42 -07:00
parent 858dee2210
commit 7d5a7b47ac
4 changed files with 57 additions and 10 deletions
@@ -57,7 +57,13 @@ namespace AZ
        //! Determines if a component can be created from the asset type
        //! This will be called before attempting to create a component from an asset (drag&drop, etc)
        //! You can use this to filter by subIds or do your own validation here if needed
-        virtual bool CanCreateComponent(const AZ::Data::AssetId& /*assetId*/) const { return true; }
+        virtual bool CanCreateComponent([[maybe_unused]] const AZ::Data::AssetId& assetId) const { return true; }
+
+        //! Determines if other products conflict with the given one when multiple are generated from a source asset.
+        //! This will be called before attempting to create a component from an asset (drag&drop, etc)
+        //! You can use this to filter by conflicting product types or in case you want to skip for UX reasons.
+        //! @param[in] productAssetTypes Asset types of all generated products, including the one for our given type in this bus.
+        virtual bool HasConflictingProducts([[maybe_unused]] const AZStd::vector<AZ::Data::AssetType>& productAssetTypes) const { return false; }
    };

    using AssetTypeInfoBus = AZ::EBus<AssetTypeInfo>;