[Feedback] Please fix/improve the delay in the game

Here's a quick video showing what I'm talking about:
https://youtu.be/hToWKu79Jm0

As you can see, there's a significant delay between one client executing an action and another client seeing that action in their game. And this is with both clients in the same network. This is because the server updates at a very slow frequency. As far as I know the update frequency (server tick rate) has been unchanged ever since it had to be increased in 2.1 because dodging puddles in titan was incredibly difficult.

This delay may not be that big of a deal in the grand scheme of things. The gameplay still works mostly. But there are many things where this delay creates problems. It's the most evident in pvp. The enemy players are NEVER in the position that your game shows you.
Let's say you want to knock back someone away from their team and into your team. This is impossible to do without first stunning the player, walking behind them and then executing the knockback skill, hoping he didn't purify and start moving again before the server tick happens and you actually punt him into safety.
Other issues include trying to pass debuffs to other players in savage content (for example P4S phase 1), trying to do mechanics that involve the positions of other players (for example the last boss of the 24 man raid Aglaia) and overall trying to avoid other players.

Example 1: Passing debuffs
If both players run into and past each other there is a high chance that the server tick happens before and after the two players touch and the server never notices that the debuff should be passed. Of course you can decrease the chance of this happening by having one player stand still but it will still happen unless one player stands still within the other player for a short but significant amount of time.
Example 2: Balancing the scales
There is a mechanic in the last boss of Aglaia that requires a certain amount of players on separate sides of the arena. It happens with annoying frequency that the scales are balanced but 3 or 4 players keep running back and forth because on their client it still looks like the other players are moving when they aren't and they move in response, continuing the cycle and resulting in a wipe. Don't get me wrong, I like the mechanic, it's great. The described issue wouldn't happen (or at least considerably less often) if people could see where other players ACTUALLY ARE in real time and didn't have to predict their position 2 seconds into the future.
Example 3: STOP FOLLOWING ME
You know this one but I'll explain anyways.
Let's say two players have aoe markers on their heads and they run in the same direction. In their client it looks like the other player is slightly behind them, so they expect the other player to move back. In reality both players are running right next to each other and they both die screaming at the other player to stop following.
These are the most common examples. There are more but I think you get the point.
As I said, this isn't game breaking but for me (and I'm sure many other players) this is a big source of unnecessary frustration and I'd like Creative Business Unit III to fix this.

Now I'd like to preempt some arguments I'm sure will be coming.
"It's not a big deal, just adapt and get good." -This isn't hard, it's just annoying and frustrating and adds nothing to the game.
"There are more important things they need to fix" -Then fix those things as well. You don't need to tackle one issue after the other.
"It's too expensive" -The game generates millions and millions of dollars and Square Enix makes several billion dollars every year. They can afford it.
"Spaghetti code/it's too hard" -Yoshida said in an interview that there are currently no issues with the game engine that would prevent them from doing anything.
"I don't care/This doesn't affect me" -Start caring. You pay for this game, demand better. Improving the game in one aspect makes the game better for everyone.

"Japan doesn't complain about it, so nothing will change." -This is the one I'm worried about. The general impression I have about SE is that unless an issue, that isn't talked about much in japan, blows up in a very big way in the west there is a very low chance for change (see the GCD delay thing).

Thank you for reading and I hope for your support.

Congratulations. You now understand why the GCD is 2.5 seconds, and there is such a long telegraph for boss fights.

Since you can play on servers on the other side of the world, there will always be this slight delay. Since not everyone plays on a PC, and the networks we connect through vary in quality, there will always be this slight delay. It's built into the very nature of the Internet.

You don't notice this as much on other games because you're almost never playing on servers outside your local country, where the latency is more consistent between players.

Quote:

---

Originally Posted by DPZ2

Congratulations. You now understand why the GCD is 2.5 seconds, and there is such a long telegraph for boss fights.

Since you can play on servers on the other side of the world, there will always be this slight delay. Since not everyone plays on a PC, and the networks we connect through vary in quality, there will always be this slight delay. It's built into the very nature of the Internet.

You don't notice this as much on other games because you're almost never playing on servers outside your local country, where the latency is more consistent between players.

---

No, this isn't a slight delay.
A slight delay is what you see in other mmos and this is the standard that I'd like ffxiv to reach. I'm not asking for FPS tick rates. I'm asking for the minimum that other mmos have.
Also, I think you may have misunderstood. I'm not complaining about the GCD in any way. What I was referring to with "the GCD delay thing" is the lag that western players have that Yoshida wasn't even aware of.

Quote:

---

Originally Posted by Karan_Vess

No, this isn't a slight delay.
A slight delay is what you see in other mmos and this is the standard that I'd like ffxiv to reach. I'm not asking for FPS tick rates. I'm asking for the minimum that other mmos have.

---

When other MMOs accommodate the following two conditions, I would expect FFXIV to start working toward what you desire:

1) True cross-platform. Other MMOs restrict PC players and console players to separate servers, implying separate infrastructure. ESO, for example, may have PC and XBOX players, but they do not share the same worlds, nor ever actually play against each other.

2) True world-wide realms. If you'd play WoW, for example, on a European server while you live in North America, you will experience problems with latency in a similar manner as this game. It becomes fairly noticeable during peak Internet hours in Europe. Up to a few months ago, the Oceanic players logging onto North American servers had a similar problem with latency.

On the other hand, if you are frequently running into latency issues in this game, it may be time to check your own internet provider(s). Your interpretation of what is actually happening to any particular player in the latest raid tier may be a misinterpretation of what is going on.

I don't think consoles are a reason the GCD is 2.5 seconds actually. I think you're spot on the other reason tho, I only say this as I have 1gig internet wired connection and I'm on PS5 and I load faster than all of my friends on PC. Now unless I missunderstood you then throw out my cents but yeah.

Quote:

---

Originally Posted by DPZ2

When other MMOs accommodate the following two conditions, I would expect FFXIV to start working toward what you desire:

1) True cross-platform. Other MMOs restrict PC players and console players to separate servers, implying separate infrastructure. ESO, for example, may have PC and XBOX players, but they do not share the same worlds, nor ever actually play against each other.

2) True world-wide realms. If you'd play WoW, for example, on a European server while you live in North America, you will experience problems with latency in a similar manner as this game. It becomes fairly noticeable during peak Internet hours in Europe. Up to a few months ago, the Oceanic players logging onto North American servers had a similar problem with latency.

On the other hand, if you are frequently running into latency issues in this game, it may be time to check your own internet provider(s). Your interpretation of what is actually happening to any particular player in the latest raid tier may be a misinterpretation of what is going on.

---

What you're listing are excuses. Not reasons why things can't be better. If those are critical problems, they can be solved. Refer to

Quote:

---

"Spaghetti code/it's too hard" -Yoshida said in an interview that there are currently no issues with the game engine that would prevent them from doing anything.

---

My ping is rarely above 30ms. My connection is fine. If you look at the example you see that even with clients in the same network the delay is significant. The issue I'm describing is not latency related. The problem is is the frequency at which the server checks and sends updates. As I have explained in my opening post.

Quote:

---

Originally Posted by Karan_Vess

My ping is rarely above 30ms. My connection is fine. If you look at the example you see that even with clients in the same network the delay is significant. The issue I'm describing is not latency related. The problem is is the frequency at which the server checks and sends updates. As I have explained in my opening post.

---

FFXIV servers have tickrate most abysmal of .3 ticks per second. It takes roughly three seconds for server to register a tick unless this has changed (still used to calculate dot tick potency so unlikely to have changed). For added perspective a Minecraft server ticks twenty times per second.

GCD length has nothing to do with tick rate or it would default to three seconds and more to do with limiting ogcd usage within the gcd window. All animations have base delay of .7 seconds. If you multiply .7 by three you get 2.1 (the shortest gcd where one can double weave). If you multiply .7 by four you get 2.8 (making triple weaving without clipping impossible at any base gcd). The client introduces additional delay onto each queued action (50 ms I believe? Cannot remember) for "sanity checking" making even insubstantial latency increases felt.

FF14 is more sensitive to any latency increases when you consider the low server tick rate and needless additional 50 ms delay ontop of .7 second animation lock for all animations before ability/spell will register.

They could hypothetically increase this tick rate at cost of additional cpu cycles and bandwidth. Tick rate is easily one of most demanding aspects so is first thing to be reduced. Hope this assists!

The game has a very poor tick-rate. It wouldn't really surprise me if it was a result of building the game atop legacy net-code from 1.0, which was meant to be an almost pseudo turn-based game with extremely long ability CDs.

Quote:

---

Originally Posted by Karan_Vess

What you're listing are excuses. Not reasons why things can't be better.

---

Part of the problem is physics. You have a propagation delay from you to the server and back. Mind you, that's just for one bit over the wire. That's before we talk about the transmission delay. These add up awfully quick and only a few of them are something the server can do something about.

The "jump action" is produced client-side for the jumper. It is nearly instantaneous. It is why you can run around still when your link is lost. However, we have the client building the packet(s) to send out to the server showing you jumped (along with any other actions you might send, like your position, etc etc). It bundles all of these packets together and sends them out probably at set intervals. These ARE things they can change. Maybe it is optimized, maybe it isn't.

However, then you have the "over-the-network" time. These are all the switches/routers/underwater cables/etc that connect you to your DC. These are outside of the developer's control. For example, my ping from my location to my DC is 100ms. There is absolutely nothing SE can do about that. Some of this is physics - the propagation delay over a wire. I can't say for sure how much delay they can lower, if any. There is an overhead for each packet sent. If they doubled the frequency at which packets are sent out, the servers might actually handle them slower since they'd need to parse more packets. It isn't clear if there are any gains.

In other words - the excuse is partially physics (outside the control of SE), network transmission delay (out of their hands) and internal packet delay (in their control).

For your edification:
From a terminal window (windows command prompt on windows), run tracert <ip address of your DC> This will show you the path(s) taken to the DC and where the delay is. You'll likely find that the delays are in the distance between you and the DC or from nodes that are saturated with other network traffic.

Quote:

---

Originally Posted by Karan_Vess

As far as I understand that only impacts GCDs? In which case this isn't the topic of this thread.

---

Yes if your ping bad like me (200+ ms) it helps in CD / GCD (even makes double weaving possible).
If you are looking for server / client simultaneous synchronization I doubt it is possible.

In Lost Ark it feels different I believe server already registers upcoming event in client to solve problem, but player 2 player interaction still delayed (or it is what I observed).

Quote:

---

Originally Posted by dspguy

Part of the problem is physics. You have a propagation delay from you to the server and back. Mind you, that's just for one bit over the wire. That's before we talk about the transmission delay. These add up awfully quick and only a few of them are something the server can do something about.

The "jump action" is produced client-side for the jumper. It is nearly instantaneous. It is why you can run around still when your link is lost. However, we have the client building the packet(s) to send out to the server showing you jumped (along with any other actions you might send, like your position, etc etc). It bundles all of these packets together and sends them out probably at set intervals. These ARE things they can change. Maybe it is optimized, maybe it isn't.

However, then you have the "over-the-network" time. These are all the switches/routers/underwater cables/etc that connect you to your DC. These are outside of the developer's control. For example, my ping from my location to my DC is 100ms. There is absolutely nothing SE can do about that. Some of this is physics - the propagation delay over a wire. I can't say for sure how much delay they can lower, if any. There is an overhead for each packet sent. If they doubled the frequency at which packets are sent out, the servers might actually handle them slower since they'd need to parse more packets. It isn't clear if there are any gains.

In other words - the excuse is partially physics (outside the control of SE), network transmission delay (out of their hands) and internal packet delay (in their control).

---

I understand that it may not be an easy fix and may require more than just flicking the "increase tick rate" switch. But other games can do it so I see no reason why this game cannot do it. Wow is a very good example. I've never played it myself but from videos I've seen you can easily tell how responsive it is. When you see another player move, you can have a high degree of confidence that that is where that player actually is.

Quote:

---

For your edification:
From a terminal window (windows command prompt on windows), run tracert <ip address of your DC> This will show you the path(s) taken to the DC and where the delay is. You'll likely find that the delays are in the distance between you and the DC or from nodes that are saturated with other network traffic

---

Tracert shows the round trip for each packet for each hop individually. A game packet will not go from one hop and back and then to the next hop and back, etc. It will go straight through and that's it. Then the server will send the update.
You can get hints with tracert but it will not give you accurate results for everything.

As others have been saying, the game servers have terrible tickrates. Shitty servers paired with what is probably 1.0 netcode makes for heavily delayed interactions. Honestly, I'm surprised that a game in 2022 can have such stoneage servers/netcode. This game would be A LOT better off if it was actually as responsive as WoW.

Quote:

---

Originally Posted by MiaShino

FFXIV servers have tickrate most abysmal of .3 ticks per second. It takes roughly three seconds for server to register a tick unless this has changed (still used to calculate dot tick potency so unlikely to have changed). For added perspective a Minecraft server ticks twenty times per second.

GCD length has nothing to do with tick rate or it would default to three seconds and more to do with limiting ogcd usage within the gcd window. All animations have base delay of .7 seconds. If you multiply .7 by three you get 2.1 (the shortest gcd where one can double weave). If you multiply .7 by four you get 2.8 (making triple weaving without clipping impossible at any base gcd). The client introduces additional delay onto each queued action (50 ms I believe? Cannot remember) for "sanity checking" making even insubstantial latency increases felt.

FF14 is more sensitive to any latency increases when you consider the low server tick rate and needless additional 50 ms delay ontop of .7 second animation lock for all animations before ability/spell will register.

They could hypothetically increase this tick rate at cost of additional cpu cycles and bandwidth. Tick rate is easily one of most demanding aspects so is first thing to be reduced. Hope this assists!

---

Only DoTs and HoTs are on a 3 second tick. The game checks for positional updates every 300ms. (last we knew) I believe some instances have faster positional updates.

I'd like to see a fix for this in the future. The delay is definitely one of the other reasons why some people that come from different MMOs feel that FFXIV's gameplay is clunky. It just doesn't have that crisp response that other games do, although it can be gotten used to.

Quote:

---

Originally Posted by kpxmanifesto

I'd like to see a fix for this in the future. The delay is definitely one of the other reasons why some people that come from different MMOs feel that FFXIV's gameplay is clunky. It just doesn't have that crisp response that other games do, although it can be gotten used to.

---

Definitely. You can get used to a great many things. But living with a huge splinter in your foot isn't optimal.
What I'm hoping for with this thread is to get some support from the community to maybe get the devs' attention. Yoshida keeps saying they do read the forums after all. (I hope that includes the non Japanese ones)

Quote:

---

Originally Posted by Karan_Vess

Tracert shows the round trip for each packet for each hop individually. A game packet will not go from one hop and back and then to the next hop and back, etc. It will go straight through and that's it. Then the server will send the update.
You can get hints with tracert but it will not give you accurate results for everything.

---

Right, it shows each hop and back. The idea is that all of these delays, aside from maybe the last one (SE's server) are outside of SE's control. The point I'm trying to show you is that the distance (and path) that your data travels between you and SE is the big culprit. Tracert was to demonstrate that if you look at the difference in ping times between hops, you'll see the the delay is between nodes transmitting your data to the DC. If I look at mine, my pings are about 20ms to get from my area to someplace in Atlanta. And then 60ms to get from ATL to CA. SE doesn't control those servers. So my ping of 100ms is mostly due to one leg between ATL and CA and has nothing to do with SE at all.

If only they could solve this issue ... it was even worse before for some EU region but after almost 9 years of playing the game i still wish they get rid of that.

Quote:

---

Originally Posted by Valkyrie_Lenneth

Only DoTs and HoTs are on a 3 second tick. The game checks for positional updates every 300ms. (last we knew) I believe some instances have faster positional updates.

---

If any do it would be instance server but doubtful it snapshots at anything beyond 300 ms for mechanics.

Correction, meant 500ms delay sanity check on initial post for ability usage. Unsure why I put 50 other then my brain is broken.

Ability delay appears to be greatest at roughly three seconds.

Player position update packets appear to be processed roughly every one second or greater. The server may know where you are every .3 seconds but it does not share this with other clients.

Mechanics are about the only thing that appear to even attempt snapshotting at the .3 tick mark and depending on latency/server load this can wildly fluctuate.

Sometimes I feel like I am having the stroke when I type in English, please forgive. :D I speak it every day almost yet still feel like neophyte speaker and typer.

Ohhh right! Forgot the mentioning of this during my initial post. It may say .3 tick on the tin but that is equivalent of monitor giving black to black refresh rate. Many more systems working here and .3 tick only appears to apply to if in bad apply damage if not good. Much like Minecraft twenty ticks apply mostly to block logic and not update player position.

If you wish to test this without firing up packet monitoring software attempt making many quick but subtle movements with your character. Now watch 70% of that be dropped on second client. FF14 uses some of worst ping interpolation I have ever ever ficken seen, outright dropping certain player inputs entirely rather then estimating movement.

It is most common to be in quantum state of movement in FF14 land (I blame magic). You can be both in front of someone and behind them at same time. It is something to behold.

Quote:

---

Originally Posted by dspguy

The idea is that all of these delays, aside from maybe the last one (SE's server) are outside of SE's control.

---

The majority of ping related delays occur upon entry to their network or within this network. NTT is notorious for this. Uncertain if this is traffic shaping issue or shoddy nodes but it really really exacerbates the low tick rate issue. Doubtful the tick rate will be increased any time soon. It works for them and is inexpensive. Would love at minimum thirty ticks buuuut understand this will probably never happen.

FF14 is also awful at handling dropped packets. Even handful of dropped packets (common as heck) will result in total disconnect rather then reconnection attempt.

TL;DR - Not gonna happen because one single data center is not enough for multiple countries. It works in Japan though so it should work here is mentality.

So I ran a quick test between my PC and my wife's PC - same network, wired. Ability usage seems to match my ping of 80-100ms. Whether this be using abilities on a dummy or crafting abilities - I see the animations and messages at a nearly indiscernible time difference. Drawing a weapon is also as quick as other abilities.

Movement though is delayed by more than abilities. It is as if displaying movement to another client is a lower priority than other actions. It seems like they smooth movement a bit. If I strafe back and forth quickly, ultimately not changing my position by much, the other client just sees the "walking animation" but the turning is mostly negated and it can look like I'm moonwalking.

In my opinion, movement being a lower priority makes good sense. Another player's exaction position shouldn't really matter much to the client. The server figures out if a player is "in range" for abilities or stepping in the red telegraphs. If someone ONLY looks at movement, like the jump by the OP, I could see someone thinking the delay is longer than it should be. However, I think movement is a special case. Many other actions taken in game seem to be very quick.

It's painful in PvP when you use Purify, it takes so long to activate while it should be instant the moment you press it

Quote:

---

Originally Posted by dspguy

So I ran a quick test between my PC and my wife's PC - same network, wired. Ability usage seems to match my ping of 80-100ms. Whether this be using abilities on a dummy or crafting abilities - I see the animations and messages at a nearly indiscernible time difference. Drawing a weapon is also as quick as other abilities.

Movement though is delayed by more than abilities. It is as if displaying movement to another client is a lower priority than other actions. It seems like they smooth movement a bit. If I strafe back and forth quickly, ultimately not changing my position by much, the other client just sees the "walking animation" but the turning is mostly negated and it can look like I'm moonwalking.

In my opinion, movement being a lower priority makes good sense. Another player's exaction position shouldn't really matter much to the client. The server figures out if a player is "in range" for abilities or stepping in the red telegraphs. If someone ONLY looks at movement, like the jump by the OP, I could see someone thinking the delay is longer than it should be. However, I think movement is a special case. Many other actions taken in game seem to be very quick.

---

This is exactly what I notice in FFXIV character movement not priority..

Quote:

---

Originally Posted by dspguy

Right, it shows each hop and back. The idea is that all of these delays, aside from maybe the last one (SE's server) are outside of SE's control. The point I'm trying to show you is that the distance (and path) that your data travels between you and SE is the big culprit. Tracert was to demonstrate that if you look at the difference in ping times between hops, you'll see the the delay is between nodes transmitting your data to the DC. If I look at mine, my pings are about 20ms to get from my area to someplace in Atlanta. And then 60ms to get from ATL to CA. SE doesn't control those servers. So my ping of 100ms is mostly due to one leg between ATL and CA and has nothing to do with SE at all.

---

My ping to the server is 18ms. My tracert to the server adds up to 190ms.
Tracert does not show how quickly a packet gets to the server and back. That's what ping does. Tracert is a good troubleshooting tool to locate a problem but it's not what you should be using here.

For me I can just say that the way it is designed, castbar starts -> telegraph appears -> castbar ends - damage gets evaluated now -> telegraph fades out + attack animation starts is very poor concept. It is unintuitive, because people do not understand taking damage they seemingly escaped (the animation is the most visible part of the workflow to the player) and it creates perception of lag even when there is none. The server tick being very poor also adds to that perception most likely, but changing the synchronization of cast, telegraph, animation and damage evaluation can do a great deal to defeat the perception of lag/delay without any backend improvements whatsoever. That's something they should definitely look into. The intuitive thing is to get damaged when the animation ends and you can literally see yourself taking the damage, simple as that.

The problem is obvious and really simple. its all because of very few server ticks. ofc individual latency can worsen things but the thing is even if you can literally can get 5ms server will be too later to register what you are doing. And the reason for that is 1 and really simple as well. older console compatibility. I bet ps5 can and will work fine with alot ticks but no way ps3 could keep up. that was the reason of keep it low tick and as well to be compatible with lower spec pc's as well. I'm not sure if PS4 is strong enough to keep up with the more ticks but i bet it can do better from what we got now.I think since they dont support ps3 anymore they can do it but they have not bothered yet... Maybe now that ps3 and even windows 32bit is not more supported means that they are about to make some real tuning to their servers. I hope so cause everything else that is bad is really berable but the clunkiness of the ticks is driving me crazy and its really a deal breaker for the long run to invest to this game. I only Hope PS4 is not what is bottleneck it cause it gonna really sad to see the game go down because of ps4 or sad to see ps4 players go away or forced to go to ps5 or pc since the ps5 is really hard to get and really expensive... but at some point they gonna let ps4 support to go away cause its really too old already ands a bummer to keep the whole game down

Quote:

---

Originally Posted by sodade21

The problem is obvious and really simple. its all because of very few server ticks. ofc individual latency can worsen things but the thing is even if you can literally can get 5ms server will be too later to register what you are doing. And the reason for that is 1 and really simple as well. older console compatibility. I bet ps5 can and will work fine with alot ticks but no way ps3 could keep up. that was the reason of keep it low tick and as well to be compatible with lower spec pc's as well. I'm not sure if PS4 is strong enough to keep up with the more ticks but i bet it can do better from what we got now.I think since they dont support ps3 anymore they can do it but they have not bothered yet... Maybe now that ps3 and even windows 32bit is not more supported means that they are about to make some real tuning to their servers. I hope so cause everything else that is bad is really berable but the clunkiness of the ticks is driving me crazy and its really a deal breaker for the long run to invest to this game. I only Hope PS4 is not what is bottleneck it cause it gonna really sad to see the game go down because of ps4 or sad to see ps4 players go away or forced to go to ps5 or pc since the ps5 is really hard to get and really expensive... but at some point they gonna let ps4 support to go away cause its really too old already ands a bummer to keep the whole game down

---

Simple, well yes for a normal game I would say that this problem wouldn't occur, but FF14 and the developer team behind the code are, well to be nice, not that skilled in modern net codes. SE:s net codes in a lot of their games are just straight up bad in comparison with other companies.
I think this is part of an issue that we still have since 1.0, I mean just look at their login servers, Wow has always had one system that handles the logins, after the login process you can then choose your server. If the login is handled by the specific server (or rather the login server is tied to the server you are wanting to connect to), that's just ass backward design, which gives you issues where you don't receive a ticket and can skip past the queue if you are disconnected or your game crashes. If you rebuilt the system from the ground up I think this would be very easy to make it work a lot better, but to rebuild the current system when their entire game is built around the server ticks, snapshotting, and so forth is NOT as simple. And yes, I've always thought that the game feels slow and stiff compared to other MMO:s, when you get used to it's not a big problem but for someone who used to play wow back in the days (back in 2010) and Rift, yeah FF14 is very, VERY stiff with awful net code. I don't know why they did it, it could be because of consoles, it could be because of incompetence or maybe it was a conscious design decision to make combat "feel" a certain way, more of a strange almost turn-based combat, not fluid.

Quote:

---

Originally Posted by Brandter

I don't know why they did it, it could be because of consoles, it could be because of incompetence or maybe it was a conscious design decision to make combat "feel" a certain way, more of a strange almost turn-based combat, not fluid.

---

My guess is that it was made this way to accommodate the PS3 crowd which doesn't exist anymore. I really wish they would fix it because PVPers suffer from the delay.

Fix delay and bring us 1.0 animations

FFXIV would easily be a 10/10 MMORPG.

I know the delay is a huge turnoff for people coming into FFXIV from other online games. I think it's the kind of thing you get used to playing at a high level (at least in PvE; frustrating as all hell in PvP), but like, that's like learning how to tiptoe around nails on the floor. I would classify general game feel as the most important component, and I can't grade FFXIV very well unless they address the underlying issues.

Quote:

---

Originally Posted by Elissar

Fix delay and bring us 1.0 animations

FFXIV would easily be a 10/10 MMORPG.

---

I saw a few 1.0 cutscenes recently and I have to wonder how the game went from all those custom animations to virtually every interaction involving static characters reusing short emotes that players have.

Yes please, the lag/delay in this game makes pvp really annoying sometimes.

Quote:

---

Originally Posted by Gameovers

I don't think consoles are a reason the GCD is 2.5 seconds actually. I think you're spot on the other reason tho, I only say this as I have 1gig internet wired connection and I'm on PS5 and I load faster than all of my friends on PC. Now unless I missunderstood you then throw out my cents but yeah.

---

Your internet isn't the reason you load faster.

PS5's have high performance PCI-E 4.0 NVMe SSD's in them, the better your SSD the faster you load.

Quote:

---

Originally Posted by Jagick

I saw a few 1.0 cutscenes recently and I have to wonder how the game went from all those custom animations to virtually every interaction involving static characters reusing short emotes that players have.

---

They totally replaced the underlying game engine, for one.

Reminder that this game is 12 years old :)

Reminder that in 12 years of time improvements can be made.