29 replies to this topic

[Jon Cunningham]

Seems like we've gotten a pretty good idea of what is happening and how we can fix both.

Thanks to all of our users who have provided us with custom logs, we have pretty good insight into what is causing the Unknown Error, and hopefully we can put in a fix for it soon.

--

What we need now is some help from users who are stuck in patcher cycle loops. If you are, please get in touch.

Thanks!

[MauttyKoray]

Good to hear, hopefully it goes well! I'm not having much issue myself but I look forward to the return of those warriors who are. Good luck with your progress!

[Sarlic]

Thanks for the update / communication, Jon. Much appreciated.

[Tangent253]

"Get in Touch"
so....been stuck in this loop for about 4 days now...
is this in touch enough? or do i need to do something else?

[Jon Cunningham]

Tangent253, on 20 January 2015 - 08:31 AM, said:

"Get in Touch"
so....been stuck in this loop for about 4 days now...
is this in touch enough? or do i need to do something else?

Mostly I'm posting this to reach out to a couple of users to help test a new solution we'll be trying out post-patch (patch day is today).

[AlmightyAeng]

One of our guys had good success getting out of the patcher loop by resetting the DNS in his router, instead of just doing a public IP flush.

[blood4blood]

Crashing worse than ever tonight after patch, every 3rd game or so is a complete lock-up requiring a full reboot and/or running repair tool before the game will launch again. Already sent my log file days ago, what now?

EDIT: No really, crashed out 2 out of the last 3 games I played...we still in closed beta? No...closed beta didn't crash this often.

EDIT: Tried to get a game in this morning. Loads OK, I started moving, screen freeze crash.

Edited by blood4blood, 21 January 2015 - 05:27 AM.

[ohtech]

I was stuck in the endless patch loop (patcher crashing without completing) and decided to run the repair tool and let it do it's fixes overnight (it found plenty of issues). Unfortunately I still had a missing pak file, but after running the tool again all seems fine.

Won't have to time to check for in-game crashing etc. until after work though.

Edited by ohtech, 21 January 2015 - 11:41 AM.

[Insects]

Patching corrupted two pak files. heromechs.pak and objects.pak, just one dds in each.
Repair tool redownloaded heromechs.pak, but it downloads objects.pak (1.6GB to fix one 5MB file!) then deletes the downloaded file when complete without saving it to the game folder (which is under c:\games so no Program Files permissions issues causing that).
So that is an endless repair tool loop.

Can either reinstall the whole 6GB package, or try and get someone to email me the extracted dds file I need so I can manually replace it in the pak.
Much of the world has limited monthly downloads not unlimited as is common in USA and cant keep endlessly dowloading big GB+ files!

Should have cloned the whole MWO folder as a backup before trusting buggy patcher, grrr.

[Jon Cunningham]

We're finding some edge cases that are keeping us from testing out the new solution just yet.

Anyone in this thread with existing problems, just fyi, not caused by anything but the current repair loop being buggy.

Patience soon - hoping for tomorrow or Friday.

[blood4blood]

Thanks for the update. 3 games out of 4 have crashed tonight. I'm going to give up until the fix comes in, it's more frustrating than fun right now.

[ollo]

I guess the "unknown failure" while supposedly trying to redeem inexistent stuff which crashes the game with pure function call is another problem?

[Insects]

Managed to fix problems reported by repair tool, but still getting FReads in game so must be more wrong besides what repair tool finds.


Edit: Seems working now after manually downloading a new objects.pak
Compared with old self repaired objects.pak every file is identical and present and valid (compared with Meld)

Must be crashing out with FRead simply due to minor compression differences in objects.pak?
Perhaps a trap someone threw in to catch texture hackers catching own patcher? lol?
CRC's are different, but Repair Tool doesnt notice.
It only seems to notice if a files CRC is corrupt not an incorrect match to the official versions.

So yeah, confirmed that a pak can be invalid and cause FRead CTD without Repair Tool detecting it.
That is what might cause people to crash out of matches when someone is using a certain uncommon hero mech or cammo pattern with an invalid pak. It would only happen "randomly" and repairs wont ever find it.

Edited by joelmuzz, 22 January 2015 - 05:08 AM.

[PharmEcis]

This unknown error disconnect bug... Is this the crash to mechlab issue? The issue that has been making me curse my almost $1,500 investment in this game?

[Jon Cunningham]

ollo, on 22 January 2015 - 12:48 AM, said:

I guess the "unknown failure" while supposedly trying to redeem inexistent stuff which crashes the game with pure function call is another problem?

Yes.

I can't help with the pure function call, it's a bug in the game code - for that, email support@mwomercs.com

PharmEcis, on 22 January 2015 - 06:11 AM, said:

This unknown error disconnect bug... Is this the crash to mechlab issue? The issue that has been making me curse my almost $1,500 investment in this game?

Yes.

[PharmEcis]

Please make it so! It has gotten progressively worse for me, to the point I couldn't complete the challenge this past weekend. After multiple games with multiple disconnects back to back to back I gave up. It would be nice if you guys gave me that mech since the discos aren't an issue on my end and I would have completed the challenge if it wasn't for all the discos. Some premium time back in my account would be nice as well since I haven't been able to play reliably and my premium time is still burning.

The only good thing is I've gotten more work done at the shop w/o being able to play this game! lol

[Bill Lumbar]

I am now also stuck this morning in a endless loop too. I tried to start MWO, it says servers are down, or if I can start it up and load into the game it comes back a unknown error before I get to the lab and I have to try and log back into the game. So much for the extended event this weekend?

[kf envy]

ollo, on 22 January 2015 - 12:48 AM, said:

I guess the "unknown failure" while supposedly trying to redeem inexistent stuff which crashes the game with pure function call is another problem?

iv been getting that error too. but i find it odd as soon as i use my phones hotspot an not the normal DSL or cable in my area that Error goes bye bye but as soon as i go back onto DSL or cable behold that same error pops up


note i did reinstall MWO a few times an it still gets that fun error an repair tool see nothing wrong with anything.

Edited by kf envy, 24 January 2015 - 04:57 PM.

[Insects]

kf envy, on 24 January 2015 - 04:56 PM, said:

but i find it odd as soon as i use my phones hotspot an not the normal DSL or cable in my area that Error goes bye bye but as soon as i go back onto DSL or cable behold that same error pops up

Sounds like DNS problems, try forcing your computer to use the google 8.8.8.8 DNS instead of the autodetected ISP settings.

[Appogee]

Jon Cunningham, on 22 January 2015 - 10:28 AM, said:

Anyone in this thread with existing problems, just fyi, not caused by anything but the current repair loop being buggy.

Over the Christmas holidays, I was able to fix that problem - for myself and for several other users - by copying three core game files from a working installation of MWO across to the broken. Ping me if you want me to know which files I copied to fix it.