Improve game responsiveness

[MikeWW]

I am new to this game, but am enjoying it very much, especially crafting and gold saucer. Something I've noticed though is that this game has a very slow, laggy, or unresponsive combat system, even with ~50 ping. The primary cause of this is poor lag compensation. For many years, shooters have effectively implemented lag compensation to make games feel very responsive, and there are even some MMO's that have some very good lag compensation. If there is one issue I have with FF14, it is the pervasive lack of lag compensation and resulting poor game responsiveness. It is my opinion that by implementing lag compensation or at least work around poor game responsiveness, the enjoyability of the game can be greatly improved.

The following are a few examples of this kind of issue and suggestions on how they can be fixed.

I have to link to pastebin because I am limited to 1,000 characters on this forum.

http://pastebin.com/ddLQwWFK

[DisFlavored]

You can edit your post to bypass the character limit

[Valkyrie_Lenneth]

Not really sure what you mean, the game tends to be pretty responsive if you aren't lagging.

[Xlantaa]

Well. There is a issue on some systems, when you play full screen mode, the control is a bit laggy. Probably you're suffering that. It is about the control, not the connection. I didn't find solution, because I never see anyone comment this weird issue. On windomed mode and bordeless window the game responds correctly if you have no conetion lag. I play usually with a ping of 70-80, and the game runs perfectly.

It is true that sometimes, youcan interrup a spell moments after you stop from runnig. But is a latency that cannot be fixed even with the best of the connection. You can use this as your advantage too. You can move when yoor spell is about to finish cast (Around 80-90%) and the spell still will work and you can move faster. This latency is normal in all games. Latency on online games will always be there.

[WeekendSoja]

This game has relatively no lag honestly. I used to live in Hawaii and play this. That was terrible, even more-so with a bad GPU.

I will tell you this though, if you are talking about "hundredths of seconds" delay...that is, in all honesty due to two separate things. First being your distance from your data centers server which can be mitigated but programs like battle ping (only an option of you are a progression raider and live in the middle of the Pacific Ocean or Australia) and second, which most of the time is the case, poor performance in the processing power of your graphics card. If your game is running any where below 45-50 FPS, than you are experiencing hundredths of seconds delay due to your rig / console.

[Laraul]

1. When you move, stop moving, and then immediately try to use an ability with a cast time, your ability will be interrupted. And it will take a few hundreths of a second for the ability to be interrupted after casting. The problem here is the game processes your movement input server-side before determining whether or not you are moving while casting, resulting in movement needing to cease a few hundreths of a second (or longer for high ping players) before attempting to cast, and resulting in movement being able to start a few hundreths of a second BEFORE casting ends without interrupting casting.

You are mistaken. If you interrupt a cast it's because you've started casting while still moving.

2. AoE markers disappear a few hundreths or even several hundreths of a second before the AoE's appear to hit targets, and AoE's can hit targets even after they have moved out of the AoE's several hundreths of a second before the markers disappear. Although these two are similar problems, it is possible to relatively much more easily address the first by simply altering the duration of the AoE markers, while addressing the second would require implementing lag compensation, but proper lag compensation would address both issues.

If you are still within the radius of an AOE marker before it vanishes, that means you are going to be hit.