It's a bit weird with the recent iOS, if you test your game and it plays music, you can see it in the AirDrop menu, the exactly folder & music file name is displayed.

I think Apple is doing some funky stuff, if it detects Safari playing audio it somehow separates it to it's main audio player for other purposes.

The thing is our wrappers are Safari based and iOS is treating it like a website and not a standalone app.

This must be a plugin issue though, checked around on the steamworks forum and nobody has experienced this before, and people said that the overlay has nothing to do with GPU. So my guess is that it's a plugin/c2/html5 issue which hopefully means Ashley can fix it

It's a NWjs/Chromium issue.

Nothing related to C2 or Greenworks.

Its just the way NVIDIA treats the detection of Chromium.

Do you guys have the audio/music bug on iOS with CocoonIO?

There's other threads too, they know about it but nothing has been done and it seems to be a case of "OSX-issues"... seems to be a lost cause.

0.10.5 works for even moderate sized games. However, over 1000 images and it often encounter the same red loading bar.

The thing is OSX has the new Safari that is much faster than Chromium. There should be a Safari based wrapper, similar to the mobile approach. Very small filesize overhead, much more compatibility.

Ashley

This is a NWjs bug, not C2. On Github, it's a well known problem. Some of the fixes suggested by folks in this thread spawn from github discussions.

0.10.5 was the last NWjs that works on MAC for me.

Everything else since is just the red bar load scene being stuck.

Even with all the attempted work-arounds, for some reason if your game has lots of assets/images, it will not work on MAC with NWjs.

The problem with 0.10.5 is a very nasty memory leak bug (which wasn't fixed until NW 0.13 builds!), in smaller games it's not so noticable, you have to play for an entire day to start seeing memory usage explode and the game stutters/crashes. Bigger games get to this point faster, ~30 minutes for my latest game.

That's why I went with NW 0.13 alpha7, as it fixed the memory leak bug, rendering is very smooth and performance is good.

But it's broken for GreenWorks support, and newer C2 builds will crash on NWjs older than the 0.13 betas (which are buggy).

Overall, not a good situation for PC export options for bigger games, and MAC is even worse.

Of all the things I love about C2, exporting builds to the different platforms has been the worse experience by far. If that's something C3 fixes, it would be the best 2D game engine around.

Performance is poor on Android, due to the JS engine of Chromium being pretty slow compared to Safari. Apple's Nitro JIT is insane fast.

For mobiles, avoid using any of the C2 shader effects, ie. don't add effects to your sprites. It's extra slow on mobile.

The new NWjs beta 5 does that, it cannot exit the game properly, the instance is still running.

You need to hack it to fix that bug.

so which versions of (C2>NWjs>Greenworks>SteamSDK) work for you.. all together? or does anything work at this point?

None for the new NWjs 0.13s.

I only wanted the Steam achievements but if its not possible, oh well.

I wonder how the subscription service works, if your sub expire, does the game no longer work? Or it's just you no longer can build but the existing game works fine?

Yeah doesn't work on my main PC, using a nvidia gpu. Damn

Yeah very annoying that Steam overlay injection fails on many NV GPU, since NV are the dominant dGPU brand, very popular for gamers.

So the current setup:

C2 (v218)

NWjs 0.13 alpha7

Greenworks 0.13 (for NW 0.13)

works?

and by 'works' I mean only on some systems?

Nope.

C2 latest

NWjs 0.13 beta 5

Ashley's latest Greenworks

Latest Steam SDK

I don't know if it works for others, but it doesn't for me. Game hangs on start-up. Also beta 5 doesn't exit properly, requiring a hack-workaround to fix it.