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 7 of 14 View original ↗

Danitinkis

#121 Feb 9, 2022, 02:11 AM Source

TheMeowingFox said:
Hey, can anyone tell me what this means? The game itself seems to run fine, but should I be worried about this?

View attachment 215625
According to OP in their video (7:25), it's something that 99% of people can ignore. I don't know exactly what it its tho.
ShiningPhoibe

#122 Apr 27, 2022, 11:08 PM Source

Hello.
I'm considering doing this for my MZ game. What version of Pixi would you recommend? I checked the file and it says v5.2.4. Should I leave Pixi alone?
Yilou

#123 May 7, 2022, 05:28 AM Source

Featherbrain said:
Just to follow up, this version of nwjs seems to do something slightly different with the windows. If I call Graphics._switchFullScreen() or Graphics._requestFullScreen() in a plugin, when I start the game, it briefly flashes into full screen, then goes back to window. If I call those functions through a script call before the title screen (luckily I have pre-title events), the calls work just fine and the game starts in fullscreen seamlessly. (And F4 works fine either way.)

My guess is that the old nwjs used to set the window dimensions first and then process plugins, while this one loads the plugins before it sets the window, so the later call is resetting the plugin calls. But, just a guess.

In any case, if you were using those calls in a plugin to start in fullscreen, you might have to use them as a script call in-game (e.g. pre-title event)... or, this could be something with my set up only. I didn't actually test a blank project. YMMV.
I have the same problem, how can I call the call script before the title screen?
Frostorm

#124 May 26, 2022, 08:33 AM Source

So what's the latest version of NWJS that people have gotten to work flawlessly?

Edit: Nvm, I just upgraded from v0.57.1 to v0.64.1!
ShadowDragon

#125 May 26, 2022, 11:55 AM Source

I tried both, but it doesn't seem to work as I get drawImage error on boot.
I dont know why though, so I have no clue what I do wrong as I followed
the tutorial video 100% correctly.

the title scene works, new game does not, even on a clean project.
Frostorm

#126 May 27, 2022, 10:23 PM Source

ShadowDragon said:
I tried both, but it doesn't seem to work as I get drawImage error on boot.
I dont know why though, so I have no clue what I do wrong as I followed
the tutorial video 100% correctly.

the title scene works, new game does not, even on a clean project.
If you'd like, I can upload a copy of my nwjs-win & nwjs-win-test folders onto Dropbox or Google Drive.
Raizen

#127 May 27, 2022, 10:42 PM Source

ShiningPhoibe said:
Hello.
I'm considering doing this for my MZ game. What version of Pixi would you recommend? I checked the file and it says v5.2.4. Should I leave Pixi alone?
Everything you can update, you do update, it shouldn't be an issue, but usually it can havesome improvements on the game :)
ShadowDragon

#128 May 28, 2022, 07:37 AM Source

@Frostorm what version do you use? if its 49.2 or another, it's good to
test anyway.

DM the link and I can try out.
Frostorm

#129 May 28, 2022, 11:18 PM Source

ShadowDragon said:
@Frostorm what version do you use?
I'm using v0.64.1 (64-bit). @ShadowDragon reports that 32-bit doesn't work. I imagine it's cuz I only downloaded the 64-bit SDK? Not sure, but for anyone that wants it, I have uploaded my nwjs-win & nwjs-win-test folders onto Google Drive. Simply replace your nwjs-win & nwjs-win-test folders, but remember to create a backup just in case.
masterlobo

#130 Jun 21, 2022, 08:35 PM Source

Two questions...
1. Any concerns with using a 32bit version of nwjs? People are asking me for 32-bit support for my game.

2. Is there any 32bit version of nwjs known to integrate with Steamworks?
ShadowDragon

#131 Jun 25, 2022, 02:56 PM Source

@masterlobo
my MV version is installed on x84 folder for some reason,
and have 64bit version of windows.

32bit version is something I dont get to work somehow.
but so far I know, 64bit version should work on a 32bit version as well.
specially vice versa.
masterlobo

#132 Jun 28, 2022, 07:01 PM Source

ShadowDragon said:
@masterlobo
my MV version is installed on x84 folder for some reason,
and have 64bit version of windows.

32bit version is something I dont get to work somehow.
but so far I know, 64bit version should work on a 32bit version as well.
specially vice versa.

No, my 64bit app doesn't work on 32-bit environments. Steam won't even allow the installation of it.
ShadowDragon

#133 Jun 28, 2022, 07:15 PM Source

weird, I got both 64bit and 32bit as that mostly comes on pc's
from 2010? or later?

I dont really thing 32bit is even sold, or they have really old window,
I cant remember what is the oldest that only have 32bit.
contentdeleted

#134 Jul 18, 2022, 06:40 PM Source

masterlobo said:
No, my 64bit app doesn't work on 32-bit environments. Steam won't even allow the installation of it.

Hey I could be misremembering but I'm pretty sure this error is a result of your settings in steamworks.
You should be able to configure what your game supports as part of the builds page. IIRC theres a checkbox there for 64 and 32 bit support for windows.
HalcyanStudio

#135 Jul 19, 2022, 08:33 PM Source

contentdeleted said:
Hey I could be misremembering but I'm pretty sure this error is a result of your settings in steamworks.
You should be able to configure what your game supports as part of the builds page. IIRC theres a checkbox there for 64 and 32 bit support for windows.
Can confirm this.
EndlessGame

#136 Aug 2, 2022, 11:57 PM Source

This worked amazingly. Thank you!
EndlessGame

#137 Aug 4, 2022, 05:10 PM Source

EndlessGame said:
This worked amazingly. Thank you!
The only issue is that my gamepad configuration plugin isn't working anymore. Different buttons mean different things now. Odd. I'll try a different gamepad plugin to see if the issue is fixed.
Arthran

#138 Aug 4, 2022, 05:19 PM Source

EndlessGame said:
The only issue is that my gamepad configuration plugin isn't working anymore. Different buttons mean different things now. Odd. I'll try a different gamepad plugin to see if the issue is fixed.
If you upgrade NW.js to version 0.49 or higher, it can break plugins that involve input or window manipulation. I personally recommend going with version 0.48.4 (the same one MZ uses). I haven't noticed any notable performance benefits from going higher than that, and it should be safe for all of your plugins.
EndlessGame

#139 Aug 4, 2022, 05:55 PM Source

Arthran said:
If you upgrade NW.js to version 0.49 or higher, it can break plugins that involve input or window manipulation. I personally recommend going with version 0.48.4 (the same one MZ uses). I haven't noticed any notable performance benefits from going higher than that, and it should be safe for all of your plugins.
Ah, I see. Would reverting from the newest version to 0.48.4 be the same process as I did before?
Arthran

#140 Aug 4, 2022, 06:13 PM Source
EndlessGame said:
Ah, I see. Would reverting from the newest version to 0.48.4 be the same process as I did before?
Yeah, it would be the same. But it's possible that you will start getting the NW.js profile error mentioned in the original post. If that happens, then you just gotta delete the files mentioned in the original post:
To fix this error click your file explorer and type in %LOCALAPPDATA%/ (You can also go to users/*your user name*/Appdata/Local to achieve same effect)

Then go into KADOKAWA\RPGMV\User Data\Default

Delete both Web Data and Web Data-journal.