I see what you're saying.Jonci said:miracleofsound said:I never said the demo wasn't as good as a finished product. I merely said what I did and didn't like about it. If you read the OP you'll see this.
Unfortunately even Valve fans can't say anything negative about a Valve game these days without getting blasted with fanboyism.
As for your points on bugs, everything you said is true but surely most bugs can be dedected by extensive playtesting?
Bethesda for example: people couldn't even play The Pitt when they released it. It made my copy of the came crash. That's a pretty damn big bug for something you just paid your good money for. Surely you can understand the frustration of the consumer in this instance?
And I remember laughing to myself playing F3 for the first time, when it entered a game-breaking glitch within the first ten minutes, during the G.O.A.T. exam... Beth obviously hadn't playtested the intro properly.
Thankfully, Valve's games tend to be more bug-free than almost anyone else.
But nowhere in my OP did I mention bugs anyway, that coversation was a tributary.That.miracleofsound said:Demos are meant to be a way to experience the best the game has to offer, so people will then go and buy it.
They should function as well as the finished game.
As for playtesting, you also have to consider how many people can a company really hire to playtest. Then consider how large games are that need to be playtested. Multiply by the number of systems to be tested on. The consoles tend to be straight-forward testing. There should not be any notable different between one 360 and another 360. Same with the PS3, though that does mean that you need teams to test for a 360 and a PS3. Even still, they could have only 50 people playtesting and all 50 could miss that crash. Suddenly you have 100,000+ players playing and the chances of one of them finding that crash is much higher.
If you go PC, that's a whole other hell. Different versions of Windows, types of video cards, sound capabilities, processors, RAM, drivers, etc.... They can only test so much and even a slight difference in the versions of your C++ runtype libraries sitting on your computer could result in a crash. The process of optimizing for any one thing can result in bad performance on another, if the company isn't careful. If something absolutely breaks, it's most likely because whatever you are running wasn't a test machine they had or didn't have the conditions that cause your crash.
I once had to figure out why a program I developed wouldn't work on ONE machine my clients had. The machines should have been the same. Turned out to be as simple as having the wrong version of some library because it hadn't been connected to the internet for Windows updates. Knowing this, I made sure all future versions would properly add those library files necessary. It's is tricky and there are just so many things you have to take account for and it is too easy to miss something.
I've only ever played Morrowind (form Steam), Fallout 1 and Zelda: A Link to the PAst on my PC, so my knowledge of this area is small.
You get used to things just working in one way when you're a consoler! Put the disc in and play. So when it doesn't work it can be confusing.
But having seen the modding that people did to Morrowind, I hope to invest further in PC gaming in a year or two, when I can find the cash.
But what you said about PC play testing was very interesting there, makes you see things from a whole different perspective.