194 replies to this topic

[Krist Smith]

Soulgorger, on 04 November 2012 - 07:01 AM, said:

Trist;

I thought about this some more in my sleep last night. Amazing how you can wake up with an idea.

The problem is that we're chasing ghosts, and only making guesses as to what it could be. The reason we're doing this lies within the error message itself. The error message is vague, and needs more detail.

Is there a means that PGI can turn on a more detailed "FRead" error message? We need to know what file it's trying to read, and the path that it's trying to read it from. When we have that error message, tracking this bug down will be much easier.

Additionally, I also made the assumption we're all getting this FRead message at the same point in game play. Mine occurred when the match started. The last number I saw was the "1" on the countdown timer, then the game would close and the error box would pop up. Can everyone with this issue concur that's when they saw the error? If not, when are you getting the error?

Maybe Trist can shed some light as to what files are read when the match actually starts. This would be another means as to discover which files are involved that could cause the error.

Just some thought.... Hope it helps.

Well, the thought did cross my mind at first, but the thing is that the FRead error pops up when it's reading a pak that's already got the corruption in there. In order for it to be helpful, I'd need to catch the problem when it's causing the corruption. That's what I was hoping to catch by setting the files to read-only, but so far there's no luck there.

Krist

[x Marder x]

The patch-er is causing now problems he is downloading the the first file but
he loads 1056 MB but he shod loud 1068,18 MB.
The next thing is he closes him self. No error message nothing. Just closes it self and i have to restart the install process.


I cant install teh game any more -.-

MD5 Mismatch, its imposibel.

Edited by x Marder x, 05 November 2012 - 11:39 AM.

[Hideki]

x Marder x, on 05 November 2012 - 10:20 AM, said:

The patch-er is causing now problems he is downloading the the first file but
he loads 1056 MB but he shod loud 1068,18 MB.
The next thing is he closes him self. No error message nothing. Just closes it self and i have to restart the install process.

had exactly the same issue here.
like i said in the win8 topic:

]i installed win8 fresh on a samsung 830 ssd yesterday but im getting the "fread" crash after log in immediatly. reinstalled mwo twice and it still crashes every time..i had no problems with win7 - but i had no ssd back then

Edited by Hideki, 05 November 2012 - 10:49 AM.

[Soulgorger]

Krist Smith, on 05 November 2012 - 10:09 AM, said:

Well, the thought did cross my mind at first, but the thing is that the FRead error pops up when it's reading a pak that's already got the corruption in there. In order for it to be helpful, I'd need to catch the problem when it's causing the corruption. That's what I was hoping to catch by setting the files to read-only, but so far there's no luck there.

Krist

But, if you recall our initial conversation, none of my .pak files were corrupted per 7-zip.

[Tarskin]

I got this error as well after 2 games that went fine, games 3 and 4 gave me the error just after drop.

For Reference, my system:

I7-860 (CPU)
Nvidia GTX260 (GPU)
4GB (Memory)
Win7-64 (OS)
AVG (anti virus)

Edited by Tarskin, 05 November 2012 - 11:48 AM.

[ltwally]

I've been reading that some think it's their AntiVirus somehow corrupting the PAK files (which are nothing more than ZIP files with a different extension).

For the past 3+ years I have used Microsoft Security Essentials on most of my home systems, including machines that I use to work from home on.

I have downloaded a great many files, ZIP or otherwise, and played many games (including the Crysis line-up). Never have I had files corrupted like this. Not once.

While I am not married to my AV, and I do not discount the possibility that it is my AV somehow causing this.... I really doubt it. It's just too much of a freak coincidence. It seems far, far more likely that MW:O is the source of the corruption.

[x Marder x]

05.11.2012 21:35:39 - main - Config file: A:\Games\Piranha Games\MechWarrior Online\Bin32\PatchBot.cfg
05.11.2012 21:35:39 - main - Setting null proxy to False
05.11.2012 21:35:39 - main - Local frontend version: 0
05.11.2012 21:35:39 - main - Checking patch inventory.
05.11.2012 21:35:39 - main - Connecting...
05.11.2012 21:35:39 - main - Connecting for maintenance check.
05.11.2012 21:35:39 - main - Fetching patch inventory data..
05.11.2012 21:35:40 - main - Remote frontend version: 38
05.11.2012 21:35:46 - patch - Patch 1 of 38
05.11.2012 21:35:46 - main - Fetching update from server...
05.11.2012 21:35:46 - main - Connecting...
05.11.2012 21:35:46 - main - Downloading....
05.11.2012 21:46:23 - main - Extracting patch zip...
05.11.2012 21:46:23 - main - Extracting all...
05.11.2012 21:47:01 - main - Caught an exception somewhere in the patcher. Closing down...
05.11.2012 21:47:01 - main - Exception: CRC error: the file being extracted appears to be corrupted. Expected 0x894C08E2, Actual 0x2CC137C1


thats what in the frontend_patcher_log

How do i fix it? I would realy like to play MWO but i cant even install it any more.

Is there a manual way to do it?


I have restrtet m system serveral times and did always click retary with md 5 error now i have mwo istaled again.

I have no some new data in my game directory where the objects.pak and other pak fiels are siting like FrozenCity_ig.pak.

Ok this are new files, they get alsow broken, if they do I am stuck in the louding screen of the map.

Edited by x Marder x, 06 November 2012 - 08:45 AM.

[Series]

I am also getting the Fread error even after the latest patch. I tried running the 7z software test and found the following broken files.

Caustic Vally, frozen city and forest colony, animations and gamedata. I have sent a detailed e-mail with this info to your game master Magius ( refer to ticket: ticket #50418). If it is helpful, I am also prepared to send the corrupted/broken files to you as well.

I hope this helps!

Series

Edited by Series, 06 November 2012 - 07:38 PM.

[Malcom Cruise]

So yeah also getting the FRead error still as well, and again it's the objects.pak file. Can we still download this .pak from the link earlier in the thread?

[Soulgorger]

For anyone who locked their .pak files to read only, make sure you unlock them BEFORE patching or you'll be in my boat and having to re-install the game.

[Krist Smith]

ltwally, on 05 November 2012 - 12:02 PM, said:

I've been reading that some think it's their AntiVirus somehow corrupting the PAK files (which are nothing more than ZIP files with a different extension).

For the past 3+ years I have used Microsoft Security Essentials on most of my home systems, including machines that I use to work from home on.

I have downloaded a great many files, ZIP or otherwise, and played many games (including the Crysis line-up). Never have I had files corrupted like this. Not once.

While I am not married to my AV, and I do not discount the possibility that it is my AV somehow causing this.... I really doubt it. It's just too much of a freak coincidence. It seems far, far more likely that MW:O is the source of the corruption.

Very true. It is indeed the game (or patcher) causing the problems, but it is highly possible that the game is conflicting in some way with another piece of software (which would most likely be AV software). For example, an early iteration of the patcher would incrementally update itself. It would patch, then replace itself, patch, replace, etc. until it was fully updated. This set off red alarms in some AV software, since it looked so much like a virus replicating. So now the patcher does a cumulative patch to itself once and that's it (at the cost of about 1 MB of download size, which is small enough to ignore in this case).

Not that this is the same, by any means, but AV isn't being blamed, it's just a suspect in these pak file murders. It hasn't been proven and is looking less and less likely, but the thought is just that some other software is impacting the way the game runs, streams files, something along those lines. The fact that it happens continuously even after reinstalling to some, and not at all to others (particularly anyone in our studio or QA) suggests that there's something else that exists outside the game playing a part. Again, it's not blaming anything else, just a combination that we hadn't accounted for, or something along those lines.

Anyway, sorry to rant, but this bug is really annoying me. I've debugged PS2 core engine bugs that were more fun than this... Sorry it's taking so long.

[Captain Greene]

Just cking back in on my end. After the patch the game started and ran juft fine.
A 7zip shows the same 4 errors still exist I posted the screenie of a couple days ago.

[Kmieciu]

I added the MWO directory to the exceptions list in Microsoft Security Essentials and I did not experience a single CTD in 2 days. I don`t know if it proves anything but it`s worth trying.

Some users reported that moving the game to another drive fixed the problem for some time...

[Korrius]

I'm not sure why this is happening, but I did copy the files from my mechwarrior directory to a computer in teh house with this problem, and allowed them to play with no further errors.

[Hobo Dan]

I reinstalled for this new patch and was able to use the Mech Lab without issue. I was able to play one game on Frozen City as well with no issues. The second game I played crashed to desktop while loading Caustic Valley. The third game I tried on River City gave me the FRead error before crashing. I have been having the FRead issue for about a month and a half. Very frustrating.

Last week I tired swapping corrupted files for good ones, but it seemed to just creorrupted too quickly so I gave up. I really hope a solution is close...

[Tarskin]

I am also very close to just giving up, the files get recorrupted way to quickly

[Legionn]

For those experiencing the FRead issue and DO NOT have any corrupted .pak files, deleting the "Shaders" folder (C:\Games\Piranha Games\MechWarrior Online\USER\) fixed my issue.

[Oldmanfang]

Just started getting this error today any fix in the works..

[RudWolf]

It is also possible to make crc check of .pak files using Winrar. I have discovered thah my obejcts.pak became corrupted again. After opening support ticket, Magius sent me this link

http://patcher.mwome...ame/Objects.pak

for downloading new one. That was 2 patches ago however.

[Alexandrix]

Hello all,
just encountered this error after downloading the patch today.Used 7zip and found the corrupt file in textures.pak.The new mechbay floor/smoke texture got corrupted.Any link to the textures.pak file?

Deleted the textures.pak hoping the patcher would detect it's removal and replace it.no luck.the game does look quite hilarious without textures tho.Takes me back to the 90's and mechwarrior 2 lol

Edited by Alexandrix, 08 November 2012 - 07:08 PM.