Instance-specific Latency spikes
At some instances and some locations latency spikes several hundred with any character action. This persists throughout the instance.
It happens on all hub locations I've seen yet (Clearfell Encampment, Vastiri Outskirts, Ardura Caravan) and recently started happening on some other locations (Traitor's Passage, Trial of Sekhemas). In the latter case creating a new instance (by Ctrl-clicking on the waypoint) sometimes solves the issue for the current instance. Dying and respawning may also normalize ping or break it if it was already normal. I tried Japan, Singapore and Moscow servers, the issue is present on all three. I've encountered this before on PoE 1. The issue's prevalence varied between leagues and made me quit a few, since in the endgame it can just randomly render some maps unplayable. The random nature of the issue (game plays perfectly and then may completely break down after dying to a boss, making the next attempt impossible) adds a lot to the frustration. I don't recall encountering this much the last league, which allowed me to enjoy it quite a bit. If it persists as it is in PoE 2 it may dissuade me from playing it altogether. That would be a pity, so I'm hoping for the fix. Much love to the team Last bumped on Jan 7, 2025, 11:54:26 PM
|
|
Can confirm this is a problem. Just now my char died to the first act 3 jungle miniboss, after reviving, the instance will just give me constant high latency, sometimes disconnect me even, whilst in town, other zone or by simply creating a new instance for the prolematic zone, the latency will be back to normal. And this also happened in previous acts several times.
| |
I have the same issue. An random instance will have 1000+ ping spikes every 3-4 seconds. During the campaign I could fix this by reloading the instance. However, it makes mapping unplayable because I cant reload the instance and if I die because of the lag spikes, I loose all portals.
|
|
+1 get this in maps, i can sorta predict when it happens when the map portals are delayed to open
|
|