Thank you for your report. I will begin investigation into this issue as soon as possible. If I am unable to reproduce the problem, or I need more information, I or another staff member will follow up with some additional questions for you. Otherwise, I will post an ‘Answer’ once I have logged the issue in our bug database or we have a solution for it.
In the meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide:
Can you let me know what type of sound you are using? Are you using a sound cue called through a actor or level blueprint? Are you using a Ambient Sound in the level? Are you using any attenuation settings or is it an always on and always attenuated to the world?
Can you be more specific as to exact what you want out of this sound? My is looping correctly as you have designed the cue, so each time the sound plays a random node then chooses another random node for the next loop. If that is not your intent then you may want to move the looping node to before the random node then rach time teh cue is called it will only select 1 sound randomly and loop that until the next time the cue is called.
For reference - I’m having exactly the same problem. Looping randomly selected sound waves plays them once and then they stop. I’ve tried changing from “Loop indefinitely” to looping 1000000 times but it still only plays once.
This is on a Nexus 9 tablet. It works fine on PC.
As a workaround I’ve done the same thing in a BP, which is working well but is less than elegant.
Is there anything I could print out from the BP for the sound cue that might help diagnose? Is there any info at all that would help diagnose?
Tried it, that didn’t change anything. Presumably having the looping before the random node will have a completely different result to having it after it. Certainly it works on the PC, just not on the tablet, whereas setting the looping checkbox doesn’t work on either.
I am going to set up a test project using a similar set up you have provided in the screenshot above. The device I am testing with (Galaxy Note 10.1 2014 Edition) is a little bit older, but If I can reproduce it on that device, then I can enter a bug report and we can get a fix integrated for a future release.
If I am unable to reproduce it on this device, I will hand the project to another team member with a device that more closely matches your own and we will test there. Thank you for your patience while we work through this issue.
I was unable to reproduce this on the device I mentioned in my previous post. Would you mind testing something for me on your end to see if this resolves your issue?
Try placing the looping nodes before you introduce the delays which are placed immediately after the random nodes in your Sound Cue.