18 replies to this topic

[TLBFestus]

Anyone else experiencing a lot of DC's with this event?

I never intentionally leave a match until after I am dead, but in a little over 2 hours tonight I've had 4-5 DC's.

None intentional, but I'm accruing penalties for my unintentional DCs.

Anyone with more knowledge than I know if there is anyway on PGIs part that they can fine tune the punishment system to minimize getting nailed for accidental DCs?

[Mech Jager]

Even if it appears to be none of your fault, it still may be in part due to your home network or providers network.

I assume PGI has done this make folks with non-reliable systems (or just who hate the map/team) share the pain that was caused to the group of teammates who just played with a man down.

I personally have found that when it is PGI's servers the punishment time frame is less than the other issues caused just by getting back into game. If you are getting dropped reset your router, check with your network provider and/or do a Google search for your area and provider name with gaming attached. These items have always resolved the problem for me or MWO just goes offline for a bit and they post a notice and it gets taken care of.

FYI Weekends and events tend to putter a higher strain on the servers, so hidden issues with your connection may now surface on PGI's end because the servers do not have enough hamsters to spin though it. Fill out a report so that they can know what you have on your end and hopefully be able to work towards a solution.

[Davegt27]

I have had my PC in TX and now in CO and I still have problems

They sent me this

Quote

When you get a moment, please run through any or all of the troubleshooting steps outlined below and let us know if the issue persists.
Try to determine if any Firewall or Anti-Virus software might be preventing a stable connection:
- Temporarily disable your Windows Firewall or any 3rd-party firewall software and attempt a connection
- Temporarily disable your anti-virus software and attempt a connection
- If you are able to establish a connection after disabling any of the above software, you will need to add a profile or filter for MWO in that software to allow a stable connection to go through
Try to determine if your router or modem setup might be contributing to the issue:
- If you are connecting to your modem or router through Wi-Fi, please attempt a direct connection with an Ethernet cable and see if the issue persists
- Try opening the following ports in your router and see if the issue persists:
TCP 45461
TCP 45464
Release and Renew your IP and flush your DNS:
1. Press Windows key + R to open the Run window.
2. Type cmd and hit Enter.
3. In the command prompt window, type:
4. ipconfig /release and hit Enter.
5. ipconfig /renew and hit Enter.
6. ipconfig /flushdns and hit Enter.
Change your DNS settings:
Using the information provided either by OpenDNS (http://208.69.38.205/) or Google (https://developers.g...-dns/docs/using) please apply either of these DNS settings to your system.
Using either of those custom DNS providers is generally preferred over the standard DNS servers your ISP might currently use.
If you still cannot connect after running through these steps, please provide the results of a trace route, ping test, and DirectX Diagnostic, along with a copy of the Omicron.log located in your \MechWarrior Online root folder.
Trace Route:
- Press Windows Key + R
- Type CMD
- Click OK
- In the Command Prompt, type: tracert 192.99.109.129
- Take a screenshot of the results and attach it to your reply.
- In the Command Prompt, type: tracert 192.99.40.103
- Take a screenshot of the results and attach it to your reply.
Ping test:
- Press Windows Key + R
- Type CMD
- Click OK
- In the Command Prompt, type: ping -n 100 192.99.109.129
- Take a screenshot of the results attach it to your reply.
- In the Command Prompt, type: ping -n 192.99.40.103
- Take a screenshot of the results and attach it to your reply.
How to obtain and attach a DxDiag
- Press Windows Key + R
- Type DxDiag
- Click Save All Information. If prompted about WHQL drivers, click no.
- If the Save All Information button is not present, simply click on Run (32/64 bit)DxDiag. The Save All Information button will appear after the diagnostic.
- Log file location: C:\Program Files (x86)\Piranha Games\MechWarrior Online\Bin32\PatcherLogs
- Attach the file to this support ticket. Please do not copy/paste the contents in the body of your message as it will get truncated.
Regards,

My problem was so bad my PC would lock up and I would have to turn it off
I went in and set my video settings to min (except for resolution) and I think that solved the PC lock up problem

I still get some DC's but far less frequent

HTHs

[Davegt27]

After all that I was still getting discos
They sent me this yesterday

Quote

Could you please also back up your C:\Users\<username>\Saved Games\MechWarrior Online folder somewhere safe and then delete it?
- Shut down the MWO client
- Bring up your Start Menu
- Search for and run Internet Options
- Click the Advanced tab
- Click the 'Reset...' button
- In the next window, click the Reset button
- Attempt to launch MWO
If the issue still persists after running above steps, please try following next instructions:
- Open Internet Explorer
- Hit the Alt key to bring up your File, Edit, etc toolbar
- Click File
- Check Work Offline
- Click File again
- Uncheck Work Offline
- Close IE
- Launch MWO and attempt a log-in
Please let me know if issue persists and send me
- your location
- your ISP
- Whether you use wifi or wired connection
Regards,

The first part I tried (you will have to go in a reset all your weapons groups)
And I just had a match where I and others could not get into the match
So I will try the 2nd part

[Troutmonkey]

There's no technical way to tell the difference between a crash / unintentional DC and an intentional timeout. The system is intended to catch rage quitters / people who leave matches to pick different mechs, It's a side affect that's it catches those with legitimate problems

[Valkyrie73]

whenever there is an event on I experience DC's but I don't normally? I don't know why this is

[Tripzter]

My buddys been having this problem. Probably gotten kicked 8-10 times in the recent 5 hours we've played. His connection is stable.

[Mech Jager]

If you are Dcing Frequently it is on your end.

Do you run wireless - If yes that means you share 6 different radio channels that other folks within your range can jump on and interfer, never use a wireless connection and game (I applaud if PGI says your bad and gives you a penalty for DC)

Do you have applications running in the background - If yes, turn them off. If you do not know what I am talking about , I applaud if PGI says your bad and gives you a penalty for DC - then do a google.

I understand that different folks may only have access to lower end connections and/or machines, but if they cause issues for the larger populations on a regular basis (more than 1 per night) then they should also have a penalty to reflect the pain they cause to the folks they are teaming with.

The penalty is a motivator for folks not to leave a game or to take responsibility for their own equipment. IE It is your job to get mid range or higher connections and/or computers. It is not the Job of PGI or teammates to be hindered by the lowest common denominator or to try to provide answers for a problem they are not responsible for.

PGI has had issues in the past, but on the worst night over the last 1.5 years I have never had more than 2 Dcs per night (only 2 times) with a 6 year old AMD computer on a grandfathered low end plan from comcast. I have a new $800 dollar intel with a low end dsl plan, and I have 1 DC every other month, maybe.

[LordNothing]

i just had a false punishment because the game locked up my rig and i had to reboot (should point out that no other game or software does this, mwo locks, crashes video drivers, and is generally not very well behaved). i got back into the game and got 2 kills. still get penalized for it. fix your crap pgi.

[Davegt27]

I have had up to 6 disconnects in one match

But this happened last night


After several minutes watching the loading I canceled and then rejoined and still did over 700 dmg

Put I still got penalized on the next match



At one time I got discos' only when I fought the Clans in CW
At another time I would disco when my Huggin go near a generator

When I started I had 100% disco rate (cry engine failure) on Crimson Straight (worked fine on the testing ground)

[1Grimbane]

pgi should remove the DC penalty... it's an over reach and penalizes unintentional dc's very nanny-state ish of them

[DAYLEET]

My locust grew fat yesterday, i got 2 dc 1 match and many single dc kill. But yeah as a whole there have been a lot more dc than usual and only once has one reconnected after i killed him.

[Herodes]

I do find the concept of this "penalty" funny. Nothing is going to stop me from terminating a match that I do not want to go through with. The only thing a penalty changes is that the players penalized for whatever reason they disconnected for will do something else with their time and stop playing for the day. As if one had nothing else to do and would cry rivers for not being allowed to play a video game.
After all, if a game is that bad that it makes me want to disconnect and then adds a penalty for that I have to ask myself on which end the problem is located.
Either way ... let's hope we won't need to disconnect willingly that often and let's mourn for the folks that get penalized for their computers or networks failures. Funny concept.

[LordNothing]

at the very least they need to remove the time out on returning. any return to game should immediately void the penalty.

[TLBFestus]

Just for clarity, I hardly EVER disconnect.

But yesterday it happened about 6 times in rapid succession. Most likely on my end, but the annoying part is getting punished for "intentionally" DCing for stuff like that.

I doubt that there is anything they can do about it, no method to determine the difference between accidental and deliberate. Just blowing off some steam because it was very frustrating to bust my arse to get back in only to find I'd been given a "time out" because the match must have ended before I could rejoin.

[Fryepod]

^ Pretty much sums it up. Cant tell if discos are intentional/ non intentional. Not too much to be done. Understand the steam on that.

[LordNothing]

possible yes, but pgi doesnt have any programmers (yes im doing it again, i keep seeing them do things that unpaid modders could do better).

the game has to handle a termination command. alt+f4 for example has to be handled by the game, to free up memory, relinquish control of other resources, close file handles, shut down networking. before the game closes its connections it could send a packet to rat you out for the intentional disconnect. in case of a failure of the network or the game crashing, such a packet would never be sent.

there would be a few edge cases. like ive seen one failure mode where the game keeps running but rendering is all screwed up, you can still exit the way of the rage quitter and restart properly (usually needs a complete restart and not just a reload of the client). but simply checking to see if you return from the game would prove that you were innocent. thats why you extend the 2 minute time out because sometimes you just cant get going that fast. considering how long it takes the game to start up and how long it takes to connect after you log in. it takes less time to reboot my computer thanks to my ssd, but then it sits and waits for pgi to accept the login request, then you have to wait for that damn popup. then you have to rejoin which sometimes doesnt work. also someone looking to bail on what seems like an unfruitful game to save time isnt going to try to rejoin at all.

[TLBFestus]

Still weird......while I accept that my DCs are more related to an ISP problem on my end, it still doesn't explain what happened to me tonight.

Getting a DC about every 6th match or so at this point. Everything else I use internets wise isn't making a peep.

Then, my last DC I log back in, rejoin only in time to see I've been killed and we were down and losing rapidly. No problemo. I play another match in a different mech, and it lasts 6-8 minutes.

Finish that match and I go to pick another mech and a match and I get a penalty warning that I had 12 seconds left before I could join another match.

WTF? I DC'ed and rejoined, then played another match, THEN next try I'm serving a time out? That's weird and it ain't my internets.

[Brandarr Gunnarson]

I get DC in bursts. Sometimes the game will have no issues all day. Other days I can't hardly connect at all.

Nothing is wrong with my computer or my connection, per se; but, I'm sure this has to do with routing and packet loss.

I can add that since switching to Akamai (I have nothing against this company, just stating a noted change), the hops in my Tracert have incrased by 3. That's not helping.

My DCs are never intentional.

I do understand that some kind of discouragement has to be used to prevent people from just quiting whatever map they don't like.

BUT, when last Saturday (over the Champion 3 event) my penalty went to 20 minutes I thought it was ridiculous.

Can we at least put a cap on how long the penalty is? Say 8 minutes or even 10? That would be more reasonable.