Peer pressured badly to switch engines?
I did forget about MV's crashing, but that might happen on XP with large and ambitious enough games, as well. I should mention, crashing never ocurred much during PFCs development. I only remember one or two times.
A game like Fantasia just wouldn't be possible in XP. XP like VX and Ace is built with only RPGs in mind, and trying to stretch the makers beyond that capacity can be done, but its hard to make it work well. In MV, there's a lot more optimization.
I also shall say what Steel6 said earlier, that expecting the community to supply scripts for features that should be baseline is not an excuse in the engine's favor.
I'm comparing RTPs for the general use of it, I never personally use the RTP so that doesn't effect me in the slightest.
There was a noticeable downgrade in VX, especially in the music and sounds from XP, but then a noticable visual upgrade in MV where they finally ditched that ugly purple shading technique. Also the music in MV is fire.
We don't really talk about MZ. It's the VX of the Javascript engines.
XP was impressive for its time. It isn't anymore.
As for the resolution thing. yeah you can upscale it like that. but are you really gonna go and do that for every window and viewport? As you might notice, it appears the text window is overlaying Aluxes. But realistically, that's just as far as the the default resolution takes it. nothing was dynamic back in this day and age. The screen size and view port have changed, but the resolution of the windows hasn't. Your own screenshot confirms this.
Meanwhile in MV, it reads the resolution typed in and auto-resizes everything to scale with the resolution entered. because of this, every plugin or script created does so as well. The comparison is blazay and in your own words DerVVulfman, misguided and flawed.
A game like Fantasia just wouldn't be possible in XP. XP like VX and Ace is built with only RPGs in mind, and trying to stretch the makers beyond that capacity can be done, but its hard to make it work well. In MV, there's a lot more optimization.
I also shall say what Steel6 said earlier, that expecting the community to supply scripts for features that should be baseline is not an excuse in the engine's favor.
I'm comparing RTPs for the general use of it, I never personally use the RTP so that doesn't effect me in the slightest.
There was a noticeable downgrade in VX, especially in the music and sounds from XP, but then a noticable visual upgrade in MV where they finally ditched that ugly purple shading technique. Also the music in MV is fire.
We don't really talk about MZ. It's the VX of the Javascript engines.
XP was impressive for its time. It isn't anymore.
As for the resolution thing. yeah you can upscale it like that. but are you really gonna go and do that for every window and viewport? As you might notice, it appears the text window is overlaying Aluxes. But realistically, that's just as far as the the default resolution takes it. nothing was dynamic back in this day and age. The screen size and view port have changed, but the resolution of the windows hasn't. Your own screenshot confirms this.
Meanwhile in MV, it reads the resolution typed in and auto-resizes everything to scale with the resolution entered. because of this, every plugin or script created does so as well. The comparison is blazay and in your own words DerVVulfman, misguided and flawed.