

#41
Posted 30 January 2015 - 09:14 AM
OP: does it also crash when you try MC on testing grounds, or only on live-games with other players?
#42
Posted 30 January 2015 - 09:16 AM
Ronan, on 30 January 2015 - 09:14 AM, said:
OP: does it also crash when you try MC on testing grounds, or only on live-games with other players?
Sometimes CTRL+ALT+DELETE and press cancel works for me.
Sometimes the whole map locks me up. Total Freeze.
When i try to join the game again i am either dead or killed. So i dont bother and pick another mech.
Because it takes some time to fire up the game. Annoying.
I can understand OP's frustation.
Edited by Sarlic, 30 January 2015 - 09:16 AM.
#43
Posted 30 January 2015 - 09:19 AM
Ronan, on 30 January 2015 - 09:14 AM, said:
OP: does it also crash when you try MC on testing grounds, or only on live-games with other players?
The last two nights I've had success with alt-tab and ctr-alt-del clearing the screen freezes but prior to that I would always alt-tab back in to a completely black screen and have to force-close the client and re-launch it.
#44
Posted 30 January 2015 - 09:29 AM
#45
Posted 30 January 2015 - 09:47 AM
Levi Porphyrogenitus, on 29 January 2015 - 09:09 PM, said:
Step 1 - Run the repair tool.
Step 2 - Switch from 64 to 32, or from 32 to 64, depending on what you use currently.
Step 3 - Turn down your settings to minimum.
Step 4 - Switch from DX11 to DX9, or from DX9 to DX11, depending on what you use currently.
Step 5 - Uninstall and reinstall.
I think there's also a folder you can delete that will force MWO to load fresh shaders or something, which might fix your problem. I'd include it in the steps above as Step 0 if I could remember the details correctly.
I keep having freezes on that map too, and honestly, it is not MY job to fix PGI's game. I don't have the time or the patience to deal with that crap. If they can't make their game work, without constant re-installs and repair tool uses... well, they are bad at their job, plain and simple. Thankfully the freeze usually gets fixed by opening the task manager, put it's a big issue that needs to be fixed by PGI, not their costumers...
#47
Posted 30 January 2015 - 10:45 AM
Quote
Kyocera has disconnected
Dead when I reconnect

There's also been no acknowledgement from PGI they are even aware of the issue and it's been present for about 3 patch cycles now.
Edited by Kyocera, 30 January 2015 - 10:45 AM.
#48
Posted 30 January 2015 - 10:46 AM
Sarlic, on 30 January 2015 - 09:16 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 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
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.
#49
Posted 30 January 2015 - 10:55 AM
Edited by Kain Thul, 30 January 2015 - 10:56 AM.
#50
Posted 30 January 2015 - 11:41 AM
Yasuoka, on 29 January 2015 - 09:23 PM, said:
That has to be a weird anomaly then. If the Map shaders were really "BAD", way more folks would have issues but don't. What are his system Specs, Video card etc etc. Laptop or Tower...?
#51
Posted 30 January 2015 - 11:57 AM
Alexander Garden, on 30 January 2015 - 10:46 AM, said:
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
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.
Thanks i will do this shortly.
And i can imagine your frustation to deal with it! Haha.
Edited by Sarlic, 30 January 2015 - 11:58 AM.
#52
Posted 30 January 2015 - 12:19 PM
#53
Posted 30 January 2015 - 12:25 PM

#54
Posted 30 January 2015 - 12:32 PM
Prosperity Park, on 29 January 2015 - 08:50 PM, said:
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.
and supposedly theyll ban you for it
Alexander Garden, on 30 January 2015 - 10:46 AM, said:
Why has this not been resolved yet?
It has been extremely difficult to replicate consistently in-house
For example, Ive never had the issue
#55
Posted 30 January 2015 - 12:33 PM
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's NOT that he doesn't like the map, he said he DCs 50% of the time..
He's not saying he doesn't like the map, he's saying he can't play the map currently
Meaning he is WASTING his OWN time when he gets that map if he has to ATTEMPT to reconnect and or DC again.
Who the "F" are you to tell him he has to waste his time on it..??
Until he fixes (IF POSSIBLE) whatever issue he has (maybe hardware related), then let him do what he wants.
You know what happens when I get a PHONE CALL when playing..??
75% of the time I DC to take the "MORE IMPORTANT" call. Make Money or worry about MWO..??
You see business is business, and if MWO wants any more coin out of me EVER, then MWO will have to deal with an occasional DC.
What's more important to the OP, worrying about a map he is barely able to play, OR is his OWN time more important..???
I think wasting time from HIS life is something he considers NOT an option when it comes to a map for a "F"ing video game.
What do you think is more important to the OP..??
Edited by Odins Fist, 30 January 2015 - 12:34 PM.
#56
Posted 30 January 2015 - 12:34 PM
#57
Posted 30 January 2015 - 12:36 PM
That said, when I switched from DX9 to DX 11? It stopped happening, ever. Well, maybe once. But not in the same place it did before so probably just a random different sort of crash./
As for new computer, no issues, thankfully! Aside occassional random crash that could be any map.
#58
Posted 30 January 2015 - 12:47 PM
Kevjack, on 30 January 2015 - 09:29 AM, said:
This is what worked for me.
I would crash almost every time I played Mining Collective until I changed to DX11 in the options.
Edited by James Warren, 30 January 2015 - 12:50 PM.
#59
Posted 30 January 2015 - 03:57 PM
Rorvik, on 29 January 2015 - 08:48 PM, said:
No more.
Until PGI fixes this map, I'm just going to cut to the chase and DC and play another Mech. There's just no point. I've got Premium Time going and I'm wasting it by CONSTANTLY being DCed on this map.
So, if you see my DC while on Mining Collective, don't bother reporting me. File a support ticket on my behalf instead.
use to happen to me, now I'm running the 64 bit client with Dx11 and its virtually eliminated the problem
#60
Posted 30 January 2015 - 04:03 PM
blood4blood, on 30 January 2015 - 10:23 AM, said:
Just FYI, I've been on DX11 the whole time, and tried both 32 and 64 bit clients, with no noticeable change in the crashing.
That's interesting. On DX9 I literally crashed every time the map loaded, but haven't crashed a single time on DX11.
The DX11 suggestion has fixed it for a lot of people I give it to, sorry it didn't apply to your situation.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users