How to Update NW.js to Dramatically improve Game Performance!

[KillerGin]

Hey, thanks for the suggestion. I tried replacing SceneManager.exit(); with SceneManager.terminate(); but unfortunately it's providing the same result... everything fades to black, window goes from fullscreen to windowed, but never closes the actual game window.

Ah, well, I actually use "SceneManager.terminate();" in a small plugin I wrote that is tied to the menus and it works, even though I am using 49.2 I think it would work for you as well.

Here is a small part of it:

"Scene_GameEnd.prototype.exitCommand = function(){
SceneManager.terminate();
}; "

 

[Ace of Spades]

Ah, well, I actually use "SceneManager.terminate();" in a small plugin I wrote that is tied to the menus and it works, even though I am using 49.2 I think it would work for you as well.

Here is a small part of it:

"Scene_GameEnd.prototype.exitCommand = function(){
SceneManager.terminate();
}; "

Yeah, that's pretty much the same function I'm using. I even tried to revert back to 49.2 to see if it'd work and it was still giving me the same issue.

After thinking it through, I tried to deploy the project to see if that would work. Turns out this bug only occurs when test-playing from RMMV. I was able to revert back to v 0.51.0 and the bug did not occur after I tried to deploy the project, which was a huge relief. As long as the bug doesn't occur in the final build of the game, I'm perfectly okay with manually closing the game window during test play.

Thanks so much for your time and efforts, it's greatly appreciated!

 

[Hudell]

  if (Utils.isNwjs()) {
    require('nw.gui').Window.get().close();
  } else {
    SceneManager.terminate();
  }

 

[KillerGin]

Yeah, that's pretty much the same function I'm using. I even tried to revert back to 49.2 to see if it'd work and it was still giving me the same issue.

After thinking it through, I tried to deploy the project to see if that would work. Turns out this bug only occurs when test-playing from RMMV. I was able to revert back to v 0.51.0 and the bug did not occur after I tried to deploy the project, which was a huge relief. As long as the bug doesn't occur in the final build of the game, I'm perfectly okay with manually closing the game window during test play.

Thanks so much for your time and efforts, it's greatly appreciated!

Hey, as long as it works for the deployed version, thats what matters, yay!

 

[TenTranVN]

Does it improve performance better when manufactured to mobile?

 

[Hudell]

Does it improve performance better when manufactured to mobile?

mobile doesn't use nwjs

 

[villko05]

I guess I only need to update PC windows folders and deploying to mac/linux it'll use windows new nw.js?

P.S With the most recent version nw.js v0.51.2 I get multiple bugs/errors. One-time parallax map was all black throughout the saves (parallax failed to load for all saves).
My custom save/load menu was stuck had to close the game and overall doesn't look stable (a couple of errors etc.)
+issue with not closing properly for "test" build (delayed closes properly).
+in game's/project folder file "package.json" don't forget to add
"position":"center"
just before fullscreen to properly position your game.

Will try v0.49.2, I hope it's more stable.

P.S.S and unfortunately getting this randomly. I think this happens when showing pictures.
I have Pixi updated to 4.8.9 in my project. First time seeing this error, probably 99,9% caused by new nw.js.



P.S.S.S
Upon further testing, I found updating nw.js to be very unstable. I get many black screens. Sometimes battles start with a black screen while audio still playing, sometimes opening F8 will make the game screen black. This could happen only in the editor as I haven't tested deployed projects and this can be caused by many plugins I use (it's a complex project with over 250 plugins+compatibility fixes).
I'd love some extra performance, but this seems very unreliable.

P.S.S.S.S
Using nwjs-sdk-v0.44.6-win-x32 (because I want to support even old x32 platforms and the difference between x32 vs x64 seems non-existent) seems to be stable, but needs more testing. So far no black screens or errors. And the Editor test game window closes properly now.
I Will update about stability within a week and further testing, but it seems working fine.

 

[KillerGin]

I guess I only need to update PC windows folders and deploying to mac/linux it'll use windows new nw.js?

P.S With the most recent version nw.js v0.51.2 I get multiple bugs/errors. One-time parallax map was all black throughout the saves (parallax failed to load for all saves).
My custom save/load menu was stuck had to close the game and overall doesn't look stable (a couple of errors etc.)
+issue with not closing properly for "test" build (delayed closes properly).
+in game's/project folder file "package.json" don't forget to add
"position":"center"
just before fullscreen to properly position your game.

Will try v0.49.2, I hope it's more stable.

P.S.S and unfortunately getting this randomly. I think this happens when showing pictures.
I have Pixi updated to 4.8.9 in my project. First time seeing this error, probably 99,9% caused by new nw.js.

View attachment 180791

P.S.S.S
Upon further testing, I found updating nw.js to be very unstable. I get many black screens. Sometimes battles start with a black screen while audio still playing, sometimes opening F8 will make the game screen black. This could happen only in the editor as I haven't tested deployed projects and this can be caused by many plugins I use (it's a complex project with over 250 plugins+compatibility fixes).
I'd love some extra performance, but this seems very unreliable.

P.S.S.S.S
Using nwjs-sdk-v0.44.6-win-x32 (because I want to support even old x32 platforms and the difference between x32 vs x64 seems non-existent) seems to be stable, but needs more testing. So far no black screens or errors. And the Editor test game window closes properly now.
I Will update about stability within a week and further testing, but it seems working fine.

Lol, Well, im glad its slowly coming together. Depending on your plugins etc, there may be a conflict somewhere.

Anyways, awesome.

 

[Vis_Mage]

Quick question, ever since I went through these steps to upgrade my project (Windows, to 49.2), when I playtest my game, the playtest window always opens at the top-left corner of my screen, instead of the center like it had before. Is there any way to fix this?

 

[Ronove]

Quick question, ever since I went through these steps to upgrade my project (Windows, to 49.2), when I playtest my game, the playtest window always opens at the top-left corner of my screen, instead of the center like it had before. Is there any way to fix this?

How to Update NW.js to Dramatically improve Game Performance!

Thanks for the tutorial! I tried it and I bumped onto something unusual. My RPG Maker MV is a pretty old standalone version I've had over 5 or years or so. I might have messed it up quite many times. So now I went there and found no nwjs-win-test, just nwjs-win. I don't how stuff works that...

forums.rpgmakerweb.com

It's mentioned in this post in the thread.

 

[sirnameless]

Thank you so much for this guide. It's helped a lot.

For my Mac deployment, though... it appears as if NWJS is not updated there? When playtesting, it does not crash, and I don't see the "Your profile can not be used because it is from a newer version of NW.js" error. After I deploy, I see that annoying error, and the game crashes a whole bunch again (because the old version of NWJS is useless on MacOS).

I've updated the nwjs-osx-test folder with version 0.49.2 NWJS. I didn't touch nwjs-osx-unsigned.zip. What could I be missing? Does Mac deployment work perfectly for everyone else? (I am deploying from a Mac, fwiw).

 

[hernieren]

I'm using MV on PC. I updated NW to 54.1 (only the win and win-test folders) and Pixi to 4.8.9. I haven't noticed any improvement in performance and suddenly my game has no sound... Maybe I need an older version for MV?