@Xx-Gimmle-xX, it depends on the type of bug. A error you might see with the level itself for example (of which I've seen at least 2 with Andromeda) would require fixing in the SDK or taking the level back in to Maya or Max to fix.
Task / quest / whatever you want to call them bugs are pure and simple scripting errors that for a good scripter usually are not difficult to fix. The only people familiar with Frostbite 3 will be the ones who have the SDK tools to work with it so I can't say how easy it would be to address the issue of having to be face to face with a NPC to talk to them but from working with other engines this is not something that should ever be a problem anyway which says to me only being able to talk to a NPC when you are face to face with them was a deliberate design decision, which given there are a bunch of NPCs that lean against railings and things like that, was a pretty stupid one.
A good deal of audio errors are more than likely down to poor scripting as well, lets take for example the "Safe Travels" task that has you eventually landing on Kadara to fight the pirates in the badlands, once you reach the pirates location you get a short dialog, if you then kill all the pirates, accomplish what you have to do at this location and then drive off, or hell leave the planet entirely you would expect that would be the last of that dialog, but no. If you visit this location again you will still get that initial bit of dialog because theres nothing in the script to tell the game that part of the task is complete and to not play the dialog again. You will encounter this problem MANY times with varying tasks and even story related missions, worse still, even after you complete these tasks / missions with some at least (if not all) you can go over a area that once had you needing to do something that also had some dialog and still get the piece of dialog that originally played even long after that task or mission is complete.
@ketxxx I totally agree on the sound bugs, it seems to me they didn't even think before they did these audio scripts and worse, they didn't even test it out correctly.
Another "problem" I have with this game is once you create an outpost on Eos lets say, you still run into a bunch of Kett all over the place, after you defeated their main base.
Now I can understand the idea of skirmishes here and there, the fact that defeating the kett is one of the main obstacles in getting the viability to 100% doesn't make sense that Kett are still around and in the same spots over and over and over and over (you get the point) again.
It's tedious and in fact very boring to fight them so many times, I just don't bother with them anymore.
Same thing goes for Havarl where you need to keep fighting those god damn creatures over and over again, and even though you finish Jaal's loyalty quest you still have Rokkar encounters (In this case they didn't really say what happened with them, or at least I didn't get to the point where they do, but come on...EVERY SINGLE TIME WE LAND THEY COME BACK TO THE SAME PLACE?).
and wasn't one of the quests in Havarl meant to make the animals less aggressive?? I am sure one of the quests had this in it.
@Xx-Gimmle-xX wrote:
@ketxxx I totally agree on the sound bugs, it seems to me they didn't even think before they did these audio scripts and worse, they didn't even test it out correctly.
Another "problem" I have with this game is once you create an outpost on Eos lets say, you still run into a bunch of Kett all over the place, after you defeated their main base.
Now I can understand the idea of skirmishes here and there, the fact that defeating the kett is one of the main obstacles in getting the viability to 100% doesn't make sense that Kett are still around and in the same spots over and over and over and over (you get the point) again.
That would actually _create_ bugs, you do realize? There are a few missions dependent on finding random sensor/bug/device in the kett outposts/camps.
I just ignore the kett too, I only stop to kill them if I have to because theres a objective there I need or something. Otherwise I'd rather just run them over, which as I covered a while ago, doesn't even work right in this game either... no doubt because the cannon fodder foot soldiers are bullet sponges. Even from point blank range with what is as far as I can tell the 2nd best shotgun in the game, the Asari Disciple (which the Asari themselves don't even use on their own Ark by the way Bioware.. they use the N7 shotgun.. another continuity problem) it takes FOUR blasts to kill a lowly kett foot soldier with just a red health bar. I don't care how dense their "bone armour" (which is purely aesthetic) is, it is not going to stand up to four bloody point blank shotgun blasts.
I guess we will know if anyone at Bioware read this thread in the next patch or two. Unbelievable this game got released in the state it is. Utter waste of £37, but it yet might be a salvageable mess based on how much fixing it gets, and how many good DLCs are released as a "We're sorry" statement.
@arthurh3535, no, it wouldn't. A lot of tasks that are linked to these random scattering of enemies are also random in their spawn placement as well. I've lost count of the amount of times I've cleared a area out, picked up a task with a random spawn spawn at a area I've already cleared and just walked right in, grabbed / blew up what I needed, then walked right out again. These tasks needed structure to make the game better, they have no structure at all and painfully obviously just use a math.random variable in the script.
And... yeah, you are just being whiny because it isn't perfect with no bugs at this point. Those devices spawn with the Kett, so removing the Kett entirely after taking out the bases would break those missions.
@arthurh3535, I already gave you a dumbed down easy to understand reply, do I really have to dumb it down to picture book level? Nobody is complaining because the game isn't perfect, people are complaining because this game is a complete mess and obviously got shoved out at least 6 months before it was ready.
Now to essentially dumb things down to picture book level...
Player kills kett at small outpost / barricade > player picks up task with random spawn locations > ends up at area already cleared, just walks in, grabs / blows up objective, walks out. End result: No structure to task at all, akin to a auto-generated "busywork" task. Does this scenario cause bugs? No. Is the task boring and may as well been left out entirely? Yes. If you are going to do a auto-generate type task you at least have the objective spawn at bigger locations and respawn enemies to make the task more interesting and give it the illusion of being something meaningful. It is easy to script things like this.
How many times has everybody ended up at some random pile of debris / rubble in tasks like this to pick up a out of place datapad or blow up a out of place vase looking thing or scan some out of place spawned object? I personally have encountered it with almost every busywork task. It is so easy to spawn objects at locations that make even a busywork task feel important even though its not the level of effort to do so is barely above lazily throwing in a math.random variable (or equivalent depending which scripting language you are using, my example comes from LUA) in the script.
