2 replies to this topic

[Kadix]

I've seen a lot of "CryEngine Error" "FReed did not read expected number of byte from file, only 128 of 0 bytes read" after the last patch.

I've seen this a few times in the past, but it's now close to 50%. The error comes up at start of a match, after the 3d stuff renders but before the player list overlay is drawn. It might be map specific, but I haven't done enough testing to be sure.

I'm running an i5-2500, nvidia 450, 8 gigs of ram, Win8 (not 8.1, but otherwise up-to-date). Game is running as admin.

Is this a known issue? If not, how can I help debug? Are their any client-side crash logs I should send?

EDIT:
System info:
Game config:
Error screenshot:


EDIT2: It is not map or mech specific.

Edited by Kadix, 05 November 2013 - 08:23 PM.

[warner2]

It's a large known issue that has effected me for months. It's caused by .pak files with broken files inside (CRC failure).

You're first step is to run the repair tool. One of the major things that it does it check for corrupted .pak files. It'll re-download them.

What's clear is that this doesn't effect everyone. The general problem can be attributable to dodgy memory or a dodgy hard disk. What's also the case is that PGI have admitted that this has been due to their .pak files in the past. So I'm not entirely sure whether my issue is an on-going issue with PGI's .pak files, or a problem with my machine. I don't get these sorts of issues with any other game or software and I've run a few things like a memory test and hard disk check but all that was OK.

So I'm stumped and PGI aren't really forth coming as to what the issue is/might be via their support email.

http://mwomercs.com/...public-release/

[Kadix]

Thank you. There was a "mismatch" (I assume that means a hash of the file was wrong) on Objects.pak.

Still kind of annoying. It's a new (less than 6 months old) hard drive; there shouldn't be errors, and this is the only game that's had this problem.