Forum Discussion
Good news, everyone!
I set up a packet capture on my firewall's external and internal network interfaces, and on my desktop with the game. After analyzing the packet capture, I noticed something strange: my router was requesting my desktop to fragment all its UDP packets down to 576 bytes (whereas 1500 bytes is a normal packet size).
I traced this to my external network connection on the firewall, which was configured with an MTU of 576 bytes (where, again, 1500 is a normal value). This configuration doesn't match my ISP's end of the link (which is, you know, the normal 1500 bytes). I fixed the misconfiguration, started up Titanfall, and...
Immediately connected to a server!
People of the world who are stuck at "Initializing...", I have found one more thing you can look at to fix the problem! Good luck to all. I have no idea how my system got into this configuration, and I think that theoretically the network connections still should have worked (albiet slower, with fragmented packets), but I will ignore those details for now and celebrate.
the MTU thing... it works!!!
thanks man, you're my saviour.
you should work at EA or respawn man, you are way smarter than those people who tried to fix this issue. thanks a bunch 😕mileyhappy:
I don't understand why they can't figure this out until now even they said that the servers already patched to fix this.
I set MTU value to 1500 on my wireless router and it good to go.
- 12 years ago
I tried to change my MTU to 1500 but nothing have changed. Don't know if I do anything wrong. I went to Command prompt as Admin and wrote down nesth>interface>ipv4>set subinterface "Local Area Connection" mtu=1500 store=persistent. Any one have any idea why my games still stuck at initializing? ☹️
- 12 years ago
You need to do it on your router as well as your PC. Your router is what sends the connection out to the game.
About Titanfall Franchise Discussion
Recent Discussions
- 2 days ago
- 11 days ago