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

KillerGin · 2020-12-31T07:20:34+0900

WARNING: This is a step by step guide for MV users to update their NW.JS to dramatically increase the performance of their game. (Updating NW.js for Mac may make RPG Maker MV compatible with OSX Catalina and Big Sur! OMG!) MZ users can use the ideas presented in this guide to update their NW.js from 44 to 50 if they like, but I'm not sure how much of a performance update this will be. (To update MV from 29 to 50 (or in my case 49.2) is a massive update!) It's actually easier to update MZ since the engine folders are structured much better. Just find the "Resource" folder, and replace the proper NW.js folder with the new downloaded versions and it should work just like that. Of course, I advise making backups, etc. (do NOT rename nw.exe to Game.exe) Have fun! I just updated my MZ to NW.js version 50, everything is working great. Deployed and test games run just fine. Do you guys want me to create a MZ section of this guide? ///////////////////////////////// Youtube Video Version! ///////////////////////////////// Upgrading your NW.js is a great way to massively improve your game performance, especially if you are using RPG Maker MV! NW.js (previously known as node-webkit) lets you call all Node.js modules directly from DOM and enables a new way of writing applications with all Web technologies. New way of writing native applications using web technologies: HTML5, CSS3, and WebGL. Full support for the features in the browser. ///////////////////////////////// Some Explanation: RPG Maker MV comes default with NW.js Version 29.4 RPG Maker MZ comes default with NW.js Version 44 So, a great way to GREATLY improve the performance of your MV Game is to upgrade the default NW.js version 29.4 to a higher version. You can easily use the same steps I’m going to outline below to get MVs NW.js to virtually any version. You can choose version 50 which is the newest, but I personally chose 49.2 (Higher than MZ) because this is the latest version that all three platforms PC, MAC, and Linux support STEAM integration with Orange Green works. (I’m not covering this in this guide) Also please note, there might be some small quirts with the NW.js version you choose. For example, before I upgraded to 49.2 (which works flawlessly) I upgraded to 33.3 which had a small text glitch (text sometimes showed up slowly). Just keep in mind these things may happen (I tried 33.3 because I thought that’s the highest version Orange Green works could use, I was wrong, its 49.2, but I digress). ///////////////////////////////// So to check what version of NW.js you are using, in the editor, when you are testing your game, press f8 (or function f8) to bring up the console. Type “process.versions” and press enter to see what version or Nw.js or just “nw” that you are running. (Example of when you update NW.js to 49.2 like I did!) ///////////////////////////////// So now that you are all caught up with a general idea of how it works and how to check we can get to the final details of how to get this upgraded! Keep in mind I will provide the PC and Mac instructions, I do not have a Linux Machine however I feel the process will be very similar to either the PC or Mac version of the update (they differ slightly) Here we go! ///////////////////////////////// 1) You need to be able to locate RPG Maker MV’s Local files. On STEAM, just RIGHT CLICK -> Properties -> Local Files -> Browse Else you will have to find the application folder on your PC. 2) You will see these two folders: a) nwjs-win (Windows platform) b) nwjs-lnx (Linux platform) c) nwjs-osx-unsigned (Mac platform, yes its zipped up, don’t worry about it) So if you want to update all 3 versions, you have to keep these folders in mind. (This is prob a great time to save a copy of these folders just in case you want to revert back, minus the zipped osx unsigned folder that we never touch) 3) Most likely since you are using a PC you will also see a “test” version of this folder. This is the folder used when you are testing the game in the editor. So a PC user will see a) nwjs-win b) nwjs-win-test 4) Now Download the version of NW.js that you want from the internet. This should work https://nwjs.io/downloads/ If you want an older build (If you want to integrate STEAM functionality with Orange Green Works I recommend 49.2, you can find older versions here: https://dl.nwjs.io/ (Scroll down) Get the SDK versions, minus the “symbol” listings, I would get all the 64 bit versions, so these minus the “win-ia32” version. (Or just the bottom “win-x64” version if you plan to just update the PC version, yes, the deployed and test version of rpg maker) 5) Now that you have everything you need. Now comes the hard part! But before we get too crazy. I would suggest saving all your work. Make a copy and back it up to the cloud just in case. (even though we are just updating RPG Maker MV itself lol). However, do keep in mind, at least for the STEAM version, if you want to revert back to default, you will have to del…

● ARCHIVED · READ-ONLY

Started by KillerGin Dec 30, 2020, 10:20 PM 273 posts Page 13 of 14 View original ↗

Welleran

#241 Jul 8, 2024, 02:08 AM Source

KillerGin said:
MZ users can use the ideas presented in this guide to update their NW.js from 44 to 50 if they like, but I'm not sure how much of a performance update this will be. (To update MV from 29 to 50 (or in my case 49.2) is a massive update!) It's actually easier to update MZ since the engine folders are structured much better. Just find the "Resource" folder, and replace the proper NW.js folder with the new downloaded versions and it should work just like that. Of course, I advise making backups, etc. (do NOT rename nw.exe to Game.exe) Have fun!
It worked like a charm!
I had some maps with lots of people moving and an occasional drop in FPS. After updating everything got much smoother. Thank you!
Franz_Pantalon

#242 Jul 28, 2024, 12:08 PM Source

Hi. Just providing a short feedback.

I've updated today for my linux version of MV (steam), following the method you provided for windows.

It somehow worked.

However few remarks:
- I first tried to update to the latest version of nw.js (v0.89.0) without success. I then tried again with an older version (I picked v0.49.2 because it seemed to be used quite often), and it worked.
- you have to pay attention that the same permissions as the removed files are granted for the new ones.
- after update, the console delivers some warning during playtest (see picture). As far as I could find out (though I am far from an expert), those are harmless.
ShadowDragon

#243 Jul 28, 2024, 08:55 PM Source

@Franz_Pantalon you can ignore them, but you can remove it as well.
as the js.map are just data, it isn't required and can be safely ignored, so don't
pay to much on them unless you really want too, but I don't really bother with
it to much.
AndreWharn

#244 Aug 3, 2024, 01:30 PM Source

Hi, I've been encountering something rather weird while playtesting with this; sometimes, when you close the game, a NW process keeps staying in the background preventing to reopen the game again until I terminate it through the task manager. This happens completely randomly, and it is incredibly annoying. Did any of you encounter this? (I am using Windows 11 by the way.)
inc0der

#245 Aug 3, 2024, 02:46 PM Source
AndreWharn said:
Hi, I've been encountering something rather weird while playtesting with this; sometimes, when you close the game, a NW process keeps staying in the background preventing to reopen the game again until I terminate it through the task manager. This happens completely randomly, and it is incredibly annoying. Did any of you encounter this? (I am using Windows 11 by the way.)
That is an issue with MV itself (technically the nwjs version it uses), they fixed it in MZ.

Just throw this into a plugin and enable it, this should fix it although I've never tested it.
JavaScript:
const aliasSceneBootStart = Scene_Boot.prototype.start; Scene_Boot.prototype.start = function () { if (typeof nw === "object") { const window = nw.Window.get(); window.on("close", () => window.close(true)); // Alternative way if default does not work // nw.App.quit() } aliasSceneBootStart.call(this); };
AndreWharn

#246 Aug 3, 2024, 03:26 PM Source
No, it
inc0der said:
That is an issue with MV itself (technically the nwjs version it uses), they fixed it in MZ.

Just throw this into a plugin and enable it, this should fix it although I've never tested it.

JavaScript:
const aliasSceneBootStart = Scene_Boot.prototype.start; Scene_Boot.prototype.start = function () { if (typeof nw === "object") { const window = nw.Window.get(); window.on("close", () => window.close(true)); // Alternative way if default does not work // nw.App.quit() } aliasSceneBootStart.call(this); };
No, it doesn't seem to work, sadly. If I use the alternative way, the game just immediately closes upon starting. Unless I'm using it in a wrong way?
inc0der

#247 Aug 3, 2024, 03:39 PM Source
AndreWharn said:
No, it

No, it doesn't seem to work, sadly. If I use the alternative way, the game just immediately closes upon starting. Unless I'm using it in a wrong way?
View attachment 313587
The alternative way would be to do it like this, I should've made the example better, sorry. Hopefully this works
JavaScript:
const aliasSceneBootStart = Scene_Boot.prototype.start; Scene_Boot.prototype.start = function () { if (typeof nw === "object") { const window = nw.Window.get(); window.on("close", () => nw.App.quit()); } aliasSceneBootStart.call(this); };

AndreWharn

#248 Aug 3, 2024, 07:33 PM Source

inc0der said:

The alternative way would be to do it like this, I should've made the example better, sorry. Hopefully this works

JavaScript:

const aliasSceneBootStart = Scene_Boot.prototype.start;

Scene_Boot.prototype.start = function () {

  if (typeof nw === "object") {

    const window = nw.Window.get();

    window.on("close", () => nw.App.quit());
  }

  aliasSceneBootStart.call(this);

};

Now that works, thank you!! :D

aLostSolo

#249 Oct 24, 2024, 08:01 AM Source

Thank you very much for this @KillerGin!
I've upgraded pixiJS to 4.8.9 before but didn't apply this update as well to NW.js.

It works but for some reason audio doesn't play at all.
When I check the "Network" in the DevTools I see the files are indeed loaded but no sound.

I tested on a new Project without any plugins and it doesn't work either.
Running with RPG Maker MV.

Any clue what it might be?
Thanks again!
hexxor

#250 Jan 27, 2025, 10:30 AM Source

I've done this recently, worked well except for the fact that the console instantly closes now. Making it impossible to view the console unless I revert it back to the default nw.js. I'm using v0.94.1, could it be just this version? Does anyone else have this problem?

Any thoughts on how to prevent this?
ShadowDragon

#251 Jan 27, 2025, 10:56 AM Source

hexxor said:
I'm using v0.94.1, could it be just this version? Does anyone else have this problem?
I don't have this problem and I use 0.48.0 or 0.48.4 the same MZ uses to start.
so I think it might be the 0.94.1 version.

you can try 0.88.x or lower that can work out.
utunnels

#252 Jan 27, 2025, 11:24 AM Source

The newest greenworks release is for nw 0.94.0, not 0.94.1
Releases · greenheartgames/greenworks
utunnels

#253 Jan 27, 2025, 11:30 AM Source

By the way, I've seen multiple people who tried nw 0.49.2 and failed.
So I just upload the specific greenworks build here just in case someone might need it.
The one on the prebuild site doesn't work anymore, it seems. It was modified some time in 2024.
chris-cote

#254 Mar 29, 2025, 05:30 AM Source

Has anyone had trouble getting newer versions of nwjs to work on SteamDeck?

I had upgraded to 0.69 a while ago, and at the time I couldn't get any newer version to run on SteamDeck. Today, I tried updating to several newer versions (0.94, 0.88, 0.86, 0.78) and they would all launch the game just fine on Steam Deck, however when updating to any of these versions, the game doesn't detect any inputs from the Steam Deck controller (only touch input on the screen via the cursor).

I am not using any greenworks plugin, just deleting the contents of the win nwjs folder, replacing with the new files from the 64 bit SDK, exporting the game, and then running with the latest stable proton version on the SteamDeck.

Any help is much appreciated!
ElvenNeko

#255 Apr 26, 2025, 06:51 PM Source

Is it normal that console does not open after updating? F12 does nothing, f8 opens page that gives error "unable to acsess site".

utunnels said:
By the way, I've seen multiple people who tried nw 0.49.2 and failed.
So I just upload the specific greenworks build here just in case someone might need it.
The one on the prebuild site doesn't work anymore, it seems. It was modified some time in 2024.

What is that? How to use it? I can't find any files like in your archive to replace within the MV folder.
SGHarlekin

#256 Apr 26, 2025, 08:10 PM Source

ElvenNeko said:
Is it normal that console does not open after updating? F12 does nothing, f8 opens page that gives error "unable to acsess site".

What is that? How to use it? I can't find any files like in your archive to replace within the MV folder.
User error. Sounds like you put the non-sdk nw.js into your playtest folder.
ElvenNeko

#257 Apr 26, 2025, 08:53 PM Source

SGHarlekin said:
User error. Sounds like you put the non-sdk nw.js into your playtest folder.
I thought this will work as well:

"(Or just the bottom “win-x64” version if you plan to just update the PC version, yes, the deployed and test version of rpg maker)"
Thank you, it's good to see that i messed up just a bit and it's fixable)
So i need to download the sdk file that is NOT symbol, right?
SGHarlekin

#258 Apr 26, 2025, 09:09 PM Source

ElvenNeko said:
I thought this will work as well:

Thank you, it's good to see that i messed up just a bit and it's fixable)
So i need to download the sdk file that is NOT symbol, right?
You can try my guide. It's less confusing and only has the necessary infos.
MV, Steam achievements & You (And also how to update nw.js!) But yes. Not the symbol ones. SDK is the developer version, which has the console enabled. The normal one is for your regular windows folder when deploying.
jofa

#259 Aug 29, 2025, 06:59 AM Source

My original pixie version in rpg maker is 5.3.12 can I upload to 6 for exemple?
fizzly

#260 Oct 30, 2025, 10:31 PM Source

If anyone else digging through this topic to find answer how to update for MZ & Windows:
- download NW.JS (SDK)
- delete everything from "nwjs-win" folder (RMMZ folder; remember to do the copy of that folder before!)
- extract the downloaded file and put everything from the folder to empty "nwjs-win" folder

That's it! No more.