Jump to content

- - - - -

FRead did not read the expected number of bytes from the file?


33 replies to this topic

#21 Win Ott

    Member

  • PipPipPipPipPip
  • The Serpent
  • The Serpent
  • 153 posts
  • LocationSomewhere in the Southern Reach

Posted 18 November 2013 - 12:21 PM

After I uninstalled and reinstalled the program (1 hr job), the error has gone away and hopefully will not return. Of course, tomorrow may change things after the patch....

#22 undiscovered

    Rookie

  • The Kicker
  • The Kicker
  • 2 posts

Posted 18 July 2014 - 11:38 AM

I just find out, that this error "FRead did not read... and so on" appears only in one map = Tourmaline Desert and variation of this map.. is anyone with the same problem? Thx

#23 Inappropriate74849

    Rookie

  • 2 posts

Posted 06 September 2014 - 12:06 PM

Same error, dont want to load to caustic, and mew city map

#24 zaid

    Member

  • PipPipPip
  • Elite Founder
  • Elite Founder
  • 52 posts

Posted 07 September 2014 - 08:41 PM

Run the patcher. It usually means some of your files are corrupted.

#25 etarm

    Member

  • PipPipPipPipPip
  • Philanthropist
  • Philanthropist
  • 124 posts
  • LocationCalifornia

Posted 29 November 2014 - 12:24 PM

View Postzaid, on 07 September 2014 - 08:41 PM, said:

Run the patcher. It usually means some of your files are corrupted.


I just started getting this error on Manifold. When you say "run the patcher" do you mean the repair tool from 2013 here:

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

or is there some other way to initiate a re-patch?

#26 zaid

    Member

  • PipPipPip
  • Elite Founder
  • Elite Founder
  • 52 posts

Posted 30 November 2014 - 11:49 PM

Yes that one, but it is also included in game now. There's a little cog-wheel top right just after you log-in. Click it and choose the repair tool. Run it. It will tell you what files it needs to fix. Then it will download them. Then it might erase the file you downloaded. So then you have to quit, re-run the patcher, re-download the file, and hope it works the second time. Then you need to re-run the patcher a third time to make sure the downloaded file isn't corrupt.

Yes this has been happening to me almost weekly since beta. Yes they know of the problem. No they don't know how to fix it. Have fun.

#27 etarm

    Member

  • PipPipPipPipPip
  • Philanthropist
  • Philanthropist
  • 124 posts
  • LocationCalifornia

Posted 01 December 2014 - 07:44 AM

It worked for me. I used the external tool, since I ran it before I saw your reply and didn't know it was built in. One time through seemed to do the trick (fortunately). Thanks!

#28 83DJKam

    Rookie

  • 1 posts

Posted 07 February 2015 - 02:00 AM

Ran the last patch over a week ago and haven't been able to get on a match. FRead file read 128 of 0 bytes. I've tried everything I can think of. I'd send a support claim but your support line continually takes me to Outlook and I don't use Outlook for my email

#29 TheCaptainJZ

    Member

  • PipPipPipPipPipPipPipPipPip
  • Storm
  • Storm
  • 3,708 posts
  • LocationUnited States

Posted 07 February 2015 - 07:24 PM

View Post83DJKam, on 07 February 2015 - 02:00 AM, said:

Ran the last patch over a week ago and haven't been able to get on a match. FRead file read 128 of 0 bytes. I've tried everything I can think of. I'd send a support claim but your support line continually takes me to Outlook and I don't use Outlook for my email

Use your own email program and send it to support@mwomercs.com. The hyperlink will use whatever your browser and operating system are set to use for default programs for email. (Your computer is not that smart). Also, it might take a few days for them to get back to you, fyi.

Did you try using the repair tool in the launcher? Click the gear icon to get to it.

#30 etarm

    Member

  • PipPipPipPipPip
  • Philanthropist
  • Philanthropist
  • 124 posts
  • LocationCalifornia

Posted 07 February 2015 - 10:04 PM

I've had this error twice in the past. The first time, the repair tool worked on the first try. The second time, I had to run it twice before the error went away. Good luck!

#31 Repasy Cooper

    Member

  • PipPipPipPipPipPipPipPip
  • The Vicious
  • The Vicious
  • 1,131 posts
  • LocationAlpheratz

Posted 29 April 2015 - 07:58 AM

Still getting this error, even after running repair tool. This is some pretty dirty laundry PGI...

#32 Richter Kerensky

    Member

  • PipPipPipPipPipPipPip
  • Bridesmaid
  • 601 posts

Posted 29 April 2015 - 01:34 PM

View PostRepasy, on 29 April 2015 - 07:58 AM, said:

Still getting this error, even after running repair tool. This is some pretty dirty laundry PGI...


The only way I was able to fix it was to uninstall and reinstall the game.

#33 Eldamar

    Member

  • PipPipPipPipPip
  • FP Veteran - Beta 1
  • 102 posts
  • Facebook: Link
  • LocationPleasant Valley, NY

Posted 29 April 2015 - 08:32 PM

Uninstalling does not always help tried that myself about a month ago and with this latest patches I am guaranteed to get the fread error on every match I try to play past my first. I got more detailed post in the patch notes forum that I expect will be ignored by pgi as my emails to them about this for the past week have been with the log files they asked me to send when it happens.

#34 Davz Not Here

    Rookie

  • 7 posts

Posted 10 October 2015 - 08:39 AM

apparently this hasn't been fixed, or it has popped up again

i am getting the error now, crashing as i load into the mech bay
when i run the repair tool it's the "textures.pak" that is the culprit
several un / re installs later + several runs of the repair tool and nothing is fixing it.

Edited by Davz Not Here, 10 October 2015 - 08:39 AM.






2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users