TheRealDannyyy's Forum Posts

  • Everade Thanks a lot for the effort!

  • Uploading a blank, desktop exported nwjs project would make things even more convenient for me but a screenshot is also fine.

  • I'd like to gather information regarding the current state of exported NWjs projects and how they are being provided by Scirra. Specifically which files have been included/excluded and their purpose.

    Would appreciate if anyone with an active license could:

    1. Export a blank NWjs project (latest version)
    2. Unzip the exported archive (if required)
    3. Upload screenshot of the file structure

    Example:

  • > > Has there been any luck with the fullscreen/ close function?

    > > it seems with each update to C3 it breaks further and further.

    > > I think i am going mad with these bugs lol

    >

    > Still investigating: github.com/nwjs/nw.js/issues/7542

    TheRealDannyyy

    I have a work around for the close issue, if you want to add it to your list.

    Use the action - Browser -> Execute Javascript

    And run this:

    "var gui = require('nw.gui');

    var win = gui.Window.get();

    win.close();"

    There are too many issues with C2's NWjs plugin. You are generally better off using Construct 3.

    I know that Javascript can seem difficult and overwhelming at first but most window related issues, can be worked around by executing JS and a selected function like in your example.

    when someone plays the NWjs export, and plays it "windowed" is there a way to save their window settings and position for the next time they play?

    I didn't know players would even want this feature until I got feedback on it!

    I would save the window state (position, fullscreen/windowed, size etc.) as variables and run actions on startup. NWjs should by default save these but it might be broken for various reasons.

  • THIS PROJECT HAS BEEN DEPRECATED!

    The software itself might keep working but I will no longer provide support. Thanks for using it and thanks again to armaldio for additional help with the back-end.

    Scirra has officially retired running Construct 3 inside NWjs. For more information and alternatives. Please read the release notes and the forum post, for remote previewing your projects in NWjs instead.

  • Would be cool if you guys could update the tutorial's confusing/broken parts, so that others don't run into the same problems in the future.

    Also a big thanks for doing this ACCES-Mathieu!

  • This has been super useful! Thanks!

    One thing I can't seem to figure out right now is that the Browser: Close command doesn't work correctly after I set it up for Steam. This happens pre-upload to Steam, and I'm still not 100% that it's the Greenworks itself but so far in my process that seems to be the dividing line between when it works or not.

    What happens normally is that Browser: Close turns off the game and closes the window.

    What happens after replacing the Greenworks files is that Browser: Close will turn off the game but the window itself will remain. This happens on both Windows OS and Mac OS.

    Any ideas about this?

    Current Version: 0.52.0 using Construct 2

    This is a bug with the Construct 2 NWjs plugin. Many plugin actions have never received proper updates to support more recent changes.

    Try adding the browser plugin and use the "execute javascript" action to execute this code:

    "var win = nw.Window.get(); win.close();"

  • Ok I uploaded it via wetransfer but the link is not supposed to last more than a week.

    If this is for public access, you should find an alternative that lasts forever. Maybe GitHub or similar platforms will work out.

  • I can't upload the zip file with all the needed scripts because they have unsupported extensions. How can I do that TheRealDannyyy

    You could try to directly upload those files to a cloud service and see if that works.

    Oh and BTW TheRealDannyyy you are allowed to edit this tutorial if you want to.

    Thanks for the access but I have no clue about MacOSX at all, so I doubt I could provide any kind of help regarding this.

    I'm currently still converting this topic into a tutorial. I will make sure to reference your tutorial when things are ready. (Old forum topics like this one, turn into "read-only" after a while.)

  • > Hi MoonMonky,

    > feel lucky that I read this because you didn't tagged me and I'm not always checking forum posts.

    > I just made a quick test-sign with my signing method and it worked.

    > Unfortunately, the signing method kinda evolved since this message with the help of a real developer. And even if some files are still used, NWsign.sh for example is not used anymore. I'll try to find some time to retrace what has changed in the process.

    > cheers,

    > M

    Hi ACCES-Mathieu!

    Wao, I thought that a quote was enough for a notification!

    I thought that the process must be evolved as Nw.js continue to update.

    If you want to explain how to do it would be amazing!

    I can't find anyone on web who explain how to sign a Nw.Js exported file clearly.

    I can offer you a coffee via Paypal if you'd like, just pm me ;)

    Cheers

    Please do not do this privately. It would tremendously help if the entire process was explained in a place that's open to the public.

  • Hi there,

    What about Steam Overlay Feature on Mac exports?

    I can't manage to get it work correctly.

    If none of the mentioned methods work, I can't really help. I have no experience with MacOSX and NWjs support for their latest OS architecture is still experimental at best.

  • If you look around in the registry you should find HKEY_CURRENT_USER\SOFTWARE\Scirra\Construct2\NodeWebkitPath, which is the first path it checks.

    If it can't find NW.js at that path, it checks a hard-coded fallback list of the following paths:

    C:\Program Files\NWjsForC2\

    C:\Program Files (x86)\NWjsForC2\

    C:\Program Files\NodeWebkitForC2\

    C:\Program Files (x86)\NodeWebkitForC2\</p>

    Thanks for the info! I'll just tell people to put the NWjs files into one of those file paths in the future.

  • C3 keeps defaulting my loader style to "C3 splash screen".

    https://github.com/Scirra/Construct-3-bugs/issues/3744

    I'm not sure if this is a problem with the launcher or with C3, since Ashley thinks it might have been fixed.

    This looks like a C3 issue. Ashley explained it quite well in the issue post. The launcher doesn't have anything to do with NWjs startup times, it just lauches NWjs and closes itself.

  • Is the path for the NWjs file/folder check always "C:\Program Files\NWjsForC2" or is the path stored somewhere in the registry or a config file?

    Was going to provide installers myself but I feel like it's not worth it, if the path is absolute and never changes. People could just download the files and put them there themselves.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I don't see any point to open sourcing it. It's just a tiny tool that does one very specific job.

    Was just out of interest. I've never been able to get Windows to cooperate with app icon editing and refreshing the icon cache.