Community ManagerHi there TUBBYSEASTAR ,
I'd like to jump in and clarify a few points to keep this thread productive.
First, the marked post is correct: “Santiago” was simply the internal codename for BF6 during development. It’s not an error and is not connected to anyone’s connection problems. Since that part has already been addressed, please refrain from removing the marked solution. If you feel extra clarification is needed, that’s totally fine -- just bring it up in conversation rather than changing the solution status.
As for connectivity issues:
There isn’t a known or widespread problem at the moment. Connection issues tend to vary from person to person, depending on their setup, region, ISP, and local network conditions. To help cover the bases, here are resources you can check for your specific platform:
If none of that helps, your ISP may be able to investigate the issue on their end.
Lastly, I’d really appreciate it if we could maintain a respectful tone. Everyone here is just trying to help one another out, and constructive conversations make that a lot easier for all of us.
If you have new details about what’s happening on your side, feel free to share them -- the community is here to help where we can.
"There isn’t a known or widespread problem at the moment." So the game has to reach ZERO players for you to start being serious about fixing this?
THE GAMES CODE IS UNOPTIMIZED! Relies too much on CPU and not enough on GPU..... on pc at least
Here is the problem ... now start working toward a solution....
Or.... if the games code is broken beyond repair and wouldnt be fixed without spending millions in software engineering just admit to it.
This "oh well there is not egough people affected by this for us too look into a fix" is downright pathetic customer care.
The issue is high TN. Santiago not being the issue is great, but at least address the actual issue. If it was an issue with my ISP then I would also have issues on other games but I don't. Same with other people on different ISPs. How isn't this a known or widespread issue at the moment if there has been hundreds of replies to this thread alone, other threads created, and probably a whole lot more people who don't create a post about it? There has even been posts on other social media platforms like reddit about it and it's been mentioned in the battlefield discord. Personally, I have lowered my graphics all the way down to the point where the game looks like a potato AND have used 3rd party software like the NVIDIA app to optimize the game and it has barely helped. I have a 3060 a Ryzen 7 5700G, and 32 gigs of RAM. Other players with better specs than I have has posted about this same issue. At least have the devs acknowledge the issue and try to optimize the game/routing. Just because streamers with $2k+ setups don't have this issue doesn't mean nobody else doesn't. There is nothing WE can do to fix this except buying new computer components which is a ridiculous thing to do just to play one unoptimized game made by huge companies or trying to follow the links you guys send that are for generic network issues that don't help our case at all. I don't understand how this happens on full release, I didn't have these issues during the beta.
I made a post about how bad this game performs on Ryzens. I had a CPU like yours and simply had to upgrade. It needed it anyway I guess.
The 2 posts where about 1k replies + reedit posts and also youtoube videos would tend to dissagree but sure , let`s blame the ISP :D
Poor netcoding + optimization are at fault - atleast from what I`ve seen and checked out from these threads.
There`s no explanation why portal games work great but multiplayer has rubberbanding.
There aren't any new details because you have not done anything. The problem persists just the same as it did on launch day. It has absolutely nothing to do with the ISP. Have you read any of the other hundreds of replies? I'm not trying to be rude, but the customer support I have experienced is abysmal. Please escalate this to someone who cares or knows what they are doing. It's been 3 months with no solution. You would be upset too.
This is not, and has never been an ISP issue.
