Titanfall screenshot
Titanfall screenshot

EA has acknowledged a number of issues that are currently affecting some Titanfall players, including connection errors, crashes, and installation issues, and offered advice on how to work around them.

The errors have reportedly seen the game crashing when accepting match invitations mid-game, and infinite loops when trying to join servers. The publisher has also addressed the issue of players being randomly assigned to the IMC or Militia during the Campaign mode, which it claims is not a bug but designed intentionally to give players a "taste of each perspective".

Connection errors and infinite loop when trying to connect on slower internet connections
Exceedingly slow internet connections may cause an error message when trying to join a server or play your game. Some players may even get stuck in an infinite loop when trying to connect.

Titanfall screenshot

Try resetting your router or modem by unplugging it from its power source for at least fifteen seconds and then plugging it back in the game.

Crashing when accepting an invitation to a match in progress while currently in a match
If you're in the middle of a match and accept a friend's invitation to join their match also currently in progress, your game will crash when accepting your friend's invitation.

To solve this issue, make sure before you either inviting a friend or accepting an invitation to exit to the game lobby first.

Players randomly assigned to the IMC or Militia when starting Campaign
When starting the Titanfall Campaign, you'll be randomly aside to one of the two-opposing forces of Titanfall, either the IMC or the Militia.

While this is by design and intentional, to complete the Campaign you must complete all the missions of the Campaign on your assigned side.

Titanfall screenshot

You can always join the party of a friend assigned to the opposite side to get a taste of each perspective, however personal Campaign progression is limited to your completing all missions on your game-assigned side.

Kinect cannot be used for voice-comms, and Voice and microphone functionality on PC
Xbox One and Xbox 360 players cannot use Kinect for Voice over IP, or voice-communication, in-game.

Similarly, PC players with a microphone-containing-webcam set as your default microphone will have your microphone turned on automatically when playing Titanfall.  If you do not wish to have your microphone on during gameplay, simply disable it in your game settings or disable it as your default microphone in your computer settings.

Some Intel processors must install specific beta graphics drivers
PC players with specific Intel processors, specifically those with Intel Graphics, must download and install a special beta graphics driver to ensure their game runs properly

You can find this driver, along with a full list of what Intel processors the driver is compatible with, straight from Intel.

Hard-drive related installation issues
Some players are reporting installation issues with Titanfall when using a hard drive formatted FAT32. Due to file-size restrictions inherent to FAT32 systems, some of the larger files within the Titanfall installation are unable to be managed by these hard drives.To successfully install Titanfall, make sure your hard drive is formatted NTFS. You can find instructions on how to convert a hard drive partition to NTFS straight from Microsoft.

Titanfall launched on Xbox One and PC in North America yesterday. However, the launch didn't go as smoothly as Microsoft would have liked with Xbox One users left unable to log in to their Xbox Live profiles on the console's most important day since launch.

Source: help.ea.com

New stuff to check out


To add your comment, please login or register

User Comments

Karlius's Avatar

Karlius@ dav2612

I took down the uni server on presentation day once by running a code that "accidentally" started an infinite loop and every time it ran the loop it started an additional new process hitting that hit the same loop that ultimately led to hundreds of processes asking for processor time that ended with a system shutdown lols.

Moral of the story make sure you don't copy and paste the wrong section of code into your loop.
Posted 13:13 on 12 March 2014
dav2612's Avatar

dav2612@ Karlius

I'm a master of infinite loops... but I never ship them out, they are purely for my own 'enjoyment'.
Posted 13:09 on 12 March 2014
Karlius's Avatar

Karlius@ dav2612

Same however it isn't going to affect me or the most of the players read somewhere it can affect those with less than 1mb connection. But agree any infinite loop is bad times!
Posted 12:55 on 12 March 2014
dav2612's Avatar

dav2612@ Karlius

As a developer, I'd have an issue with infinite loops.
Posted 12:52 on 12 March 2014
Karlius's Avatar


Hmm I just re-read everything and actually think I was being a little harsh.

There doesn't seem that much wrong. The only two points I have concerns over are:

Crashing when accepting an invitation to a match in progress while currently in a match.
I'm hoping this gets resolved soon. It could be a minor inconvenience.

The other

Xbox One and Xbox 360 players cannot use Kinect for Voice over IP, or voice-communication, in-game.
Not sure entirely what this means. Can I use Kinect for ingame chat? If not that's a ridiculous oversight as it is basically a selling point(feature) pushed at launch for XB1.

I personally use a headset but a few friends do rather comms through kinect and TV using a stereo headset they plug into the TV for all audio. Something I'm quite interested in trying myself.

So if my fears are correct then I hope this one gets fixed ASAP.

Nothing is really a killer bug though just minor issues. No specific global match making or server errors though which is good. There was XBL downtime but that isn't thought to be the fault of Titanfall.

On a side note Battlefield 4 is broke on all iterations not just XB1.
Posted 12:41 on 12 March 2014
SPACED73's Avatar


Pandora's box of online only gaming
Posted 11:29 on 12 March 2014
essex1212's Avatar


Oh dear...
Posted 11:06 on 12 March 2014
altaranga's Avatar

altaranga@ Karlius

Agreed. Not sure what EA are playing at right now. Thankfully I don't have an XB1 otherwise I'm sure I'd be joining in with the disappointment of more bugs and crashes.

I honestly think the only way they'll learn from this is if it costs them financially. If the game is as bad as they say it is people should be entitled to some of their money back. I'm sure EA would think twice about releasing a crappy, bug-riddled game if they ran the risk of having to pay refunds.
Posted 10:57 on 12 March 2014
dav2612's Avatar

dav2612@ Karlius

Successful beta or not, I can't help but feel there shouldn't be errors like this on the release build on any game.
Posted 10:57 on 12 March 2014
Karlius's Avatar


Oh dear god it's battlefield 4 all over again. Well not that bad but you get what I mean. Hopefully these issues won't take as long as BF4 did to resolve. 4 Months and counting on XB1.

Really don't understand how there are so many issues after such a successful beta.
Posted 10:24 on 12 March 2014

Game Stats

Release Date: 14/03/2014
Developer: Respawn Entertainment
Publisher: EA
Genre: First Person Shooter
Rating: PEGI 16+
Site Rank: 1,080 174
View Full Site