RPG MAKER VX ACE

author=Despain

author=Archeia_Nessiah
And the layers are still the same :C

Upper = XP
Lower = VXAce screenshot that is so tiny ffff

three layers? YESS!!!! RMVX has no layers at all, but some horrible two-layer system that's based on the tiles themselves. really, VX with XP's mapping system would be more than enough to make me happy.

EDIT:

ahhahhahaha the dub is so bad.

If I'm not mistaken, XP had 4 layers with one of those layers being events. VX always had 3 layers, with the third layer being events. Looking at the image, the Ace seems very similar in layers to VX, so unless I'm mistaken, the 3 layers you are seeing is the same as VX, since the third layer is handled with events.

I haven't used RM2K/3 a whole lot, so not sure what the difference in layering is compared to VX. Could you fill me in?

That RPG VXAce trailer failed to sell me. They need to show details.

author=amerkevicius
I haven't used RM2K/3 a whole lot, so not sure what the difference in layering is compared to VX. Could you fill me in?

Fallen-Griever
I don't know how VX works, but I do know that RM2K/3 allowed for way more chipsets.

The way RMVX's layer system works is a bit convoluted.

There are three layers in VX just like in RM2K(3): Bottom, Upper, and Event layers. The difference between VX and RM2K(3) is in the way the layers are handled, specifically the way Bottom and Upper layers are treated.

In RM2K(3), the Bottom and Upper layers were always separated and independent from each other. This meant, for example, that you could select a bunch of tiles on the Upper layer that you already placed and move them around without disturbing what was below in the Bottom layer. You could also erase and/or redraw an Upper tile without disturbing the Bottom layer tile.

In RMVX on the other hand, the Bottom and Upper layers are treated as one single layer once you place the tiles. This means that if you wanted to change a tile in the Upper layer, you also disturbed the tile on the Bottom layer. If you wanted to move an Upper layer tile, you also have to move the tile below it on the Bottom layer. This obviously leads to unneccesary headaches as it entails much more work even for just a very minor edit to a map.

For an easy-to-relate example, pretend you're working in Photoshop and after every single action you always flatten the image (combine all layers). That is what RMVX is effectively doing and it's immediately obvious how stupid that is.

Thankfully, the Event layer in RMVX is at least separate like it was in RM2K(3), but it isn't really much of a consolation all things considered.

Thanks, King, that explains a lot. I guess it hasn't bothered me all that much, but I do see the point of not being able to adjust the upper layers without fudging up the bottom.

Of course, with idiotic borders around the auto-tiles, it gets frustrating having to manipulate the upper pieces just so grass forms correctly behind a building, instead of somehow appearing to run around the roof.

I'm more concerned with learning more about paint/image programs so I can test my hand at tweaking the squares into octagonal shapes like XP to make a more natural, less blocky look.

But at least they brought back unlimited tilesets and added a few additional features.

About damn time we can use variables for calculating damage.

Versalia, convenience. Not everyone wants to open the Script Editor for everything. :)

author=Versalia
Open it ONE time, write your script snippet, use <damage: type> tag without ever opening the script editor again. This is a pretty weak argument. It's like saying you shouldn't have to open the database for everything. They're just the front and back of the exact same interface.

Well, not everyone will be using YEM, you know.
Although it is an excellent script compilation, it doesn't fit everyone's needs.

In general, an average user would probably pick a built-in damage algorithm editor than opening the script editor and finding and using the damage formulations in there (even more if they don't use a script that makes this easier). RGSS(3!) still exists for those who want "advanced" control over their damage algorithms.

e:
It's maybe the same thing, but it'd be easier and much more convenient for people now (time saver, ease of use, and user friendliness). Forgettable Forgetful people can forget what script snippet they wrote and will have to refer into the editor every time. Including it in the database makes it much easier for them.

That's been my primary argument about the Ace. It's great for newbies and people who don't want anything to do with scripts, but those who've already mastered the VX will be able to do just about everything in VX that can be done with the Ace and will be hard-pressed to spend the money on a program where they already have the same features.

I do admit convenience is a factor, and I like having the face/sprite maker in the program, but again, there are programs available for free that make this possible with VX.

I will say one thing: While we do have SwapXT, and it was a Godsend over the past couple years, it can be tedious to use if you are planning a big project and trying to remember all the various profiles you might have. At least this way, it's all included in the package and will hopefully make things easier with mapping.

However, easier mapping doesn't necessarily mean "improved" mapping, which is my biggest gripe.

What they really should have considered was a separate mapping editor that allowed parallaxing to be done within the editor. Until they get smart about features people really want and can use (parallax mapping, stacking events, resolution, etc), it's really nothing more than an upgrade, and unfortunately as an upgrade it's just going to encourage people to go out and download illegal copies.

IT'S F*CKING CONFIRMED VXACE IS USING RUBY 1.9
HERE

I recently visited the blog of someone who's had playtime with RPG Maker VX Ace. It's the author of one of the sample games that will be coming with the Japanese edition. They recently made a new post explaining things about RGSS3, and it confirms that RGSS3 will utilize Ruby 1.9.2.

http://d.hatena.ne.jp/ktakaki/20111201

Here are some new features as YF eloquently translated:

More importantly, a new automatic event trigger called "Near Screen". It's different from Autostart and Parallel. And only triggers once it enters visible screen and TP is toggle-able.

Fiber classes used instead of Game_Interpreter. Fibers are basically ran externally. Which means, Game_Interpreter won't slow down the system at all. Thus! Event Systems are legit!

Nessy observations and YF confirms a lot of these stuffs:

According to the first paragraph, aside from the upgrade from Ruby 1.8-1.9 and the Fiber classes, they also said the specs for the PC has been increased thus making VXAce becoming more "heavy" (such improvements is the Direct X). They also commented that they are very happy about the increase in speed in VXAce.

They are also talking about a new feature. Basically, in VX, all the Scenes are child classes of Scene_Base. Now, there's an even more... erm, higher tier overseer. and this is the SceneManager. There is also a BattleManager. Game_CharacterBase and all that stuff.

I also noticed they made the scripting more simpler now, such examples:

@ Cache | | = {}

is now

if @ cache! = nil
@ Cache = @ cache
else
@ Cache = {}
end

And it's more aimed towards beginners. But also beautifully coded as they said here.


They were also saying something about the helpfile being more friendly. However there's this part here called Part decoding where everyone even the veterans should read because of the massive changes in RGSS3.

While RGSS isn't the most efficient, it still is limited by what version of Ruby is capable to do. So Ruby 1.9 is a great upgrade still~