Construct 3 NW.js desktop app [Deprecated]

The desktop app is great - really easy to setup.

Quick question: when developing addons and using the "add dev addon", what URL should we use to refer to the webhost nw launches?

Assuming I have everything setup on the defaults folder and I have the addon folder in there with this structure "addons/myaddon/addon.json".

I cannot load my project. C3 nwjs is stuck forever loading files.

NWJS and C3 up to date.

Here are some details:

1. When loading the project

2. Memory use: it should be around 1,6 Gb - which means not all files are loaded.

It doesn't matter if I start the C3 in elevated mode.

What is weird - opening the project succeeds in 1 on 10 tries.

Anyone encountered the same problem?

Just popping in to say that this solved my performance issues in the browser. While I think the browser integration is fantastic, and certainly has its place- a pure-browser stance isn't what I prefer.

I don't know what the community consensus is, just contributing my two cents.

SecondDimension Try changing the Script mode in the project. Might be a similar issue to the one I posted:

github.com/Scirra/Construct-3-bugs/issues/4524

dop2000 Thanks for letting me know, I tried it and still getting the issue though unfortunately. I know these things are always a fight over who is at fault, but on this occasion I updated Construct and not nwjs, then the issue appeared, and it's across every one of my projects.

Not sure if this is related, but I had issues with r235 not previewing, it worked on and off, but mostly off.

I couldn't manage to pin the problem to report it, but I got a bunch of domside.js (if I remember correctly) errors on each of the plugins (official and 3rd party), see if you get those.

I reverted back to r233 for now.

Ashley maybe we could try Edge Webview2 for the desktop if you get it working?

Hi everyone, so I logged on today after a few weeks away from C3 and realised there was another stable update, and that means obviously that my desktop install breaks :(

I can't use the debugger, on any project. Anyone else having this issue at all?

EDIT: Tried upgrading nwjs in case that was an issue, so I have tested on nwjs versions 50 & 51, and debug does not work for me on either since the new updates. Running Debug just results in the application closing with no error.

Same issue here. Preview works fine, but debugger just causes the app to crash without any error messages, which makes debugging difficult.

This is on a brand new PC with a fresh installation of Windows 10, but I had the same problem with my previous PC as well. That went away somewhat mysteriously, but I can't find a way to solve this issue now.

Using the NW.js 0.51.1 and latest stable version of C3.

I did a quick test using TheRealDannyyy's Construct 3 Launcher and I can confirm that the issue cropped up with r234 and onwards. Reverting to any release before r234 prevents the issue.

Unfortunately it's too late for me to roll back to r225 for my current projects, so I'll have to make do without the built-in debugger until the issue is resolved.

Once again this brings up the concern of forced "stable" updates in the desktop app, but it seems to be an argument that ends with nobody being happy. For this reason, the desktop launcher is an absolutely required tool for anyone working on any commercial projects, and I'd love to see it incorporated in a formal fashion.

Sorry for spamming, but I have another update. I reverted and updated both NW.js and C3 multiple times.

After more testing, I rolled back to NW.js v0.51 and it started behaving itself. But then I updated back to v0.51.1 and now it's working again. That might've been the mysterious fix I stumbled upon previously.

Anyway, if anyone is having issues, try roll back NW.js, then update to the latest version. There might be more playing around you need to do, but eventually you might find the combination of versions that works for you :P

GeoffB - nice to know it's not just me! I would love to turn off updates for the desktop version, so I could get a stable setup and know it won't change until I want it to. From previous responses on the subject I don't think it's going to happen though. It affects me a lot because I only do this part-time, so have big gaps between periods of gamedev. I usually take a day or two off from my full time job to work on my games, and because I leave big gaps there is often an update. So I find I spend most of my time off fighting upgrade issues with nwjs or similar, rather than working on my games. Perhaps I am just unlucky.