Forum Discussion
Well, I'm glad to know we can commiserate in company. I'll let you know if we find anything that works, although I'm hesitant to waste too much time on this as it was exactly correlated in time with the latest update, and as I mentioned, the exact same setup worked without issue for 2 years.
If you don't mind saying, what router are you guys using? And do you happen to have Verizon as your ISP?
- 2 years ago@HammerStrike815 We're on a netgear nighthawk and verizon, so I guess it's not an issue with some particular router or ISP.
We did just get to play like 6 games in a row and never ran into the issue. I don't know if it means that it is fixed, but you could maybe give it a go and see if we just got lucky. Maybe restart your router first for the good vibes. - 12 months ago
@HammerStrike815 Not sure if you're still having the issue, but things worked fine for us for about a week and then on this past Friday, July 19, things stopped working again.
The behavior is always the same. We get about 2-3 good games in, then after one game, our third player who is on a different network is hit with the "Persistence Transfer Cancelled" or whatever that is, and then after that one of the 2 of us on the same network always gets kicked loading into the game.
@EA_Aljo We have a gaming router, uPnP, and again, I can't stress this enough, everything worked with our setup just fine for 2.5 years. This issue is perfectly correlated in time with the split 2 update.
- 12 months ago
My group is also affected by this. It's been accompanied by the persistence transfer cancelled error as well, and I saw today a thread implying that that has been patched and fixed for most users. https://answers.ea.com/t5/Technical-Issues/Disconnect-persistance-transfer-canceled/m-p/13896839/highlight/true#M204066
Unfortunately, we tried to play today and immediately couldn't load into Firing Range together. We couldn't even play a single game today.
@EA_Aljo: It's the same for us. Gaming router, uPnP set appropriately. Not a single setting changed from before the mid-season update and after. This literally only started with the mid-season update. What do we need to do to get this escalated? I've seen others on reddit also mention similar symptoms starting on the same timeline. It's not just us. Should we file a bug report?
- 12 months ago@HammerStrike815 So, we came back to the game after a few weeks and found that if we changed our NAT type on the router to "Open" from "secure", things seem to work now. Hopefully there aren't too many consequences for doing so.
Again, we had this set to "secure" for 2.5 years before and we could play with two xboxes no problem, but maybe they did something in one of those updates to make Apex no longer play nice with this NAT type set to "secure".
Or, maybe it was a totally separate issue that they fixed and it's just total coincidence that I changed something and it worked. But that's about all I can give ya at the moment. Good luck!
About Apex Legends Technical Issues
Community Highlights
- EA_Blueberry7 years ago
Community Manager
Recent Discussions
- 54 minutes ago
- 3 hours ago
- 4 hours ago
- 5 hours ago
- 6 hours ago