So here is the most recent conversation that I had with the Game Specialists :
Mark: Sorry about the delay there Bryan. I can see that the majority of these crashes are as a result of the same file/module on your computer, which is showing as materialsystem_dx11.dll. This is actually an issue that is being investigated by the Titanfall studio at the moment, as they have seen a lot of reports of it recently. Unfortunately I do not have a timeframe for a fix on it at the moment, but it is being looked into as we speak
you: OK. So what do I do in the mean time?
Mark: Unfortunately the only thing we can advise in the meantime would be to wait. I know this is probably the last thing you want to hear, but none of the tools that I have access to here will be able to fix this. I have seen some reports where people report the crashing stopped when running MSI Afterburner (http://event.msi.com/vga/afterburner/download.htm), or by going into the computer settings and enabling Software Automatic Fan Control, but this is not something that we would recommend doing, and is not a guaranteed fix
you: is there any estimated timeframe that this should be fixed in? I understand that there are never any definite answers, I am just looking for an educated guess.
Mark: Nothing definite, but as this seems to have affected quite a few people I would guess it is a pretty high priority. It will depend on the complexity of the issue, but once the cause is determined it should be no more than a few days to get a fix in place
Mark: The only problem is that I wouldn't know how long it will take to locate the exact cause, especially for a game as complex as Titanfall
Mark: If you wish I can take a look on he developer forums for any possible threads that might be of use, and email them out to you, so that you can keep an eye on them for any updates?
Mark: *the
you: It seems to have happened after the patch that occurred on the 10th or 11th - everyone that i have seen in the forums have only recently purchased the game
Mark: Yeah, have actually stumbled across one or two myself and definitely seems to be a pretty recent issue. Hopefully that will mean they can isolate it to be something caused by the update, and that should speed it up slightly. From what I have seen so far the have been very quick to address any issues, so I would be confident that as soon as they figure out the cause this will be fixed up pretty swiftly
He siad that this issue is being looked at by the development team and they should have something fixed "soon"...here's to hoping...
