[RMMV] [RMVX ACE] PROS AND CONS: RMMV VS. VX ACE

The two engines are virtually the same with a few key differences:
Rpg MV database can store twice the amount of information in variables, switches,
and entry slots. The mapping resolution appears 1.5x better.
(48 pixels instead of 32). The selection of music is somehow limited.
Extra compatibility with smaller screens namely tabloid devices.

Hey there StormCrow!

Just wanted to say that RMMV by default doesn't have all there songs in it, the rest of them come in another folder which is titled base resources. If you purchase RMMV, you should get them both, just to be clear there.

When you put the extra resources into the default RMMV project you should have a good number of songs. I think then the number of songs are roughly the same as RMVXA.

You can also import as many songs as you want, or at least there is not limit to my knowledge.

Instead of pros and cons, it will be better to tell the difference between them since pros and cons are depends on each individual.

1. First, and the first thing I noticed when tried MV is. It doesn't play MIDI. It understandable on the design perspective since MV value is for multi platform. Whether it's a pros or cons is up to you. But for me, it was the whole reason I don't use MV.

2. MV does not have built-in script editor. If you're a scripter, and you want to use your fave IDE or text editor, you can. Unlike VXAce that you're bound to built-in script editor. If you prefer built-in script editor, you don't like MV.

3. Plugin control has more friendly config that you can easily turn on / off make it easier to control. And (maybe) a config that lead to less user config error, unlike VXAce which sometimes require the script user to have a little knowledge on scripting.

4. RTP, the new project you created in MV imports all(?) the resources in your project, effectively adds almost 400mb by creating a project alone. VXAce in other hand, referenced the RTP to their respective folder. Creating multiple project is much space friendly than MV.

5. Bigger tileset. MV use 48px tiles while Ace use 32px. Whether you like or not is entirely up to you. There had been a plugin that allow you to switch to 32px tiles, but afaik, it's really not convenient.

6. MV natively support bigger screen by default. VXAce can only support 640x480 before you started to use third party tool like resolution breaker script or RGD.

7. The selling point of MV itself, a multiple port. Cmiiw, the exe(?) of MV is effectively a browser, which mean it supposed to be able to run in other platform well. If you are aiming for multiple port, you should go with MV instead of sticking with Ace and try to get a workaround with it.

8. A dark theme in MV editor for people who prefer it.

9. Built-in sideview battle system and a better character generator that doesn't exist in VXAce. Granted, VXAce also has generator, but do people already use that?

10. Also another selling point of MV is that the developer still care about it and keep updating it. You can even suggest the improvement of it. While VXAce, you're stuck with this current version. No UI update, no QoL update whatsoever.

EDIT 2:
11. It also claimed that MV also use GPU advantage unlike VXAce that only use CPU that is supposed to make it run faster/smoother, yet in fact many reported that MV runs horrible compared to VXAce, so take it with a grain of salt.

There might be more things I missed, but idk.
-------------------
My personal preference?

I don't need all the additional features offered by MV. All they did was to remove something I need and introduce something I don't need. Including removing MIDI player and built-in script editor. I don't need multiple port so I have no reason to jump to MV.

Besides I already settled all the things I need for my game. I know how to script, and already have custom battle system in my hand. I don't want to redo all the things myself. Including to learn js and deal with external text editor.

I think multiple port itself is enough as a reason to jump over to MV though.
-------------------

EDIT: As for the question whether you want/need to buy it though, I'd say buy it anyway. But wait for sales. Even if you don't use it, having MV itself is already worth, just in case in future or so. Besides the new RTP resources aren't that bad

One thing to note as well, RGSS3 scripts are dying. People stop making a new script, so new plugin stuff mostly for MV. Most of nowdays scripter aren't interested to make new RGSS3 script. Or at least, as far as I know. However, that doesn't deny the fact that there are already plenty of RGSS3 scripts that available and already enough to make a lot of stuff.

Majority of VXAce user afaik are veterans and know what they are doing. They know how to deal with this fact, and maybe even create their own stuff for themselves. A new user (that maybe also don't know how to deal with the back-end of the script) should look at MV for better support.

I believe you can get trial versions of both, so you can check them out before deciding to purchase either.
Ace's Trial
MV's Trial

Checking out the trials give you a good feel for how they'll run on your computer as well as what they both have to offer. Both have limitations to the amount of things you can add for the trials but you should get a good feel for what the base engines feel like at least.

If you ever think about using lots of pictures in your game, or custom resources larger than the usual resolution then you should consider running away from MV. MV really does not like that.

Last time I used MV was like 5 weeks ago. It still puzzles me that I can play Batman: Arkham City on 60fps at full graphical settings and somehow a game engine that makes cheapo 2D snessy rpg's somehow makes my computer breathe heavy and reach for the inhaler. The lag is still very much present and ever the turd in the cherry pie. I will never not complain about this.

If I could have VX Ace with support for web browsers and mac executables I'd be so happy.
But i know that will never happen. The larger pool of exporting options is what's attractive about MV for me, but really, how larger would my audience really be, if lots of people will experience lag or will get odd bugs because MV had a panic attack when it saw the bunch of pictures I asked it to put on screen at the same time?

Maybe it's different for Mac computers, maybe the android builds arent super wonky like people say, i dont know because I am not being allowed to do what I want to do.

There is much that can be done with the engine, as some people on rmn have demonstrated with a few of their games, it just wasnt for me at the time I used it.

Get it on sale, it is being put in one often. I would have had a much louder tantrum had I paid full price for this crazy ride.

I can only say I kind of regret buying it, but then again I said the same thing about Ace when I first got it, so maybe what MV needs is time to become less disappointing. I don't know when that will happen or if it will, but yeah..

They're basically the same (sorta).
The tile size however bothers me, 48x48 is weird as it's 1.5x 32x32 and 32x32 is a lot cleaner to make.

MV has some issues likely caused by it being HTML5/web heavy but it was done in such a poor way it causes a lot of issues.

MV does allow you to use tiled which is nice but you can use the ace engine with XP so that kinda is a moot point.

I mean for desktop Ace > MV and I've used both.

My meager understanding is that some of the problems with MV may be the fault of the architecture it's based on (Node Webkit, which was already fairly old when MV was released) so there's no telling if those issues can ever be fully resolved.