TheRealDannyyy's Forum Posts

  • The Roundup has just been updated!

    This update mainly includes updates to existing workarounds to get your games to work right with Steam, while using more recent versions of NWjs.

    There will soon be more news posted on how to use the Greenworks plugins with newer versions of NWjs. Stay tuned by following this topic!

    Changes:

    • <Added> How To: Workaround Steam Overlay Displaying Window Content
    • <Updated> How To: Workaround Steam Overlay Not Refreshing
    • <Updated> How To: Workaround Steam Overlay Not Appearing

  • Thank you, so why doesn't Ashley publish how to convert NWjs to C2 / C3? So we don't have to wait for those we don't want to wait for.

    No reason to since he's providing them already (sometimes slower but still). There is also the problem of user errors caused by not downloading and installing stuff the right way.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Construct 3 - Launcher V2.0.0 Released!

    Complete overhaul of the launcher. It now does everything including downloading and updating Construct 3. Adding to the monthly Construct 3 official build updates, there are now future proof custom builds of Construct 3 available, for when the official builds get deprecated.

    Full Changelog

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

    Cheers!

  • Is there a list of steps to prepare a version of NWjs for C2?

    So I don't have to wait for the official launch of Scirra.

    It's pretty straight forward. You just have to go to their website, get the files and put them into your NWjs source folder. Keep in my mind that their versions are bloated and don't have the DirectX dependency, which some PC's might require.

    Ashley based on the blog post, v0.42.1 might be significant enough to justify an update for C2/C3 desktop exporting and C3 desktop in general (web worker crash fix). Would you mind updating when you find the time to?

  • > Here is the report for the startup performance regression: github.com/nwjs/nw.js/issues/7192

    >

    > Will wait with the other report until there is more info available.

    I think Roger just fixed it in today's nightly build :D Awesome work!

    I will check it out later and ask for the release date. If you follow the issue there you'll know.

  • Here is the report for the startup performance regression: github.com/nwjs/nw.js/issues/7192

    Will wait with the other report until there is more info available.

  • I forgot to say, my system is win10 Home 64 with the latest update.

    Good to know. I can reproduce it on Win7, they'll probably end up testing on OSX and Linux.

  • The only thing I change in package.json is the last instruction that I add manually :

    --disable-devtools

    Alright, no problems here.

    Then I follow your instructions to use the tool to secure the assets...

    This is a very outdated feature which might have been broken over the years. I'd honestly recommend not doing this anymore because it really doesn't matter. People that want to steal your project's assets, will be able to do it regardless. Not only that but it will also increase startup loading times by quite a bit, depending on your project.

    I removed this now. Again, you can keep using it but I don't recommend it.

    My problem is that our customers are not happy with the bug, and DO NOT want to be beta testers of my different tries to find a solution.

    I know but there is not much the NW team could do with a report stating the stuff you mentioned.

    I'll check this also, but it seemed to me that the last windows update was 2+ years old.

    As long as they use an OS that is supported by NWjs, it should be fine from the OS side of things. Outdated drivers can still be an issue. You could test this in the future by checking if "WebGL" is supported on startup and displaying a prompt if it isn't. There should be a condition for that.

  • Here I have uploaded an empty project exported with NWjs.

    https://www.dropbox.com/s/881v2to5wf4nfnq/errorNwjs.rar?dl=0

    It takes approx 10 seconds for the NWjs window to appear.

    Sometimes it takes a little less time.

    Then the problem:

    In C2 when I press the "Run layout" button and the nwjs window appears, this window remains black for a long time until the game starts.

    With the exported project, in most cases the NWjs window takes a long time to appear.

    Thanks but I could actually reproduce this already. Will use this anyway for consistency. it's gonna take a bit of time before I create the report, I'll post a heads up when it's done.

  • —ACCES-Mathieu If you modify the package.json file after exporting, please also provide the edited version. So far I can't notice anything special with the files.

    ACCES-Mathieu The only version I could find is the one released on the 12th August 2019 (v0.40.1), I will base the report on that. I still need more info.

    Any minimal project for reproduction would help. Since part of what you're reporting is a crash, could you please ask a user to zip up the folder called crashpad? I know it's probably something you'd like to avoid but there are no other options, unless you can provide something for reproduction. [%LOCALAPPDATA%\#PROJECT NAME#\User Data\CrashPad]

    A common point between them is that their Windows are not kept up to date.

    How outdated are the systems? The problems that come with outdated systems are usually not caused by the OS itself but by the drivers not being up to date. Most of them are included in the Windows Updater nowadays. Issues with the renderer (e.g. outdated graphics driver) should be inside the crashlog as well.

  • In my case, version 0.42.0 has not solved anything.

    The screen is now black when it was previously white but everything remains the same.

    The startup takes a long time while the screen remains black.

    Nothing has changed.

    Alright next step would be narrowing it down so I can do proper bug reports.

    Current issues:

    • Slow startup [V0.41+]
    • High CPU usage + Crashes on older Windows systems[?]

    ACCES-Mathieu — Please provide the version this started happening and try to narrow it down if you can. How old are systems you both are basing this on? Any minimal project to reproduce and providing your package.json* file would help.

    — Is it correct that this started with V.0.41? Could you also please provide your package.json* file for reproduction.

    (*See "Important Files & File Paths" to find it.)

  • Everyone that reported issues with NWjs and performance/bugs recently. The new version is out and available for both Construct's. Please test it and do a post if your problems have been fixed or are still there.

  • I've discovered that updating from 272 to 273 reduces performance with many SHADOW CASTING objects on screen.

    I'm asking someone else to reproduce the problem, confirm it, and possibly build a CAPX to show that to Ashley, as that's a major issue for me and i guess for some of you.

    If it's only happening in NWjs I could look into it, else it's kinda unrelated to this topic.

  • Found this info from Eren on how to revert to older desktop releases:

    Open "package.json" and edit "main" line

    (image here)

    I've written a small native App that does exactly that. You can try it out yourself if you like: construct.net/en/forum/construct-3/general-discussion-7/construct-3-desktop-simple-lau-139502

    In a week or two, I'm going to release an overhauled version with even more features like automatic updating and using custom release builds (e.g. for use after the official release builds have been deprecated). If you follow that topic you'll get a notification when it comes out, currently in testing.

  • There are probably loads of cases along the lines of "use keyboard to close something that you currently have a context menu open for". To be honest, given we have limited resources available for maintaining C2 I'm not sure it's worth spending that on tracking down all sorts of edge cases like this, versus more important issues.

    I guess this should be the last one then. These two are quite common in my opinion.