RPG Maker MV 1.3.3 Update

Archeia · 2016-10-20T18:23:18+0900

Hey everyone, the latest version of RPG Maker MV is here! 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 Generator folder if you edited it. If you already upgraded from 1.2.0 this is unnecessary. Replace BGM files if you got it from 1.3.0. 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 or it will replace your plugin settings. Copy index.html files to your current project. It should now be updated! Download Links (1.3.3) Update Only Latest Full Installer Download Links (1.3.2) Update Only Latest Full Installer Reporting Issues Script Changelog http://yanfly.moe/2016/10/20/rpg-maker-mv-1-3-2-update/ Editor Fixes Character Generator JSON Save and Load is fixed. RPG* Updates Fix to the Skill owned condition in Event Condition Fixed some crashes in mobile play Fixed to the Scroll Text event command Pixi Bug: Unnatural Tile Scaling Pixi Bug: resolution is not defined WebGL Blend Mode: Overlay not working on certain features Character Generator：ID can now not be sequential, and qXXX can be used for ID too Fix to the damage popup when drain skill is reflected TilingSprite Scale Bug Fix to prevent negative value to be entered in Attack State Support for Direct Input Controllers (not ALL controller are supported) Plugin Updates Fix to some Kadokawa scripts so that their files are not removed by the "Removed unused files" in Deployment BattleVoice.js Foreground.js TinyGetInfoWnd.js

● ARCHIVED · READ-ONLY

Started by Archeia Oct 20, 2016, 09:23 AM 266 posts Page 8 of 14 View original ↗

takuantoono

#141 Oct 22, 2016, 05:00 AM Source

I'm afraid that ver 1.3.3 still has lethal memory leak bug which might cause crash your game very quickly.

To replicate this, please make new project and implement test play, but what you need to do is only to keep opening and closing menu screen, while watching task manager.

Then you can probably see dramatic ascending amount used memory (30-50 MB par one open- close ), which will result in heavy lagging or crash game screen.

And more, I realized that even only "show text" command or very normal battle screen also has memory leak.

Any patches for memory leak can do nothing this problem.

I hope developer team already be aware of this serious problem and it can be solved next update soon.
Ai696

#142 Oct 22, 2016, 05:31 AM Source

KaYsEr said:
Might be a good habit to get close to a POT (for some situations when possible) in order to exploit the "waste of memory" once in RAM, but keep in mind nothing in MV can really be a POT since the tile-size is 48 by default. 16 or 32 are POT... 48 is not, the next POT is 64.

Maybe those people advocating POT are talking from a 3D-texturing point of view (in a real time situation of course, because in CGI trust me we don't bother with optimization that much haha), no time to read those links tonight I'm afraid, but I think you can relax about that, it's not an issue for RM imo.

Exactly right when in terms of "people coming from 3d texturing." I think I'm more worried in terms of textures I use for graphics effects / particles. And the fact that I grew up learning that making an texture atlas is a preferred method for designing games. So for particle systems/light systems I cut out from a POT atlas.

I just found it shocking to learn that NPOT was a thing, and that people advocated it as a reason why memory may be high. What I'm actually wondering is if they meant really large pointless images (for parallaxes and stuff) and cutting those down into smaller pieces, over using NPOT...

Whatever, its not the biggest of deal breakers/problems... just a concern/confusion I wanted to sort.
Archeia

#143 Oct 22, 2016, 06:46 AM Source

Oscar92player said:
This problem happen only if you work with the actual version of YEP Core Engine, and happen with the fullscren mode too. If you disable the COre Engine, the game runs fine. I already reported this bug to @Yanfly in his topic:

Try this. Press F4, then if it's still like that, Press F3 again. If it's right it should be big.

I actually requested @Yanfly to add something in his Core Engine code because I wasn't sure if it's going to get approved. It was causing some rendering problems. But before that, I wanted to be sure that it's something you already tried doing that first.

Anisoft said:
I just found it shocking to learn that NPOT was a thing, and that people advocated it as a reason why memory may be high. What I'm actually wondering is if they meant really large pointless images (for parallaxes and stuff) and cutting those down into smaller pieces, over using NPOT...

We were talking about how people are using more than 1024 (or even bordering there) for parallaxes and some such. It's one thing if it's just ONE image, it usually hits 3~5 or so images per map. That is a problem.
Ai696

#144 Oct 22, 2016, 06:52 AM Source

Archeia said:
We were talking about how people are using more than 1024 (or even bordering there) for parallaxes and some such. It's one thing if it's just ONE image, it usually hits 3~5 or so images per map. That is a problem.

Oh okay, I thought it was something like that. Sorry for the derail and for clarifying.
Megablackdragon31

#145 Oct 22, 2016, 07:27 AM Source

Yana made a patch for the skills learning bug present in the latest version.

https://twitter.com/yanatsuki_/status/789349648607514624

By my part im going to wait until a more stable release,until then i will use 1.3.1.
Dad3353

#146 Oct 22, 2016, 07:32 AM Source

takuantoono said:
I'm afraid that ver 1.3.3 still has lethal memory leak bug...

Whilst it's true that memory usage increases dramatically if one 'hammers' the Menu On-Off, it also reduces automatically after a short while, presumably when the 'Garbage Collection' kicks in, every few minutes. In 'real life' gaming, this is unlikely to be a problem; the memory usage will not cumulate fast enough to 'crash' a Game (at least, that's my experience since 1.3.3...). Projects that I had that could not play for more than a few minutes now run smoothly, with no more 'crashes'.

Hope this helps.
CrimsonNightfox

#147 Oct 22, 2016, 07:34 AM Source

I just wanna know how I could fix the size. That's all. All this heavy info is putting a strain on my head. Give it to me short please?
Hikitsune-Red

#148 Oct 22, 2016, 11:26 AM Source

CrimsonNightfox said:
I just wanna know how I could fix the size. That's all. All this heavy info is putting a strain on my head. Give it to me short please?

At the moment, Archeia's fix below this post.

Archeia

#149 Oct 22, 2016, 11:28 AM Source

CrimsonNightfox said:

I just wanna know how I could fix the size. That's all. All this heavy info is putting a strain on my head. Give it to me short please?

You are using Core Engine right?

remove this line

Code:

	//=============================================================================
	// Graphics
	//=============================================================================
	Graphics._updateRealScale = function() {
	  if (this._stretchEnabled) {
	    var h = window.innerWidth / this._width;
	    var v = window.innerHeight / this._height;
	    this._realScale = Math.min(h, v);
	    if (this._realScale &gt;= 3) this._realScale = 3;
	    else if (this._realScale &gt;= 2) this._realScale = 2;
	    else if (this._realScale &gt;= 1.5) this._realScale = 1.5;
	    else if (this._realScale &gt;= 1) this._realScale = 1;
	    else this._realScale = 0.5;
	  } else {
	    this._realScale = this._scale;
	  }
	};

Oscar92player

#150 Oct 22, 2016, 02:15 PM Source
Archeia said:
Try this. Press F4, then if it's still like that, Press F3 again. If it's right it should be big.

I already tried when the error appeared for first time, but nothing happens, sorry.
Archeia said:
You are using Core Engine right?

remove this line

Code:
//============================================================================= // Graphics //============================================================================= Graphics._updateRealScale = function() { if (this._stretchEnabled) { var h = window.innerWidth / this._width; var v = window.innerHeight / this._height; this._realScale = Math.min(h, v); if (this._realScale >= 3) this._realScale = 3; else if (this._realScale >= 2) this._realScale = 2; else if (this._realScale >= 1.5) this._realScale = 1.5; else if (this._realScale >= 1) this._realScale = 1; else this._realScale = 0.5; } else { this._realScale = this._scale; } };
I'll try this fix, but I'm agree with Yanfly. This resolution problems should be fixed if the editor itself give an option to change the resolution of the project, insted of using plugins for that purpose. I understand, too, that developers don't want to approve the resolution change inside the MV editor, maybe they have it's own reasons for that, but for many people using RPG Maker, this change it's necessary for the actual desktop and mobile devices.
Hackerham

#151 Oct 22, 2016, 02:19 PM Source

Oscar92player said:
I'll try this fix, but I'm agree with Yanfly. This resolution problems should be fixed if the editor itself give an option to change the resolution of the project, insted of using plugins for that purpose. I understand, too, that developers don't want to approve the resolution change inside the MV editor, maybe they have it's own reasons for that, but for many people using RPG Maker, this change it's necessary for the actual desktop and mobile devices.

Well, first &gt is actually ">" symbol :)

Second, devs just cant decide what to do with it, so this place is OK for modding.
jupitersdaughter

#152 Oct 22, 2016, 02:24 PM Source

Yanfly said:
My main suggestion? About how to fix this problem once and for all?

Can the developers PLEASE implement INHERENT options found within the EDITOR to alter the screen resolution. This is year 2016. The majority of the world isn't running 4:3 ratio screen resolutions anymore, and instead, are making games that fit wide-screen, mobile devices, etc. If RPG Maker MV is to be made to accomodate for desktop AND mobile, then why isn't there an option to do such a thing in the editor? It's only the sensible thing to do. Resolution control is an absolutely vital feature for development for games made in the year 2016 and onward.

What is NOT sensible is to rely on plugins to do these kinds of things. Plugins like mine shouldn't have to exist to add in completely basic features that ought to be available in the first place.

I never understood why it wasn't native. Every other engine I've worked in has had some sort of resolution option. However, for ease of use, RPGM is more hard-coded so I assumed that it was hard too implement (but since you had a pretty much day one plugin that did it...)
Yanfly

#153 Oct 22, 2016, 02:26 PM Source

The Yanfly Engine Core is updated 1.20. You can grab it here. I might be making updates to it later but overall, the main issues have been taken care of.

This should serve to fix the issue that @CrimsonNightfox and @Oscar92player were having regarding scaling.

In addition to that, a few other changes have been made to serve as a means to clear staggering objects from memory. I'm not 100% sure it will solve everything, but it should solve quite a bit.
Oscar92player

#154 Oct 22, 2016, 03:20 PM Source

Yanfly said:
The Yanfly Engine Core is updated 1.20. You can grab it here. I might be making updates to it later but overall, the main issues have been taken care of.

This should serve to fix the issue that @CrimsonNightfox and @Oscar92player were having regarding scaling.

In addition to that, a few other changes have been made to serve as a means to clear staggering objects from memory. I'm not 100% sure it will solve everything, but it should solve quite a bit.

Thanks, Yanfly. The fullscreen mode works fine with the changes you made.
Smartboy123

#155 Oct 22, 2016, 03:33 PM Source

So I've been off the train for a while. Didn't notice that I had v1.0. I just downloaded and updated to 1.3.3. I made the backups and copied over the new js files as told to do so. Now, whenever I go to open the software it asks me for a Product Key. However, I bought this off Steam a long time ago and was never given a Product Key (Steam just loads it up normally. Never used a key). What can I do to fix this and get back into making my game? I love this software and want to continue working on my project.
Andar

#156 Oct 22, 2016, 04:01 PM Source

Smartboy123 said:
However, I bought this off Steam a long time ago and was never given a Product Key

You installed the standalone version in addition to the steam version, you only need a product key for the standalone version, never for the steam version.

And steam has its own, automatic update function - you should never have installed the exe from this topic.

If you still had 1.0 on steam, that means you disabled the automatic updates for steam - please go into the steam program properties of MV, and make sure that

1) the beta setting is to off

2) the automatic updates are enabled

Then you'll get automatically updated to the newest version whenever it is released, no need for any manual editor update (you only have to update your projects manually like averone else)
_Chronos_

#157 Oct 22, 2016, 04:45 PM Source

jupitersdaughter said:
I never understood why it wasn't native. Every other engine I've worked in has had some sort of resolution option. However, for ease of use, RPGM is more hard-coded so I assumed that it was hard too implement (but since you had a pretty much day one plugin that did it...)

It should just be an option in the system tab, let the user decide the resolution.

But MV makes it pretty easy to do with a script.
Smartboy123

#158 Oct 22, 2016, 06:07 PM Source

Andar said:
You installed the standalone version in addition to the steam version, you only need a product key for the standalone version, never for the steam version.

And steam has its own, automatic update function - you should never have installed the exe from this topic.

Okay. So I want to be careful going forward. I did Backup Up the local files via Steam. I am thinking just wipe the local files I have then recover the Backup files? Ill save a second copy elsewhere with the data just to safe.
SimProse

#159 Oct 22, 2016, 07:09 PM Source

Nice work with the new Yanfly Core! I don't know if its normal, but my game is now a good 10% faster than before (of course, I was still using version Core 1.15, it appears).
Yanfly

#160 Oct 22, 2016, 07:57 PM Source

SimProse said:
Nice work with the new Yanfly Core! I don't know if its normal, but my game is now a good 10% faster than before (of course, I was still using version Core 1.15, it appears).

It was something purely experimental I wanted to try out, but I had a bit of inspiration from the changes made by Ivan to the 1.3.2 source code. I took it a step further and removed each and every addition added on to the heavier scenes: the map and the battle. All child elements added by the scene are to be cleared as the scene switches to keep the running game light-weight on memory consumption.