If you knew anything about programming, testing, or any process/system these companies use to ensure a quality product, you wouldn't be so confrontational.
I do and I agree with them.
However, I do see the big list of problems others have on the forums, and perhaps the play testers just got lucky and had machines that didn't offer any oddities in the code.
If Obsidian's QA team and platforms were this narrowly confined it's an indication of their utter failure to properly test. In other words, your defense of Obsidian is to imply they're incompetent buffoons.
No software in the history of software has ever been released 100% bug free for 100% of it's users.
Nice straw man argument you got there. Nobody but
YOU has so much as implied it ought to be 100% bug free.
I am sorry you have problems, but if you give it some time, all your issues will hopefully be resolved in a patch. I know that isn't what you want to hear, but it's going to have to suffice for now. I can't even imagine how beta testers feel when they hear/see complaints like this. For doing nothing but playing games, they actually do have a pretty difficult job (I should know; I was an in-house tester for Electronic Arts for 3 years).
That explains a lot.
Blizzard and Rockstar have a lot more money, and they publish their own games.
Which is irrelevant, they charge the same price.
Yes, they had plenty of time after DEVELOPING the game for a good majority of the 2 years they were. At most, they probably had like 3 weeks to bug test. Reason why, Bethesda wanted the game out by the 19th, no questions asked.
Unless Bethesda
changed the deadline and moved it up without sufficient notice this is complete horsecrap. It is not Bethesda's job to manage the project. If we setup a deadline ahead of time and my team misses it or rushes a poor product out the door it's
our fault for mismanaging the project, not someone else's fault for sticking to the plan. That said, if Bethesda forced an unrealistic time frame on them in the first place, fine. But then Obsidian still bears the responsibility for agreeing to it.
Mine is its an equal opportunity screw up most likely from too many cooks in the kitchen so to speak (I can think of three entities - maybe four).
It's usually too many managers who think meetings are a productive use of a developer's time. Meanwhile they look for ways to justify their salary by interfering in work they know nothing about.
Then throw in the occasional sales [censored] who just promised the customer they'd have it ready to make them coffee by next weekend.