15 replies to this topic

[Mcgral18]

Started with the most recent patch, where previous, after a crash I could start the game back up instantly, and get back into the game.

Since the patch, however, trying to re-open the game (launcher works, repair tool starts, but pressing play goes to a never-ending Mechwarrior Online black screen, not responding) does not work anymore.

Trying to access the Shaders folder also causes Windows Explorer to lock and and share the never-ending "not responding" loop, requiring the process to be killed and restarted.



Something's broken. Memory leak?
I did a fresh install today hoping it would fix it, but no, same issue.





Perhaps the second part is related to a memory leak of sorts? When the program exits unintentionally, causing something to break?

Fresh install with this, but same result as the old.

Edited by Mcgral18, 14 December 2015 - 11:28 PM.

[TheMadTypist]

I had this same issue today, where it would open the MWO window but never load beyond a black screen, the repair tool would get stuck on trying to "clean" the shaders, and accessing or attempting to delete the shaders cache folder with windows explorer would cause explorer to hang forever.

I was able to get around this by booting into safe mode, and deleting the shaders cache folder (the c:/users/username/saved games/mechwarrior online/Shaders folder). I'm not sure if it was just restarting the computer or safe mode itself that allowed me to delete the folder, but after doing so I was able to run the repair tool to completion and launch the game normally.

This was on a Windows 7 64bit machine.

Edited by TheMadTypist, 06 December 2015 - 12:38 PM.

[Mcgral18]

TheMadTypist, on 06 December 2015 - 12:37 PM, said:

I had this same issue today, where it would open the MWO window but never load beyond a black screen, the repair tool would get stuck on trying to "clean" the shaders, and accessing or attempting to delete the shaders cache folder with windows explorer would cause explorer to hang forever.

I was able to get around this by booting into safe mode, and deleting the shaders cache folder (the c:/users/username/saved games/mechwarrior online/Shaders folder). I'm not sure if it was just restarting the computer or safe mode itself that allowed me to delete the folder, but after doing so I was able to run the repair tool to completion and launch the game normally.

This was on a Windows 7 64bit machine.

I've also done that, but the same issue repeated with the next crash.

Repair tool running fine, but without results. Just coming from one of those...swapping from a map back into Mechlab seems a common crash point, but it's also happened inside a match.

[Goose]

Run chkdsk

[TheMadTypist]

I see what you're saying- just finished a match on Crimson Strait, was loading back to 'mechbay. Game hangs, freezes. Have to end task to get out of it. On attempting to load the game again, ran into the same thing where it loads forever and repair/explorer can't get at the shaders cache folder. Restarting (without using safemode this time) lets me delete and relaunch as normal. Just logging my user off/back on isn't enough, had to be a full restart. Like the crash isn't letting go of something in that folder.

Irritating but not blocking play of the game, got several hours of matches in before getting it to happen.

[Mcgral18]

Goose, on 06 December 2015 - 04:26 PM, said:

Run chkdsk

No issues found there. Memory's fine as well.


Might be Drivers, but I had these issues after I patched, but before I updated my Drivers (to try and fix this issue).

[blacklanner]

TheMadTypist, on 06 December 2015 - 06:37 PM, said:

I see what you're saying- just finished a match on Crimson Strait, was loading back to 'mechbay. Game hangs, freezes. Have to end task to get out of it. On attempting to load the game again, ran into the same thing where it loads forever and repair/explorer can't get at the shaders cache folder. Restarting (without using safemode this time) lets me delete and relaunch as normal. Just logging my user off/back on isn't enough, had to be a full restart. Like the crash isn't letting go of something in that folder.

Irritating but not blocking play of the game, got several hours of matches in before getting it to happen.

I´m having the same problem. It started after the last patch. I tried repair tool - freezes, I downloaded the game via steam - problem remains, I even downloaded new nvidia graphic drivers. Problem reamains. Never had any problem with this game since beta.

[Goose]

Does your video card have any kind'a overclock? Buy "any kind," I mean "from the factory," also …

Also; I've learned that one lap with ether of the MemTest86(s) mean not much: You got'a do at lest two laps …

[Mcgral18]

None default that I know of...an old HD6850

I do have MSI AfterBurner and the Crimson drivers, which both offer overclocking, but none enabled.


Still pretty sure it had to do with the lookupdata.bin

That freeze the moment you try to change it, or load it, which is kinda needed to start the game. The crash affects it somehow. Failing to close the process? I know C++ has an issue with that...but not sure what they're using.

[Goose]

Did your fan speed stop changing with load after the driver update? ATI derp'd it, and issued a "hotfix" replacement driver …

But moar importantly, installing Catzilla has fixed MWOs' software dependencies once or twice before …

[Mcgral18]

Goose, on 12 December 2015 - 01:42 PM, said:

Did your fan speed stop changing with load after the driver update? ATI derp'd it, and issued a "hotfix" replacement driver …

But moar importantly, installing Catzilla has fixed MWOs' software dependencies once or twice before …

Not that I noticed, but I don't really look into it.

The GPU fan still changes, the others are too quiet in comparison to really notice.

[desolator777]

I'm having the exact same problems and I repair computers for a living so needless to say I tried EVERYTHING

[Mcgral18]

And after some advice, it seems it was Avast causing the issue. Turning off protection (remaining with Windows Defender, not nothing), and the game seems to work fine. An hour and no crash or stuttering, compared to crashes every 20 minutes.

[Vermaxx]

I am also having the dead game of deadening, I have to fully restart to wipe out the hang. This is doubly annoying because my computer is lightning damaged and to fully restart actually requires a shut down and unplug, or the network card won't initialize on restart.

I will do this killing of Avast you speak of.

[Mcgral18]

Vermaxx, on 14 December 2015 - 09:53 PM, said:

I am also having the dead game of deadening, I have to fully restart to wipe out the hang. This is doubly annoying because my computer is lightning damaged and to fully restart actually requires a shut down and unplug, or the network card won't initialize on restart.

I will do this killing of Avast you speak of.

Only applicable if you're using Avast.
Disabling the protection until restart (right click, "Avast Shields control", disable to your preference).

[Vermaxx]

Well I killed avast, and steam to boot...and the game worked fine until I got sick of trying to make gauss work.

I guess I can set it back to 64 bit now!