@Rynex_FNC Including ambient sound actors is something we are turning off for the time being in open beta as this would prevent new users from using workarounds as you have described and creating more content that might have to be updated. It’s still something we will monitor closely as we continue to collect feedback.
In the meantime, our team is looking into making an update for open beta so that any projects with existing ambient sound actors in it already can still work ( but you just won’t be able to add new ones ). This would provide a bit of run way for users with existing content done this way. There might be edge cases where something won’t work, but we can try a few scenarios out to evaluate. Can you clarify this scenario for us “Audio Cues have been added as Components inside some of our Building Props”. Is there a screenshot you can share or steps you can provide for us to test it out on our end?
On quick spot checking of the audio player device memory usage compared with ambient sound actors, they appeared comparable. Are you seeing something different on your end? We can investigate more.
Lastly, we’ll look into the “Unregister Player” and “Deactivate” options not working. They should.