More positive impressions.Follow

http://rpgamer.com/news/Q3-2013/072513a.html

The game seems to be getting the right attention this time around. Not sure if everyone is familiar with this site, but I've been following it for years.

The game feels at least as responsive as FFXI. Are you referring to that blink of an eye between running and casting (which is in ffxi, too, grrr)?

I didn't experience any kind of lag/unresponsiveness that I'd consider to be anything remotely near being a deal breaker.

There is a crippling responsiveness issue in instanced dungeons on the PS3 version, and sometimes out in the open world. Party members will stay still on your screen even though they are clearly out of range, leaving you unable to cast any spells on them. It may be due to lag or the size of the dungeon. I didn't have the issue at all while running Haukke Manor, which is considerably "smaller" compared to the rest of the dungeons because it's all under one roof. Tam-Tara and onward to Brayflox, excluding Haukke, I had that problem constantly. It's not non-existent in the Manor, because I had a party member experience the issue instead of me for once. S-E have moved the grievance to a "known" bug. I haven't done any research to see if they're working on it for phase 4 and launch.

The responsiveness issue isn't 'crippeling' at all.

To explain to those who haven't noticed it. There's a ~.5 second recognition delay when registering certain damage and buff registries. This is best illustrated when evading Charged attacks when they are nearly full, or jumping and receiving fall damage.

Gameplay wise, its easily adjusted for if you keep in mind you need to be out of range/have stunned the enemy before their attack bar reaches 75~80%, otherwise the attack will go through and hit/miss you as if you were still in the position you were at that moment.

It's possible that their damage check servers are different than their positional servers, as more than once I have been hit by a bomb when i was out of range, and my allies SAW me out of range. If it was a latency issue, to them I would have still been in range according to their camera.

It's not game breaking in the least, however. Given the fact that not even everyone has even noticed it, it can defiantly be played through until it is addressed.

You know, Phase 2 I didn't notice this issue at all... perhaps it's a server strain problem. I've never encountered the chat delay spoken about here.

Edited, Jul 26th 2013 8:01pm by Hyrist

I was on the PS3 and never experienced those issues. Could it have to do with people not opening their ports? When I went to initially update the client, I had my ports closed, and the connection speed was horrendous. After accessing my router and opening them, the download went a whole lot faster. I don't know if that could cause anything that severe, but I wouldn't be surprised if some of the less common lag issues were caused by it.

Only if they want to pay more taxes, lol. Canadians pay a lot of tax. But we don't have uninsured patients left to die on the floor of emergency rooms, either. You pick your battles.

I'm pretty sure the location was taken because it's easy to find both English and French support staff, it's near a "freeway" of the most advanced underwater fibreoptic lines to Europe which is the next best thing to being there, and it's well connected to North America. The only thing missing in abundant supply is German-speaking support, but there are plenty such communities in Canada to draw from.

No you got it the other way around.

I moved out of range.

My party saw me move out of range.

I got hit?

Why?

I didn't get out of range until after 80% charge on the attack, and I got hit.

I've tested this repeatedly, it's pretty much the same or similar in multiple areas. There's a certain, but minor, delay in responsiveness and it's easily anticipated. Given that there's a fairly large charge time on those kind of skills, as well as most skills being stunnable, it can be compensated for by the players until it is addressed.

It would be game breaking if it were flat out stopping players from playing. But as it is, the mechanics are forgiving enough for people to be able to adjust for it.

We'll see how much of an impact this has on endgame once we can get to it, but they may even have it fixed by then.

I feel like if the red ring issue isn't addressed to some degree, it could be a problem with some late game stages, where the difference between success and failure is getting out of those circles. In the Ifrit fight, especially on extreme, not avoiding just one of his fire circle spells could be big. Just doing the lvl 20 Ifrit, it's tough to get out in time unless your reaction time to it is flawless. There were times when I was well clear, and still got dinged pretty damn hard. It worries me for end game, and I hope they find a way to clean it up.

I'm not sure they know fully what's going on, which is going to be the delay in repairs. If it is as game breaking as people say they'll likely delay out the game. But so far they seem to be progressing as per normal.

We're about due for a wave of responses from them, which will likely come right before Phase 4. So It's probably smart to sit tight on it for now. Not that the official boards will at all. As usual it's a madhouse in there.

In order to fix your 9 second delay, scroll your chat window back down. You've got it scrolled up with the bottom 3-4 lines hanging off. I've done the same thing before.

It doesn't matter if you're connecting to a server in Mongolia, your latency isn't going to be 9 seconds. Latency between the US and Canada is a fraction of a second, even on a bad connection. I think my latency is in the 90ms range, using Comcast from the Chicago suburbs, without using a latency hack or tunneling. You might have noise on your line that's causing problems, but not 9 second delays. Especially not with chat, where your own /say will appear instantly in your client when you hit return, even if you pull the cord while typing. The client doesn't wait for the server to echo your own text back to you, it just does it.

Anyway, there may be server side or distance issues, but yours doesn't sound like that.

This is my experience on PC too. The AoE delay should be fixed, but it's not a big deal currently. At end game and in crazy fates it will be.

I didn't have any other problems regarding lag or latency.

Glad the game is getting good reviews! I've enjoyed it myself all in all during B3, something I couldn't say about 1.0 when I played its beta.

A little OT but since it was mentioned, the lag issue centers around some of the player positioning issues mentioned in this thread. And this kind of thing...

http://forum.square-enix.com/ARR-Test/attachment.php?attachmentid=2137&d=1362316058

I didn't see anything this out-of-whack, but the red circle timing was pretty awful for me. I didn't notice the cast bar, just the animation so either there is a syncing problem with the cast/animation (full bar should align with damage splash from animation) for a lot of mobs. Or there is a 1-2 second responsiveness issue with the servers, which sounds really, really problematic. A 0.5 second delay max should be expected with a good connection otherwise players will not be where you expect them to be and damage spells will hit you that you appear to be out of range for. And of course you'll possibly die from 12HP damage after getting healed for 60HP apparently.