Signed. I haven't reached end game yet, but Batraal's instant kill AOE kept hitting me when I was a good distance out of the red. You shouldn't have to predict AOEs in order to avoid them. Moving out of the red should be good enough.
Signed. I haven't reached end game yet, but Batraal's instant kill AOE kept hitting me when I was a good distance out of the red. You shouldn't have to predict AOEs in order to avoid them. Moving out of the red should be good enough.
@Soukyuu you cancelled your subscription!? Noooooooooo
There is a fairly recent thread that talks and explains about the situation with the 0.3. I would recommend people reading it. The gentlemen explains it pretty thoroughly on how it occurs. Yes it occurs, it does not exist at all times.
We have populations in the community who do suffer from it and don't.
My problem stems from the fact that the nodes on my path to the SE servers are overloaded as they're not used to all this traffic. So those routers are dropping packets and causing lag spikes. I've had my traffic rerouted a couple of times but so far it hasn't worked as I still end up on a path going through an overloaded router. There isn't much SE can do about this other than complain to the providers or put the servers somewhere that actually has a robust infrastructure like most companies.
You must be talking about this Thread: Why the netcode issue exists, and why it cannot be fixed.There is a fairly recent thread that talks and explains about the situation with the 0.3. I would recommend people reading it. The gentlemen explains it pretty thoroughly on how it occurs. Yes it occurs, it does not exist at all times.
We have populations in the community who do suffer from it and don't.
Indeed, I recommend people read it too, it's very enlightening!
“Focus on the journey, not the destination.
Joy is found not in finishing an activity but in doing it.”
Yeah, it ran out back on the 15th. Something must be done to show them the problem is serious, and losing players explicitly because of this should draw their attention. I'm willing to come back, but they have to make a statement for this to happen. And one not loaded with evasive PR BS.
That thread originated from this one actually :PThere is a fairly recent thread that talks and explains about the situation with the 0.3. I would recommend people reading it. The gentlemen explains it pretty thoroughly on how it occurs. Yes it occurs, it does not exist at all times.
We have populations in the community who do suffer from it and don't.
[ AMD Phenom II X4 970BE@4GHz | 12GB DDR3-RAM@CL7 | nVidia GeForce 260GTX OC | Crucial m4 SSD ]
Sorry for double posting but: the actually answered!
From what I understood, they are aware of it and already tested increasing the position check frequency for hard primals and endgame dungeons and it works very well. They are kinda uncertain if it's a good idea to increase it everywhere because of server stress, so they're looking into how to handle that. Hold on for an official translation though.
From my part, it would be fine to have the frequency increased in endgame only for a start, since AoE on lower levels aren't that punishing.
[ AMD Phenom II X4 970BE@4GHz | 12GB DDR3-RAM@CL7 | nVidia GeForce 260GTX OC | Crucial m4 SSD ]
That's about what I got from Reinheart's translation as well. So glad they addressed it! Seriously makes me happy, and some faith restored. Hopefully what they have planned works outSorry for double posting but: the actually answered!
From what I understood, they are aware of it and already tested increasing the position check frequency for hard primals and endgame dungeons and it works very well. They are kinda uncertain if it's a good idea to increase it everywhere because of server stress, so they're looking into how to handle that. Hold on for an official translation though.
From my part, it would be fine to have the frequency increased in endgame only for a start, since AoE on lower levels aren't that punishing.![]()
Yeah, I just saw that; they actually talked about it!
Which is a VICTORY in itself for these threads!
I can't comment on the solution he talked about obviously, we'll have to see it first-hand, but at least that means they're actually working on this issue. And that is what many players wanted to hear at the very least!
It's reassuring if they say that the increased position check frequency works well though, because that means they see the problem (by comparison). Hopefully, they're on to something!
“Focus on the journey, not the destination.
Joy is found not in finishing an activity but in doing it.”
Indeed! I went and updated my thread already. Will likely edit again once full translations are up and I'm awake (I'll likely crash after the live letter).Yeah, I just saw that; they actually talked about it!
Which is a VICTORY in itself for these threads!
I can't comment on the solution he talked about obviously, we'll have to see it first-hand, but at least that means they're actually working on this issue. And that is what many players wanted to hear at the very least!
It's reassuring if they say that the increased position check frequency works well though, because that means they see the problem (by comparison). Hopefully, they're on to something!
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.