Thanks Ashley, Is there an example or capx demonstrating usage

Yes there is, the template/example is called "Canvas Recording" and it's included in C2.

Going back to working on C3 now.

Hi all,

We've hit an issue where latest nw.js v0.19.2 (Chromium 55) 32bit builds crash immediately as they boot up, but 64bit exports work perfectly.

...

Do you have a lot of sounds in your game? Keep in mind that sounds will remain loaded into RAM regardless of the layout to layout un/loading.

(The community already worked out a plugin to unload audio from memory but it's currently in an experimental state, that's why we keep it private for now.)

Is it possible to have the option to switch to a 64bit nw.js preview in C2?

For the preview you could do a sneaky workaround by renaming the folders temporally, just don't forget to rename the folders back again when you do the exporting.

Hi Ashley, What is the canary flag you are referring to

Already supported in Chrome and NW.js, no need for flags or other workarounds anymore.

The signalling server is now hosted with Rackspace (we moved it recently). The recent crash was due to a bug in the signalling server software which I subsequently fixed and updated the server with the patch.

...

Thanks a lot for the info. Hoping that my game will reach about 5% of Scirra's connections per month, there will most-likely be no crashes at all on my end, if they're somehow related to that. Setting up the server shouldn't take longer than a weekend and for the given price, it's great to hear that active support is included. Although I'm currently not really feeling the need to buy and run my own server, Scirra's server is doing the job just fine.

I'm not sure if this has been asked already but would you maybe consider adding a monthly restart to reduce the chances of the server crashing? The most server-hosters offer automated systems/scripts to do that. I think it would be better to have one predictable downtime each month instead of having a crash every few months (not constantly ). The plugin expression onerror could return the message that "it's down for maintenance" as well.

Obviously the community should be asked about this as well (maybe in form of a poll), if you would consider adding this.

Let me explain.

The video recording issue was related to the flickering issue. It was reported to the Chromium team and fixed with Chromium 56.

The point is that there is no NW.js version based on Chromium 56 yet and that's why we still have to use --disable-direct-composition as a workaround.

...

EDIT: What BackendFreak said below, changed roundup back to v0.19.1 as expected.

—: I don't know which one was specifically in cause.

All I know is that the server is far from "constantly" crashing (at least according to the dates in this topic, the previous crash issue was during October 2016, that's not what I would call "constantly").

Moreover, anybody running a website and or software on a server knows that they need regular rebooting and other maintenance (whether hardware or software).

...

Alrighty, still very thankful that Scirra takes care of the hosting for us.

You seem to be working very closely with Ashley, if you're allowed to I would like to ask you a question. Could you maybe share the name (or link) of the hoster that Scirra uses?

I would like to work with a trustworthy hoster and if Scirra decided to work with the current hoster, it must be trustworthy in my opinion.

I'm interested in buying a server for my commercial game and hosting from my private home-server doesn't seem to be the best option since it's mostly busy with hosting other game servers and services.

Server had crashed and has been reboot now.

If you have questions about reliability you can always buy the signalling server software in the online shop and run it on your own hardware server to keep a constant access on your server and configure it as you like.

Thanks for getting it back online again!

To be clear, when you say "server had crashed", you mean the actual server and not the software itself right?

I see no point in buying software that constantly crashes on me, I'd rather let Ashley do the job of maintaining it instead, if the software is at fault of course.

I noticed you're using the old OBS and not the new "Studio" version, I thought that might help, but it doesn't work either

When I switch out of the game window and it loses focus I can see the NW.js window frame with the game title in the recorder but the inside window is still black.

My game is already live on Steam for a few days now, but it's in early access, so maybe they treat it differently.

Make sure you record the inner window only and set the "sub-region" correctly. (No clue about version differences, I use Action!. )

I wish I could provide better help but NW.js and game recording/steaming is still a big issue and it looks like the upcoming versions will not fix these issues as well. I've tested out the latest NW.js nightly build with the recent Chromium version, game recording is also not working for that one.

I still think that single processing (when it works as intended again), will fix these recording issues.

I was talking about windows capture, it still needs the --disable-direct-composition to work, I couldn't get game capture to work for quiet a while now regardless of version or args.

Oh I didn't know Steam had it as a requirement, good to know, I was taking my time with it, I'll add it asap.

Nope it doesn't on my end, I'm using the exact same args and the same NW.js version and it works just fine.

Preview using "Window Mode" | "Window Mode" Properties | Recorded Video Playing Back In VLC (1080p@60fps)

As far as I know Tinimations (creator of Klang) had to add it in order to pass the certification process but I'm not sure.

It's really hard to tell if you have to do it or not, I recommend trying to submit your game without it first and see if the certification process starts complaining or not.

Has the server crashed again or is it just for me?

Can confirm it's dead again...

Ashley Could you investigate the problem please, feel free to keep us updated about the cause for the downtime.

I was talking about windows capture, it still needs the --disable-direct-composition to work, I couldn't get game capture to work for quiet a while now regardless of version or args.

Works totally fine without --disable-direct-composition and without --single-process on my end, might be related to wrong settings or hardware differences?

EDIT: Please upvote (react) THIS report of mine so we can get this single processing bug out of the way.

Oh sorry I missed that, here it is:

--disable-plugins --disable-internal-flash --disable-popup-blocking --enable-gamepad --enable-html5-camera --allow-file-access-from-files --disable-software-rasterizer --ignore-gpu-blacklist

using NW.js 0.19.2 on windows 10 64bit with obs studio 17.0.0

So I've tested "game capture" and it's indeed not working (detection issues probably related to multiple processes).

Unfortunately our lovely NW.js team broke --single-process once again and I will have to create a bugreport soon (It's running 2 processes instead of 1).

As a temporally workaround you can use "window capture" mode, my tests were successful using that method.

Quick question, why are you targeting

%LocalAppData%\GameName\User Data[/code:dpjggi5h]
For the uninstall script and not [code:dpjggi5h]%LocalAppData%\GameName[/code:dpjggi5h]
Is there any reason to keep the other cache directories on the root directory of the game?

I think that's the folder that Steam/Valve complains about and that's why we delete it but Madspy is one of the few people that has experience with that, so I'm just speculating.

Generally there should be no issues with deleting the whole folder I guess, since NW.js will just recreate all the files on the next run.