The game originally checked to see if Donnelly and Daniels survived, and if they did, the dialogue would initiate. However, when fixing a dialogue bug with Ashley, it introduced a bug in Engineering that instead of checking for their survival, checks to see if you are "good friends' with Ashley. To clarify this does not mean you need to be in a romance, if you are, it will automatically set this flag, or should, otherwise you will need to bring her the gift in the hospital and go through all the subplots with her to become friends. If you do, you'll eventually see this dialogue. This bug may also be preventing dialogue between Garrus and Tali.
Subplots are very important to the experience Mass Effect offers, as the main plot is only a portion of what the rich story offers. However, this bug may also be in low priority meaning it may not get fixed. We need to push the issue enough to get the devs attention to add this to their list of fixes. It is said that only a small portion may actually care about this, but I doubt that. If you play RPG games you most likely want to immerse yourself into the story, it is what they are about. And I doubt 99% of the community saved Ashley, and if they did, I doubt 100% of them made the extra effort to set the friend flag. So that leaves quite a few of us without some important subplot content.
Will this bug ever be passed up the chain to be fixed and eventually seen in a patch? I'm not concerned with time as much as if it will actually ever get attention.
Here is the posts from Dusty Everman explaining the situation:
Dusty Everman wrote...
To my great sadness and embarrassment, it looks like there is a bug here that got introduced just before ship. It looks like the test for "is it time for ambient dialog in engineering" accidentally got switched to "are you good friends with Ashley". How did this bug happen? I have no idea, and need to do some detective work. This doesn't just block Ken and Gabby banter, but I think this blocks some Tali and Garrus banter in engineering too. As it stands now to see that banter, I believe you'll need to get Ashley in your party and take her on missions and/or give Ashley lots of attention by speaking to her and giving her the gift in the hospital. If you have Kaidan in your game, obviously this can't be done, and that sucks.
Though the fix is easy, the difficult part is getting the fix into a patch of some sort. Getting content fixes into patches is much harder than you'd think. It's a giant process. I'll try to get that fix through, but sadly, the odds of getting this type of fix into a patch is very low. It just kills me that so many of the people who care about Ken and Gabby (those of you reading this forum) didn't get to see that content. I tested the heck out of it too for weeks before ship. You just don't now how sorry I am.
Dusty Everman wrote...
avatar2396 wrote...
thanks for letting us know. I actually didnt have a problem with this since i had the appropriate conditions to generate the conversation. Also to note they dont really say anything until later in the game like after the attack on the citadel i believe
Actually, they are SUPPOSED to banter much earlier and through out the game. The reason you only saw it later was that you can only buddy up to Ashley after she joins the Normandy, and the bug connected a check to Ashley for who-knows-why.Priisus wrote...
So to trigger our lovely engineers
together... I need to be nice to Ashley throughout the game? I hope this
does not mean that Shep has to romance Ashley.. If not I'm screwed -
the only playthrough I have Ash alive is with a femShep Sentinel
You don't need to romance Ashley, but you do need to speak with her a bunch. However, romancing her definitely enables the banter. Basically the erroneous check is "Is Ashley a good friend?" and your true love is automatically considered to be a close friend.
Dusty Everman wrote...
CptData wrote...
By the way, Dusty, is Ashley's content bugged too?
As far as I know, Ashley's content is not bugged. Are you seeing something wrong?
Dusty Everman wrote...
I’ve heard a couple people ask that if a fix is easy, why would a patch be difficult? That’s a very good question. Here are a few reasons why.
1. Fixing a bug could accidentally introduce worse bugs.
The Gabby/Ken bug is a great example of this. It turns out that just before ship QA found a bug where an Ashley dialog on the Citadel could get stuck under certain import/game mode situations. The person who fixed that bug unknowing introduced the Gabby/Ken bug, and this was after Gabby/Ken had been tested. The Ashley fix was tested on the Citadel, but of course the whole game of 30+ hours with many import and choice variations can’t be retested for every small change. That portion of the Normandy wasn’t retested because we believed it hadn’t been changed and was solid.
2. There can be technical issues.
In this case, the bug was introduced in a tool we call Story Manager. As of today, changes in Story Manager content can’t really be put into a patch due to some technical limitations. Our programmers are fixing those limitations, but until that work is actually successful, we can’t be 100% sure that Story Manager fixes can happen.
3. Content fixes in DLC bloat downloads.
Sometimes we can do fixes in the content instead of the code. However, this adds to the size of download on your disk, and due to how the content is structured, you don’t just get the fix. You get a copy of a bunch of other stuff, so depending on the situation, the amount added could be large.
4. The people who notice the fix may be so small as to not offset the risks and costs of a fix.
For example with the Ken/Gabby bug, the only people who notice that bug are those that imported a save game from ME2 where Ken and Gabby survived the Collector base, and they care enough about Ken and Gabby to recruit them again and go down and visit them in engineering. Though I’d like to believe that is a huge number of people, truthfully it’s probably a small fraction of the players. As with everything in life, our resources aren’t infinite, so we need to make judgment calls of were to apply our QA and development efforts.
I’m in no way saying that the Ken/Gabby bug won’t be fixed. Actually, I’m more encouraged than ever that the fix will get put into a future patch or DLC. We just can’t make any promises. I just wanted to shed some light on why knowing about a fix isn’t the same as being able to deliver a fix. I know that any answer that isn’t “We will fix 100% of the known bugs” will make some people angry, and I apologize for that. If we followed that, it would be impossible for us to make a large, rich game for you. I can say that everyone on our team cares deeply about the quality of experience we are providing to you. We do try our best.
And here is the original thread:
http://social.biowar...ndex/10147092/1
Retour en haut
