![]() The selling point of MV itself, a multiple port. VXAce can only support 640x480 before you started to use third party tool like resolution breaker script or RGD. ![]() MV natively support bigger screen by default. There had been a plugin that allow you to switch to 32px tiles, but afaik, it's really not convenient. Whether you like or not is entirely up to you. Creating multiple project is much space friendly than MV. VXAce in other hand, referenced the RTP to their respective folder. RTP, the new project you created in MV imports all(?) the resources in your project, effectively adds almost 400mb by creating a project alone. 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. Plugin control has more friendly config that you can easily turn on / off make it easier to control. If you prefer built-in script editor, you don't like MV. Unlike VXAce that you're bound to built-in script editor. If you're a scripter, and you want to use your fave IDE or text editor, you can. But for me, it was the whole reason I don't use MV. Whether it's a pros or cons is up to you. It understandable on the design perspective since MV value is for multi platform. First, and the first thing I noticed when tried MV is. Instead of pros and cons, it will be better to tell the difference between them since pros and cons are depends on each individual.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |