Community ManagerCommunity ManagerAre you saying you resolved the issue with input lag by contacting your provider?
@EA_Aljo Can we have someone from the EA dev or QA team actually investigate this? Every single one of us has experienced this problem repeatedly and at random intervals. I work in high-tech (25 years experience in R&D, both as a developer and as a senior executive). When it's so widespread and repeated, it's not your end-users connection, it's the game. For reference:
* I'm on a fiber connection (500 down, 50 up)
* I have cat-6 wiring throughout my entire house, including to the PS5 I'm on.
* I get the problem whether I'm on a wireless or wired connection to my PS5 controller
* I get the problem even when I have fully power cycled the PS5
* I get the problem even when I have fully power cycled the modem and my own mesh router nodes (I'm using an Asus Zen-Wifi with two access points)
* I get the problem even when no other major activity is going on on my local network.
* I have 2 controllers - switching controllers mid-game does not resolve the issue.
* The game ping says I have a sub-20ms ping, but in game I feel a delay, sometimes has high as half a second.
* This delay extends to everything - not just player controls, even line switching is delayed.
* When the delay happens, you get it for the entire length of a match (which seems to suggest it's not network related - if it was, you'd expect it to be intermittent).
* I can randomly get the delay or not from game to game, but when I do, it's for the entire length of the game.
* The delay seems to be worse when I play players from Montreal
* The delay seems to be worse or more prevalent at peak player times - i.e. Friday night, Saturday, Sunday.
* When the delay happens, AI and player movement becomes erratic, puck pickup, intercepts and pokecheck go down the tubes; and at times you get "telekinetic" puck - I.e. my players are skatign with the puck a foot in front of their stick. Basically, you see strange and erratic behavior.
* My opponent does not appear to be suffering from the same issue.
If I had to guess, there's some sort of concurrency bottleneck in the server code. Note you can have an overloaded server with low CPU and memory utilization - contention for filehandles for example or IO wait-times can explain poor server performance.
