No more sound in Chrome

That's a new chromium "feature".

Chromium bug

Corresponding blog post by Ashley

Edit: Oops, I didn't see that there are two pages in this thread, only read the second one. I guess this has already been clarified.

Is this fixed in Construct 3 R98 (last stable)?

Because.. if I start my code within Construct and try to play a sound (or mutliple sounds) after initialization of my layout, nothing happens.. I need to press a key (or input in general) first.. then all sounds start playing.

UPDATE: Never mind.. R100 is the last stable... my offline version was still R98, so it couldn't work out..

Because.. if I start my code within Construct and try to play a sound (or mutliple sounds) after initialization of my layout, nothing happens.. I need to press a key (or input in general) first.. then all sounds start playing.

That is the fix. Chrome doesn't let pages autoplay without interaction any more. Previously you might not have heard any audio at all.

FWIW Google just announced that they will revert the autoplay change... and then reinstate it in October. This is totally bananas because it will just repeat the same problem, but later. Still, you have more time to re-publish content now.

FWIW Google just announced that they will revert the autoplay change... and then reinstate it in October. This is totally bananas because it will just repeat the same problem, but later. Still, you have more time to re-publish content now.

So will the new standard be like Browser>RequestFullscreen? (requiring a user interaction). So we should always have "CLICK TO START" at the beginning of our games? Will NWjs eventually implement this as well?

It's the same idea, yes - you need a user input event to unmute audio. However the difference is Construct automatically unmutes audio for you at the first opportunity. So you might not need a "click to start" preloader, unless you want to avoid sounds being cut off prior to the first input.

NW.js won't ever implement this - they've already turned off user input requirements, e.g. you can request fullscreen at any time in NW.js, whereas the browser requires an input event.

It's the same idea, yes - you need a user input event to unmute audio. However the difference is Construct automatically unmutes audio for you at the first opportunity. So you might not need a "click to start" preloader, unless you want to avoid sounds being cut off prior to the first input.

NW.js won't ever implement this - they've already turned off user input requirements, e.g. you can request fullscreen at any time in NW.js, whereas the browser requires an input event.

good to know, thanks!