Ricardo
Member
Hey guys!
Using runtime 2.1.4.288 and Chrome 66.0.3359.139 (PC, Windows 10), I'm getting an error like this as soon as my game starts:
The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page.
Then, as you can expect, audio doesn't work in the game. This kind of issue was well-know in HTML5 mobile games, but this limitation for Desktops appears to be a very recent change in Chrome's Autoplay Policy Changes.
Does anyone know a workaround for this or have some info? I have some big projects in production affected by this issue and the old trick (play a sound in a click/gesture event) doesn't seems to work as the AudioContext doesn't even start and it crash during the game loading, even before the application starts.
Re-build my projects right now using a old runtime (this bug doesn't affect runtime 2.1.4.189) isn't also a good option for me at the moment, unfortunately...
Using runtime 2.1.4.288 and Chrome 66.0.3359.139 (PC, Windows 10), I'm getting an error like this as soon as my game starts:
The AudioContext was not allowed to start. It must be resume (or created) after a user gesture on the page.
Then, as you can expect, audio doesn't work in the game. This kind of issue was well-know in HTML5 mobile games, but this limitation for Desktops appears to be a very recent change in Chrome's Autoplay Policy Changes.
Does anyone know a workaround for this or have some info? I have some big projects in production affected by this issue and the old trick (play a sound in a click/gesture event) doesn't seems to work as the AudioContext doesn't even start and it crash during the game loading, even before the application starts.
Re-build my projects right now using a old runtime (this bug doesn't affect runtime 2.1.4.189) isn't also a good option for me at the moment, unfortunately...