HM Titan Quicksand delay

[Syncness]

Running 140ms from Aus to Japan.

On the Titan fight, sometimes I'm very clearly out of the quicksand circle but I'm still being hit by it, yet sometimes I make a mistake a strafe a little inside before getting out and I'm safe?

Anyone else experiencing this? The quicksand reaction requirement is very unforgiving.

[e] I fixed this issue by using Battleping or Wtfast.

[Alise]

This is just how primal fight are since v 1.0. their positioning and refresh timing is kind of bad, so with higher ping you screw.

[guyaume]

I agree, I have a 130ms ping to server (from europe to the so-called "European" datacenter located in america).

I play with keyboard, and I never achieve to avoid the big "corridor" strike that pushes you outside...

This fight in NOT beatable for a non local keyboard player !!!!
Especially as a caster, not being able to move while casting.

[TirionCrey]

I agree, I have a 130ms ping to server (from europe to the so-called "European" datacenter located in america).

I play with keyboard, and I never achieve to avoid the big "corridor" strike that pushes you outside...

This fight in NOT beatable for a non local keyboard player !!!!
Especially as a caster, not being able to move while casting.

I do Titan on my SCH...I'm in europe playing on the NA datacenter...I have yet to be pushed off the arena cause of the latency. The plumes however are really a "start running before the visual" starts kind of race. But Landslide...to not dodge that, you have to be really slow.

[Alindra]

I agree, I have a 130ms ping to server (from europe to the so-called "European" datacenter located in america).

I play with keyboard, and I never achieve to avoid the big "corridor" strike that pushes you outside...

This fight in NOT beatable for a non local keyboard player !!!!
Especially as a caster, not being able to move while casting.

THIS! I gave up on this fight yesterday because I would run out of that attack every single time and still get knocked off can cause a wipe. There was one time that, according to my screen, I left the area at the same time as another player and stopped moving in the same spot, but I got knocked off and they didn't.

I'm basically at the point where if next time I try this fight I have the same issue, I may just quit the game because I can't progress in the story anymore.

[Jinko]

I agree, I have a 130ms ping to server (from europe to the so-called "European" datacenter located in america).

I play with keyboard, and I never achieve to avoid the big "corridor" strike that pushes you outside...

This fight in NOT beatable for a non local keyboard player !!!!
Especially as a caster, not being able to move while casting.

This !

I'm Europe as well and barely managed the easy mode, I don't wana even consider the chances of me in Hard mode. (well its zero basically)

Something should be done about this because its pretty game breaking IMO.

Fact is SE if you don't have the servers and infrastructure to accommodate this kind of game play then you shouldn't' be designing the bosses in such a manner.

[Joypad]

I agree, I have a 130ms ping to server (from europe to the so-called "European" datacenter located in america).

I play with keyboard, and I never achieve to avoid the big "corridor" strike that pushes you outside...

This fight in NOT beatable for a non local keyboard player !!!!
Especially as a caster, not being able to move while casting.

130 is heaven.

Me and my friends dared to check our ping to the server and got over 160ms. That's almost double of what a US player has on the so-called EU server.

[Alindra]

130 is heaven.

Me and my friends dared to check our ping to the server and got over 160ms. That's almost double of what a US player has on the so-called EU server.

My ping (Pacific time) averaged 102, and I still have this issue.

[Deculture]

I just automatically assume I'm going to get hit by something if I'm not out of it for a good 2+ seconds. If this has been around since 1.0 then I wouldn't count on it being fixed, heh.

[CheshirePuss]

I just automatically assume I'm going to get hit by something if I'm not out of it for a good 2+ seconds. If this has been around since 1.0 then I wouldn't count on it being fixed, heh.

If they can bother to fix something as little as the positioning of mobs in CM to avoid speed running from happening anymore, they can fix an unfair game changer such as this. I see no reason why it hasn't been yet.