Initially, this map blackscreened the game, but sound still played. Alt-tabbing didn't do anything.
Then that was changed to it blackscreening, but I could alt-tab, and after enough alt-tabbing, it'd recover from the blackscreen.
When I played in december, it had gone back to perma blackscreen, and only closing the program would fix it, which usually meant I'd not be able to rejoin before someone had killed my mech.
I've gone through one computer since the map initially came out (same problem on that one), reinstalled windows and my drivers several times, and replaced my RAM for general upgrade purposes. Yet the issue persists to a lesser or greater degree. MWO is the only game I consistently play that has issues like this.
Edited by Vassago Rain, 30 January 2015 - 04:14 PM.
Alexander Garden, on 30 January 2015 - 10:46 AM, said:
Likewise.
An update on the status of this is well overdue since my last message on it when it first started occuring.
Why has this not been resolved yet?
It has been extremely difficult to replicate consistently in-house, and user-level fixes that have worked for one player aren't guaranteed to work for another. You can see that in action in this thread alone.
I experienced two instances of the freezes back when they first started manifesting, but after a complete driver re-install they disappeared. That 'fix' involved choosing the Custom driver install option and selecting the 'Perform a clean installation' box.
For a few users the driver refresh was the answer for eliminating or at least minimizing the problem, but unfortunately the issue seems more complex than a simple driver refresh can resolve, as it has persisted for many users with whom I've run through those steps already.
A quirk of this issue is that so far I've only ever seen it occur under NVIDIA GPU's. As far as we know AMD is completely unaffected by it.
What's being done about it?
While we continue to work on the issue in-house, we still need player data. If you're up for it, there are two diagnostic steps that I would like you to run through.
The first is a simple rundown of your system specs provided through a DirectX Diagnostic. If you want to provide this information, please submit *** through a support ticket with the subject heading "Mining Collective Freezes". Also, if your issue resulted in a crash to desktop, please provide the crashdump.dmp file from your "\Users\'your username'\Saved Games\MechWarrior Online" folder.
How to obtain a DirectX Diagnostic
Spoiler
Press Windows Key + R
Type DxDiag
Click Save All Information. If prompted about WHQL drivers, click no.
If the Save All Information button is not present, simply click on Run (32/64 bit)DxDiag. The Save All Information button will appear after the diagnostic.
Attach the file to this support ticket. Please do not copy/paste the contents in the body of your message as it may get truncated.
The second is a bit more complex. It involves running Microsoft's PIX tool to capture live GPU data while your MWO client is running. Rather than list those steps here, I request that you instead submit a support ticket with the subject heading "Mining Collective Freezes".
Finally, sincere apologies to everyone being affected by this. We will resolve it.
Sorry Alexander I didn't realise you'd already acknowledged the issue.
As predicted I'm an Nvidia user and I've already submitted the crashdump file once before. I'm not sure about this PIX data but if it helps you to resolve the problem I'm happy to submit it if you can provide more details.
Have the people with the issues updated stuff NOT related to MWO so much? I mean, simple stuff like Windows Update, and going into the "optional" stuff and selecting all the little wierd stuff that can show up there? How about updating the latest video drivers? Are the video cards they run old enough to not support some part of the graphics package?
Could there be some kind of memory allocation issue, due to an older video card having too small of memory or some such? Is there a common ground when it come to CPU, are any of the players with issues running quad core? or is it smaller/older stuff? Could it be some thing wonky like hard drive write speed/read speeds not being up to snuff related to the way this map loads?
i ask, because, despite my ISP giving me terribad latency issues, I do not crash. Well, ONE time, right after some update not to long ago, but that was the first crash going all the way back to UI 1.0, when we had some pretty significant bugs going on. My rig is not some elite thing, I have a core I7, but it is a 920 from like 2009, I have significant RAM though(I bought future proof at the time, so it isnt top notch now but it isnt outdated yet) I upgraded to a SSD a while back, and I also bought a pair of 650 TI Boost cards for SLI on the cheap. I can honestly say, the only bugs I have dealt with were crazy invisible mech bits from SLI a ways back, the rest is all latency BS from Frontier Communications.
Just always seems odd to me, this game has a history of some players running on uberultra graphics mode and some that crash out to desktop on minimum for no apparent reason. Crazy crashes- HOW DO THEY WORK?!
Have the people with the issues updated stuff NOT related to MWO so much? I mean, simple stuff like Windows Update, and going into the "optional" stuff and selecting all the little wierd stuff that can show up there? How about updating the latest video drivers? Are the video cards they run old enough to not support some part of the graphics package?
Could there be some kind of memory allocation issue, due to an older video card having too small of memory or some such? Is there a common ground when it come to CPU, are any of the players with issues running quad core? or is it smaller/older stuff? Could it be some thing wonky like hard drive write speed/read speeds not being up to snuff related to the way this map loads?
i ask, because, despite my ISP giving me terribad latency issues, I do not crash. Well, ONE time, right after some update not to long ago, but that was the first crash going all the way back to UI 1.0, when we had some pretty significant bugs going on. My rig is not some elite thing, I have a core I7, but it is a 920 from like 2009, I have significant RAM though(I bought future proof at the time, so it isnt top notch now but it isnt outdated yet) I upgraded to a SSD a while back, and I also bought a pair of 650 TI Boost cards for SLI on the cheap. I can honestly say, the only bugs I have dealt with were crazy invisible mech bits from SLI a ways back, the rest is all latency BS from Frontier Communications.
Just always seems odd to me, this game has a history of some players running on uberultra graphics mode and some that crash out to desktop on minimum for no apparent reason. Crazy crashes- HOW DO THEY WORK?!
It's the game being what it is. Hardware and outdated drivers have nothing to do with this; it's almost entirely due to years of neglect, and Soon ™.
The above was a long-standing issue, and PGI's response was that we totally needed to download nvidia beta drivers. Then they looked a bit closer, and oops, it was the game itself that was broken. Who would have thunk it?
Edit: note also that it's only mining collective that crashes, and it's been doing that since it came out.
Edited by Vassago Rain, 30 January 2015 - 05:01 PM.
Vassago Rain, on 30 January 2015 - 04:58 PM, said:
It's the game being what it is. Hardware and outdated drivers have nothing to do with this; it's almost entirely due to years of neglect, and Soon ™.
The above was a long-standing issue, and PGI's response was that we totally needed to download nvidia beta drivers. Then they looked a bit closer, and oops, it was the game itself that was broken. Who would have thunk it?
Edit: note also that it's only mining collective that crashes, and it's been doing that since it came out.
Actually I've had issues with Crysis 2 and 3 as well in regards to video lock ups and freezes. It's an issue with the Crytek engine, not just MWO.
I've actually seen a handful of other players complain about DC/Crashing issues on this map as well. The last time I saw it, a guy got DC'd, reconnected and DC'd again two or three times before it looked like he gave up. One guy even predicted his crash a minute or two into the match.
And this one guy was me. I have a 99,5% chance of crashing in the first minute on Mine Collective (I had 1 crashless match last year). I got so pissed last week that I uninstalled the game, deleted all MWO and Mechwarrior entries from registry and downloaded the game again (slow as f***). No change.
This is the only map I have problem with.
The sad part is that I like it.
The saddest part is that I hate Mordor (NOT for the heat) and based on the stats page it's my best map.
Alexander Garden, on 30 January 2015 - 10:46 AM, said:
Likewise.
An update on the status of this is well overdue since my last message on it when it first started occuring.
Spoiler
Why has this not been resolved yet?
It has been extremely difficult to replicate consistently in-house, and user-level fixes that have worked for one player aren't guaranteed to work for another. You can see that in action in this thread alone.
I experienced two instances of the freezes back when they first started manifesting, but after a complete driver re-install they disappeared. That 'fix' involved choosing the Custom driver install option and selecting the 'Perform a clean installation' box.
For a few users the driver refresh was the answer for eliminating or at least minimizing the problem, but unfortunately the issue seems more complex than a simple driver refresh can resolve, as it has persisted for many users with whom I've run through those steps already.
A quirk of this issue is that so far I've only ever seen it occur under NVIDIA GPU's. As far as we know AMD is completely unaffected by it.
What's being done about it?
While we continue to work on the issue in-house, we still need player data. If you're up for it, there are two diagnostic steps that I would like you to run through.
The first is a simple rundown of your system specs provided through a DirectX Diagnostic. If you want to provide this information, please submit it through a support ticket with the subject heading "Mining Collective Freezes". Also, if your issue resulted in a crash to desktop, please provide the crashdump.dmp file from your "\Users\'your username'\Saved Games\MechWarrior Online" folder.
How to obtain a DirectX Diagnostic
Press Windows Key + R
Type DxDiag
Click Save All Information. If prompted about WHQL drivers, click no.
If the Save All Information button is not present, simply click on Run (32/64 bit)DxDiag. The Save All Information button will appear after the diagnostic.
Attach the file to this support ticket. Please do not copy/paste the contents in the body of your message as it may get truncated.
The second is a bit more complex. It involves running Microsoft's PIX tool to capture live GPU data while your MWO client is running. Rather than list those steps here, I request that you instead submit a support ticket with the subject heading "Mining Collective Freezes".
Finally, sincere apologies to everyone being affected by this. We will resolve it.
FYI. I had this then upgraded video drives, it appeared to "fix" the issue until very recently, in fact I didn't notice/experience a CTD on Mining Colony until tontight. I submitted a support case today with the information you requested.
I was DC'd on MC and it took awhile to rejoin. When I did my team and the other team were beat up leading to easy pickings for me. Profit!
I am ore annoyed by the screen freeze bug that can happen on all maps. You have to be fast on the CTRL+ALT+DEL on that one, and it happens at least once per logon.
Prosperity Park, on 29 January 2015 - 08:50 PM, said:
Quitting a map for no reason other than "You Don't Like It" is a violation of the game's Code of Conduct. It ensures you get a 100% D/C rate instead of a 50% rate. if you drop in, just play it while you can. Quitting makes you a loser.
Edit - 100% Drop rate is worse than a 50% drop rate. If you drop, fight while you can. If you quit up-front, then you're letting the map win.
MC is the only map this happens to me as well and tried all the known fixes. Doe's not happen to often but when it does its about 30 - 60 seconds into the game so for the first minute I try to stay in an obscure route with cover so that in the event of DC I can get back in with out being dead.
One thing I have not seen mentioned is try closing the HUD as soon as you can on this map and see if this helps. R Shift + F11 to close HUD gives a significant performance boost and I almost bet this will help the DC
I will test this out today and see what happens unless someone already has info on that. I do not normally run in that mode because my system can handle this game just fine however sometimes it's just fun to do so and really not that hard.
just for people that dont know the HUD if done with "flash player" so make sure your flash player is up to date.
Too cheap to get a Scaleform license maybe? If that even requires a license purchase, anyways.
OK, despite being a software developer by trade, the only real game programming I've done was during the four years where I taught kids at a game programming camp. Our games were pretty simple most of the time, but we did do some 3D games, though they were never finished products and had only the most rudimentary UI, if any. So I'm speaking from ignorance here.
However...I'm still trying to wrap my head around why you wouldn't just use the game engine to render the UI.
I crash or disconnect pretty much every time I play the map as well. This is before/after switching to the 64 bit client as well, and the last round I had on it, I crashed...came back back, and 2-3 people were disconnected on either team...I went around in my locust and got 3 afk kills...pretty sure most people just give up on the map and don't rejoin.
7
