Announcement RPG Maker MV - v1.6.1 Stable Release!

[Mrs_Allykat]

LOL! I love "should" Anyway, thank you for the responses. I feel better now. I forgot that I had opted for 1.52 beta, and you're correct that should prevent any surprises. (Just in case, I made a back up of the generator folder!)

 

[TheOddFellow]

RPG Maker MV updated today, and it was the previous release (I auto-update the RPG Maker.) And F9 does not bring up variables and switches, and holding control won't let me go past walls.
I *did* upload a game for my friends to playtest, and haven't brought the game up myself since then.
I only bring this up now because of the update, and this hasn't happened before.

 

[Archeia]

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.

 

[Franklin_Van_Ruin]

I guess there is something to be said about having my first post ever since registration being a complaint.

I bought RPG Maker MV since October and I've generally used it without many issues, however after this update my antivirus software detected the main .exe as malware which, based on the fact that it never happened before, leads me to believe that something changed. I would like to know what exactly changed because there is no way in hell I'm making a security exception and I would rather not move the software to my DMZ.

Additionally, if possible, I would like to know if there is some method to perform a roll-back to the previous version so I don't have to deal with this.

 

[Archeia]

I guess there is something to be said about having my first post ever since registration being a complaint.

I bought RPG Maker MV since October and I've generally used it without many issues, however after this update my antivirus software detected the main .exe as malware which, based on the fact that it never happened before, leads me to believe that something changed. I would like to know what exactly changed because there is no way in hell I'm making a security exception and I would rather not move the software to my DMZ.

Additionally, if possible, I would like to know if there is some method to perform a roll-back to the previous version so I don't have to deal with this.

Your copy of RPG Maker MV standalone does not auto-update. Also RPG Maker MV always had false positive reports in previous versions. It just varies. The main post should tell you how to downgrade. If you're steam, it tells there too.

Looks like doodads isn't compatible with 1.6.1

False. Do a proper update.

Spoiler

 

[fizzly]

False. Do a proper update.
[/spoiler]

Interesting... I'll try again, then. Thanks for checking that out.

 

[Dankovsky]

[rmod]

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.

[/rmod]

Does this mean we can't report and share plugin problems and incompatibilities publically in this thread? This is important information for the users to share and discuss. I'm sure lots of problems are caused by incorrect upgrade, but I'm sure there can be plenty of actual incompatibilities and possible game-breaking issues. Should we create 1.6.1. plugin problems thread instead?

 

[Aloe Guvner]

This is just my opinion, obviously, and not an official view.
Kadokawa doesn't have to support any plugins besides the few official ones that come with the engine. Sure, they try to keep compatibility in mind, but the plugin ecosystem is not their responsibility.
This thread should be for questions directly pertaining to the 1.6.1 update and the basic engine. If there's truly an issue with a plugin (and the steps to upgrade were actually followed), then the plugin issue should be posted in the same place we always post it - either the plugin's own thread or in the "Plugin Support" forum.

Again, just my personal opinion, but I think you'll get the most help by following the normal procedure.

 

[SOC]

[rmod]

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.

[/rmod]

I have done this correctly and even did it again to make sure, and my RMMV still only shows the splash window then auto closes.

 

[Jonforum]

am sick or I already have version 1.6.1 for a long time?
this version seem have 2 day ?
if i understand this is the version 1.6.11 (1.6.1)
and the beta was 1.6.10 ? (1.6.1b)
i have the same version after update ?
it destabilizes me a little.

 

[Sharm]

Version 1.6.1 was out before, but there was a major problem that wasn't discovered in testing so it had to be rolled back to an earlier version while the huge bug was squashed. So maybe you didn't do the rollback? People are a little more aware of the need to join in with the (completely open, you're free to join too) testing process now so hopefully this sort of thing will be caught in the future.

 

[Jonforum]

Version 1.6.1 was out before, but there was a major problem that wasn't discovered in testing so it had to be rolled back to an earlier version while the huge bug was squashed. So maybe you didn't do the rollback? People are a little more aware of the need to join in with the (completely open, you're free to join too) testing process now so hopefully this sort of thing will be caught in the future.

thank also if you have any idea here , discussion about a strange issue in rmmv about the graphic update.
http://www.html5gamedevs.com/topic/38309-animatedspriteprototypeupdate-doesnt-update-rpg-maker-mv/

Not sure since when, long time not work with animations, but now all animations Sprites also include Videos elements need to hack update.
I don't know if it chromium or the nodejs or the new rmmv core 1.6.1 , but pixiTikers not seem scoped shared anymore to the update textures.
Need to hack it manually.

    var aniContainer = new PIXI.Container();
    var aniSprite = new PIXI.extras.AnimatedSprite(frames);
    aniContainer.addChild(aniSprite);
// hack update tiker (rmmv chromium seem not take anymore the core shared tiker, i don't know why)
// you need to scope the tikers or force a default value.
    aniContainer.update = function(detla=1){
        aniSprite.update(detla);
    }

// add container to rendered screen
    SceneManager._scene.children[0].addChild(aniContainer);

But what it very very strange, if i force open project with fireFox ! no need hack, the update work and animations or video work!!
did you have any idea what append here, ?

 

[Sharm]

Me? I don't know anything about programming. I don't even know enough about it to know if what your asking is off topic or not.

 

[Aloe Guvner]

@Jonforum I don't think that this behavior is due to the changes in the RPG Maker MV core scripts from the 1.6.1 BETA to the 1.6.1 STABLE. You can check a comparison I did here for all the engine core script changes.

PIXI version is also the same. So maybe something with the nw.js version.

 

[Archeia]

Does this mean we can't report and share plugin problems and incompatibilities publically in this thread? This is important information for the users to share and discuss. I'm sure lots of problems are caused by incorrect upgrade, but I'm sure there can be plenty of actual incompatibilities and possible game-breaking issues. Should we create 1.6.1. plugin problems thread instead?

This is just my opinion, obviously, and not an official view.
Kadokawa doesn't have to support any plugins besides the few official ones that come with the engine. Sure, they try to keep compatibility in mind, but the plugin ecosystem is not their responsibility.
This thread should be for questions directly pertaining to the 1.6.1 update and the basic engine. If there's truly an issue with a plugin (and the steps to upgrade were actually followed), then the plugin issue should be posted in the same place we always post it - either the plugin's own thread or in the "Plugin Support" forum.

Again, just my personal opinion, but I think you'll get the most help by following the normal procedure.

Pretty much post to the plugin developers or post in Javascript Support Boards.

Care to explain why you've censored one of the default sprites?

No idea. Maybe there's a change in rules in CERO Japan for all we know.

 

[ArielSystem]

For me, I should Reinstall it because It's always forced to "Close the Program" instead "Wait the Program to Respond"

 

[Jonforum]

@Jonforum I don't think that this behavior is due to the changes in the RPG Maker MV core scripts from the 1.6.1 BETA to the 1.6.1 STABLE. You can check a comparison I did here for all the engine core script changes.

PIXI version is also the same. So maybe something with the nw.js version.

i also think it from chromium or nwjs.
For now i don't know how solve it, we need manually add a update hack.
am waiting more info from pixiGuys or rmmv dev.
In fireFox, no need hack, only in chromium.

It same thing for play with native video canvas

Scene_Title.prototype.createVideoPlayBack = function() {
    const vidTextures1 = $Loader.ress.title.intro_vid1.vidTextures;
    const vidControler1 = $Loader.ress.title.intro_vid1.vidControler;
    var videoSprite1 = new PIXI.Sprite(vidTextures1);
    // hack video update
        videoSprite1.update = function() {
            vidTextures1.update();
        };
    this.vidControler1 = vidControler1;
    this.addChild(videoSprite1);

};

 

[liamx2000]

I have the steam version installed and every time I got an update for MV my game project would be fine along with the newer update but now after this update I can no longer test battles , every time I go to test battles it just now takes me to the title screen , so I decided to test a battle in game on a map and the battle works that way it just will no longer work in Test battle.....
Is there a way to fix this ?

 

[Oscar92player]

I have the steam version installed and every time I got an update for MV my game project would be fine along with the newer update but now after this update I can no longer test battles , every time I go to test battles it just now takes me to the title screen , so I decided to test a battle in game on a map and the battle works that way it just will no longer work in Test battle.....
Is there a way to fix this ?

And this kind of issue was supposed to be reported in the Improvements forum within the thread for the 1.6.1 Beta version. Why is this bug still there?

I haven't tested this 'stable release', and I'm having doubts about it, if a reported bug like this one is still happening...

I will wait, just to see what happens with other users.

 

[Aloe Guvner]

@liamx2000
Does it happen on a new project?

If not, it's because you didn't follow the steps to update your existing project.
Somebody posted the exact same "bug" earlier today and it was because they hadn't updated their project:
https://forums.rpgmakerweb.com/index.php?threads/battle-test-opens-up-title-screen.96727/