By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - Microsoft Discussion - Fable II players report game breaking glitch

vlad321 on 24 October 2008
twesterm said:
Jordahn said:
pbroy said:
thejuicingamer said:
just another example of a game getting rushed off the line to achieve some quick sales, sign of the times

 

How is this comment being productive? Ohh wait your just trying to rub it in. Don't you have a game you can play on your PS3 or something?? o_O Don't tell me your jealous because people with a 360 have lots of fun games to play and you just want to find the smallest things to make anything not on the PS3 look bad. Your better than that, aren't you?

 

In principle, what he's saying is true.  With online options and fierce competition, I see it becoming more and more common to "skimp" a few things for the sake of time to later patch it if a common problem arises.  I'm not saying for sure this was the developer's intent.  It's either more noticable because it is, or it's simply because games are getting more complex so there is a higher chance of things getting missed.

Bugs just happen.

I would be impressed with any game that shipped with bugs.  Some bugs are just harder to catch but when you have hundreds of thousands, those bugs are going to be found.  Most of the time they are little things like a floating tree, other times they're things like this.

It's true that bug should have been caught but it being there in no way means it was rushed.

 

There are no bug free programs yes, yet I have yet to see game crippling bugs like these in any Valve game or Blizzard game, or a whole bunch of other companies I can name. How can they do away with crippling bug-free launches and Lionhead can't? Bugs are causes of lack of testing and lack of testing is caused by rushing a game. 1/4 of the time I spend on my programs is solely for testing and debugging, yet even after the game went gold they were making the co-op. This game is rushed and I hate how this is starting to be a trend with today's developers. It really serves to weed out the trully great developers from the rest IMHO. I'm also honestly surprised that a game with game breaking bugs is getting such a high score, sure the content is great, but what's the point if I can't even get to experience it? Reviewers should be more stern on issues like these, and then maybe developers will stop rushing their games.



Tag(thx fkusumot) - "Yet again I completely fail to see your point..."

HD vs Wii, PC vs HD: http://www.vgchartz.com/forum/thread.php?id=93374

Why Regenerating Health is a crap game mechanic: http://gamrconnect.vgchartz.com/post.php?id=3986420

gamrReview's broken review scores: http://gamrconnect.vgchartz.com/post.php?id=4170835

 

Around the Network
twesterm on 24 October 2008
vlad321 said:
twesterm said:
Jordahn said:
pbroy said:
thejuicingamer said:
just another example of a game getting rushed off the line to achieve some quick sales, sign of the times

 

How is this comment being productive? Ohh wait your just trying to rub it in. Don't you have a game you can play on your PS3 or something?? o_O Don't tell me your jealous because people with a 360 have lots of fun games to play and you just want to find the smallest things to make anything not on the PS3 look bad. Your better than that, aren't you?

 

In principle, what he's saying is true.  With online options and fierce competition, I see it becoming more and more common to "skimp" a few things for the sake of time to later patch it if a common problem arises.  I'm not saying for sure this was the developer's intent.  It's either more noticable because it is, or it's simply because games are getting more complex so there is a higher chance of things getting missed.

Bugs just happen.

I would be impressed with any game that shipped with bugs.  Some bugs are just harder to catch but when you have hundreds of thousands, those bugs are going to be found.  Most of the time they are little things like a floating tree, other times they're things like this.

It's true that bug should have been caught but it being there in no way means it was rushed.

 

There are no bug free programs yes, yet I have yet to see game crippling bugs like these in any Valve game or Blizzard game, or a whole bunch of other companies I can name. How can they do away with crippling bug-free launches and Lionhead can't? Bugs are causes of lack of testing and lack of testing is caused by rushing a game. 1/4 of the time I spend on my programs is solely for testing and debugging, yet even after the game went gold they were making the co-op. This game is rushed and I hate how this is starting to be a trend with today's developers. It really serves to weed out the trully great developers from the rest IMHO. I'm also honestly surprised that a game with game breaking bugs is getting such a high score, sure the content is great, but what's the point if I can't even get to experience it? Reviewers should be more stern on issues like these, and then maybe developers will stop rushing their games.

 

Testing Half-Life 2 is different from testing Fable II.  One is a linear shooter with limited options, one is a vast open world game with many options.

As for things like WoW, I guess you've never known anyone in any of the WoW betas.



 

vlad321 on 25 October 2008
twesterm said:
vlad321 said:
twesterm said:
Jordahn said:
pbroy said:
thejuicingamer said:
just another example of a game getting rushed off the line to achieve some quick sales, sign of the times

 

How is this comment being productive? Ohh wait your just trying to rub it in. Don't you have a game you can play on your PS3 or something?? o_O Don't tell me your jealous because people with a 360 have lots of fun games to play and you just want to find the smallest things to make anything not on the PS3 look bad. Your better than that, aren't you?

 

In principle, what he's saying is true.  With online options and fierce competition, I see it becoming more and more common to "skimp" a few things for the sake of time to later patch it if a common problem arises.  I'm not saying for sure this was the developer's intent.  It's either more noticable because it is, or it's simply because games are getting more complex so there is a higher chance of things getting missed.

Bugs just happen.

I would be impressed with any game that shipped with bugs.  Some bugs are just harder to catch but when you have hundreds of thousands, those bugs are going to be found.  Most of the time they are little things like a floating tree, other times they're things like this.

It's true that bug should have been caught but it being there in no way means it was rushed.

 

There are no bug free programs yes, yet I have yet to see game crippling bugs like these in any Valve game or Blizzard game, or a whole bunch of other companies I can name. How can they do away with crippling bug-free launches and Lionhead can't? Bugs are causes of lack of testing and lack of testing is caused by rushing a game. 1/4 of the time I spend on my programs is solely for testing and debugging, yet even after the game went gold they were making the co-op. This game is rushed and I hate how this is starting to be a trend with today's developers. It really serves to weed out the trully great developers from the rest IMHO. I'm also honestly surprised that a game with game breaking bugs is getting such a high score, sure the content is great, but what's the point if I can't even get to experience it? Reviewers should be more stern on issues like these, and then maybe developers will stop rushing their games.

 

Testing Half-Life 2 is different from testing Fable II.  One is a linear shooter with limited options, one is a vast open world game with many options.

As for things like WoW, I guess you've never known anyone in any of the WoW betas.

I've been in all 3 WoW betas. Interestingly minus the crippling lag of thousands of players getting on at the same time in the same zones, there's no real crippling bugs that I've noticed in the release version. Nothing where WoW would freeze or you wouldn't be able to progress your character further in the game. There were those 2 quests back in terokkar, but you skip them and they didn't even give good loot or exp to begin with. And that one BWL bug they had when that patch went though, but a GM got on and unlocked the door for them manually. Also the WOTLK beta seemed very stable, but I won't judge until after the 13th when all millions of people have given it a go. There have been no game breaking bugs in WoW, and that's an MMO, which can run on hardware from 10 years ago, just think of how much hardware and drivers they are supporting. Meanwhile here's a single-player game which is supposed to run on only 1 hardware architeture and you can't even iron out the game breaking bugs like the game freezing? Blatant rush job, or just a poor job on part of the developers if it wasn't rushed.

 



Tag(thx fkusumot) - "Yet again I completely fail to see your point..."

HD vs Wii, PC vs HD: http://www.vgchartz.com/forum/thread.php?id=93374

Why Regenerating Health is a crap game mechanic: http://gamrconnect.vgchartz.com/post.php?id=3986420

gamrReview's broken review scores: http://gamrconnect.vgchartz.com/post.php?id=4170835

 

twesterm on 27 October 2008
vlad321 said:
twesterm said:
vlad321 said:
twesterm said:
Jordahn said:
pbroy said:
thejuicingamer said:
just another example of a game getting rushed off the line to achieve some quick sales, sign of the times

 

How is this comment being productive? Ohh wait your just trying to rub it in. Don't you have a game you can play on your PS3 or something?? o_O Don't tell me your jealous because people with a 360 have lots of fun games to play and you just want to find the smallest things to make anything not on the PS3 look bad. Your better than that, aren't you?

 

In principle, what he's saying is true.  With online options and fierce competition, I see it becoming more and more common to "skimp" a few things for the sake of time to later patch it if a common problem arises.  I'm not saying for sure this was the developer's intent.  It's either more noticable because it is, or it's simply because games are getting more complex so there is a higher chance of things getting missed.

Bugs just happen.

I would be impressed with any game that shipped with bugs.  Some bugs are just harder to catch but when you have hundreds of thousands, those bugs are going to be found.  Most of the time they are little things like a floating tree, other times they're things like this.

It's true that bug should have been caught but it being there in no way means it was rushed.

 

There are no bug free programs yes, yet I have yet to see game crippling bugs like these in any Valve game or Blizzard game, or a whole bunch of other companies I can name. How can they do away with crippling bug-free launches and Lionhead can't? Bugs are causes of lack of testing and lack of testing is caused by rushing a game. 1/4 of the time I spend on my programs is solely for testing and debugging, yet even after the game went gold they were making the co-op. This game is rushed and I hate how this is starting to be a trend with today's developers. It really serves to weed out the trully great developers from the rest IMHO. I'm also honestly surprised that a game with game breaking bugs is getting such a high score, sure the content is great, but what's the point if I can't even get to experience it? Reviewers should be more stern on issues like these, and then maybe developers will stop rushing their games.

 

Testing Half-Life 2 is different from testing Fable II.  One is a linear shooter with limited options, one is a vast open world game with many options.

As for things like WoW, I guess you've never known anyone in any of the WoW betas.

I've been in all 3 WoW betas. Interestingly minus the crippling lag of thousands of players getting on at the same time in the same zones, there's no real crippling bugs that I've noticed in the release version. Nothing where WoW would freeze or you wouldn't be able to progress your character further in the game. There were those 2 quests back in terokkar, but you skip them and they didn't even give good loot or exp to begin with. And that one BWL bug they had when that patch went though, but a GM got on and unlocked the door for them manually. Also the WOTLK beta seemed very stable, but I won't judge until after the 13th when all millions of people have given it a go. There have been no game breaking bugs in WoW, and that's an MMO, which can run on hardware from 10 years ago, just think of how much hardware and drivers they are supporting. Meanwhile here's a single-player game which is supposed to run on only 1 hardware architeture and you can't even iron out the game breaking bugs like the game freezing? Blatant rush job, or just a poor job on part of the developers if it wasn't rushed.

 

 

Then you are just having a completely different experience than the friends I have that are playing the WotLK beta.



 

EaglesEye379 on 27 October 2008

I am one of the unlucky ones to experience game breaking freezes and bugs. And its not the two bugs discussed above, its more widespread than that and you just have to go to the Lionhead forums to know this problem is quite big and can happen almost anywhere in the game.

On my main character, I clocked in about 6 hours and into Brightwood but no matter what I do after loading the save game, it will freeze after about 1 minute. I tried rebooting countless times, warping to other locations, but to no avail. So my main character is now unplayable. I just tried tonight again and now the game wont even load! Just a blank screen. Awful. I think whoever thought about just one slot for a save file on such a huge RPG should be shot!

So I restarted a new character, and now it freezes about every 15 mins. Although, this is not game breaking, I am frustrated to no end. Its just a HUGEEE shame though because this was shaping up to be one of my favourite games ever.

I am now resigned to wait for a patch, but actually Ill most probably return the disc as the warranty will probably run out by the time Lionhead issues a patch.

Sigh.