Has the ability to trigger actions in another scene been removed? There used to be a little double box next to the current scene in the actions dialog where you could choose another scene and have the action affect an asset in that scene. I don’t see that little double box anymore.
thanks
Brad
Hi Brad @emphelp,
Yes, this feature has officially been removed, mainly for performance purposes. When trying to call an action on another scene, the Player needed to know what this target scene actually contains, meaning having more than 1 scene loaded at the same time. This caused issues, especially on low powered devices.
Generally speaking, we also considered this a “not so good practice”, since in 99% of the cases, scenes are set to reset all asset properties when loaded, calling an action on an unloaded scene could yield unexpected results.
Depending on what you are trying to achieve, using an Experience Layer or an Interface Asset such as the Global Variable are better options to pass info from 1 scene to another, then use the “Scene has been entered” trigger to call any actions necessary on that target scene, when actually entering it, using the Variable values as conditions. See examples here.
It’s been a while since we had a chat, send me a dm / email if you want to set up some time so we can talk about your specific use case 
That being said, !! use at your own risk !!, you might want to try and hold the CTRL key on your keyboard while hovering the scene name in your Trigger & Action panel