.3 Second Positional Update Delay (Requesting Dev Response)

Just imagine the uproar if a shooter had this much lag.

But w/e, I believe they already said this is working as intended and they have no plans to even look into it. :(

Best solution is to move right next door to where the servers are being hosted. LOL!

Quote:

---

Originally Posted by sasakusaku

Just imagine the uproar if a shooter had this much lag.

But w/e, I believe they already said this is working as intended and they have no plans to even look into it. :(

Best solution is to move right next door to where the servers are being hosted. LOL!

---

I haven't seen anywhere that it's been said it's working as intended. I know going from beta to live Yoshi released a statement saying they'd reduced the delay from .5 to .3 seconds, and that players with great connections would still see the .1 second delay. In that same address he said they wanted to work towards people being able to rely on the cast bars and markers to get out of effects. That was at the end of beta though. It's become apparent that the "fix" from .5 to .3 didn't really fix it for a large portion of players... this is one of the few things I think could potentially kill the game long term if not addressed in some fashion.

I don't think there's anything on the hardware end that can possibly be done. In any other MMORPG, if you tried to move while casting, and assuming you're not supposed to be able to do this, your spell generally gets interrupted immediately. There's no reason for your client to even consult with the server, because the client knows how to resolve this. Even if you're disconnected from the server, you can generally still target someone, cast something, and then interrupt it by moving until you get kicked off the server. There is no way your client can even communicate with the server (you're already disconnected) but it still knows it can interrupt your spell when you moved. FF14 obviously does not work like this. Your client absolutely has to consult with the server first to interrupt your spell, and that's the root of the problem as your client cannot use information it has to make a call, even though it surely knows you moved long before the server does.

Quote:

---

Originally Posted by Maoxx

I concur with the OP and for the record we need to keep beating SE over the head on this until it's fixed. I'm sorry but there isn't any excuse for it in this day and age ESPECIALLY if we are PAYING for the servers

---

We're paying for the rights to use our characters - basically a license to actually play. For example XI pretty much funded every project ever from 2006-2011.

Quote:

---

Originally Posted by Astarica

FF14 obviously does not work like this. Your client absolutely has to consult with the server first to interrupt your spell, and that's the root of the problem as your client cannot use information it has to make a call, even though it surely knows you moved long before the server does.

---

Actually, it's been proven the client handles way more work than it actually should - It doesn't work this way because they designed the way spells cast/interrupts quite differently from how every other MMO generally uses the same systems.

Quote:

---

Originally Posted by Tupsi

Actually, it's been proven the client handles way more work than it actually should - It doesn't work this way because they designed the way spells cast/interrupts quite differently from how every other MMO generally uses the same systems.

---

The client absolutely does less than any other client ought to in a MMORPG. When you think you got out of a Weight of the Land, only to see the damage pop up half a second after the casting is done, it's an example of the client not actually doing any work. If it was up to the client to determine whether you get hit, it'd be able to tell you whether you dodged the AE or not as soon as WotL is finished casting. This is never the case. You'll only find out if you got hit or not shortly after WotL is over, but never the moment it's done. All the client is doing is waiting for the server to tell it whether you got hit or not.

One way to change it is to change the casting times on certain abilities/spells by the bosses. Add that .3 or .5 to the casting time, giving the client a better chance to give the player a bit better information. Of course those with "perfect connections" would cry out about this since they like to claim lag doesn't exist.

Quote:

---

Originally Posted by WintersMoondancer

One way to change it is to change the casting times on certain abilities/spells by the bosses. Add that .3 or .5 to the casting time, giving the client a better chance to give the player a bit better information. Of course those with "perfect connections" would cry out about this since they like to claim lag doesn't exist.

---

That would simply band-aid the underlying root cause, which is that there is a built-in latency to every positional calculation in the game because of the way they have architected it. While I think SE would be reluctant to rearchitect how positioning is synced, it is really the only right way to handle it. Have the client only pass keystrokes, let the server figure out where you are. That same server also knows when the AOE will finish, so there should be zero lag between the two. This should also prevent the mass teleporting going on, as bots couldn't inject a new position into the position info being sent.

Quote:

---

Originally Posted by Sunarie

I would honestly be happy with any response that netted a little crown on the thread.

---

I think the point was that it doesn't matter what you name your thread, because contrary to popular belief, they DO read everything. Part of the reason players should bump threads instead of making 20 duplicates because "MY opinion MUST be heard!"., but that's another point entirely.

A thread with [To the devs] or [Requesting Dev Response] in the title has as much chance of getting a response as [Banana banana banana banana banana banana banana banana banana banana banana]

I think the reason is that every move in this game must be sent to server to get 'approved', while other games only do this for some of the moves. So ppl cannot hack the client to do some really game breaking things like instant cast for all spells or 100% dodge of AOE.

thumbs up /10char

Quote:

---

Originally Posted by Arcaloid

I think the reason is that every move in this game must be sent to server to get 'approved', while other games only do this for some of the moves. So ppl cannot hack the client to do some really game breaking things like instant cast for all spells or 100% dodge of AOE.

---

if the servers did have checks there wouldn't be teleporting bots in the game