RPG Maker MV 1.3.3 Update

@haydengames3 You can go to Steam -> RPG Maker MV -> Properties -> Betas -> Choose v1.3.1.

 

Thank you, and to everyone else aswell, have a project coming up and I didn't want to let people down, have a good day everyone.

 

Yeah, I'm having the same json file bug as well.  What a let down.  I can't save any new characters.  So much for working on my games this week.

 

I wish this could be a general fix for all plugins.

 

Thank you for suggesting this.


I simply cannot praise you guys on an update that breaks an essential part of the software.

 

Created a brand new, empty project with 1.3.2 and deployed it to an iPad3 and it still runs very sluggishly.

 

I can't really answer that because all iOS devices have some manner of Apple-designed processor (even the very newest iPhones).


If I have an event set to wait 300 frames, it will take roughly 2X that on the iPad before it completes. Sound works normally, though, and things move more slowly but still not 2X as slow.


This leads me to believe it's an issue with the game artificially choking its framerate some how.


Here's an example of the same deploy of a fresh game running on iPad and Macbook side by side:


https://dl.dropboxusercontent.com/u/67091205/party_compare.mp4

 

Thanks so much for all your hard work, everyone! Just updated and everything is running as smoothly as possible.  

 

But guys, do you really expect miracles from MV? You are using Apple devices that are more than 4 years old.


Also the .json bug is something minor come on, I never even bothered using that thing in MV when making my characters. Not even once.

 

Oh this is well

 

That you can only take to the pluginwriters themselves and ask them why they don't update their plugins.


The specifications on how to register plugin resources with the engine to prevent their removal on deployment has been part of the helpfile since the "exclude unused files" option had been added, they just have to add those lines to their plugins.


But Degica and Kadokawa can't rewrite all plugins, and they can't even know which plugins need which files, so this has to be done by the plugin writer who wrote the plugin.

 

So at which point in Apple's mobile lineup should MV run properly?

Four years old and are still the most used tablets out there, and iPad2 still has the highest % of usage out of all Apple tablets.


And not trying to be mean, but I hardly consider one 2D object moving across another without dramatic slowing to be a "miracle".

 

So we should wait until the character generation stuff is fixed, should i go back to the 1.3.1 or wait until the 1.3.3? 

 

In the article you link, the guy mentions this file format: pvr.ccz. I am unfamiliar with this despite a degree in graphics. It isn't an export option in photoshop, at least not the aging version I have access to. If it's better for the system than .png, how does one export to it, and can MV use this file type? I did some pc configuration stuff and got my game to run smoothly, but my ram is always maxed out because my maps are image based and don't use tyles. I csn play around in it now without a crash, but I'm looking for further optimization. I will adjust what i can per article instructions, but this file type eludes me. Any info on the matter would be greatly appreciated. Especially how one would convert to this file type and if mv can use it. Thanks, guys.

 

Are there any plans for further optimization on these platforms?


I'm currently working on games that are designed to be played by a parent and child together in front of an iPad (the touch functionality is vital) and was planning to use RMMV to handle characters, events, and whatnot.


I understand if there's no further plans for optimization, but I just need to know now to plan for the future.

 

There is a gigantic difference between something running off of native (compiled) code, and something running off of interpreted code. JavaScript is interpreted code. Most, if not all systems running on mobile primarily from JavaScript are going to face these issues. I imagine JavaScript was chosen for this engine as it is highly approachable from a programming perspective.


In the case of MV, the heavy lifting is done by a web browser shell with the game running inside. Any systems that use this format are naturally not going to be as fast as something that is compiled into the native format for that particular device.


In a case like this, it comes down to developers to optimise as best they can with the system they choose to use.

Ooo! Do want. I've never been a fan of parallax mapping, and never quite succeeded in impressing on others how bad for performance and game size it is.