20 replies to this topic

[Davegt27]

I tried to play a CW match and before I even got in game the game crashed

I tried 2 more times before I got back in game
That’s 3 times with 3 crash reports
(You can get back in game faster if the crash report did not take so long)

Yesterday was the same thing, one time I got back in game and was flying around
The map like a spectator



The penalties really piss me off since it’s their effort to computer control the matches that’s the problem


I wish they would work on their current game modes and get them right before coming out with something new

(oh and I been in contact with support about the problem)

[nehebkau]

Ya I know -- something that is intended to stop people DC-ing on purpose causes grief for people who just want to play the darn game.

[Monkey Lover]

I know it's not nice to say but really after so many disconnects there comes a point where you're effecting not only your games but 23 people each time. The system they have is very forgiving.

[ScarecrowES]

Realistically, whether you disconnect intentionally, or your gaming setup is crap and is dropping your connection for you... either way you're having a significant negative effect on every other player in the match you got thrown in. The punishment is fair. In fact, generous.

[Wintersdark]

Yeah.

A tip: if you are running AMD, be aware that the Crimson Edition drivers can cause severe crashes, usually showing a "D3D device removed" error. If you roll back to the last Catalyst drivers from Nov 2015, this fixes the problem.

But yeah, while it may not be your fault (probably is not), your crashing is impacting everyone, so it needs to get resolved rather than wrecking other people's gameplay.

I don't see what game modes have to do with it, or adding new ones (note that they ARE changing the game modes AND adding new ones at the same time, BTW). You'll never have a bunch of game modes everyone likes to play, no matter what they do. I assume you're arguing that they shouldn't have a disconnect penalty and should just make all the game modes fluffy and perfect, but there are MANY reasons people disconnect, be it intentionally or not.

I've known people to disconnect intentionally because:
Dislike the map
Dislike the mode
Dislike friendly players
Afraid of enemy players
Just cbill farming
Some personal emergency
They're just idiots.

Then there's people who just keep crashing or whatever. You should get on the horn to Support and get that resolved, because crashing isn't normal.

[Davegt27]

I had problems with my nvidia card so I spent over $200 for the AMD card lol

The laugh is on me since I still have problems
I submit the problems are 100% PGI’s fault

We have all played video games, me since the 1970's
Never have I seen so many problems
Of course it’s all my fault (if they had checked their log they would see it wasn’t)

Every time a crash report was sent to PGI but they said I left the game when in fact I never got into the game

So how is them lying about what happened fair or generous

I am now up to 2 min punishment



And every time I did make it back into the game and was never the lowest damage producer

Edited by Davegt27, 05 March 2016 - 09:38 PM.

[Triordinant]

If you're the only one having the problem, then the problem is either at your end or somewhere along the way between you and PGI's servers (like your ISP, for example). If the problem was at PGI's end a whole lot more people would be having the exact same problem.

[Narcissistic Martyr]

If I disco more than once a night I typically leave until next patch as that will usually fix it...

[Agent1190]

Davegt27, on 05 March 2016 - 05:53 PM, said:

I submit the problems are 100% PGI’s fault

And every time you die it's because your killer was aimbotting, yes?

Despite your attitude, I will try and explain a few things hoping that you will work through your problem.

PGI crash reporting and the in-game penalties are 2 separate entities. The crash reports are compiled (conjecture here) by PGI, and if a trend appears, then they can try to correct it. This takes time, because you do not want to create a new issue to fix an old issue. Just because you send a crash report does not mean the software people are jumping on it right away. I don't think there is ANY software company that has the capacity to do that, much less PGI.

This of course means your game is ticking up the number of crashes in a given time, which happens instantly, regardless of your sending a crash report.

There are things you can do on your end to help diagnose the problem. If you find something that stabilizes your client, then you could send that info to PGI (since it sounds like you are communicating with them on the problem. The other thing you could try is use the testing grounds. Make some changes, whether it's to your graphics drivers (as already suggested, which it appears you ignored because "it's not your problem" or to your graphics settings in game) so you are not affecting other players. It shouldn't cause disconnect penalties using the testing grounds.

[Wintersdark]

Davegt27, on 05 March 2016 - 05:53 PM, said:

I had problems with my NIVID card so I spent over $200 for the AMD card lol

Did you listen to me at all? It's a driver issue, crimson drives + mwo = crashes. You can fix by reverting to nov 14th catalyst drivers. Here, I'll post em for you:

Drivers: https://dl.dropboxus...-win7-nov14.exe
AMD Cleanup Utility to fully remove current drivers: https://dl.dropboxus...anuputility.exe

Or if you're one of those people who insists everyone trying to help is trying to fill you up with evil malware, just get those from AMD directly or Guru3d (I dunno if 15.11.1b is available on the AMD site, but Guru3D always has older driver versions).

Quote

The laugh is on me since I still have problems
I submit the problems are 100% PGI’s fault

Why? That's as silly as them insisting it's your fault (pro tip: they don't)

Quote

We have all played video games, me since the 1970's
Never have I seen so many problems

********. I could name many, many cases in AAA major releases with massive multi-million dollar budgets with way, way worse problems that hit everyone.

Quote

Of course it’s all my fault (if they had checked their log they would see it wasn’t)

Every time a crash report was sent to PGI but they said I left the game when in fact I never got into the game

So how is them lying about what happened fair or generous

Ok, seriously here, you understand that what the game client says != what PGI says? The game client is just a program, there are real support people at PGI who will be very eager to help you, and not just say it's your fault.

There's no lying going on.

Quote

I am now up to 2 min punishment

Deal with the problem. It's two minutes until you can crash again and ruin another match. I've already showed you the solution, but you're also highly recommended to contact PGI support and deal with them too.

Quote

And every time I did make it back into the game and was never the lowest damage producer

Relevance, this has none.

Triordinant, on 05 March 2016 - 05:59 PM, said:

If you're the only one having the problem, then the problem is either at your end or somewhere along the way between you and PGI's servers (like your ISP, for example). If the problem was at PGI's end a whole lot more people would be having the exact same problem.

He's not. It's a known problem. AMD Crimson drivers cause intermittent crashes for many people - for me, I'll crash in 1/5 games. I test it every time there's a new release (in case it's fixed) but to date, I still crash. It's not just me, either.

Reverting to the drivers linked above fixes the problem completely.

But he totally should fire off an email to support (WITH a dxdiag file), so they can better work with AMD to fix it.



EDIT: Removed unnecessary assholery. My apologies.

Edited by Wintersdark, 05 March 2016 - 06:27 PM.

[John1352]

I think I was in the game when this happened, we still won. It's really frustrating when MWO crashes and it takes 5 minutes to get back in (it often takes ages to get the crash report sorted out). Then they give you a penalty because the game crashed.

Narcissistic Martyr, on 05 March 2016 - 06:07 PM, said:

If I disco more than once a night I typically leave until next patch as that will usually fix it...

Sometimes I just want to shoot robots, today.

[Wintersdark]

John1352, on 05 March 2016 - 06:23 PM, said:

I think I was in the game when this happened, we still won. It's really frustrating when MWO crashes and it takes 5 minutes to get back in (it often takes ages to get the crash report sorted out). Then they give you a penalty because the game crashed.


Sometimes I just want to shoot robots, today.

Because obviously the server has no way of knowing that your game crashed. The crash reporting is unrelated to the game server.

If you keep crashing, though, you need to get that **** sorted out, not keep trying to drop thinking it's magically going to get better.

[Wildstreak]

@Davegt27

Don't feel bad, you are in the place I was at the end of 2015.
I had the same thing, getting Discons, I pack up everything for the report, come back to find I am penalized for something not my fault.
At least by sending in the reports, PGI knows you did not do it on purpose.
You're not the first for this.

[Wintersdark]

Wildstreak, on 05 March 2016 - 06:45 PM, said:

@Davegt27

Don't feel bad, you are in the place I was at the end of 2015.
I had the same thing, getting Discons, I pack up everything for the report, come back to find I am penalized for something not my fault.
At least by sending in the reports, PGI knows you did not do it on purpose.
You're not the first for this.

He's not the first, and not alone, but sending in the crash reports doesn't link to the actual event/match - they just know a user is having MWO crash.

He SHOULD be emailing support with the details (and dxdiag results) so they can actually help him. Just playing and crashing more doesn't help the problem get fixed.

Dave: If you're running the AMD Evolved app, close it completely (not minimized to system tray, fully closed) before launching MWO. Sometimes, that helps people crash less.

But reverting to the drivers linked above corrects it completely.

[Wolfways]

Plays for 3 years with matches constantly crashing.
Leaves for a year.
Returns to find that matches (now called quick play) no longer crash, and there's CW!!!
Now there's CW has no interest in quick play.
CW constantly crashes...

[Monkey Lover]

Davegt27, on 05 March 2016 - 05:53 PM, said:

Every time a crash report was sent to PGI but they said I left the game when in fact I never got into the game

So how is them lying about what happened fair or generous

I am now up to 2 min punishment

Corrupt files will stop the game from loading and crash your game. Did you try the repair tool? If you keep getting corrupt files often your harddrive might be going out.


A bad power supply will give you these problems because this is when the videocard starts to ramp up the power usage. Do you run any other 3d games ? If you dont you might try to stress test you system with a 3d benchmark program.

[Narcissistic Martyr]

John1352, on 05 March 2016 - 06:23 PM, said:

Sometimes I just want to shoot robots, today.

Fair enough.

[Endost33L]

Were you trying to play the game after your pc was hibernated or after sleep mode?
I've had the same problem as you (nvidia gfx card tho), was getting the crashes and the time punishment.

A simple reboot and things were back to normal.

Edited by Endost33L, 05 March 2016 - 10:00 PM.

[meteorol]

I think it has been over a year since my game crashed the last time. No idea how those guys constantly getting crashes.

[Tarogato]

If you're disconnecting, you deserve to be punished. I don't care if you are doing it intentionally or having hardware or driver compatibility issues, your mech is still sitting in the match with 23 other people playing the game.