Is there still no fix for this problem on the horizon? been having issues with this problem for months now.
Only workarounds are
a ) Use the repair to fix the broken *.pak file/s
b ) After pak files are fixed back them up then use backups after they break again (this has to be done after every patch)
I have tried setting these files to read only (as some others have suggested) with minimal affect before they break again. Having to do the above workarounds or sit and wait for 10 minutes + due to mech/s stuck in battle after crashing with this error is not fun at all. Neither is having to download gigs of data every time it breaks and backing up gigs of data.
Very annoying, this should be a high priority to get this sorted and shouldn't have taken this long to address TBH.
Edited by Eblean, 07 September 2013 - 06:52 AM.