TheRealDannyyy's Forum Posts

  • Construct 3 - Launcher V2.2.1 Released!

    Small update that fixes some issues from the previous release. The web database received an update and should be more reliable now.

    Full Changelog

    To view it, go to the Main Post and click the Software Changelog tab.

    Cheers!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Known issue, reported here: github.com/nwjs/nw.js/issues/7542

  • This is GREAT! the launcher is very user-friendly, clean and simple!

    Thank you for this great tool for people who prefer using the desktop version such as myself.

    -

    Suggestion / request:

    Is it possible to make a "check" option for people who like it to create a shortcut on the desktop with the C3 icon? that will be SUPER!

    For now, I do it manually but the icon is NW.js... C3 shortcut will be perfect.

    Thanks ahead!

    I checked but it doesn't seem to be possible within the engine itself. I'd really like to avoid including a batch script just for this edge case.

    Ideally you should always use the launcher to launch C3.

  • Thanks! that's MUCH better looking than the NW.js icon :)

    Maybe the icon file should be included in the setup of the launcher? (for future versions)

    It isn't really necessary because NWjs automatically applies the included PNG file as the app icon on startup. Anyway let's keep Launcher related stuff in the Launcher topic.

  • Again, it's not critical because it's just an icon, "cosmetic" user experience, nothing more because everything works :)

    You could also do the following:

    1. Right Click on "nw.exe" > "Create shortcut"
    2. Rename the shortcut to "Construct 3"
    3. Right Click the shortcut > "Properties" > "Shortcut" > Change icon
    4. Select the Construct 3 icon and apply (download)

    Always keep "nw.exe" at the same location. The shortcut should keep working, even if you update NWjs by extracting and replacing files inside the existing folder.

  • Hi! Would it be possible to get a Linux port of this or would that be too much of a hassle?

    Sorry I can't. The engine I used to make this only supports Windows.

  • Hey,

    After speaking a bit with Dannyyy, I cleaned up the updated ForceRedraw addon I made.

    https://www.construct.net/fr/construct-2/addons/435/greenworksredraw ...

    Thanks! I've tested "Activate constant redraw" using letterbox integer scale and it worked as expected. From my measurements, this has next to no noticeable performance impact but it might vary based on the device.

    Updated the Roundup with this new info. If you decide to port it to C3, please add a "tip" with a C3addon link to the top of your addons page. Should be good enough for people to find it that way.

  • Construct 3 - Launcher V2.2.0 Released!

    This is the last major update. It adds an option to select custom NWjs release build versions. Making it possible to up/down-grade or stay with a specific version of NWjs. The old custom NWjs release build is now the default release build and can be one-click updated.

    The entire update system is now fully automated and runs its own versioning database (service provided by armaldio).

    Full Changelog

    To view it, go to the Main Post and click the Software Changelog tab.

    Cheers!

  • These scripts will probably work fine but I think it would still be better to wait for the core issue to be fixed. From my experience any NWjs version before v0.46.3 worked fine.

    If it doesn't, please give me a heads up.

  • Thanks for the info I'll try disabling node workers in the next build. I usually patch on Fridays so it will be a few days.

    Only do this if your game doesn't run in worker mode.

    It would still be better to find a clear way to reproduce instead.

  • "user-agent": "Mozilla/5.0 (%osinfo) AppleWebKit/%webkit_ver (KHTML, like Gecko, Chrome, Safari) NWjs/%nwver",

    "chromium-args": "--enable-node-worker --disable-plugins --disable-internal-flash --disable-popup-blocking --allow-file-access-from-files --ignore-gpu-blacklist --in-process-GPU"

    }

    Looks alright to me. The "--enable-node-worker" arg is exclusive to C3 and needed if you run your game in worker mode. NWjs worker mode did make problems in the past, it could be in conflict with "--in-process-gpu" but it's difficult to tell. If you don't use worker mode, I'd recommend removing "--enable-node-worker" and try to reproduce again. At least this way we could try to isolate the underlying cause.

    When you say you get reports of it not launching or running the in the background. Do you mean on Windows or other operating systems?

  • It definitely doesn't work in nwjs, I use Construct on desktop via nwjs and I tested exporting multiple projects ot nwjs. None of my projects work. I also just recreated a very simple project in nwjs and tested - it didn't work

    There seems to be a strange bug with NWjs v0.46.3+ and performing basic browser actions. This affects more than just requesting fullscreen.

    I've reported it here: github.com/nwjs/nw.js/issues/7542

  • No problem, bug report is here:

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

    Not sure if the route of this going to end up being construct or chromium, but something very odd is that it does work when you right-click on the project name and select preview project. However if you preview the project using the dropdown shortcut on the toolbar it doesn't work. It also doesn't work when you export as nwjs project.

    Outside of NWjs this is expected behavior. As Ashley said, it requires a user gesture for obvious reasons. If you however experience this in NWjs, that's a bug. NWjs should by default allow requesting fullscreen without a gesture or any additional permissions.

    Do you experience this in NWjs or does it work as expected there?

  • Would you mind uploading your "package.json" file? I can be found inside the exported folder if uncompressed or compressed inside the "package.nw" file (rename to ".zip" and unzip).

  • > Default fullscreen can be achieved by simply running the Browser action "request fullscreen" on start of your 1st layout (ideally based on in-game settings).

    TheRealDannyyy that's exactly what I have always done, it has worked for a long time but it no longer does. I submitted a construct bug which was immediately closed as 'not a bug'. Perhaps this is a new problem for all of us exporting to desktop.

    Please link to the report. Might be one of those days for the Scirra Team.