OP, sh|t happens. It sucks but that's the way it is to deter anyone from purposely disconnecting. Just try to fix it on your end and hope it doesn't happen again.
To everyone giving the OP crap about his "network" problems... As I said to the OP, sh|t happens. I've had a number of routers and each of them have had an issue that requires a power on/off. I've had the same thing on the PC side. Networking has been one of the most fickle things I've ever worked on just because it won't work and then just by a restart it all of a sudden does with no settings being changed.
You all need to lighten up some. Heaven forbid OP is a little frustrated for being penalized for something he didn't intentionally do.


Getting Punished For Being Disconnected
Started by Squarebasher, Apr 04 2016 12:08 PM
22 replies to this topic
#21
Posted 05 April 2016 - 06:29 AM
#22
Posted 05 April 2016 - 06:33 AM
LordNothing, on 04 April 2016 - 03:55 PM, said:
the thing that gets me is video driver crashes. no other game does this, its strictly a pgi thing. its the kind of glitch that you have to reboot from. its a 750ti, so its not the fastest card in the shed, but it gives me a solid 60fps at modest settings. you would think with that nvidia splash screen at the start of the game would mean that i got the right stuff. nope. i might be able to blame nvidia for this, maybe, maybe crytek. pgi probibly doesn't have low enough level access to the closed source blob to fix the bug. but what pgi can do is not blame me for what for them should be a common issue. then again, frequency is low enough i can just shrug off the few seconds (which given the amount of time it takes to get back in game is minuscule in comparison). so perhaps its not worth it for pgi to do anything.
if they do, i would like the time allotted to rejoin to be slightly longer. ive had games where i had to reboot, got back in, got 4 kills and top damage, won the game for my team, and then had to wait 20 seconds for my next one.
if they do, i would like the time allotted to rejoin to be slightly longer. ive had games where i had to reboot, got back in, got 4 kills and top damage, won the game for my team, and then had to wait 20 seconds for my next one.
I get the video driver crashes as well, and you're exactly right - no other game crashes like MWO. I'm running a GTX 980 btw. I've read people saying it's nVidia's drivers... That may be, but like LordNothing said - no other game with this issue. Matter a fact I can't remember the last time I've had such a problem that I actually expect to crash at least once every time I decide to play the game.
#23
Posted 05 April 2016 - 06:51 AM
Astrocanis, on 05 April 2016 - 04:23 AM, said:
Of course you are representative of everyone, so I agree completely. Since you have only crashed once in 750 games, I must not have crashed 5 or 6 times over the weekend. And if I did, it HAS to be my fault because only I can control the interaction between my CPU and the PCIE slot and the associated drivers. Drivers which are provided by the hardware manufacturer. Which is the one sponsoring this game.
I still play. But it's annoying as hell and seems to happen sporadically. What I find especially telling is that MWO is the ONLY game I experience this problem with. Still, I agree, it's our own faults.
average users cant control much really. me, i have lots of experience in pc building, maintenance, and a networking degree, and some programming, engineering, and game dev hobbies on the side. with all this under my belt i still dont know how to fix my crashes other than throwing more money at the rig (and from my experience that doesn't work either, the cutting edge is where all the bugs lurk). but you run through the troubleshooting process and eventually find the issue.
you buy a nvidia card, plug it into a mobo that is rated to handle that pcie version, you put in ram according to the qvl. stick an i7 in there, also on the mobo's qvl. you run a power supply calculator and choose a supply rated 200-300 watts higher than what you actually need (they lie!). you install code blob after code blob, os, drivers, software. prune services and auto starts, update all the things, secure everything. ive built thousands of machines commercially, done tech support, and ive seen and fixed every possible computer problem.
you buy a router many times more expensive than what you actually need and pay off the isp huge sums for mediocre connections (and for many people where you live dictates the quality of connections, asking people to move because the game crashes is kind of overkill). i have installed many networks and can get the router to do exactly what i want it to do. then you run a tight ship and one game gives you crashes (all other games run stable, even ones much more demanding than mwo). you start to run out of things to point fingers at.
what you are left with is a beta game engine that is hellishly out of date, a developer known for its corner cutting, and server side glitches completely out of your control. perhaps the potato is in the data center and not on my desk. sure its our own faults, for installing mwo in the first place.
Edited by LordNothing, 05 April 2016 - 07:07 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users