

#1
Posted 29 January 2015 - 08:48 PM
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.
#2
Posted 29 January 2015 - 08:50 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.
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.
Edited by Prosperity Park, 29 January 2015 - 08:51 PM.
#3
Posted 29 January 2015 - 08:55 PM
#5
Posted 29 January 2015 - 09:03 PM
Are you running the x64-bit client or the 32-bit?
DirectX-9 or 11.
Have you run the repair tool?
Me personally, I was getting crashes on certain maps too using the 64 bit client, had to switch back.
I see this constantly, at least 1 guy every other game I'm in gets disconnected right at the start, then rejoins to find his team has moved to the other side of the map, and they just get murdered by a swarm of lights or w/e depending on the map.
Gotta be frustrating.
#6
Posted 29 January 2015 - 09:09 PM
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.
#7
Posted 29 January 2015 - 09:11 PM
Levi Porphyrogenitus, on 29 January 2015 - 09:09 PM, said:
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.
It's the Shaders folder in your user profile folder... but I think when you run the repair tool it does that for you
#8
Posted 29 January 2015 - 09:18 PM
Not sure if that will help you, but it helps me.
#9
Posted 29 January 2015 - 09:22 PM
Thermal or NV will shorten the view depth significantly. Probably dropping graphics settings will do the same thing. Be something to test if you could be bothered.
#10
Posted 29 January 2015 - 09:22 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.
alternatively you could email support yourself about the issue and try to get it resolved.
you know...like an adult.
#11
Posted 29 January 2015 - 09:23 PM
Edited by Yasuoka, 29 January 2015 - 09:24 PM.
#12
Posted 29 January 2015 - 10:23 PM
Prosperity Park, on 29 January 2015 - 08:50 PM, said:
Oh, I LIKE the map. I think it's one of PGI's best maps! I'd love to play it more often.
But the fact I keep getting DCed is causing me to waste precious Premium Time that could be better spent on another map that does NOT crash most of the time.
And just to make fun of the eventual obligatory idiot who doesn't read this far down and asks "If you care about Premium Time, why are you on the forum instead of playing?", I am actually playing the game right now; I typed this message out while waiting in the queue(s).
White Bear 84, on 29 January 2015 - 09:02 PM, said:

I'm only going to send one ticket once. PGI tends to take notice of mass uproars more than a handful of issues here and there.

Mister D, on 29 January 2015 - 09:03 PM, said:
Are you running the x64-bit client or the 32-bit?
DirectX-9 or 11.
Have you run the repair tool?
I'm on 64-bit client on DX9 on Medium settings. I'll try running the repair tool, but from what others say below, it doesn't sound like it will help.
Mister D, on 29 January 2015 - 09:03 PM, said:
Yeah, that's the CryEngine for you. Every time I attempted to run Crysis on 64-bit DX10 it would crash after 20 - 30 minutes.
Kilo 40, on 29 January 2015 - 09:22 PM, said:
you know...like an adult.
Calm down, dude, it was only a joke.
#13
Posted 29 January 2015 - 10:27 PM
#15
Posted 29 January 2015 - 11:50 PM

Edited by CocoaJin, 29 January 2015 - 11:51 PM.
#16
Posted 29 January 2015 - 11:51 PM
#17
Posted 30 January 2015 - 12:12 AM
#18
Posted 30 January 2015 - 12:19 AM
I would say PGI needs to sort this stuff out, but I'm not sure they have the technical ability.
#19
Posted 30 January 2015 - 12:20 AM
Edited by Kahadras, 30 January 2015 - 12:20 AM.
#20
Posted 30 January 2015 - 12:45 AM

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users