What 1.0 Did Better...

[Gilraen]

all animations were simplified to partly because the game lagged terribly on anything but the best pcs of the day and even then only just.

Yeah, too many people watching videos of people playing then, not quite realizing that those videos were likely made on PCs that cost a fortune. My laptop, an Asus g53sx, was only a few months old at the time and couldn't handle much more than medium settings, and that was in the field. In town the draw distance was terrible. 1.# was made using a 'game' engine that was designed for making cutscenes, and what beautiful cutscenes they were. But such an engine a game does not play well with average PCs, even today.

[Qeius]

The cut scenes were suppose to be fully voiced always at some point, i also miss the tall white haired elf guy that basically became the twins.

[MYFATHERBEATSME]

actually my comment had nothing to do with why it failed or even running animations, it was just a joke at the title of the thread. xD

I see -_-...but still, that running animation...

[Avin00]

But with how far the standard of gaming systems have come, it is probably possible to reintroduce this feature without it being an issue. just maybe .

doubt it the fact it didn't run well on those systems means that integrating those animations and anything else would have negative consequences on the majority of players as most people do not have top of the line systems required to run 1.0 at full spec. I'm talking about now btw I think we have just caught up to the true recommended specs for 1.0.

[Kaisha]

1.0 animations only looked good as long as you were running on a flat surface. Not suddenly going up a two foot steep climb because the devs realized how much a nuisance it was back then to have to run around even single little piece of ground that was more than a foot step high, because we couldn't simply jump over minor obstacles.

While they looked nice in general, I would never want them in dodge-heavy fights where I always want to know exactly where I'm standing without having to second guess the movement animation.

[MYFATHERBEATSME]

Yeah, too many people watching videos of people playing then, not quite realizing that those videos were likely made on PCs that cost a fortune. My laptop, an Asus g53sx, was only a few months old at the time and couldn't handle much more than medium settings, and that was in the field. In town the draw distance was terrible. 1.# was made using a 'game' engine that was designed for making cutscenes, and what beautiful cutscenes they were. But such an engine a game does not play well with average PCs, even today.

That whole engine though was very different from the one they use now. I remember seeing the leaked footage of 1.0 when it was still in Beta hell and remembering being like "How are those graphics even possible". Now those graphics are pretty mediocre by today's standards.

[Ashkendor]

No thanks. Given how a lot of our raids have "stop and stand here" style mechanics, when I stop it means I want to freakin stop. It doesn't mean I want to stumble forward a few more steps and end up dying to the mechanic.

[Qeius]

Gotta stop sooner ;0

[MYFATHERBEATSME]

No thanks. Given how a lot of our raids have "stop and stand here" style mechanics, when I stop it means I want to freakin stop. It doesn't mean I want to stumble forward a few more steps and end up dying to the mechanic.

A lot of the fights in ARR existed in 1.0 though, and people were able to pass them just fine. ARR has become TOO much "stop, stand here" mechanics. Whenever you do a dodge heavy fight, its like watching a repeat of your first time doing it. As ARR we basically just run a script every time we do a boss fight. As well, the sliding wasn't huge by any means, I seriously think it wouldn't interfere much at all with boss fights.

[Catwho]

I hated running on my Lala in 1.0 - I know I'm in the minority here but I felt like I was going to fall over and trip every time I stopped. It was really jarring.

That, and because the UI overlay had no similar weights on it, so to speak, your name would judder terribly above your head and it made me absolutely seasick to watch. (This issue is still present in 2.0-3.0 but it has been greatly reduced.)