Jump to content

Matchmaker Hangs And Wait Times


289 replies to this topic

#41 Damocles69

    Member

  • PipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 888 posts

Posted 29 April 2014 - 01:04 PM

ggclose

PGI

ggclose

#42 Kaldor

    Member

  • PipPipPipPipPipPipPipPip
  • 1,239 posts
  • LocationWisconsin

Posted 29 April 2014 - 01:10 PM

View PostFunkadelic Mayhem, on 29 April 2014 - 12:43 PM, said:

It got in my dusty run down candy van. You will never see it again. BWHAHAHAHAHA!



Would it be this van?
Posted Image

#43 Rebas Kradd

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,969 posts

Posted 29 April 2014 - 01:10 PM

View PostIIIuminaughty, on 29 April 2014 - 12:41 PM, said:

So you telling me pgi......you hold a public testing and no one seen this coming? no one had these problems we are experiencing today? That or everyone that did the public testing just completely ignored this problem? If it is here now wouldn't it have been a problem in the test servers?


Not necessarily. Nobody seems to understand how internal testing works. There are factors in live environments that just don't exist in test environments.

Instead of just accusing PGI of incompetence, the community needs to learn a thing or two about software development and accept the fact that Bugs Happen™ no matter how hard you test for them. This is an unfortunate one, but give them a few hours and see what they come up with.

#44 Kaldor

    Member

  • PipPipPipPipPipPipPipPip
  • 1,239 posts
  • LocationWisconsin

Posted 29 April 2014 - 01:11 PM

View PostRebas Kradd, on 29 April 2014 - 01:10 PM, said:


Not necessarily. Nobody seems to understand how internal testing works. There are factors in live environments that just don't exist in test environments.

Instead of just accusing PGI of incompetence, the community needs to learn a thing or two about software development and accept the fact that Bugs Happen™ no matter how hard you test for them. This is an unfortunate one, but give them a few hours and see what they come up with.


Yeah, this is true. If PGI had a spotless track record, Id believe that....

#45 Flaming oblivion

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • 1,293 posts

Posted 29 April 2014 - 01:11 PM

Well I was going to log in , Not now 3/3/3/3 was the closest thing to anything I thought could be positive about this game ., I'll be back when you fix it , Sad really I spend huge amounts of cash gaming, Because I enjoy it, its my thing, yet when it comes to MWO for reasons of balance/matchmaking , the whole PuG/premade lark you have managed to get a huge $0 off me, So much potential wasted.

Edited by Flaming oblivion, 29 April 2014 - 01:13 PM.


#46 luigi256

    Member

  • PipPipPipPipPipPipPipPip
  • Overlord
  • Overlord
  • 1,082 posts
  • LocationUnited States

Posted 29 April 2014 - 01:12 PM

I usually don't get to play the game on patch day Tuesday because of life and this is the one instance I am glad for that. Never before has the patch broken the game. I mean LRM buff, ghost heat, AC/jump jet nerf CHANGED the game but never BROKE the game.

Anyways hope they fix it by tomorrow when I actually get a chance to try out the new 3/3/3/3 if it is working properly.

#47 Papaspud

    Member

  • PipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 639 posts
  • LocationIdaho, USA

Posted 29 April 2014 - 01:12 PM

No choice for game modes = fail, I don't like playing skirmish on Terra Therma every round.

#48 Nicholas Carlyle

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Bad Company
  • 5,958 posts
  • LocationMiddletown, DE

Posted 29 April 2014 - 01:12 PM

View PostRebas Kradd, on 29 April 2014 - 01:10 PM, said:


Not necessarily. Nobody seems to understand how internal testing works. There are factors in live environments that just don't exist in test environments.

Instead of just accusing PGI of incompetence, the community needs to learn a thing or two about software development and accept the fact that Bugs Happen™ no matter how hard you test for them. This is an unfortunate one, but give them a few hours and see what they come up with.


Only thing I will say, is PGI should be leaving their Test Server up for longer periods of time, and should be testing builds earlier than 4 days before the patch.

Might have been able to sniff this out before hand.

Not saying bugs won't creep in, they happen. But their testing has been shown to be lacking.

#49 RG Notch

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • 2,987 posts
  • LocationNYC

Posted 29 April 2014 - 01:14 PM

View PostNicholas Carlyle, on 29 April 2014 - 01:12 PM, said:


Only thing I will say, is PGI should be leaving their Test Server up for longer periods of time, and should be testing builds earlier than 4 days before the patch.

Might have been able to sniff this out before hand.

Not saying bugs won't creep in, they happen. But their testing has been shown to be lacking.

Yeah, some people need to learn about software development, some people working at PGI. :lol:

#50 Rebas Kradd

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,969 posts

Posted 29 April 2014 - 01:14 PM

View PostNicholas Carlyle, on 29 April 2014 - 01:12 PM, said:


Only thing I will say, is PGI should be leaving their Test Server up for longer periods of time, and should be testing builds earlier than 4 days before the patch.


I think they extended their testing time to last through the U.S. evening hours.

As far as testing sooner, I agree with you from here, but I'm sure PGI has some heavily technical consideration for not doing so. That's what usually happens. :lol:

#51 MarneusB

    Member

  • PipPipPipPipPip
  • 105 posts

Posted 29 April 2014 - 01:18 PM

"Our quick fix to this issue for the patch was to hard lock the public match queue to ANY. For now, players joining public matches will be unable to select Game Modes." -Nikolai

Perhaps you should be doing more fixing before launch of a complete revamp of your public matchmaking than just a "quick fix", we've all seen how well that's gone so far. So not only are you too lazy to actually check your code before a deployment for something that would break all your user's ability to enter a game, but you're also too lazy to ensure it launches with all the features intact from the previous version.

Seriously, do you guys know how to QA your own code? Since when does a short (and by short I mean VERY short) testing time account for all of the possible errors? Did the overlords holding the whip tell you that it's gotta be launched today or they pull your funding? Or are you just incompetent?

But it's okay, just go back to making gold skins and more paid-for variants, we don't give a crap if the game works either, we'll wait.

#52 RG Notch

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • 2,987 posts
  • LocationNYC

Posted 29 April 2014 - 01:19 PM

View PostNikolai Lubkiewicz, on 29 April 2014 - 01:17 PM, said:


Temporarily. We'll keep you posted on when it returns.

Temporarily like the temporary removal of groups larger than 4, or temporary like the temporary removal of collisions?

#53 Flaming oblivion

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • 1,293 posts

Posted 29 April 2014 - 01:19 PM

View PostNikolai Lubkiewicz, on 29 April 2014 - 01:17 PM, said:


Temporarily. We'll keep you posted on when it returns.


Thanks for the response its annoying though , I thought You'd finally introduced something that would make the game less toxic and repelling to new players (which every game needs)

#54 Rebas Kradd

    Member

  • PipPipPipPipPipPipPipPipPip
  • 2,969 posts

Posted 29 April 2014 - 01:19 PM

View PostMarneusB, on 29 April 2014 - 01:18 PM, said:

"Our quick fix to this issue for the patch was to hard lock the public match queue to ANY. For now, players joining public matches will be unable to select Game Modes." -Nikolai

Perhaps you should be doing more fixing before launch of a complete revamp of your public matchmaking than just a "quick fix", we've all seen how well that's gone so far. So not only are you too lazy to actually check your code before a deployment for something that would break all your user's ability to enter a game, but you're also too lazy to ensure it launches with all the features intact from the previous version.

Seriously, do you guys know how to QA your own code? Since when does a short (and by short I mean VERY short) testing time account for all of the possible errors? Did the overlords holding the whip tell you that it's gotta be launched today or they pull your funding? Or are you just incompetent?

But it's okay, just go back to making gold skins and more paid-for variants, we don't give a crap if the game works either, we'll wait.


While you're merely venting, would you like to consider the fact that they spent an afternoon on the Public Test server to test this patch? And that none of these issues popped up then?

#55 Night Fury76

    Member

  • PipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 300 posts
  • LocationAustralia

Posted 29 April 2014 - 01:20 PM

View PostRebas Kradd, on 29 April 2014 - 01:10 PM, said:


Not necessarily. Nobody seems to understand how internal testing works. There are factors in live environments that just don't exist in test environments.

Instead of just accusing PGI of incompetence, the community needs to learn a thing or two about software development and accept the fact that Bugs Happen™ no matter how hard you test for them. This is an unfortunate one, but give them a few hours and see what they come up with.


ah the old operational is totally different to testing.
Poor programs with no insight, love to hide behind this one.
GG PGI

at least I know the quality of programmers I have to compete with for a job

#56 DirePhoenix

    Member

  • PipPipPipPipPipPipPipPip
  • 1,565 posts
  • Google+: Link
  • Facebook: Link
  • LocationSan Diego

Posted 29 April 2014 - 01:20 PM

View PostRebas Kradd, on 29 April 2014 - 12:59 PM, said:

Only a fraction of the community has tried playing on it so far, so the buckets are probably just as small right now as they were during the Public Test.

As far as tonnage matching, well, this was the cost of it. Longer wait times and possible hangups. Hopefully it's just a bug, but it wouldn't surprise me if tonnage matching turns out to need much more work and time for the matchmaker. You wanted this, just wouldn't accept the cost of it.


I consider myself lucky in that I am usually able to work from home on my own hours, but it always amazes me that there are enough people online from 1-2pm on a Tuesday immediately after a patch drops to have matches at all.

#57 MonkeyCheese

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 3,045 posts
  • LocationBrisbane Australia

Posted 29 April 2014 - 01:20 PM

It's a pity to see that because of problems the matchmaker is set to any game mode. But hopefully this 3/3/3/3 matchmaker gets sorted out eventually as more balanced matches might make me play more and might just make my other friends on Ts who were all closed beta founders with my actually take interest in the game again.

#58 wanderer

    Member

  • PipPipPipPipPipPipPipPipPipPipPip
  • Civil Servant
  • Civil Servant
  • 11,152 posts
  • LocationStomping around in a giant robot, of course.

Posted 29 April 2014 - 01:23 PM

Wow. The launch module crashed on the runway this time, folks. I got in just before the switch, and we had four people "No Pilot" on our team.

Glorious random pub matches for EVERYONE, but at least now we see most people able to play.

#59 MarneusB

    Member

  • PipPipPipPipPip
  • 105 posts

Posted 29 April 2014 - 01:26 PM

View PostRebas Kradd, on 29 April 2014 - 01:19 PM, said:


While you're merely venting, would you like to consider the fact that they spent an afternoon on the Public Test server to test this patch? And that none of these issues popped up then?
A whole afternoon?  My, that's more than enough time to find all the bugs with a new complicated algorithm, whip up a creme broulet, and make it to the Centauri system and back.  Why didn't I think that a whole afternoon spent on bug testing by a tiny fraction of the playerbase couldn't fix the issue?My biggest beef right now is the fact that they're launching a new way to play the game, forcing the whole active playerbase to use it as an actual test, and not calling it a test.  Feeding us crap and calling it lobster doesn't make it taste any better.PGI, tell us you're using your entire playerbase as a testing environment because you don't have enough players willing to test your game, and maybe less people would be upset.That still doesn't change the fact that its broken as all hell.Edit: and apparently now your forums are broke, I can't seem to format my post properly.  Nice.

Edited by MarneusB, 29 April 2014 - 01:30 PM.


#60 Flaming oblivion

    Member

  • PipPipPipPipPipPipPipPip
  • The 1 Percent
  • 1,293 posts

Posted 29 April 2014 - 01:28 PM

What sort of time base are we talking here for a fix , I'm not going to hold you to it , Best guess ? hours, days, weeks?





18 user(s) are reading this topic

0 members, 18 guests, 0 anonymous users