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)ġ) You need to be able to locate RPG Maker MV’s Local files. 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! (Example of when you update NW.js to 49.2 like I did!) Type “process.versions” and press enter to see what version or Nw.js or just “nw” that you are running. 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. 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). 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). (I’m not covering this in this guide)Īlso please note, there might be some small quirts with the NW.js version you choose. 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. You can easily use the same steps I’m going to outline below to get MVs NW.js to virtually any version. 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. RPG Maker MZ comes default with NW.js Version 44 RPG Maker MV comes default with NW.js Version 29.4 Full support for the features in the browser. New way of writing native applications using web technologies: HTML5, CSS3, and WebGL. 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. Upgrading your NW.js is a great way to massively improve your game performance, especially if you are using RPG Maker MV! Do you guys want me to create a MZ section of this guide? I just updated my MZ to NW.js version 50, everything is working great. ( do NOT rename nw.exe to Game.exe) Have fun! Just find the "Resource" folder, and replace the proper NW.js folder with the new downloaded versions and it should work just like that. (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. 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. (Updating NW.js for Mac may make RPG Maker MV compatible with OSX Catalina and Big Sur! OMG!) This is a step by step guide for MV users to update their NW.JS to dramatically increase the performance of their game. I tried following the simple fix to eliminate this error, but I do not have the following files in the KADOKAWA folder: Web Data and Web Data-journal. Please specify a different profile directory or use a newer version of NW.js." Now the following error pops up in playtest and deployment but does not affect gameplay: "Your profile can not be used because it is from a newer version of NW.js. So, I tried to delete all the files from the engine (because the game itself did not cause the error) and reinstalled RPG Maker MV from Steam. (screenshot below is the look for the game, 1080 by 786)Īfter deployment, the game would not run at all. Upon finishing the tutorial, it would make my test game pop up at the standard resolution of RPG Maker but like a weird widescreen with large black rectangles above and below the game screen. I tried to follow the tutorial on changing the nw.js version from version 29 to version 49 (the one compatible with OrangeGreenworks).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |