52 replies to this topic

[noleet]

I am really sick of [these things]. This bug existed since early beta and still not fixed at all. What [redacted] are you doing PGI?

Cheers

Edited by Andi Nagasia, 09 January 2017 - 09:56 AM.
Launguage, you know better,

[Y E O N N E]

Holy Magikarp, I haven't seen that error box since early 2015...

[RestosIII]

"That goddamned crash bug"

Bit vague, don't you think? Mind explaining what happened when it crashed, if you can reliably recreate it, what your specs and settings are, etc. by any chance?

[Spheroid]

I get that every five or six games. Does the crash log contain anything that actually shows what causes the error? Is is a DX error, is it a bad asset, etc.

I have clean a Windows 10 install, latest stable Nvida drivers and nothing running in the background. There is literally no excuse for this. 2017 needs to be the year of bug fixing.

Edited by Spheroid, 03 January 2017 - 09:38 PM.

[RestosIII]

Spheroid, on 03 January 2017 - 09:38 PM, said:

2017 needs to be the year of bug fixing.

And optimization and quality of life improvements like HTAL+colorblind support. And Clan Diamond Shark. Those are my goals for 2017 for PGI.

[NighthawK1337]

I get this crash quite frequently. I always hit send report but still not fixed. It started around October last year, It always crashes just at the start of the match.

[NRP]

I get it every few games as well. I think it's some kind of DX error. I can trigger it by ALT+TABing between the game client and a web browser (Microsoft Edge). I'm running Win 10 with an NVidia GTX 960.

[noleet]

RestosIII, on 03 January 2017 - 09:36 PM, said:

"That goddamned crash bug"

Bit vague, don't you think? Mind explaining what happened when it crashed, if you can reliably recreate it, what your specs and settings are, etc. by any chance?

sending every time PGI the crash report. nothing ever happens. really annoying by now.

[charov]

Never seen this crash. Actually, MWO crashed maybe a couple times since I started playing in closed beta. Have you done the usual checks (game cache, drivers, OS updates, etc)?

[Escef]

I've found that running in "full windowed" mode (not windowed or full screen) does wonders.

[Y E O N N E]

Escef, on 03 January 2017 - 10:25 PM, said:

I've found that running in "full windowed" mode (not windowed or full screen) does wonders.

This. Don't run full-screen.

[El Bandito]

Spheroid, on 03 January 2017 - 09:38 PM, said:

I get that every five or six games. Does the crash log contain anything that actually shows what causes the error? Is is a DX error, is it a bad asset, etc.

I have clean a Windows 10 install, latest stable Nvida drivers and nothing running in the background. There is literally no excuse for this. 2017 needs to be the year of bug fixing.

Spheroid, on 03 January 2017 - 09:38 PM, said:

I have clean a Windows 10 install

Spheroid, on 03 January 2017 - 09:38 PM, said:

Windows 10

I do not trust Windows 10.

NRP, on 03 January 2017 - 09:53 PM, said:

I get it every few games as well. I think it's some kind of DX error. I can trigger it by ALT+TABing between the game client and a web browser (Microsoft Edge). I'm running Win 10 with an NVidia GTX 960.

As the others said before me, run with full windowed mode. Fullscreen is crap, if you alt+tab a lot.

Edited by El Bandito, 04 January 2017 - 12:34 AM.

[Cion]

dude, in the spirit of helping your problem...i'd suggest send an email to support explaining, politely, your frustration. Maybe even tweet Russ to let him know you have been having this problem for years and that you emailed support. Being polite does wonders, even if it's politely frustrated.

(so, should you "have to do all that" to get a bug fixed? probably not. Should PGI devote an engineer to fix a bug that most people have not seen in ages? probably not. but both of you could bend a bit )


good luck

[Bandilly]

I think I've crashed maybe once or twice in 4 months, definitely not a common problem.

[Weaselball]

El Bandito, on 04 January 2017 - 12:33 AM, said:

I do not trust Windows 10.

*shrug* Clean install of Win 10 here, I have never once seen that error box in my life. Never once got it either on my Win7 machine either. Been playing since the days of closed beta.

[El Bandito]

Weaselball, on 04 January 2017 - 08:40 AM, said:

*shrug* Clean install of Win 10 here, I have never once seen that error box in my life. Never once got it either on my Win7 machine either. Been playing since the days of closed beta.

Saying "clean install of Windows 10", is the same as saying "clean install of donkey poo", in my book.

Anyway, try to run MWO with full window mode, as others have suggested.

Edited by El Bandito, 04 January 2017 - 08:46 AM.

[Almond Brown]

Use the File Cleaner/Scrubber/Checker if that is happening often instead of swearing like a child.

[Chavette]

RestosIII, on 03 January 2017 - 09:40 PM, said:

And optimization and quality of life improvements like HTAL+colorblind support. And Clan Diamond Shark. Those are my goals for 2017 for PGI.

You don't get to command a milliary vehicle IRL if you're colorblind, so why should you be able to do it in game?

[RestosIII]

Chavette, on 04 January 2017 - 09:40 AM, said:

You don't get to command a milliary vehicle IRL if you're colorblind, so why should you be able to do it in game?

On the tiny chance you're being serious, **** you.

[C E Dwyer]

Found it varied from patch to patch, I had periods where I'd not crash in months, and was doing what, people here are doing which is slam the O.P, other patches it would crash every third game, whether I alt/tabbed or not.

Win7/10 didn't improve it, from personal experience I found full screen better than full windowed.

Alt/ Tabbing is the main culprit, but it's not the whole reason for it, and while ranting isn't very classy, it's endless frustration with a four year old product, that causes them