Christ dude, you make no sense, and you didn't read what i said, i can tell. I dont sit and defend all day, as a matter of fact i Realize and acknowledge Next games points, even if i dont agree with some of them but for heavens sakes man, you just spit out nonsense. I know, i know, the past, the past its fun. Your angry because you bought a package for what you thought you knew what you wanted and now want to get you money back. I get it. You completely mistook me, to put it real plainly, you know, just go back and read it. Next game may have been in the same boat as you but jeez he makes you look like a second grader.
Sidekick, on 23 January 2014 - 09:46 AM, said:
Edit: WHOA, holy spelling, Batman! I really shouldn´t post with the flu in my head! Please ignore missing words/letters.
Bloodwolf...
I really have to ask you to stop "defending" PGI. I see you like MWO and I see you have an issue with those who attack the devs for the recent (recent in the context of "end of Closed Beta") issues.
But your way of argumentation is quite counter-productive. or to put it differently:
There is no meaner way to attack PGI than the way you (try to) defend them.
If we would follow your argumentation, and NG is doing it (for fun), the staff of PGI would have problems filling in an xls file. If the things are like you describe, like those "woah wtf moments in UI programming" the staff would really ride the short bus to work.
Let me tell you something.
Ressource allocation is one thing, and I think it is the most important issue.
But that issue has been discussed to death, so let´s NOT talk about it.
Let´s talk about those "wtf" moments PGI had in the past. There were some, and they were quite glorious.
There was the (famous) 4fps bug. In some matches, players fps was dropping due an unknown reason. Later, they found out that when an atlas died, the hitbox was still in the game and started inflating, conflicting with all other collision meshes, causing all involved players to loose framerate.
It was a hell of a bug. and the method it was discouvered was awesome. Some players started to drop in 8´s without certain chassis. So they filtered out one chassis by the time till they found the responsible model.
There was the quite entertaining "calleidoscope HUD" Bug, there was the damage extension via missle blast issue, there are still several hitbox-denial issues, there was the "knockdown desynchrinisation bug" that was essentially solved by removing knockdowns.....
there are lots and lots of issues the coding team of PGI is trying to tackle. but in the same time they try to progress the game. But while doing that, they try to implement and cultivate monetizing items/mechs that are important vor MWO´s economic viability.
And that´s the point. For quite a long time, UI1.0/1.5 was economically viable. So while UI2.0 was talked about, it wasn´t reqiured from an sellers standpoint. So the design department was drawing demos and the management was reffering the whats and whys of the next to the marketing who sold us on it... but it wasn´t required to actually introduce UI2.0 (and CW and lobbie) because the management saw those as unimportant in an production line sense.
And the issue was and is: If you don´t get money to to it, don´t do it! If you don´t pay your car salesman for a new set of tires and ask him to polish the rims, he will take of the rims, remove the tires, polish the metal and put on the old tires again. Why? Why not? You didn´t give him any money for new tires.
And that has happend for the last year. We were ignorant customers (look at my tags) and the seller was just following our lead.
Don´t try to pull out arguments and excuses that were never made in that way. Because right now, most of the people involved know what went wrong and most responsible parties are quite ashamed by it.
what point were you trying to make? it kinda looks like your agreeing with me from what i stated in some of my first post but i dunno.
Edited by BLOOD WOLF, 23 January 2014 - 10:11 AM.