144 replies to this topic

[MaadCat]

Maybe someone found the cure? Can the game be run on 32-bit Windows?

[Threat Doc]

I am running the repair tool right now but, from what I've read, I may as well go back to play Lord of the Rings Online; it works.

I hadn't played for quite sometime, until after the patch prior to the 17th, and couldn't get in at that time. Basically, what I'm reading in this thread, I'm being told to upgrade my OS, and there's no way I can afford that. This is the only machine that will run MWO effectively; my little four-year-old laptop can't do it, even though it has the updated OS.

I don't suppose there would be any way to set up a progress bar in this repair tool, would there, or have you guys already found a solution that you will be deploying, hopefully, soon?

EDIT: Nope. No good. Game will not start. I'm sure that's just sitting with my team mates, PUG or not, real well.

Edited by Kay Wolf, 21 September 2013 - 07:37 PM.

[MKMHPPY]

still ongoing! really tired of fighting this and now it is released. guess the person that is fixing this is on vacation?
deleted all .pac files and freshly run repair tool. deleted shader pack, screamed at it, still no game. five crashed in 3 or 4 minutes and it will keep my mech for 2 hours.
sigh.

[TinFoilHat]

Experienced this on a number of occassions - usually at least 3-4 times in a heavy session (more than 2hrs in-game) and at least once or twice in a lighter session online (less than 90mins). Running 32bit OS, game graphics were set to Medium by default on install and after running repair tool multiple times. Found after lowering settings to Low I've had far fewer crashes, but still occurring every now and then. Not looking to upgrade my PC for another 12 months minimum, so unless a fix can be patched I'm guessing just gonna have to put up with it.

[Threat Doc]

Niko, are you guys getting close to a solution for this? I would really like to get back into playing, but am unable to play at all. I'm not terribly concerned about that, now, but when you guys release leveling I would really like to get that moving, please?

[Lunatic_Asylum]

Install 8-16GB of memory and disable the page file or install a memory cleaner utility that updates every five minutes and cleans memory. I heard that it was a Microsoft Windows error for 64-bit systems.

[MrStevenWolfe]

This one's been biting me in the posterior, too. Bit it's sneaky for me:

I have ALL the graphics setting set to "Low" or "Off" except for Textures, and those are set to "High" (I don't mind fuzzy scenery, I mind fuzzy people)

Resolution is 1024 x 768 (again, I don't mind)

EVERY map runs just fine in the Testing Grounds, but as soon as I join a server, either I only get to hear my 'Mech warm up (that wonderful soumd when it rumbles to life), or I get exactly 15 seconds of gameplay, and it dies. And the number for the memory allocation irks me. The latest one was "11141818 bytes" I then did the math: It's generating a need of 1 gig, and 114 megs of memory. I have 105 GIGABYTES of free space on my harddrive!!!

It was fine during the beta, but I haven't played in a great long while (Startup said I needed 32 patches before I could enjoy this mess) They really need to fix this!

Oh, and I ran the Repair Tool three times. It NEVER found anything wrong with my system

[Threat Doc]

Yeah, perhaps the Clan 'Mechs, CW, and everything else needs to take a back seat to this problem. If people aren't able to play, they're also not going to spend money, right?

[MrStevenWolfe]

Sooo, I turned down my textures to "medium" and, surprise surprise, I haven't had a single issue with running the game since!

[Kalmarre]

I found out how to deal with the problem, guys, try to lower texture level to the medium/minimum, rest of the details can be set to super human unnatural high, and you can play, but if you set textures on high or high+ you will get this bug every time you start game, I don't know why tho :c

[Threat Doc]

Why would that affect even just being able to get into a multiplayer game as opposed to the Training Grounds? I get the black screen that's normal before getting into a match, but the screen doesn't even display any textures before I get the Memory error when gaming with others. Until the first time I mentioned my trouble, in this thread, from well over a year ago, I didn't have any problems getting into a game, at all.

For my part, I think this has to do with the net code, with regard to multiplayer, and anything to do with textures is likely not the real problem.

[Lunatic_Asylum]

Maybe it is like the bug in Battlefield 3? If you had a videocard with 768MB of memory or less, textures started falling apart.
Also, are you running a 64-bit OS?

[TheArcher]

Just had my first encounter with this defect. "Memory allocation for 4138056704 bytes failed." Occurred after I exitted my first match of this gaming session.

Edit: The only unusual thing I did this match was overheat myself to death. I'd be surprised if that was the cause, but since I haven't done that in months...

Edited by TheArcher, 18 October 2013 - 04:01 PM.

[Threat Doc]

lunticasylum, on 02 October 2013 - 10:38 PM, said:

Maybe it is like the bug in Battlefield 3? If you had a videocard with 768MB of memory or less, textures started falling apart.

Also, are you running a 64-bit OS?

Hmmm, I'm wondering why I didn't receive a notification for this 15 days ago?

I don't know anything about Battlefield 3; this is the only PvP game I play. The video card I have is a 2 gig card, I believe, a nVidia GT 450. Nope, can't be, as the internet says those only go to 1 gig (sorry, I'm on my laptop, right now, not at the desktop). On that machine, no... XP 32-Bit. I can't afford to upgrade it, right now.

[Dewey Quinn]

AMD 7970 3 GB Video card. Works perfectly for all other games. 8GB RAM. Windows 7 64-bit OS.

Crashes frequently with the same message:
"FRead did not read expected number of byte from file, only 128 of 0 bytes read."

Reinstalled three times. Used repair tool frequently. Ran CHKDSK an proved no problem on disk. Essentially I have proven that it is a problem with MWO and no other game. EVE Online runs perfectly, for example, on the highest settings across both of my monitors.

I have spent money on this game too... but I would rather actually be playing it than be sold a bunch of stuff that costs MC.

EDIT: Replaced my RAM even though all memtests came back clean and all problems have evaporated.

Edited by Dewey Quinn, 19 October 2013 - 02:18 PM.

[Threat Doc]

I haven't put all that much money into this game, yet, though I have put in $30 more than I would pay for a box at a store for a game I wanted to play. Well, I want to play this one, and it would be cool to throw money at a game I know I could run on my computer. This needs to be fixed yesterday, already.

[Epic Fail]

In our RCT we have noticed a number of players that have the issue with specific maps.

When the specific map is the case deleting the shader cache seems to help for a time.

[Lobokai]

Looking at how many people are experiencing this at a frequency of 1/5th of the time and more.... I'd think this would be a higher priority than new textures. Hey IGP! People who can't play, won't spend $$.

[Threat Doc]

Compared to the overall number of accounts -and, even if a quarter of them are ghost accounts, it's still a very high number, north of perhaps 750,000 folks-, the folks experiencing this are pretty low, so not a lot of time is going to be dedicated to solving this issue, at present. However, if this issue doesn't get solved, and soon, I have a feeling it will spawn other issues and will need to be fixed right away.

I think what's more or less putting me off is that I've already spent $90 on this game, which is more than I would spend on ANY cover for a single-player game, and a lot of other folks have spent a lot more, and I can't play, right now. This doesn't really bother me all that much, but it will once Phase One of CW is released, or after they announce that leveling is in, whichever comes first. Then you'll hear me, perhaps even before then, start to get serious.

[TAMgames]

Bummer... I'm waiting for my "IN GAME" mech to get out of a game I didn't get to play in.

I have a similar crash but I've only seen that error message once (out of maybe 20 to 40 crashes). I always crash immediately after MWO tries to fullscreen mode from the windowed mode.

Which makes me think this is a related issue:
http://mwomercs.com/...een-resolution/

I've had no luck with the repair tool as a workaround. It hasn't seemed to help I still crash to desktop with the same frequency. I'll keep trying it... Since that's the only option right now.

What makes this problem esspecially terrible is when I log back in to MWO my mech is listed as "IN GAME". As a result, instead of being able to just jump back on to MWO and hit launch I have to wait for the game I didn't get to play to finish before I can play again (with my mech).

I have a suggestion on how to fix this. Set the "IN GAME" toggle after players click the READY button before launch. That way even If you CTD you can hop back on an get in a different game.