12 replies to this topic

[Euklides]

Greetings and felicitations

As it is now, if you crash and get the bugreporter to send a report off to PGI and even if you rejoin you get a deserter penalty.
Is this really necessary?
I can understand providing penalties if no crash report was sent as there would then be no evidence against simply quitting. But when proof of unintentional DC is provided for would there still be a need for timer penalisation once you reboot the game and try anew?

My current issue stems from me upping the graphics since I recently upgraded my computer by adding a new heatsink to my intel 930 to enable it to go to 4ghz and slapped on 8 more gigs of ram to the 6 I had before.
Everything is stable and fine for roughly 2-3 hours. then MWO crashes.
I've never had this frequent crashing before which lends me to believe that there is issues with me increasing the graphics from all low to all high.
This is the sole thing related to MWO I have changed, since I doubt that overclocking a CPU will have problems with only a specific software, or adding more ram.

Now if you have a solution to my problem that would be dandy, but the question here is more about the system to stop DC's.

[RussianWolf]

more complex programing than PGI is capable of.

[adamts01]

It's kind of a slap in the face after the game disconnects you, normally right as the fight is heating up...... But I still think it's necessary. Too many people would either just quit or unplug their modem if they got a game mode they didn't want, now that that's not selectable. It's only an 8 second penalty that happens maybe once a day.

[Angela Kerensky]

You might just have to lower your settings or restart MWO/PC every couple of hours before you actually crash.

The crash penalty for the first time is only 10 seconds and the second one is negligible too. It refreshes every 4 hours I believe. If you are crashing more than that then it's time to find out what's causing it.

[Col Jaime Wolf]

some ideas and thoughts, questions.

is it just a crash to desktop or a hard freeze that requires a system restart?

double check your overclock with a couple runs of 3dmark and some prime95/hyper pi 32mil?

try putting your larger ram modules into channel 1 and the old 6gb modules into channel 2? (assuming you got a 2x2 module arrangement)

run the MWO repair tool?

run a few passes of memtest? maybe one of the new modules has a bad sector or two and you never caught it because no one realistically uses more then 4-8 gb on average. Takes about 5-8 hours to fully test 32gb of ram, longer if you want to be more thorough.

do the ram timings\speed on your old vs new ram differ significantly in any way? the state of mixed ram in a motherboard as of 2015 is far far better than in the past but ive still seen issues from mixing different ram modules.

CPU not overheating from overclock?

PSU is up to the task of handling everything+OC?

all drivers and windows up to date?

just for reference, i do run the game at max settings and with my CPU and video card mildly overclocked. Has not caused me any instability vs before when i had to run at mostly med settings.

as for the disco penalty its just a reality, not much PGI can do to discern someones game crashing vs someone just unplugging the LAN cable from their PC.

Edited by Mellifluer, 07 January 2016 - 08:50 PM.

[Jolly Llama]

With the new voting system, you should be allowed to drop out of a match. I miss the days of being able to play only conquest.

[Ace Selin]

Playing on wireless USB stick often causes me problems, especially if it heats up or lots of people using mobile 3G in the area.
If i disco more than twice i simply quit for the night.

[Euklides]

Mellifluer, on 07 January 2016 - 08:42 PM, said:

some ideas and thoughts, questions.

is it just a crash to desktop or a hard freeze that requires a system restart?

double check your overclock with a couple runs of 3dmark and some prime95/hyper pi 32mil?

try putting your larger ram modules into channel 1 and the old 6gb modules into channel 2? (assuming you got a 2x2 module arrangement)

run the MWO repair tool?

run a few passes of memtest? maybe one of the new modules has a bad sector or two and you never caught it because no one realistically uses more then 4-8 gb on average. Takes about 5-8 hours to fully test 32gb of ram, longer if you want to be more thorough.

do the ram timings\speed on your old vs new ram differ significantly in any way? the state of mixed ram in a motherboard as of 2015 is far far better than in the past but ive still seen issues from mixing different ram modules.

CPU not overheating from overclock?

PSU is up to the task of handling everything+OC?

all drivers and windows up to date?

just for reference, i do run the game at max settings and with my CPU and video card mildly overclocked. Has not caused me any instability vs before when i had to run at mostly med settings.

as for the disco penalty its just a reality, not much PGI can do to discern someones game crashing vs someone just unplugging the LAN cable from their PC.

1. It crashes MWO, not my computer. I then proceed to get a bugreporter prompting me to send a log to PGI.

2. The clock is stable under stress, I've not had any issues(so far) with system instabilities.

3. The ram is in appropriate channels. 3 2gb sticks, and two new 4gb stick is in the appropriate places (leaves one of the tipple channels open).

4. Will try the repair tool, feels like a shot in the dark however.

5. I can try a memtest when I am going to sleep later

6. The older ones are 1333mhz and the newer 1600mhz, not the biggest leap, but as far as I am aware, since they are not occupying the same tripple channels compatibility issues should be slim.

7. cpu runs at 76 degrees when stressed to max, tops at 67 when running mwo, 63 on average. around 45 when idle.
Upon previous research before I overclocked, 77 degrees is the limit upon which instabilities might occur if you go over it. I set it consciously so that it sits at 76 at maximum stress. (The clock is actually 3.9993, but its just easier to say 4 )

8. Its a 850W PSU, can't remember the brand on top of my head, but it can handle the other components, the biggest hog is probably the GTX 780.

9. Yes yes, drivers are up to date!

I thank you for the newbe checklist, brought a smile to my face

I realise that there is a local issue here, simply changing from low to high graphics would have been an issue that got noticed quick if many had them. But that doesn't necessarily mean that this is isolated to me. But you probably know that.


As for the topic of the original post. I do get a crash reporter that sends to PGI, it can be confirmed that I actually crash since I can send it in. Unless some one figures out how to crash the game and force a crash reporter in order to circumvent any potential DC penalty I fail to see the issue(seems to be a rather inconvenient way to dodge a match, but I should probably not question the tenancy of some player).

Edited by Euklides, 07 January 2016 - 09:23 PM.

[Monkey Lover]

Yep its necessary. To many people would quit games during the events because they already had a "map"


The penalties are very minor. If you ever get to the point where it has a 20 minute penalty then you should take a break because people dropping from games really hurts balance.

[Euklides]

Monkey Lover, on 07 January 2016 - 09:26 PM, said:

Yep its necessary. To many people would quit games during the events because they already had a "map"

The penalties are minor that is true, an inconvenience however.
But do you really think that many would force the game to crash in order to get a fake bug reporter? I am not simply talking about unplugging the router or alt-f4:ing the game, you actually have a achieve an error that you then send as a report through the automated bugreporter.
Do you think people except perhaps some really select few would go to these lengths just to avoid a match?
Gotta wonder if that is the case, would it not be more convenient to play the match then? ^^

[Davegt27]

Being punished for something I did not do upsets me very much

A few times my PC was locked up so bad by MWO that even ctrl-alt-del did not work, I had to reboot my PC

When the game locks up that bad an error report is not sent

Yesterday in a pug drop server connection was lost I was thinking no problem PGI's servers went down
When they came back on I get punished again for leaving a game early

I sent an e-mail to support complaining and threatening them
They sent out a long list of things to try and do
They also requested my dxdiag

I sent my dxdiag and the original dxdiag from Jul 2014
I hope there fixes work
Edit: I should also say that in the CW games that crashed I did make it back into game
And fought hard

Only the pug drop did I not make it back into the game

This heavy handed dealing is totally unnecessary look at your stats tell my how one disco is hurting you!

one reason I know is when I first started I had an 100% disco rate on crimson and when I finally found and saw my stats I had a 50/50 win loss rate
I was totally shocked by that

To this day I still have close to 50/50 win loss rate

Edited by Davegt27, 07 January 2016 - 09:47 PM.

[Angela Kerensky]

Ace Selin, on 07 January 2016 - 08:45 PM, said:

Playing on wireless USB stick often causes me problems, especially if it heats up or lots of people using mobile 3G in the area. If i disco more than twice i simply quit for the night.

I use the same but with my mobile phone set as a hotspot for my PC. I also stop for the day if I get the penalty twice.

[Monkey Lover]

Euklides, on 07 January 2016 - 09:34 PM, said:

The penalties are minor that is true, an inconvenience however.
But do you really think that many would force the game to crash in order to get a fake bug reporter? I am not simply talking about unplugging the router or alt-f4:ing the game, you actually have a achieve an error that you then send as a report through the automated bugreporter.
Do you think people except perhaps some really select few would go to these lengths just to avoid a match?
Gotta wonder if that is the case, would it not be more convenient to play the match then? ^^

When they start giving mc out and mechs people do stupid things. Crashing the software isn't hard. For me I could just turn up the frequency on my video card. Some people crash every time they alt tab ha-ha.

This has been a issue before and this is why they added it.