20 minutes with Killzone 2 and already two game stopping bugs?

[ssj12]

MaxwellGT2000 said:

ssj12 said:

MaxwellGT2000 said:

Rpruett said:

Sharky54 said:

MaxwellGT2000 said:

ssj12 said:
A random crash is nothing to call game stopping. Every game does it. Left 4 Dead (NO), Half Life (NO), Halo (NO), Gran Turismo (NO), Gears of War (NO), etc.

 

Especially when Twes is talking about the first 20 minutes of the game...

Left4dead, gears 2, and half life 2 have all crashed on me.

Likewise.

 

 

On PC that's usually a sign of incompatibility, which also doesn't address the first 20 minutes...

 

A random crash like what twest had is well random. It is possible that it just randomly did it in the first 20 minutes. I;ve had games like Resistance 2 crash my PS3 just loading the menu screen. It happens.

 

Also it doesnt mean anything about compatability when i have beyond the hardware needed for all those games on PC. It is strictly a problem with how the code was processed. If a line of code doesnt process correctly in any game it could lead to either massive glitches or the game completely crashing.

 

<_< You really said that?  It doesn't matter how powerful your hardware is if the drivers don't work with your graphics card.  Example, DK has a stronger graphics card then I do, he tries to play Fallout 3 it crashes on him, he updates the drivers it works fine, Bethesta updates the game the game crashes again, however I have a weaker graphics card and not a single error has happened to me yet?  Do I shrug off as the game has no issues? No... and OT this is console games we're talking about, the developers know the hardware they're working with and they know the limits.

It's more excusible to have a game crash that has to work on many different cards and specs then it is for a game to crash when there's one console they develop it for and no difference in the hardware aside from some PS3's having BC and others not, plus the fact it's been in development for so long they could have done enough extensive bug testing to get many of these errors... but no you release a game people find bugs and you patch it, that's the way things work now...

 

 

I know... this is why the bolded line is about hardware and the ones following is software. DK's issue had nothing to do with the hardware but the software. This is why some older games which require 32mbs of ram error with a message saying you dont have enough even though it shows you have 2GBs in the error message. The game isnt coded for the hardware.

 

As for your second paragraph, this is due to QA costs. Highering 100 people for QA testing is expensive for any company. Why do that when you higher 10 - 20, have them find the worst bugs and most common. Fix what you can. Ship off the final product and fix whats left if they hurt the overall game.