Moraelin
Posts: 5
Joined: 8/18/2002
Status: offline
|
[QUOTE=dragoniv](1) you can't patch a console game (for all intents and purposes), and the PC dev teams have gotten addicted to "no big deal, we'll fix that bug in the first patch release."[/QUOTE]
Bingo. That's IMHO the biggest factor. No console publisher would pull a "Black and White", where features advertised on the box weren't even coded until half a bloody year after release. They may have some obscure bug left in the end, but they do know that they have to do their best at testing before release.
[QUOTE=dragoniv](2) consoles are in a very restricted sandbox; PCs are not. Consoles have very few inputs and almost no variation in hardware setup. PCs are the exact opposite. Many "bugs" in released games are specific to hardware related items, and it's **** near impossible to test every combination before the software goes out the door.[/QUOTE]
Sadly, I don't buy this. There are a few hardware related issues out there, yes, but about 90% of the PC bugs are:
- script bugs (probably Fallout 2 is the prime example)
- memory leaks
- AI bugs
- poorly coded tests in the program (e.g., falling through corners in Daggerfall or through tile edges in Morrowind)
- race conditions between threads (here Morrowind again has to take the crown, as it actually caused a CTD)
Etc.
Basically things which wouldn't work any better on _any_ hardware configuration imaginable. E.g., you tell me what kind of hardware conflict could possibly cause the endless "communication ended" loop.
Again, I'm not saying that the odd hardware issue doesn't exist. But for most publishers and devs it's just become the standard excuse to skip testing at all.
|
Printable Version
- 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread