Announcement RPG Maker MV - v1.6.1 Stable Release!

[Archeia]

6/21/2018

Everyone, please read the instructions carefully. The bugs that are being reported shouldn't happen if the correct files were even copied properly. Such examples like the "CTRL BUG" shouldn't happen if you copied index.html, package.json, the rpg*.js files and so on.

I also received requests from some plugin developers that users must stop reporting incompatibility issues on this thread and towards them instead. Those are different from the official updates and all these bug reports just make them look unprofessional.

Thank you.

Hi everyone,
RPG Maker MV v1.6.1 is now on Stable! Here are some of the changes this version.

New Feature:

• It now uses NWJS version 0.29.0 which allows programmers to use Javascript ES6, ES7 and ES8 and other performance improvements.
• BONUS: new parallax resources in parallax_Resource_Pack

Bug Fixes:

• Fix to the InvalidStateError during ME play
• Fix to the deep loop error
• MacOS: Fix to shortcuts
• MacOS: Fix to tutorials
• Fix to \img\characters\People2
• Fix to \img\characters\!Chest
• Fix to the freeze when changing screen in-game
• Fixed an issue with encodeURI where it cannot detect custom folders.

Updating your Projects:
We would like to remind everyone to make sure to do the following steps before updating to ensure that when the update happens so your changes won’t be overwritten:

• Make a backup of your project.
• DO NOT OPEN your 1.5.2 below project with RPG Maker MV 1.6.1 if you have no backups!

Now for the update process.

• Backup your game! This is important!
• Make a backup of your Generator folder if you edited it.

Create a new project or go to the NewData folder in your RPG Maker MV root (where MV is installed) folder. Copy the following items and replace the ones in your existing project:

• Copy the file "index.html" and "package.json" from NewData to your project
• Copy the files libs folder, "rpg_*.js" (example: rpg_core) files from NewData/js to your project js folder
• Do not replace your plugins.js !
  
• Done!

Downgrading RPG Maker MV
If RPG MAKER MV 1.6.1 is not working for you, you can downgrade anytime.

Downloads:

• Full Installer
• Update Only Installer
• Parallax Resource Pack

 

[AceOfAces_Mod]

Sneeeeeeeeeeeeeeeeak Attaaaaaaaaaaaaaaaaaaaaaaaack!

In all seriousness, I just noticed the update going live. And I thought that it received a beta update. The Parallax Resource Pack is quite intriguing but the sample project (along with the included text files) are untranslated. I don't understand some of the things. I wish it was translated first. Also, what about the plugins that are in the project? Can we use them in our projects or do we need different ones?

 

[Splendith]

I have a problem in RPG Maker v1.6.1 (both beta and stable version)
I'm not sure that the lower performance of this version or just a bug.

If I use a many parallel events that include script command and open the developer tool (F8) while running the game. It will super lag.

Sample test
https://drive.google.com/open?id=1WV7fXFtuZbksvIO127IauhywCZkwwmAA

This project has 25 parallel events in a map, each event has just one empty script command. You can try by

1. Open the project with RPG Maker v1.6.1
2. Run the project (Ctrl + R) and press 'New Game'
3. Press F8 to open the developer tool
4. Try to walk around the map

Note that
1. This problem does not happen when the game is running but not open the developer tool
2. This problem does not happen in version 1.5.2 or below (you can try by open the above Sample test with v1.5.2)

 

[SOC]

After updating, when I go to open RMMV (non-Steam version), it shows the splash screen but then disappears and doesn't open. I've made sure to exclude it from my anti-virus just in case that was blocking it for some reason.

 

[OmnislashXX]

Think I'll hang back for awhile. Let people test it out, first.

 

[fizzly]

Looks like doodads isn't compatible with 1.6.1

 

[bgillisp]

@fizzly : That's because Yanfly probably hasn't updated the code yet. I'd report it to them so they can know.

 

[LightDiviner]

Out of curiosity, will we get more things for the Child Character Generator?

 

[Dankovsky]

This is good news. After last time I'm sure the publisher wouldn't have released a stable version unless they were 100% sure it's actually stable.
I ask everyone to please report any plugin compatibility issues you'll encounter here. This is important for people who have big projects in the works and much to lose if anything goes wrong.

 

[Aloe Guvner]

It now uses NWJS version 0.29.0 which allows programmers to use Javascript ES6, ES7 and ES8 and other performance improvements.

*rubs flippers together greedily*

 

[bgillisp]

@Dankovsky : Actually, if someone has a big project in the works they should use the version of MV they are currently using. There's a reason AAA companies don't update their engines every time a new version comes out, as redoing things to work in new versions takes time, time they would rather spend making the game.

 

[Celianna]

@Dankovsky : Actually, if someone has a big project in the works they should use the version of MV they are currently using. There's a reason AAA companies don't update their engines every time a new version comes out, as redoing things to work in new versions takes time, time they would rather spend making the game.

Like me, I'm sticking to 1.5.1 because the amount of things that break in 1.6.1 is way too much work to fix.

 

[Dankovsky]

@Dankovsky : Actually, if someone has a big project in the works they should use the version of MV they are currently using. There's a reason AAA companies don't update their engines every time a new version comes out, as redoing things to work in new versions takes time, time they would rather spend making the game.

I know, it seems like the most obvious thing. But I heard 1.6.1. really boosts performance and it might be just too sweet to pass on, especially if no serious update issues turn up.

 

[djDarkX]

Like me, I'm sticking to 1.5.1 because the amount of things that break in 1.6.1 is way too much work to fix.

Agreed with this. When I upgraded to 1.6.1, before, the editor was fine, but the engine ran like molasses. I had to downgrade back to the older, stable version. It works, so I'm sticking to it for current projects.

 

[Tuomo L]

My game doesn't stop properly after 1.6.1 Exiting the game leaves the nw.js hanging.

 

[Mrs_Allykat]

Is steam going to try to auto-push this one on us?

 

[Aloe Guvner]

@Mrs_Allykat
It depends on your Steam settings.
If you have it set to Auto-Update, then yes. If you don't, then no.

Here's an article that walks you through how to disable auto-updates.

 

[slimmmeiske2]

@Mrs_Allykat Only if you have it set to auto-update.

 

[Mrs_Allykat]

Since they said the release is stable, they may have removed the "beta" tag on steam. If that's the case it will ignore those settings. (Release versions have two options "update automatically" and "update when I launch the game.") If it's still listed under beta on Steam, I should be good since I opted out of receiving beta updates.

 

[Aloe Guvner]

@Mrs_Allykat
Of course, but our statements *should* still apply. If you do not have it set to "Update Automatically", you can opt into the 1.5.2 beta before launching the program.
If you have it set to "Update Automatically", it will likely update automatically when you open the Steam client (or earlier, if your Steam client opens automatically when your computer is started).