RPG Maker MV 1.6.0 and GENE!

[Archeia]

Hi Everyone, today we're happy to bring both one of the biggest update to RPG Maker MV ever, and a new cool tool to make your making experience ever better.

​

GENE is an intuitive new tool created for RPG Maker MV that simplifies visual event scene creation and helps you develop your project faster. Your game's opening, ending and cut scenes can now be made using an intuitive timeline and a quick preview mode.

It is now available for $19.99 or equivalent, with a first week discount of 10%.


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:

• If you are using standalone, download this!
• If you are using steam and did nothing, it should automatically update. Do not use the downloads from here!
• If you are using steam and don't want automatic updates, set RPG Maker MV's update to manual instead of automatic.
  
  
• Make a backup of your Generator folder if you edited it.

If you have an old project that needs updating, do the following:

• Make a backup of your project.
• Create a new project or go to the NewData folder in your RPG Maker MV root (where MV is installed) folder.
• Copy the new js files (RPG*.js and Libs Folder) and replace the one in your -old project.
• DO NOT COPY plugins.js (the script file that stores all your plugin settings) or it will replace your plugin settings.
• Copy the new index.html file to your current project.
• Update gamefont.css just in case.
• It should now be updated!

If RPG MAKER MV 1.6.0 is not working for you:

• You can downgrade to 1.5.1 anytime.

Changelog

Upgrades//Bug Fixes

• Update of NW.js to version 0.25.4: which include better stability and support for latest js and more. When opening your old project, an update to the core js is needed, which the editor can do for you if you let it.
• Compiled with a more recent version of Qt, which fix a number of Editor problems that were the result of using an outdated version.
• Adding support for Steam language change in the MV Tools, all will now start in the language you select for RPG Maker MV.
• Fix to img\characters\People1.png Face
• Fix to Tilesets: \img\tilesets\Inside_B.png, Dungeon_B.png, Outside_C.png
• Fix to Developper Tool warning on start (debug)

Yanfly Script Changelog
http://yanfly.moe/2018/02/21/rpg-maker-mv-1-6-0-update-is-out-but/

REPORTING BUGS
In an effort to streamline our debugging process, we ask that you bring all serious issues – such as major bugs, program errors and other unsolved issues directly to our attention by sending an e-mail to our support address: support@rpgmakerweb.com. Alternatively, you can also send a support ticket through this form: https://www.rpgmakerweb.com/support/contact-us/tech. This will ensure that we’re aware of problems quickly, so that we can work on providing you with solutions.

We would also like to remind everyone:
MAKE A BACKUP OF YOUR PROJECT!

DOWNLOAD UPDATE ONLY
DOWNLOAD FULL INSTALLER

 

[Poryg]

While I fear the release of 1.6 has been premature, I am glad it's out at the same time!

 

[BlueMoon]

Woooow! I can test finally the features of the 1.6.0 version!
Cool
On the other hand, will GENE released on the official store, too?
I'm just curious to test it, too.

 

[OmnislashXX]

Too bad it doesn't work. (For some people.) I tell you what. When the issues get fixed, I'll buy GENE.

 

[Parallax Panda]

Like @Poryg said, I'm glad 1.6.0 is out but since I'm not the only one whom it doesn't seem to work for, it feels like maybe this cookie should've been baked in the oven for a little longer?

Anyway. I'll guess I go back and fool around in RPGmaker VxAce until the current 1.6.0 build is fixed. I've confidence the developers will get on top of this and work out the kinks in a short time-frame.

 

[BlueMoon]

I have to say that, on my side, the 1.6.0 works without any problem.
I'm not using the steam version, but the standalone one.
When i have time I will continue to test.

 

[LTN Games]

I've been using 1.6.0 since beta release and have nothing but joy from it, I hit a few snags during beta but all is well and lets just say, arrow functions, const, let, promises and many other ES6 features are so lovely.

 

[Jonforum]

i check this and study this today.
Hope to see new js and pixi integration and optimisation.
Thanks

 

[Sleepy Kitten Games]

Updated to 1.6.0, tried playtesting my game, threw this error before it even got to the title screen:

Spoiler

Posting about it here because I have no idea which plugin(s) are actually causing the error (since I've had numerous cases where MV throws an error and lists several plugins in the console, but updating one plugin made the error stop occurring).

 

[LTN Games]

@GameFire that's most likely due to SRD's Super Tools trying to create a new window based off the old version of nwjs. He will most likely have to update his plugins that open a new window for them to work with this update.

 

[RisenAngel]

I also get the feeling 1.6 should have stayed in beta for a little longer. In the brief time I tried it before reverting back to 1.5.1, the editor lagged like -arg- (whenever I clicked to open a menu it took a couple seconds for it to display, and in the case of the database sometimes threw a "Not Responding" window before it loaded), I had issues with music skipping when I moved the mouse over the editor window if I had music playing at the time, and then trying to set a B tile as event crashed the editor completely. Maybe some of these problems are from using MV on a 7+ year old computer, but that last one at least has been reported elsewhere.

The larger screen size was nice, though.

 

[LTN Games]

They could've stayed in beta for another year and not found every bug, the fact that only about 5 people I know helped with testing during the 2 months it's been in beta tells you how much people are willing to help out with finding bugs before official release. Then they complain when the official release is ready and there is bugs.
If not for the official release these bugs would've remained hidden, I believe its a smart move and a good way to reveal the bugs and squash them for the next mini update. Although most of these problems can be avoided if the community was willing to put in the extra work for a more stable product.

 

[mardin]

I love it so far... the larger screen size is awesome. It also is the first update that makes my bgm sounds work on android (which should have worked in the first place, shame on the developers).

Now all I need to do is wait until the plugins get updated as well and then I can release my game on mobile (finally).

 

[Poryg]

(which should have worked in the first place, shame on the developers).

No, android is a very difficult place to support.

 

[mardin]

No, android is a very difficult place to support.

What do you mean, no? No, it shouldn't have worked in the first place because it's difficult?! The main selling point for MV over VX Ace was mobile export!

 

[Craig]

I am assuming this is just a plugin that needs to be updated? Or is it something else?

Spoiler

 

[mardin]

I am assuming this is just a plugin that needs to be updated? Or is it something else?

Spoiler

View attachment 83409

I had this issue once on a previous update when I forgot to update the index.html file as well...

 

[Jomarcenter]

Been receiving multiple avast virus warning of Win32:BogEnt on game.exe and nw.exe despite being put the rpg maker MV engine as a exception while downloading the update.

I think the Dev team should sent a false positive report to avast and other anti-virus company if applicable.

 

[Poryg]

@mardin I'm just saying that it's not easy to ensure compatibility with Android devices, because you need to solve the same stuff differently and effectively have to support tens of thousands of not only indiviual devices, but also individual devices of individual OS. For example my device acted differently with Android 5.1 than it does with Android 6. It's not the fault of app devs that my OS update broke 30% of the apps and disabled GPS in my device when some other device with the same system has no problems with running it. And if you want to doubt me, then try developing an app for androids yourself. If you want, I can lend my device as one of the testing ones, since it has very specific demands due to being an unsupported Huawei brand device.

 

[Doktor_Q]

As someone who's been maintaining and updating old unsupported plugins for my own use, is there a more technical list of the changes that are causing all of these problems? Or even just a list of common tasks that work differently?