Hi Everyone, Thanks for the overwhelming support during the first few days of the launch. We’ve been receiving tons of great feedback from all of you. Many of you have been using RPG Maker MV without running into any issues but some of you have been having problems with the program and for that we are very sorry.
We had over 30 people beta testing RPG Maker MV before launch and a number of problems were identified and fixed. Unfortunately, we didn’t catch all of them and some issues/bugs have been reported over the last few days.
We communicated these problems to the developers in Japan first thing Monday morning and have the first round of fixes/updates available. We’ve detailed them below and more are on the way.
Languages: With the new version you can now select the language you wish to use RPG Maker MV in as follows:
Steam : In your library, right click on RPG Maker MV, select properties and open the Language tab. Once you choose language RPG Maker MV will update and start in the selected language on next boot.
You can also open the RPG Maker MV folder and add/edit the Locale file to put only the language code you want (two letters) from the list below : en // English fr // French de // German es // Spanish it // Italian pt // Portuguese ru // Russian
And extract ONLY the locale folder in your RPG Maker MV Steam Folder. It will enable Steam's Language Check.
Translation issues It’s been brought to our attention that some of the translations provided for RPG Maker MV are inaccurate/incomplete. We are reviewing all of the translations thoroughly and will be fixing/updating them over the coming weeks. Our apologies for this.
Bug when the decimal is set to “,” This has been fixed.
Bug where checkbox would sometimes not display the Check Mark: This has been fixed.
Bug that could cause the map size to be empty on edition, resulting in a 0x0 map: This has been fixed.
The bugs listed below require you to REPLACE the base js files in EACH project folder, with the corrected base files. This is only for existing projects, new projects should work properly from the start.
Water Autotile Bug: Render method was changed and slowdown should be much less pronounced
Frequency 5 Bug : Now the event correctly stops when frequency is set to 5
Bug when you changed class using the keep XP This has been fixed
Base Resource : the images : BaseResource\img\sv_enemies\SF_GothicLolita.png BaseResource\img\enemies\SF_GothicLolita.png These have been replaced with a cleaned up version of the image.
Plugin : Help for MenuSubMember is now in English.
We’re working on more fixes and updates and will be sharing more info about this shortly. A roadmap will also be put up in the steam forums.
A huge thank you to everyone for bearing with us as we address these issues. RPG Maker MV was rebuilt from the ground up on a completely new platform and scripting language. We are committed to fully supporting it and continuing to update the program and add new features.
Thank you for all of the comments on the forums and social media as well as the steam reviews (both positive and negative). We’ve been blown away by the response and interest in the latest version of RPG Maker and can’t thank you enough.
Hi Everyone, Thanks for the overwhelming support during the first few days of the launch. We’ve been receiving tons of great feedback from all of you. Many of you have been using RPG Maker MV without running into any issues but some of you have been having problems with the program and for that we are very sorry.
We had over 30 people beta testing RPG Maker MV before launch and a number of problems were identified and fixed. Unfortunately, we didn’t catch all of them and some issues/bugs have been reported over the last few days.
We communicated these problems to the developers in Japan first thing Monday morning and have the first round of fixes/updates available. We’ve detailed them below and more are on the way.
Languages: With the new version you can now select the language you wish to use RPG Maker MV in as follows:
Steam : In your library, right click on RPG Maker MV, select properties and open the Language tab. Once you choose language RPG Maker MV will update and start in the selected language on next boot.
You can also open the RPG Maker MV folder and add/edit the Locale file to put only the language code you want (two letters) from the list below : en // English fr // French de // German es // Spanish it // Italian pt // Portuguese ru // Russian
And extract ONLY the locale folder in your RPG Maker MV Steam Folder. It will enable Steam's Language Check.
Translation issues It’s been brought to our attention that some of the translations provided for RPG Maker MV are inaccurate/incomplete. We are reviewing all of the translations thoroughly and will be fixing/updating them over the coming weeks. Our apologies for this.
Bug when the decimal is set to “,” This has been fixed.
Bug where checkbox would sometimes not display the Check Mark: This has been fixed.
Bug that could cause the map size to be empty on edition, resulting in a 0x0 map: This has been fixed.
The bugs listed below require you to REPLACE the base js files in EACH project folder, with the corrected base files. This is only for existing projects, new projects should work properly from the start.
Water Autotile Bug: Render method was changed and slowdown should be much less pronounced
Frequency 5 Bug : Now the event correctly stops when frequency is set to 5
Bug when you changed class using the keep XP This has been fixed
Base Resource : the images : BaseResource\img\sv_enemies\SF_GothicLolita.png BaseResource\img\enemies\SF_GothicLolita.png These have been replaced with a cleaned up version of the image.
Plugin : Help for MenuSubMember is now in English.
We’re working on more fixes and updates and will be sharing more info about this shortly. A roadmap will also be put up in the steam forums.
A huge thank you to everyone for bearing with us as we address these issues. RPG Maker MV was rebuilt from the ground up on a completely new platform and scripting language. We are committed to fully supporting it and continuing to update the program and add new features.
Thank you for all of the comments on the forums and social media as well as the steam reviews (both positive and negative). We’ve been blown away by the response and interest in the latest version of RPG Maker and can’t thank you enough.
I'm sorry for the consecutive updates but I just got news back from Kadokawa and we need your help again. Please do the following if your MV editor lags or if your MV is too fast (e.g. 1000 FPS).
Do not report if you only have issues with the animated autotiles as that is a separate issue and we're fixing that one as well.
Do not report about language errors or the traits,etc. We are now fixing those.
Thank you for the help and I once again apologize for all the troubles.
2.) Install and Run the Program. Make sure MV is open.
* If MV doesn't open, Tell in the email and send the specs. * If MV lags but the play test doesn't. Tell in the email and send the specs * If MV doesn't lag but the game playtest is lagging. Tell in the email and send the specs * If MV playtest is too fast. Tell in the email and send the specs. * If only audio lags in editor but not playtest. Tell in the email and send the specs * If audio lags only in playtest. Tell in the email and send specs * If audio lags on both, tell in the email and send specs
I'm sorry for the consecutive updates but I just got news back from Kadokawa and we need your help again. Please do the following if your MV editor lags or if your MV is too fast (e.g. 1000 FPS).
Do not report if you only have issues with the animated autotiles as that is a separate issue and we're fixing that one as well.
Do not report about language errors or the traits,etc. We are now fixing those.
Thank you for the help and I once again apologize for all the troubles.
2.) Install and Run the Program. Make sure MV is open.
* If MV doesn't open, Tell in the email and send the specs. * If MV lags but the play test doesn't. Tell in the email and send the specs * If MV doesn't lag but the game playtest is lagging. Tell in the email and send the specs * If MV playtest is too fast. Tell in the email and send the specs. * If only audio lags in editor but not playtest. Tell in the email and send the specs * If audio lags only in playtest. Tell in the email and send specs * If audio lags on both, tell in the email and send specs
Play the game and talk to the event. It should open a window and tell you some details. Please post your results. This will help us more to pinpoint issues!
Play the game and talk to the event. It should open a window and tell you some details. Please post your results. This will help us more to pinpoint issues!
OK everyone. This topic is to help you all to fix your lag issues and as such, please read the following!
However, if nothing works, I'm afraid that you might need to buy a new PC or parts especially if they're made before 2009. (Especially PCs/GPUs build before 2009, see below)
Of course, if the driver can still be updated and it was made before 2009, it could still work. But no guarantees.
We want to see if this solution will work on the majority as well.
UI/Editor Lagging
=========================================== MV uses QT with QtQuick, so no native components. Since QT supports multiple but it could be also related to OpenGL, so if the graphics card or driver doesn’t support OpenGL it could result in lagging.
Game/Test-Play Lagging
=========================================== MV uses NW.js for offline PC/Mac games and also for test-play. It uses PIXI.js which is based HTML5 Canvas/WebGL. So the same problem with OpenGL, if its not supported everything will be slow.
Except on some browsers like Firefox, Chrome, etc. since they are able to map the OpenGL calls to DirectX/Direct3D calls using ANGLE. That would explain if the web-demo works fast but the test-play not for some users.
NW.js also supports that since it based on Chromium, but sometimes its not working, for example if the DirectX 9.0.c Redistributable is not there or if some DLLs are missing.
But there is an additional problem, because Canvas/WebGL doesn’t support some GPUs/Drivers because they are on the GPU black-list to avoid crashes, etc. You have to keep in mind that HTML5 is actually a Web-Technology, so stability & security is very important.
How to Fix
===========================================
You should try the following steps.
1. Check that your graphics card supports OpenGL.
2. Go the website of your graphics card manufacture (NVIDIA, AMD, etc.) and download & install the latest driver for your graphics card. Make that the driver supports OpenGL.
3. If the games are still not running fast after these two steps, you should try to edit the package.json and add the following line:
5. Make sure your laptop is set to High Performance!
Remember to restart RPG Maker MV after!
6. If all these steps are not working, please let us know and check this information from WebGL Wiki:
Windows:
• On all versions of Windows, WebGL is disabled on all graphics drivers older than January 1, 2009. • Additionally, on Windows XP, WebGL is disabled on ATI/AMD drivers older than version 10.6, on NVIDIA drivers older than version 257.21, and on Intel drivers older than version 14.42.7.5294. • WebGL is disabled on NVIDIA driver 6.14.11.9621 on Windows XP. • WebGL is always disabled on ATI FireNV 2400. • WebGL is disabled on Parallels drivers older than 7. • WebGL is always disabled on S3 Trio cards.
Mac:
• On Mac OS X, WebGL is disabled on: • ATI Radeon X1900 • NVIDIA GeForce 7300 GT • Additionally, when an external monitor is plugged in to a Mac OS X laptop, multisampling is disabled because of rendering corruption bugs (http://crbug.com/237931).
Please make sure to follow this guide thoroughly and only post in this announcement if it's fixed or not. If it's not and you pass the hardware requirements to run OpenGL post your PC specs here
OK everyone. This topic is to help you all to fix your lag issues and as such, please read the following!
However, if nothing works, I'm afraid that you might need to buy a new PC or parts especially if they're made before 2009. (Especially PCs/GPUs build before 2009, see below)
Of course, if the driver can still be updated and it was made before 2009, it could still work. But no guarantees.
We want to see if this solution will work on the majority as well.
UI/Editor Lagging
=========================================== MV uses QT with QtQuick, so no native components. Since QT supports multiple but it could be also related to OpenGL, so if the graphics card or driver doesn’t support OpenGL it could result in lagging.
Game/Test-Play Lagging
=========================================== MV uses NW.js for offline PC/Mac games and also for test-play. It uses PIXI.js which is based HTML5 Canvas/WebGL. So the same problem with OpenGL, if its not supported everything will be slow.
Except on some browsers like Firefox, Chrome, etc. since they are able to map the OpenGL calls to DirectX/Direct3D calls using ANGLE. That would explain if the web-demo works fast but the test-play not for some users.
NW.js also supports that since it based on Chromium, but sometimes its not working, for example if the DirectX 9.0.c Redistributable is not there or if some DLLs are missing.
But there is an additional problem, because Canvas/WebGL doesn’t support some GPUs/Drivers because they are on the GPU black-list to avoid crashes, etc. You have to keep in mind that HTML5 is actually a Web-Technology, so stability & security is very important.
How to Fix
===========================================
You should try the following steps.
1. Check that your graphics card supports OpenGL.
2. Go the website of your graphics card manufacture (NVIDIA, AMD, etc.) and download & install the latest driver for your graphics card. Make that the driver supports OpenGL.
3. If the games are still not running fast after these two steps, you should try to edit the package.json and add the following line:
5. Make sure your laptop is set to High Performance!
Remember to restart RPG Maker MV after!
6. If all these steps are not working, please let us know and check this information from WebGL Wiki:
Windows:
• On all versions of Windows, WebGL is disabled on all graphics drivers older than January 1, 2009. • Additionally, on Windows XP, WebGL is disabled on ATI/AMD drivers older than version 10.6, on NVIDIA drivers older than version 257.21, and on Intel drivers older than version 14.42.7.5294. • WebGL is disabled on NVIDIA driver 6.14.11.9621 on Windows XP. • WebGL is always disabled on ATI FireNV 2400. • WebGL is disabled on Parallels drivers older than 7. • WebGL is always disabled on S3 Trio cards.
Mac:
• On Mac OS X, WebGL is disabled on: • ATI Radeon X1900 • NVIDIA GeForce 7300 GT • Additionally, when an external monitor is plugged in to a Mac OS X laptop, multisampling is disabled because of rendering corruption bugs (http://crbug.com/237931).
Please make sure to follow this guide thoroughly and only post in this announcement if it's fixed or not. If it's not and you pass the hardware requirements to run OpenGL post your PC specs here