The Big NW.js Roundup - News & Tips

From the Asset Store
Big Must Jump
$2 USD
60% off
Jump over the small square and avoid hitting it as long as you can!
  • There is still an ongoing bug with NWjs and basic browser actions. I don't know when they'll look into it but the current situation slows things down, as everyone probably knows.

    Workaround is to stay at the version mentioned inside the issue.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I will try but how do I install this version? By replacing the folders in NWjsforC2 directory or is there another process? Thanks

  • I will try but how do I install this version? By replacing the folders in NWjsforC2 directory or is there another process? Thanks

    For now I would just download it and put the "package.nw" file into the same folder for testing. Chrome 85 (NWjs v0.48.0) is coming out very soon. I'd recommend waiting for it and then using the installer.

  • (Please don't use single process anymore. It's always bugged and gives no advantages in general.)

    What do you mean by single process? Is that a NWjs flag?

  • Tested with V0.47.3 SDK after removing single process, with resizable enabled then disabled, it didn't fix it for me, I'll wait for the V0.48 to see if it improves anything, thanks for your time!

    Also yes Fib it reduces the number of process in the task manager to one + two crash handling processes (if I get it right), but apparently it is buggy so I'll avoid it for now;

    I've been using it so far because people were often confused as why a game would run up to 6/7 processes at once

  • Tested with V0.47.3 SDK after removing single process, with resizable enabled then disabled, it didn't fix it for me, I'll wait for the V0.48 to see if it improves anything, thanks for your time!

    Could you please make sure that you don't have scaling enabled. That's known to cause issues as well. In the future, please provide the capx and not just the exported files.

    Windows Scaling:

  • What do you mean by single process? Is that a NWjs flag?

    Also yes Fib it reduces the number of process in the task manager to one + two crash handling processes (if I get it right), but apparently it is buggy so I'll avoid it for now;

    I'm not saying to not use it at all, I just don't recommend it. In my testing it just made things worse. Longer startup times, worse performance on low-end devices and it also doesn't help with screen recording software detection. Those were the main reasons for why I removed it from the roundup.

    As a side note, you have to run "--disable-crash-handler=true" in command line. It won't work as a chromium arg, that's why you still see crash handler processes. For example appended to a shortcut or executed with a separate app (e.g. launcher).

  • That's why I asked if you needed anything else, I'll link a capx next time for sure;

    I won't have access to the other computer before one or two days, I'll come back to you at this moment to see if W10 scaling is for something in that bug;

    Also about single-process, when you say "it doesn't help with screen recording software detection", do you mean it makes it worse? Or it just doesn't make any difference?

    (I'm not experimented enough to implement --disable-crash-handler so I probably wont touch it)

  • That's why I asked if you needed anything else, I'll link a capx next time for sure;

    The example you provided this time was good enough but you never know.

    Also about single-process, when you say "it doesn't help with screen recording software detection", do you mean it makes it worse? Or it just doesn't make any difference?

    No improvements. It seems like most recorders don't work because of NWjs's way of rendering things and not the process structure itself.

    (I'm not experimented enough to implement --disable-crash-handler so I probably wont touch it)

    I just saw it inside your package.json file. Might want to remove it.

  • I removed it after the first test you made, since you specified it wouldn't work as an arg anyway;

    However I was using single process not for recording matters but more to avoid confusion with players with the multiple processes, some people who checked the task manager when testing my projects were mistrusful to see a game with 7 processes, I guess it's not very common in the video game domain

  • I removed it after the first test you made, since you specified it wouldn't work as an arg anyway;

    However I was using single process not for recording matters but more to avoid confusion with players with the multiple processes, some people who checked the task manager when testing my projects were mistrusful to see a game with 7 processes, I guess it's not very common in the video game domain

    Just tell them it's the game engine optimization at work. I think on Windows 10 the task manager shows all processes as one anyway.

  • > I removed it after the first test you made, since you specified it wouldn't work as an arg anyway;

    >

    > However I was using single process not for recording matters but more to avoid confusion with players with the multiple processes, some people who checked the task manager when testing my projects were mistrusful to see a game with 7 processes, I guess it's not very common in the video game domain

    Just tell them it's the game engine optimization at work. I think on Windows 10 the task manager shows all processes as one anyway.

    Had players on Steam question why my game local storage folders contain web browser histories and such, or multiple processes of nw.exe, and I always tell them its the engine I use, and point them a link to Node.js! Once they see a legit reason, its no longer a problem.

  • Thanks for the advices!

    I finally got to test the W10 scaling on HD screen to see if that was the cause, it was at 125% (the recommended for this screen), but now I understand why there is black borders :

    I made a test on another computer with W10 and the same size as mine (1366x768), but the game windows was smaller by 2 pixels and so the letterbox scaled it down, I think this is what also happen on the HD screen, the game should be fitting the windows but since the size is wrong by -2 pixels, it scales down and so creates the black borders, this isn't a problem of windows being larger but smaller;

    For the moment I'll go with resizable windows until V0.48 release, hoping it will fix it

  • 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

  • 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

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)