Bug Description

If you have the multiplayer component enabled and have a prefab that has both .spawnable and .network.spawnable, trying to spawn using the script canvas SpawnableScriptAssetRef variable asset dialog selects the wrong prefab, generating a crash.

Assets-Required

prefab_and_script.zip

Steps to Reproduce

1. Have a prefab that is both spawnable and network.spawnable (multiplayer gem must be enabled).
2. Go to Script Canvas editor.
3. Create SpawnableScriptAssetRef variable
4. Open the dialog to select the asset
5. select your multiplayer mesh prefab. Notice how it doesn't allow you to select .spawnable or network.spawnable submenu
6. Notice how the name doesn't contain the .spawnable or .network.spawnable just the prefab name.
7. Create a spawn ticket node and attach the variable to the Prefab connection.
8. Run the script and observe how the whole editor process crashes.
9. If you manually add the .network.spawnable extension to the dialog selected prefab everything works as expected

Expected Behavior

The asset selection dialog should allow for selection of spawnable or network.spawnable assets instead of defaulting to the asset name. Also, if the asset is not correctly selected (doesn't end in spawnable or network.spawnable) the editor should not crash.

Actual Behavior

Crash at line 117 in SpawnableScriptMediator::SpawnAndParentAndTransform
TransformComponent* entityTransform = containerEntity->FindComponent(); // containerEntity is nullptr or invalid thus generating a crash.

Screenshots/Videos

Found In Branch

24.09.1 release

Commit ID From

da3e1d3

Desktop/Device

PC Windows 11 Pro
AMD Ryzen 5800H
16 GB RAM
Nvidia RTX 3070.

Additional Context

No response