Jump to content

Pgi: Stop Screwing This Up


173 replies to this topic

#41 KingCobra

    Member

  • PipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 2,726 posts
  • LocationUSA

Posted 15 April 2013 - 09:19 PM

To the OP say what you want don't let the PGI troll patrol get you down we all know the game is a dam mess or we would all be playing it instead of on the forums. But you will learn after a bit the PGI troll patrol will wreck any topic or post that is not a PGI darling post about how well the game is going. Or you will just be ignored because you have a valid point. Good luck OP.

Edited by KingCobra, 15 April 2013 - 09:19 PM.


#42 HighlandCoo

    Member

  • PipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 772 posts
  • Locationbehind you

Posted 15 April 2013 - 09:20 PM

Ah well, I dont have any of these problems. Sorry.

#43 Rhent

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • 2,045 posts

Posted 15 April 2013 - 09:25 PM

View Postjay35, on 15 April 2013 - 04:55 PM, said:

I love how people with no experience in software development trot out the old "QA is harrrrd" excuse. This isn't even about QA challenges, this is about a blatant lack of QA to begin with.


Piranha games has a QA department and a Test Server. The QA Department are the people who pay to play the game and the Test Server is what everyone is on. Piranha Games is going with an innovation new technique where they lie and call the game in BETA and to save a few bucks they release the game and have the QA department pay them to play the game.

Its a craptastic strategy that I truly hope fails miserably.

#44 Roadbeer

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Elite Founder
  • 8,160 posts
  • LocationWazan, Zion Cluster

Posted 15 April 2013 - 09:29 PM

View PostRhent, on 15 April 2013 - 09:25 PM, said:

Its a craptastic strategy that I truly hope fails miserably.


Awww, someone got their peelings hurt by the big bad PGI and is now all pouty and booboo liped.

#45 KingCobra

    Member

  • PipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 2,726 posts
  • LocationUSA

Posted 15 April 2013 - 09:32 PM

View PostForestGnome, on 15 April 2013 - 09:25 PM, said:



Actually, we only seem like a troll patrol if your IQ is two digits. Most of us agree on at least one point between PPC's being op, P2W consumables, PGI's willingness to lie, 3rd person, alpha-boating, or improper weapon implementation. We just simply dislike people who spew random **** out of their *** and trash PGI without any idea of what they are talking about.


If your stupid enough to believe MWO is truly a MechWarrior game then I have to say WHATEVER the OP has the right like anyone else to post his opinions of the game. And who are WE? that your claiming to be?

#46 jakucha

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 2,413 posts

Posted 15 April 2013 - 09:32 PM

View PostRhent, on 15 April 2013 - 09:25 PM, said:


Piranha games has a QA department and a Test Server. The QA Department are the people who pay to play the game and the Test Server is what everyone is on. Piranha Games is going with an innovation new technique where they lie and call the game in BETA and to save a few bucks they release the game and have the QA department pay them to play the game.

Its a craptastic strategy that I truly hope fails miserably.



Arguing semantics just makes you look silly because you're arguing over a pointless topic. The game isn't in release state and they can call it whatever they want; changing the title won't magically make all the content that's scheduled to be added suddenly appear. This is how many F2P betas operate, you just don't seem to realize that.

Edited by jakucha, 15 April 2013 - 09:35 PM.


#47 HighlandCoo

    Member

  • PipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 772 posts
  • Locationbehind you

Posted 15 April 2013 - 09:33 PM

Oh dear this going downhill fast. Can't we all just learn to get along? :D

#48 Loc Nar

    Member

  • PipPipPipPipPipPipPipPip
  • 1,132 posts

Posted 15 April 2013 - 09:37 PM

Posted Image

#49 Ragashar

    Member

  • PipPipPip
  • Survivor
  • Survivor
  • 61 posts
  • LocationFinland

Posted 15 April 2013 - 09:44 PM

Ok, I'll put down some facts about the QA process... I ain't with PGI, but I've seen my share of QA problems during my time working. One of the biggest issues that the QA can have is that they are not seeing the error. With the PC environment, which can have gazillion different configurations, it is highly possible that the QA people and the Devs have such computers in use, that they just simply are not seeing the problems, at least not as frequently. And as such, it is next to impossible to find the issue in the code if you cannot reproduce the error. These types of errors are next to impossible to fix... Until the root cause is found.

I don't know about the hud issues or the map issues (I've seen the map issue maybe once) and never had a missing HUD on my end.

I've seen the missing graphics from time to time and mostly in Frozen City.

The messed up graphics I've seen never on my CPU. Though I remember having a similar problem back when I first played Assassin's Creed (the first one), but it was a problem on my end and went away after I updated my GPU drivers. If you are seeing this with any regularity, you could twiddle around with the GPU drivers, maybe even try an older version to see if this problem is at your end.

PC debugging is hard to begin with... Finding the reason for something that you can't even see in QA end, is next to impossible. I'm sure they are working on this and will likely have to work with some "end users" (meaning players) to get to the bottom of it. If you get in touch with the QA on the technicolor thing, they will most likely first have you re-install the game, see that your GPU drivers are up-to-date before getting to anything further. As this is still Beta, the game probably does create some sort of a log of the in-game activities to some extent that the QA would likely want to see what it says, but I'm not with PGI so I don't know for sure, but this is usually how this stuff works.

So, to sum this all up... This is probably a big item for PGI, they are most likely working on it as well as they can (meaning if they can see it or not) and it will most likely require a client update and when these updates are already rolling out every other week, the fix will most likely be in one of those coming up. A problem that is seen by some part (probably quite a small part) of the end users can wait for a week or two.

What can we end users do... We can file QA Tickets to them and wait for them to get back to us and try things they would like us to try on our end. Nothing more and nothing less... Forum trolling is really not such a good thing to do as it will most likely end up with a flame war and we all know how that ends...

#50 Texas Merc

    Member

  • PipPipPipPipPipPipPipPip
  • The Patron
  • The Patron
  • 1,237 posts

Posted 15 April 2013 - 09:46 PM

View PostRagashar, on 15 April 2013 - 09:44 PM, said:

Ok, I'll put down some facts about the QA process... I ain't with PGI, but I've seen my share of QA problems during my time working. One of the biggest issues that the QA can have is that they are not seeing the error. With the PC environment, which can have gazillion different configurations, it is highly possible that the QA people and the Devs have such computers in use, that they just simply are not seeing the problems, at least not as frequently. And as such, it is next to impossible to find the issue in the code if you cannot reproduce the error. These types of errors are next to impossible to fix... Until the root cause is found.

I don't know about the hud issues or the map issues (I've seen the map issue maybe once) and never had a missing HUD on my end.

I've seen the missing graphics from time to time and mostly in Frozen City.

The messed up graphics I've seen never on my CPU. Though I remember having a similar problem back when I first played Assassin's Creed (the first one), but it was a problem on my end and went away after I updated my GPU drivers. If you are seeing this with any regularity, you could twiddle around with the GPU drivers, maybe even try an older version to see if this problem is at your end.

PC debugging is hard to begin with... Finding the reason for something that you can't even see in QA end, is next to impossible. I'm sure they are working on this and will likely have to work with some "end users" (meaning players) to get to the bottom of it. If you get in touch with the QA on the technicolor thing, they will most likely first have you re-install the game, see that your GPU drivers are up-to-date before getting to anything further. As this is still Beta, the game probably does create some sort of a log of the in-game activities to some extent that the QA would likely want to see what it says, but I'm not with PGI so I don't know for sure, but this is usually how this stuff works.

So, to sum this all up... This is probably a big item for PGI, they are most likely working on it as well as they can (meaning if they can see it or not) and it will most likely require a client update and when these updates are already rolling out every other week, the fix will most likely be in one of those coming up. A problem that is seen by some part (probably quite a small part) of the end users can wait for a week or two.

What can we end users do... We can file QA Tickets to them and wait for them to get back to us and try things they would like us to try on our end. Nothing more and nothing less... Forum trolling is really not such a good thing to do as it will most likely end up with a flame war and we all know how that ends...


Its pretty easy if you want to appeal to a wide audience. Go to Costco buy a mid range comp with decent specs. If your F2P game is having problems on it, then don't try to appeal to the masses and be the niche game you are.

#51 James DeGriz

    Member

  • PipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 374 posts
  • LocationRainham, Kent UK

Posted 15 April 2013 - 09:52 PM

Whenever I see QQ about bugs either here or on the MWO Social Networking feeds, my first thought is "Did you send a bug report?". I do honestly wonder if the people who are vehemently insisting that this game isn't a beta are only doing so as a cop out excuse for not sending bug reports in.

In other news; Roadbeer, just read the "Why You're Wrong" thread. Loving your work.

#52 darkfall13

    Member

  • PipPipPipPipPipPip
  • Survivor
  • Survivor
  • 298 posts

Posted 15 April 2013 - 10:05 PM

View PostDax Frey, on 15 April 2013 - 09:18 PM, said:

OP cries, then calls people with differing opinion "wankers"

This my friends...is why we can't have nice things around here...


Actually... the OP made his post, with his opinion/statement and got 1.5 pages of name calling and questioning of his intelligence and experience... so yeah.. it's the OP's fault...

#53 Rhent

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • 2,045 posts

Posted 15 April 2013 - 10:08 PM

View PostRoadbeer, on 15 April 2013 - 09:29 PM, said:


Awww, someone got their peelings hurt by the big bad PGI and is now all pouty and booboo liped.


Nope, pointing out a blatant fact. If you don't like facts, its cool go elsewhere. I've done three Betas for major MMO's since 1995, and I've never seen an Open Beta do a major release that wasn't first tested out on a Test Server before going to the main Beta Server. After reading PGI's teasting strategy (hey we'll automate it to run it 16X's), instead of using 200 real life testers, you get an idea of how PGI is doing development.

Its a poor model that is driving away paying subscribers.

#54 White Bear 84

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 3,857 posts

Posted 15 April 2013 - 10:12 PM

Because every man and his dog knows best about how to develop a game and the pitfalls and challenges it presents......

#55 Rhent

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • 2,045 posts

Posted 15 April 2013 - 10:12 PM

View PostWhite Bear 84, on 15 April 2013 - 10:12 PM, said:

Because every man and his dog knows best about how to develop a game and the pitfalls and challenges it presents......


Because everyone knows you have a Test Server with real testers testing your game and pointing out major problems before they get released to the general population server. If you don't understand basics, good luck.

#56 Morang

    Member

  • PipPipPipPipPipPipPipPip
  • 1,259 posts
  • LocationHeart of Darkness

Posted 15 April 2013 - 10:19 PM

I actually find this "champion mech" a menacing sign.

I see no much point in this release. What's unique about it besides CB Bonus, when everyone can build the same DRG-5N? It looks either like first signs of plans to make all mechs MC-only, or like a futile attempt to imitate new content addition where there is no new content.

Instead of this rant around poor Dragon they can as well just allow players to give any of their ordinary mechs permanent CB bonus for some tonnage-based amount of MCs. Now that's a new feature.

It was OK when it was about trial mech to be upgraded. But releasing it as "Champion" just looks awkward and pointless.

Edited by Morang, 15 April 2013 - 10:31 PM.


#57 ElCadaver

    Member

  • PipPipPipPipPip
  • Wrath
  • Wrath
  • 163 posts
  • LocationAustralia

Posted 15 April 2013 - 10:36 PM

One major trend with creates these problems, is the move towards developers beginning to sell the beta version of the game. In the olden days of gaming, you purchased the finished product, which had a couple of minor patches if that. They way the gaming companies are run now reminds me of american banking before the global financial crisis.

As an owner of sim city, (don't get me started), developers who rush embryonic product to market are only doing themselves a disservice, as it creates exactly the type of sentiment we see on the forums of many new games these days.

Hopefully PC game developers will one day learn from this mistake, support their workers better, and allow them the time to create well executed and stable product, which will allow them for the most part to keep their failings in house and dealt with prior to release, instead of airing all their dirty laundry to the masses.

My two cents.

Edited by ElCadaver, 15 April 2013 - 10:37 PM.


#58 Barnaby Jones

    Member

  • PipPipPipPipPipPip
  • Survivor
  • Survivor
  • 434 posts
  • LocationTexas

Posted 15 April 2013 - 11:19 PM

I have to ask those of you PGI defenders out there how you justify the ELO **** up they are about to fix...and how it was not found AT ALL until just a bit ago? The months we waited since 8mans were killed, the couple of months we've had ELO, and they only find this **** now? this is not a graphical bug, this is absolutely a lack of any actual testing prior to releasing it on the servers.

Not to mention the point the OP is trying to make is best expressed by the recent LRM bs.

They introduce something in the patch that makes lrms insanely op.... Most companies would roll back that bit of code and attempt to correct it before rereleasing it. IE the status quo is better than a rushed and untested fix.

PGI on the other hand, decided that it would be better to try three distinct and seperate nerfs to missles, after just three days of work, and saying "They Feel Right" and "we'll actually fix this **** in May".

#59 jeffsw6

    Member

  • PipPipPipPipPipPipPipPip
  • 1,258 posts
  • LocationLouisville, KY (suburbs)

Posted 15 April 2013 - 11:24 PM

View PostRhent, on 15 April 2013 - 10:08 PM, said:

Its a poor model that is driving away paying subscribers.

QFT

#60 jakucha

    Member

  • PipPipPipPipPipPipPipPipPip
  • Knight Errant
  • 2,413 posts

Posted 15 April 2013 - 11:27 PM

View PostBarnaby Jones, on 15 April 2013 - 11:19 PM, said:

I have to ask those of you PGI defenders out there how you justify the ELO **** up they are about to fix...and how it was not found AT ALL until just a bit ago? The months we waited since 8mans were killed, the couple of months we've had ELO, and they only find this **** now? this is not a graphical bug, this is absolutely a lack of any actual testing prior to releasing it on the servers.

Not to mention the point the OP is trying to make is best expressed by the recent LRM bs.

They introduce something in the patch that makes lrms insanely op.... Most companies would roll back that bit of code and attempt to correct it before rereleasing it. IE the status quo is better than a rushed and untested fix.

PGI on the other hand, decided that it would be better to try three distinct and seperate nerfs to missles, after just three days of work, and saying "They Feel Right" and "we'll actually fix this **** in May".



How can you justify complaining about something you have no idea of how it works and likely couldn't do a better job of fixing?





11 user(s) are reading this topic

0 members, 11 guests, 0 anonymous users