SargeBaldy wrote:yeah i agree legacy might have done that i know eternity wouldn't have though
Legacy did something even more stupid: It applies damage immediately after entering a damaging sector.So it's impossible to run over some slime without getting hurt! It's this kind of non-improvements which is Legacy full of why I don't like it.
But they did keep the 2% chance of getting hurt by -20% sectors.
IIRC Legacy did that to stop people "bunny hopping" across damaging sectors and taking no damage. I'm not saying it was a good fix, but that's why it was done.
It's typical Legacy crap. Instead of applying damage when the player lands in such a sector they do it if he enters it. I found it totally annoying and it's one of the main reasons that I don't use Legacy for anything that doesn't explicitly require it. It's the classic case of a 'fix' that seriously alters gameplay and those suck!
Does Legacy really have any major additions besides multiplayer ingame joining, hacked-together 3D, and opengl? o.o (I'm not trying to bash it, really, I'm.. trying to figure out why the only Doomers who live around here use Legacy instead of ZDoom.)
But as you said: the 3D-stuff is hacked together and Legacy's OpenGL isn't that good to begin with. What can you say about a renderer which light effects look more like fog than light?
On the other side it has some serious gameplay issues like:
- no voodoo doll which breaks a lot of Boom levels (and hurts even some Final Doom levels, too!)
- the above mentioned damage issue
- no chance to limit a Pain Elemental to 21 Lost Souls as every other decent source port - the code for it has been completely removed.
- It's the only Boom-'compatible' port that doesn't incorporate MBF's gameplay fixes (I don't mean the AI enhancements, just the other stuff) - in fact it's so Boom-'compatible' that many newer Boom-maps don't work with it anymore.
and:
- it alters the system's sound settings
Unless the new version brings massive improvements and addresses all issues mentioned here, I'll never use it again.
Graphics Processor: ATI/AMD with Vulkan/Metal Support
Postby Chris »
- it alters the system's sound settings
If you mean volume, then this is actually the fault of Allegro (if it uses that for the Windows port). For some reason, Allegro changes the system's sound volumes. In it's defense though, Allegro does put them back the way they were when it exits (in the versions I've noticed this problem anyway).. not much of an excuse, I know. But that's not directly Legacy's fault.
Graphics Processor: ATI/AMD with Vulkan/Metal Support
Postby Chris »
Allegro's cool. And I'm not forgiving the Legacy team. They could easilly edit the Allegro source (it's really not that hard) and stop it from modifying the system volume.
The problem with Allegro is that it was originally a DOS-only lib. Then people started doing ports for it, to Windows, X, Unix, ect, and they all got lumped together at version 4. There are a few behavioral issues/inconsistencies yes, but they'll be ironed out as time progresses. I use Allegro for any app that I would normally need to use OS-specific calls for, so the program is, by default, cross-platform. And when I do need to do something OS-specific, I just remember to put a note to fix later, or put in other routines for other platforms on the spot. Considering I work in both Linux and WIndows now (actually since I've gotten my sound drivers working in Linux, I haven't touched Windows, heh), being cross-platform is pretty important. That, and the fact that I find being tied to one OS is fairly limiting in audience.
Chris wrote:I haven't touched Windows, heh), being cross-platform is pretty important. That, and the fact that I find being tied to one OS is fairly limiting in audience.
Yes, but you can't get the proper 'Look and Feel' without doing some platform specific things. True cross-platform apps nomally make nobody happy because they feel wrong everywhere. Of course this applies mainly to GUI-apps. For games it doesn't really matter.
If I have to write cross-platform apps I normally use a very thin layer I wrote myself to separate the platform specific stuff. All libraries designed to do this either have some serious flaws or usability issues (SDL's fucked up keyboard handling in fullscreen on Windows comes to mind...) I never used Allegro because currently it's too messy.