11 replies to this topic

[Toothless]

Not playing right now, because like every patch I have to uninstall and complete reinstall because otherwise I get a cryengine 128 bytes of 0 if I try to launch.

Why is this still in almost 5 months later...?

[wolf74]

I have just Patch al got this problem

FRead did not read expected number of byte from file, only 128 of 0 bytes read.

Start Game
Log in to game
Just as the Mechlab starts to show up the above error happens.


WIll being Email crashdump.dmp and Omicron logs

Edited by wolf74, 23 January 2013 - 12:30 PM.

[wolf74]

UPDATE: Remove Each File one at a time from the game folder (only the one with todays date) was finilly able to get the Mechlab to Load.

Step 1. Remove a File
Step 2. Start Game
if Error Replace File goto step 1

The Textures.pak was giving the above problem.

Edited by wolf74, 23 January 2013 - 12:58 PM.

[glycerin]

bump, this may help others. It might need to be moved to the workaround forum if this fix can be replicated.

[wolf74]

it not a Fix due to the fact it all the texture in game. But it does lets us know where the problem is.

I Can play now but No Texture Building and Smoke is BIG Blocks.

Edited by wolf74, 23 January 2013 - 01:11 PM.

[wolf74]

Update had a Friend Upload his Texture file to me, this fixed the problem.

[FissionBug]

so where can others find the folder? or should we uninstall reinstall and patch all over again?

[wolf74]

Send a Email Report to them. You can link to this thread if this is your problem they will give you a Link to the file so you can download it and replace it.

I do not have there ok (yet) to re-post the link they gave me in a email. If that Changes I will post it here.

Edited by wolf74, 23 January 2013 - 11:45 PM.

[Boulangerie]

I'm getting this problem this morning. Have to go to work though, and don't have time to fix it right now... I did find this other thread which was started a long time ago and linked in another Patch feedback forum. It's now archived, but there was a member of staff who was going to create a repair tool. If anyone has a link to that tool please let us know!!

Here's the thread
http://mwomercs.com/...in-fread-error/

Here's some mention of the incoming repair tool

http://mwomercs.com/...ost__p__1523789

And Here's the teaser for a repair tool.

http://mwomercs.com/...ost__p__1551891

[Boulangerie]

OK, update. I tried logging in again after I got home from work a couple of hours ago and this error was mysteriously gone. Does the patch loader now check for file integrity? Were my files actually corrupt? Or did the game just think they were? Anyway, I was able to play fine.

[warner2]

The link in my signature describes how to test each of your .pak files and where to re-download fresh ones from

Worked for me, I had a corrupted Objects.pak file after the last patch.

Boulangerie, on 31 January 2013 - 07:18 PM, said:

OK, update. I tried logging in again after I got home from work a couple of hours ago and this error was mysteriously gone. Does the patch loader now check for file integrity? Were my files actually corrupt? Or did the game just think they were? Anyway, I was able to play fine.

The corrupted file can be associated with a particular in-game artefact, like a mech or weapon. So for me, sometimes a game was fine, occasionally I crashed. Depends on what was on the field!

[Captain Greene]

ZacharyJ, on 23 January 2013 - 12:13 PM, said:

Not playing right now, because like every patch I have to uninstall and complete reinstall because otherwise I get a cryengine 128 bytes of 0 if I try to launch.

Why is this still in almost 5 months later...?

Yeah I've just basically shut the game down as well.
It's a shame, but this has been an issue for months now.