1 decade ago by Ant101
This is something that has only recently started happening for me, so I don't yet know if it's related to a new Chrome versions, my upgrade to impact1.20 or something I have changed by mistake (don't think so!).
The issue: Sounds are played in a 'queued' manor, rather than at the time they are triggered. Or in other words, if a sound is playing, and I do another sound.play(), the second will only start after the first has finished. It works as it should in firefox.
Anyone else experiencing this? Versions:
Impact: 1.20
Chrome: 21.0.1180.60
OS: Windows 7 Profession N SP1
The issue: Sounds are played in a 'queued' manor, rather than at the time they are triggered. Or in other words, if a sound is playing, and I do another sound.play(), the second will only start after the first has finished. It works as it should in firefox.
Anyone else experiencing this? Versions:
Impact: 1.20
Chrome: 21.0.1180.60
OS: Windows 7 Profession N SP1