Maybe the new patch will fix the talks with characters. I find that some characters who talks are supposed to randomly trigger, I actually have to talk to them to get them to say anything to me.
So a bug fix can come out and actually CAUSE bugs? That's just weird. It doesn't make sense to me, then again, I know nothing of game design
Just to note that when people say it's Programming 101, it's not always going to happen, it just means that there is always a chance of it happening.
Just to put it into basic pictographic terms:
Imagine changing something in the very bottom right corner, its task is to modify something that the top left created. In the process, B (bottom-right) asked C to make a change, C asked D, but it turns out the programmer made an edit in D. When the value is then modified it is done so incorrectly and [x3 y2] moves along to [x4 y2] with a now incorrect value. The incorrect value is passed from [x4 y2] to [x3 y3], it uses the value to calculate something else and moves along with these two incorrect values to [x2 y3]. Rinse and repeat. It's a snowball effect and it is necessary to track it back to the source in order to fix it, but since so many things are now seemingly incorrect it will now be difficult to determine which one is the culprit. A programmer may fix one issue by added or removing an innocuous if() block, but in doing so may upset something else.
Basically, it's the Butterfly Effect. Which is why additions, removals, and modifications need to be tested to ensure things still work as intended after a change in the initial condition.
It's also worth noting that modern, properly organized, object-oriented code is a great deal less susceptible to this problem. But as we all know, the Infinity Engine was written in prehistoric times when huge predatory reptilian bugs ruled cyberspace and when primitive man had only just discovered the art of code-spinning. Today, top experts around the world try to decipher the jumbled mess our ancestors had left behind, but they've found that it is insanity to even try.
It's also worth noting that modern, properly organized, object-oriented code is a great deal less susceptible to this problem. But as we all know, the Infinity Engine was written in prehistoric times when huge predatory reptilian bugs ruled cyberspace and when primitive man had only just discovered the art of code-spinning. Today, top experts around the world try to decipher the jumbled mess our ancestors had left behind, but they've found that it is insanity to even try.
I'm not sure what a huge predatory reptilian bug would look like but I now kind of want to see one. From a distance based on its description though.
I'm not sure what a huge predatory reptilian bug would look like but I now kind of want to see one. From a distance based on its description though.
You should count yourself lucky, then. The other day, a whole herd of them attacked our party in BG2 multiplayer. It was a carnage - we barely managed to escape with our save files intact. I still have nightmares of that encounter.
It's also worth noting that modern, properly organized, object-oriented code is a great deal less susceptible to this problem. But as we all know, the Infinity Engine was written in prehistoric times when huge predatory reptilian bugs ruled cyberspace and when primitive man had only just discovered the art of code-spinning. Today, top experts around the world try to decipher the jumbled mess our ancestors had left behind, but they've found that it is insanity to even try.
I'm not sure what a huge predatory reptilian bug would look like but I now kind of want to see one. From a distance based on its description though.
So that's why there are huge Baslisks on top of Durlag's tower!
Greetings everyone. This patch has been worked on a good while now. How is it going with this? I load the game every day hoping it will come out Also is there any plan of expanding the store for Baldur's Gate 1 EE or Baldur's Gate 2 EE?
It seems to be mostly silence here, from Beamdog's end. Last week, the patch was one bug away, according to Trent Oster's Twitter account at least. What has happened since then, only Oghma knows.
It seems to be mostly silence here, from Beamdog's end. Last week, the patch was one bug away, according to Trent Oster's Twitter account at least. What has happened since then, only Oghma knows.
It's also worth noting that modern, properly organized, object-oriented code is a great deal less susceptible to this problem. But as we all know, the Infinity Engine was written in prehistoric times when huge predatory reptilian bugs ruled cyberspace and when primitive man had only just discovered the art of code-spinning. Today, top experts around the world try to decipher the jumbled mess our ancestors had left behind, but they've found that it is insanity to even try.
I'm not sure what a huge predatory reptilian bug would look like but I now kind of want to see one. From a distance based on its description though.
So that's why there are huge Baslisks on top of Durlag's tower!
Pretty sure basilisks are just reptiles. Now a basilisk with giant fly-like wings would be a reptilian bug.
I don't think the situation's that bad. Okay, sometimes OG take decades to push through bugfixes, but it looks like they also have new content in the works and personally I can't wait to play more BG.
So far, nothing that wasn't there before. Things are looking good. Even multiplayer doesn't feel like a total mess, which at this point is just bizarre. We're looking forward to getting this patch out there so people can see it.
I don't think the situation's that bad. Okay, sometimes OG take decades to push through bugfixes, but it looks like they also have new content in the works and personally I can't wait to play more BG.
See, that's exactly the mistake my dumb ass made last time. "Yeah, okay, BG:EE was kind of a mess for a whole year, but BG2:EE's going to be so much better, right?" Shows what I know.
Here's how it'll probably go with Adventure Y: by week 2 post-launch, there'll be a five-page-long buglist. It'll be a broken mess (albeit a decently-written broken mess). Then we'll have a "Road to Adventure Y 2.0" subforum, followed by six to nine months of Phases and counters and whatever. And then, long after any enthusiasm has died out and very few people still care, a patch will come out that lets you get through the new content without making you want to rip your hair out by the roots.
I mean, look, I actively want to be wrong about this. I want the devs to live up to their hype for once. But the odds favor repetition here, and that doesn't bode well.
Comments
99 little buuuugs
Take one down, patch it around
120 little bugs in the code
I appreciate the explanations from you guys though.
My Baldur's Gate Patch! Yay!
Imagine changing something in the very bottom right corner, its task is to modify something that the top left created. In the process, B (bottom-right) asked C to make a change, C asked D, but it turns out the programmer made an edit in D. When the value is then modified it is done so incorrectly and [x3 y2] moves along to [x4 y2] with a now incorrect value. The incorrect value is passed from [x4 y2] to [x3 y3], it uses the value to calculate something else and moves along with these two incorrect values to [x2 y3]. Rinse and repeat. It's a snowball effect and it is necessary to track it back to the source in order to fix it, but since so many things are now seemingly incorrect it will now be difficult to determine which one is the culprit. A programmer may fix one issue by added or removing an innocuous if() block, but in doing so may upset something else.
Basically, it's the Butterfly Effect. Which is why additions, removals, and modifications need to be tested to ensure things still work as intended after a change in the initial condition.
#criesinacorner
Or maybe any form of patches for BG 2 EE?
Regards
Tom Fjellheim
Lots and lots of testing.
Can we go kill something now, huh? .............
How about now? No? ........
Come on let's kill something NOW!
mmmm.... now?
What about now?
Now? Please? Pretty please?
I don't know what you were expecting, but as a sword I'm pretty one-dimensional in what I want....."
ah lilarcor how we love you
Here's how it'll probably go with Adventure Y: by week 2 post-launch, there'll be a five-page-long buglist. It'll be a broken mess (albeit a decently-written broken mess). Then we'll have a "Road to Adventure Y 2.0" subforum, followed by six to nine months of Phases and counters and whatever. And then, long after any enthusiasm has died out and very few people still care, a patch will come out that lets you get through the new content without making you want to rip your hair out by the roots.
I mean, look, I actively want to be wrong about this. I want the devs to live up to their hype for once. But the odds favor repetition here, and that doesn't bode well.