.3 Second Positional Update Delay (Requesting Dev Response)

**Babydoll** · 11-17-2013 12:34 PM

Originally Posted by Naelle

They have reduced the lag. I've not had a single instance of the issues people in this thread are complaining about. I take that back my ISP was screwed for a few days and I had this EXACT problem. Then the net speeds came back and the issue was gone. It's been said a hundred times by now but the issue isn't the game servers (at least entirely). I played 1.0 and that was obvious but has been resolved.

Also, offensively calling out the devs is the last thing that's going to get them to post a response.

So there is no .3mms lag? Yoshida lied? O.o

**Sunarie** · 11-17-2013 01:06 PM

Originally Posted by Naelle

My point is that if it were a design choice/flaw it would effect everyone, not just some. We all have a global cooldown because that's part of the game. Only some people experiencing this issue and only being able to replicate via throttled connections paints an image far from the one you describe. I do appreciate your comment on ignorance as those who feel harmed or ignored are generally the ones ignoring fact and reality.

Everyone is effected by it. If you had read the original post of this very thread, Yoshi himself has stated that even people with a "great connection" will experience a .1 second delay on cast bars, and the positions were updated every .3 seconds. That is caused by the very same thing that causes people to get hit by AOEs they are out of. Please do tell me what facts I have missed or ignored?

The large majority of the community seem to be majorly effected by this in that strategies around Titan (one of the most movement intensive fights) all seem to involve moving before he uses the skill. There are very few people posting they don't get the issue in comparison to those that do.. and even the people who don't get the AOE thing do not see instant interrupts during casts. Add to this that there are multiple videos out there, the issue not being present in any other MMOs, and enough information compiled from enough people for it to be an accepted (but not yet investigated/confirmed) bug.. and well, the facts really point to it being a problem. I would also say that the people who are experiencing it, have spent a lot more time investigating the causes, and what it is, than those who come in and say they don't have it therefore it's not an issue. If you're going to claim it isn't a thing, at least have some research to back it up instead of just "well I don't see it". That is why I said ignorant.

**Soukyuu** · 11-17-2013 09:48 PM

Originally Posted by Naelle

They have reduced the lag. I've not had a single instance of the issues people in this thread are complaining about. I take that back my ISP was screwed for a few days and I had this EXACT problem. Then the net speeds came back and the issue was gone. It's been said a hundred times by now but the issue isn't the game servers (at least entirely). I played 1.0 and that was obvious but has been resolved.

"I don't have a problem, so it doesn't exist" is what I'm getting from that post. Where are you from? NA? Then of course you won't have as much lag as someone from the EU. Just by having less hops to the server you can avoid shitty ones that fail to forward your packets, a la this:

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                    home -    0 |   34 |   34 |    1 |    1 |    5 |    1 |
|                           217.0.116.236 -    0 |   34 |   34 |   41 |   44 |   68 |   47 |
|                          217.237.156.38 -    0 |   34 |   34 |   44 |   48 |   61 |   49 |
|                f-ed5-i.F.DE.NET.DTAG.DE -    0 |   34 |   34 |   45 |   47 |   61 |   45 |
|                          62.157.249.234 -    0 |   34 |   34 |   45 |   47 |   62 |   45 |
|      if-5-2.tcore1.PVU-Paris.as6453.net -    0 |   34 |   34 |  153 |  159 |  175 |  156 |
|     if-12-2.tcore1.PYE-Paris.as6453.net -    0 |   34 |   34 |  158 |  162 |  172 |  160 |
|     if-3-6.tcore1.L78-London.as6453.net -    0 |   34 |   34 |  157 |  169 |  214 |  160 |
|     if-2-2.tcore2.L78-London.as6453.net -    0 |   34 |   34 |  158 |  165 |  204 |  163 |
|   if-20-2.tcore2.NYY-NewYork.as6453.net -   36 |   14 |    9 |    0 |  162 |  198 |  155 |
|   if-12-6.tcore1.CT8-Chicago.as6453.net -    0 |   34 |   34 |  156 |  164 |  183 |  160 |
|   if-22-2.tcore2.CT8-Chicago.as6453.net -   32 |   16 |   11 |  177 |  186 |  197 |  190 |
|   if-3-2.tcore1.W6C-Montreal.as6453.net -    0 |   34 |   34 |  152 |  171 |  198 |  157 |
|                            66.198.96.50 -   13 |   24 |   21 |  206 |  214 |  237 |  206 |
|                             192.34.76.2 -   23 |   18 |   14 |  206 |  208 |  230 |  207 |
|                          199.91.189.234 -    8 |   26 |   24 |  206 |  210 |  233 |  210 |
|                           199.91.189.22 -   13 |   24 |   21 |  207 |  211 |  236 |  207 |
|________________________________________________|______|______|______|______|______|______|

Also, server is not the problem? Why am I seeing a 13% packet loss on the last hop (=the server) then? How about 50% packet loss?

Code:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                    home -    0 |   24 |   24 |    1 |    2 |   14 |    1 |
|                           217.0.116.236 -    0 |   24 |   24 |   41 |   54 |   63 |   51 |
|                          217.237.156.38 -    0 |   24 |   24 |   42 |   47 |   57 |   44 |
|                f-ed5-i.F.DE.NET.DTAG.DE -    0 |   24 |   24 |   46 |   50 |   62 |   53 |
|                          62.157.249.234 -    0 |   24 |   24 |   51 |   55 |   70 |   54 |
|      if-5-2.tcore1.PVU-Paris.as6453.net -    0 |   24 |   24 |  160 |  168 |  184 |  162 |
|     if-12-2.tcore1.PYE-Paris.as6453.net -    0 |   24 |   24 |  165 |  172 |  192 |  166 |
|     if-3-6.tcore1.L78-London.as6453.net -    0 |   24 |   24 |  154 |  161 |  168 |  160 |
|     if-2-2.tcore2.L78-London.as6453.net -    0 |   24 |   24 |  155 |  160 |  179 |  160 |
|   if-20-2.tcore2.NYY-NewYork.as6453.net -    0 |   24 |   24 |  157 |  168 |  208 |  164 |
|   if-12-6.tcore1.CT8-Chicago.as6453.net -    0 |   24 |   24 |  160 |  167 |  203 |  164 |
|   if-22-2.tcore2.CT8-Chicago.as6453.net -    0 |   24 |   24 |  165 |  173 |  198 |  167 |
|   if-3-2.tcore1.W6C-Montreal.as6453.net -    0 |   24 |   24 |  159 |  167 |  185 |  166 |
|                            66.198.96.50 -    0 |   24 |   24 |  205 |  211 |  231 |  205 |
|                             192.34.76.2 -    5 |   20 |   19 |  204 |  214 |  257 |  207 |
|                          199.91.189.234 -   25 |   12 |    9 |  205 |  211 |  228 |  208 |
|                           199.91.189.22 -   50 |    8 |    4 |    0 |  206 |  210 |  210 |
|________________________________________________|______|______|______|______|______|______|

Also, offensively calling out the devs is the last thing that's going to get them to post a response.

I'm stating the facts. They were all about getting back our trust. I'm saying they haven't fulfilled all of the promises yet. Nothing offensive about it.

**Naelle** · 11-18-2013 12:05 AM

There is no denying that the information sent from client to server takes time, that's fact. Do you know what controls the speed of that packet? That'd be your internet connection. I'm glad you think I'm an uneducated random player but I've got enough certifications and years in IT to tell you that you're wrong. The post you keep linking is correct. It's the way the game handles input. Once the server receives your command to move it moves, not before. If your connection isn't fast enough/close enough/being bottlenecked somewhere that's why you're seeing yourself get hit when you're outside the red ring.

It's impossible to send data from one point to another instantly, hence the .3mms. The problem is magnified when your connection can't get the info to the server that fast.

**Kevee** · 11-18-2013 12:30 AM

Originally Posted by Naelle

It's impossible to send data from one point to another instantly, hence the .3mms. The problem is magnified when your connection can't get the info to the server that fast.

Here's the simple fact: Multiple people do not have this issue in other MMOs. I'm NA, and I have this issue in FFXIV. My ISP is fine. I have played many other MMOs with no problem, but I would like to continue playing FFXIV. This simply won't be possible, with current fight design, and this issue.

It's their issue. It's something they've done/setup that is different from all other MMOs that is causing the problem. Not mine.

**HumsterMKX** · 11-18-2013 01:39 AM

Originally Posted by Naelle

There is no denying that the information sent ...Once the server receives your command to move it moves, not before. If your connection isn't fast enough/close enough/being bottlenecked somewhere that's why you're seeing yourself get hit when you're outside the red ring.

It's impossible to send data from one point to another instantly, hence the .3mms. The problem is magnified when your connection can't get the info to the server that fast.

I think you misunderstood the .3sec part. The server only checks on us every .3sec. Which means, .3sec it checks on us, the data goes to the server, which will also take sometime, then it updates.

**Soukyuu** · 11-18-2013 02:17 AM

Originally Posted by Naelle

There is no denying that the information sent from client to server takes time, that's fact. Do you know what controls the speed of that packet? That'd be your internet connection.

False. The speed is not the problem, latency is. If you're an IT person, you should know that MMOs don't even need more than a few KB/s most of the time. Latency and packet loss is what amplifies the issue. If even NA players are having it, and fromwaht I hear, some JP as well, then there has to be something wrong, especially when it does not happen with games hosted similarly.

**Naelle** · 11-18-2013 02:22 AM

You guys are right, SE is conspiring against you. I'm leaving this thread as it's just 50 pages of "Hell hath no fury...".

**Soukyuu** · 11-18-2013 02:25 AM

I bet my legacy status, you'd be one of us if it concerned you.

**Keyblade** · 11-18-2013 04:40 AM

Originally Posted by Naelle

You guys are right, SE is conspiring against you. I'm leaving this thread as it's just 50 pages of "Hell hath no fury...".

You do release not matter how much hate this game gets its still bad
The Devs dont know how to fix there server delay issue of .3 seconds
Not to mention they refuse to shorten the cast time.
Liek i was to play a game with responsive fast combat , and have my instacast skills actually instacast. Not wait 1 second for the silly animation ( THATS NOT INSTANT IS IT )
The Devs have put to much effort into the actually animation going off and not gameplay.
Not to mention this game feels rushed as they dont know how to fix the problem on Noone doing anything but speedruns on AK/WP

Thread: .3 Second Positional Update Delay (Requesting Dev Response)

Thread Tools

Search Thread

Display

Tags for this Thread