37 replies to this topic

[Death Mallet]

Tesunie, on 02 August 2014 - 08:13 AM, said:

Exactly. When I do have this problem when in a group, my mech is "in a match" longer than my lancemates when they return from their matches. They have to wait upwards of a full minute (sometimes, I haven't actually timed it though) before we as a group can launch again, typically only to have them launch without me.
(I've just been blaming my techs for pushing my mech out the mechbay doors without me. They must think it's funny or something. )

It does appear my problem is similar to Deathmallet's, but is intermittent. For me, it seems worse when I'm in a group, but still happens "frequently" when I'm solo, but I am at least still able to play matches most times. It might be weight class specific from what I'm reading, as it seems to happen when Death is trying to queue in with a heavy clan mech, and for me mostly when I'm trying to go with my Jagermech A (another heavy mech).



I'd listen to Ironwithin. Check your match selections. I don't know what happens when you have everything deselected and then try to find a match...

I'd also try to get one of your non-heavy mechs functional and test if it's weight class related. It might be MM messing up finding matches for a heavy mech when the heavy mech queue is larger than anything else. It's worth a try, right?

I'd also suggest going into "customize" with your mechs you are trying to play with, and change something, and resave them. Maybe clear out all modules, save, and replace all your modules? While PGI tries to solve this, doesn't hurt tot try stuff on your end as well, right?

I only have Heavy and Assault mechs. All I've tried so far is Assault. Maybe I'll try a heavy. But I really don't think it has to do with queue busyness since its instantaneous.

Checked my match selections. All selected. De-selected them all and reselected them. No change.

Sent the omicron file and the contents of this thread to support.

[Neema Teymory]

Death Mallet,

Thanks for providing your log file. I tracked it down through our support system and took a look. It confirms my suspicion. There is a problem when queuing you up with the matchmaker. This isn't a connectivity issue.

Unfortunately, the log file itself isn't verbose enough to point out the exact problem; however, this gives me a really good starting point. I will do some investigating today. Stay tuned.

If anyone else who is experiencing this issue has uploaded their log files through our support ticket system, let me know, and I will take a look at them as well, to confirm that the issues are all the same.

[Neema Teymory]

Thanks to help of Death Mallet, I was able to track down the issue.

The problem is related to user ELO, which is why some people are experiencing the problem and others aren't.

If you are having trouble launching with a specific weight class, try another. It's very likely you will be able to launch (but not guaranteed)

I'm preparing a fix right now. At the very latest it will be applied with this coming Tuesday's patch (Aug. 5th). I will see if we can somehow get a hot fix out even sooner for this weekend.

I will provide another update as soon as I know more.

[Neema Teymory]

Hey everyone,

You might have noticed that there was a momentary downtime a couple minutes ago. We have hot fixed this issue, so please let me know if you are able to launch into matches again.

[Ryvucz]

Neema Teymory, on 02 August 2014 - 12:55 PM, said:

Hey everyone,

You might have noticed that there was a momentary downtime a couple minutes ago. We have hot fixed this issue, so please let me know if you are able to launch into matches again.

I should report you for speed hax.

Thanks for the fast hotfix!

[Gilgamesh Drakenor]

Neema Teymory, on 02 August 2014 - 12:55 PM, said:

Hey everyone,

You might have noticed that there was a momentary downtime a couple minutes ago. We have hot fixed this issue, so please let me know if you are able to launch into matches again.

I am once again able to play with Heavy mechs. Many thanks.

[Neema Teymory]

Gilgamesh Drakenor, on 02 August 2014 - 02:10 PM, said:

I am once again able to play with Heavy mechs. Many thanks.

No problem, and thank you for confirming the fix.

Tesunie,

This hotfix will likely not improve the "Disconnected from game server" error message. However, as I mentioned earlier, we are working on some improvements to game server bandwidth usage that should hopefully mitigate this problem. If you notice any other patterns in your disconnections, let me know.

On a more general note, unfortunately I usually don't have time to browse the forums, so I'll often miss threads like this unless someone specifically points them out to me. So, and this goes for anyone, feel free to PM me to ensure I'm getting visibility on your issue.

[RazorbeastFXK3]

Lately it seems I get CTD'd when the splash screen comes up for Terra Therma battles. Latest one was a Skirmish sortie where I'd get a message that says "Memory Allocation error" with a bunch of numbers after it. When it first started happening, I'd restart the game and it'd tell me 'Disconnected from game server' but my mech would still be in play.

When it happened earlier today I managed to rejoin the battle without problems. Hopefully a solution is found for it 'cause it's just annoying when it happens.

Neema Teymory, on 01 August 2014 - 03:09 PM, said:

We are currently aware that the server sends a larger than normal burst of data when first connecting to a match, and it's possible that this could lead to problems with lower bandwidth connections.

We are still investigating, so any more specific details you can provide, including your connection quality, would be helpful.

[Death Mallet]

Hotfix worked!

Loving the new Awesome. Finally!

[Tesunie]

Neema Teymory, on 02 August 2014 - 02:35 PM, said:

Tesunie,

This hotfix will likely not improve the "Disconnected from game server" error message. However, as I mentioned earlier, we are working on some improvements to game server bandwidth usage that should hopefully mitigate this problem. If you notice any other patterns in your disconnections, let me know.

Confirmed a few moments ago. It seems to hit on the first couple of matches I try to join into for the day, and then random afterwards. I haven't submitted a report to support yet as I don't know what would help, as it's so random. Still observing the patterns (if it has any) and what else I'm doing on my computer at the time.

This morning, I made sure to keep track of some of it. I have my Firefox open, but no pages were refreshing (I always play the game with FF open, hasn't been a problem before). I made sure to have as little internet activity as possible running when a game is in session/about to be in session.
- I waited with the black screen long enough for my Screen Saver to kick in (that's 5 minutes of inactivity), so it was probably close to 7 minutes before I was sent back to mechlab with the "disconnected from server" message.
- I was once again trying to jump into a match with my Jagermech 6-A when the error occurred.
- Though I can't confirm my ping at this exact moment, my normal ping hovers around 31.

Last time I submitted a ticket about being randomly DCed from matches (would be randomly sent to mechlab in the middle of a match without me prompting any such action and the game not saying any error messages when it sent me to mechlab), I was told to provide a lot of information I didn't know how to provide.

If you want me to submit a ticket about the issue I've been mentioning in this thread, I can with my omicron if you think it will help. Otherwise, I'll continue to try and keep an eye on it and see if I notice any pattern and try to update in this thread. I don't think it's on my end, but I wont disregard the possibility of it either.

[Tesunie]

Not trying the rejoin feature, as it has never seemed to work before with this issue, and says the same error message again.
(I will note that heavy queue is at 40%.)

Second try with the 6-A.
1 minute of searching.
Less than 1 minute of "river city" splash/load screen.
And 2 minutes of black screen before being sent to mechlab.
"Disconnected from game server" message appears.
Mech is "In game"

Third try will be with my Jagermech 6-S now.
20-30 seconds of search
20-30 seconds of Crimson Straight splash
2 minutes and 20-30 seconds of black screen before being sent to mechlab
"Disconnected from game server" message
Mech is "In Game"

Fourth try will be with my Battlemaster 1G. (Assault is at 38%)
1minute 30 Seconds of searching for match
20 Seconds of Crimson Splash screen
1minute 30 seconds of black loading screen
Got into game successfully. Ping was at 29 when I checked.

(I'll post more.)

[Tesunie]

Fifth try with the 6-A.
1 minute of searching.
10 seconds of "Caustic" splash/load screen.
1 minutes 30 seconds of black screen
Loaded into the match, with a ping of 29 again.
However, only 4 teammates appeared on my minimap/hud with an IFF indicator over them for probably the first 30 seconds of the match. (Been a common thing as of late for me.)

Sixth try with the 6-A. (I'm leveling the mech up! Don't look at me like that!)
15 seconds of searching.
10 seconds of "Canyon" splash/load screen.
3 minutes 30 seconds of black screen
"Disconnected from game server" message appears.
Mech is "In game"

I'll try another heavy mech (see if it's my heavy class). Dragon 1N.
3 minutes of searching.
15 seconds of "Caustic" splash/load screen.
1 minute 30 seconds of black screen
Loaded into a match already in progress.
only 4 friendly mechs had IFF again.
Ping was 30.

Grabbing my Griffin 3M for the next match, as a medium should be in more demand.
10 seconds of searching.
15 seconds of "river city night" splash/load screen.
2 minutes 15 seconds of black screen
"Disconnected from game sever" message
Mech is "in game"



Wow. This is the most I've seen this happen (unless I'm grouped). Looks like it isn't weight class specific either.

[Tesunie]

Computer specs (as it might have something to do with this):
Windows 8.1
AMD A10-6700APU with Radeon HD Graphics 3.70 GHz
64-bit Operating System. 64x-based Processor
8 GB of ram

And I have installed a separate video card I run off of:
R6770 Core Edition
1 GB GDDR5
PCI Express 2.1
Single screen attached to the card (it has the option of up to 3)

Latest drivers as far as I know...

[Neema Teymory]

Tesunie, on 04 August 2014 - 08:14 AM, said:

If you want me to submit a ticket about the issue I've been mentioning in this thread, I can with my omicron if you think it will help.

If you don't mind doing this, yes, it would be helpful to see your Omicron.log files after experiencing one of these disconnects. When creating the ticket, you can mention specifically that I asked to see your Omicron.log files. Let me know once you have created it, so I can look it up in our system.

Also, thanks for all the extra details. I'm getting a better sense of when your problem occurs now. That black screen you see after the loading splash screen is actually "normal", for lack of a better word; however, its only supposed to last several seconds. During this time, your client is getting all kinds of information about the other players in the match, your pilot is being bound to his mech, etc. This is that time when you would be receiving that larger than normal burst of data from the server I mentioned earlier.

Having the screen for 5 minutes or longer is very strange. Your specs seem good. Can you also provide the type of internet connection you have? Wired/wireless? Up/down speed? Is it a connection you share with others, on wifi for example? if you aren't too sure about your connection speed, there are websites out there that you can use to get a rough idea. If you do a search for something like "internet speed test", you should get many relevant results. If you happen to do a test like this, make sure you choose Toronto, Canada, or something as close as possible to this location to get a more relevant result, as this is where our game servers are located.

[Tesunie]

Neema Teymory, on 04 August 2014 - 09:56 AM, said:

If you don't mind doing this, yes, it would be helpful to see your Omicron.log files after experiencing one of these disconnects. When creating the ticket, you can mention specifically that I asked to see your Omicron.log files. Let me know once you have created it, so I can look it up in our system.

Done. Sent in. I didn't know too much what I was looking at for data, but I don't think my up/downloading speeds looked good despite my low ping... But, I'm not a software person.

[Neema Teymory]

Tesunie, on 04 August 2014 - 10:48 AM, said:

Done. Sent in. I didn't know too much what I was looking at for data, but I don't think my up/downloading speeds looked good despite my low ping... But, I'm not a software person.

Thank you Tesunie, I'm looking into your log file now. Are you willing to share what your upload and download speeds were?

[Neema Teymory]

Tesunie,

I had a chance to do some investigating and thanks to your log file I found the problem. I'm working on a fix now; however, I must stress that this fix won't necessarily address the very long black screen you are experiencing. From what I can tell so far, this still appears to be a bandwidth related issue, and so will improve once we get some bandwidth optimization changes complete (hopefully the next patch).

What this fix should do is allow you to actually enter the match after this long black screen. It should also fix rejoining for these situations as well, in case you can't get in for some other reason.

We just did our Tuesday patch, so unfortunately I didn't make it in time for that, but I'll look into making a hotfix happen for this issue as soon as the fix is complete. It seems likely that this problem is affecting a large number of users.

I will post to this thread again when I have an update.

[Neema Teymory]

We are in fact hot fixing this issue today. The official post is here: http://mwomercs.com/...06-august-2014/