Bad Instance server on Amsterdam Gateway

Amsterdam gateway has the best ping for me, but I can't play on it. I think there is one server on there since 3.0 launch that causes horrible consistent stuttering. Turning off lockstep just causes massive lag in that situation. If I force a new instance then the problem will go away, which leads me to think it's a particular instance server and not something else.

But this makes the gateway unusable, because if I'm unlucky and hit the bad server during lab or a map, I'm screwed. So I have to use a gateway with twice the ping in order to have the game be playable.

Please check the Amsterdam gateway servers and see which one is dying!
Last bumped on Sep 21, 2017, 9:21:23 AM
The next time this happens, could you check your Client.txt log file for the IP address of the instance server you've been connected to?

The log lines will look similar to this:
"
[DEBUG Client 7380] Got Instance Details from login server
[INFO Client 7380] Just before calling client instance session
[INFO Client 7380] Connecting to instance server at 161.202.101.39:6112
[DEBUG Client 7380] Connect time to instance server was 171ms


This log file will usually be located here:
C:\Program Files (x86)\Grinding Gear Games\Path of Exile\logs\Client.txt

It'd be useful to grab the IP of the next 'good' server you connect to, also, for comparison.
I can echo OP's concern. Playing on Amsterdam Gateway.

I get the same issue. Massive stuttering due to lag spikes every few seconds, but forcing a new instance resolves it until next time.

Will check log next time.
Same thing is happening to me right now but because it's a map (shaped cemetery with great mods :() there is of course no way for me to create a new instance, except staring a new map... Which means I just lost x amount of currency :(

Here is the relevant logs from client.txt about the instance

2017/08/31 23:32:58 1216820562 aa6 [DEBUG Client 13756] Got Instance Details from login server
2017/08/31 23:32:58 1216820562 ac6 [INFO Client 13756] Just before calling client instance session
2017/08/31 23:32:58 1216820562 e8 [INFO Client 13756] Connecting to instance server at 64.95.100.171:6112
2017/08/31 23:32:58 1216820578 14c [DEBUG Client 13756] Connect time to instance server was 16ms
2017/08/31 23:32:59 1216821609 981 [INFO Client 13756] : You have entered Cemetery.
2017/08/31 23:32:59 1216821625 cab [DEBUG Client 13756] Entering area MapAtlasCemetery
2017/08/31 23:32:59 1216821953 1fa [DEBUG Client 13756] ClientInternalActor::NotifyOtherClientsAreaLoadComplete - players.size() = 0

Maybe this will help you solve this issue which has been around since 3.0 launch... I'm surprised that there isn't even a workaround in place, especially annoying & time consuming when it's a map or lab instance
Thanks Scripter - that was helpful.

Edit: I've pulled a system that was performing badly from the Amsterdam Gateway. You would have had a small chance to have this one selected for a new instance, but hopefully this should improve things.
Last edited by Fitzy_GGG on Sep 1, 2017, 12:44:02 AM
"
Fitzy_GGG wrote:
Thanks Scripter - that was helpful.

Edit: I've pulled a system that was performing badly from the Amsterdam Gateway. You would have had a small chance to have this one selected for a new instance, but hopefully this should improve things.


thanks for communicating your efforts. should help to motivate others to properly report those issues.

one question: wouldn't it be more comfortable for users to create a bug report? it should include the ip address?
age and treachery will triumph over youth and skill!
"
Fitzy_GGG wrote:
Thanks Scripter - that was helpful.

Edit: I've pulled a system that was performing badly from the Amsterdam Gateway. You would have had a small chance to have this one selected for a new instance, but hopefully this should improve things.

Thanks! Great service!

Report Forum Post

Report Account:

Report Type

Additional Info