339 réponses à ce sujet

[RiflemanUK]

I don't understand people that tell others to get a life for noticing things like this, I mean, you're the ones reading a video game forum. In reality they have just as much of a life, they just happen to care about different things.

[InvincibleHero]

Saphra Deden wrote...

Sylvf wrote...

We actually noticed this one. Ash and Kaidan's recording sessions were over by the time we had finalized art and realized that at the distance we could see the ship, there was no way it should be a dreadnought. Unfortunate, but there wasn't much we could do.

(I don't comment on this kind of thing too often, but it bothered one of our other writers quite a bit so I'd like to stick up on his behalf.)

You guys just can't get this kind of thing right, can you? I mean you botched the whole dreadnaught thing in ME1 too.

Sheesh.

I hope we get a bandaid codex entry later that describes how the dreadnaught lost on Earth was a one-of-a-kind with a new mass effect core or something that let it land on planets.

Come to think of it it was referred to as the dreadnaught not by title. Earth only has a dozen maybe 2 tops so really they should know of any in their area by name. Maybe it was hot off the assembly line with new anti-grav floaters installed.  Anyway it is a minor issue to me as technically it didn't land until it was blown up.

[littlezack]

Saphra Deden wrote...

Sylvf wrote...

We actually noticed this one. Ash and Kaidan's recording sessions were over by the time we had finalized art and realized that at the distance we could see the ship, there was no way it should be a dreadnought. Unfortunate, but there wasn't much we could do.

(I don't comment on this kind of thing too often, but it bothered one of our other writers quite a bit so I'd like to stick up on his behalf.)

You guys just can't get this kind of thing right, can you? I mean you botched the whole dreadnaught thing in ME1 too.

Sheesh.

I hope we get a bandaid codex entry later that describes how the dreadnaught lost on Earth was a one-of-a-kind with a new mass effect core or something that let it land on planets.

They made a mistake. They admit they made a mistake. Why do they need to make some kind of retcon to the codex just to cover it up?

[vader da slayer]

Saphra Deden wrote...

InvincibleHero wrote...

Anyway it is a minor issue to me as technically it didn't land until it was blown up.

Being anywhere near the surface/within the atmosphere should be impossible. Dreadnoughts just aren't designed for that kind of thing. There's no way it would have enough thrust to stay in the air and not just crash down to the surface.

One of the things ME2 actually got right was the way the Collector ship took off from Horizon. It was basically a big rocket-ship.

go to the thread listing (where you click to come into this thread) and click on the Bioware link below this thread and read what they had to say. the voice overs for Ashely and Kaiden were done at the point this scene was written up in the game and they couldn't go back and fix what Ash/kaiden say. They realized that it is indeed an error but not before they got to a point of no return.

Modifié par vader da slayer, 16 février 2012 - 07:06 .

[littlezack]

 He knows about that. He doesn't care.

[Gemini1179]

Saphra Deden wrote...

One of the things ME2 actually got right was the way the Collector ship took off from Horizon. It was basically a big rocket-ship.

And yet none of the Barney Fife investigation teams were able to find the half-kilometre in diameter crater at any of the other planets where colonists were taken. Or Collector footprints either. I didn't seen anyone sweeping up after themselves in Veetor's footage... but ME2 was great if you didn't think about the plot and story... maybe that's a good way to go into ME3 after all...

[Gemini1179]

Saphra Deden wrote...

littlezack wrote...

 He knows about that. He doesn't care.

It doesn't change anything is the point. It's still a goof.

It's not even a huge deal, but it is pretty funny that they managed to screw this up again.

They need their own Leeland Chee- I volunteer. Wait, is he still doing it for Lucas?

[InvincibleHero]

Saphra Deden wrote...

InvincibleHero wrote...

Anyway it is a minor issue to me as technically it didn't land until it was blown up.

Being anywhere near the surface/within the atmosphere should be impossible. Dreadnoughts just aren't designed for that kind of thing. There's no way it would have enough thrust to stay in the air and not just crash down to the surface.

One of the things ME2 actually got right was the way the Collector ship took off from Horizon. It was basically a big rocket-ship.

I would have to disagree because it is not the same. They have hot engines with less inertia already being airborne. Liftoff takes much more to achieve. It didn't seem too manueverable just hovering so it might have taken most of the engine capacity just to maintain.

Besides it was just a script error and not actually a dread being depicted.

[littlezack]

Saphra Deden wrote...

littlezack wrote...

 He knows about that. He doesn't care.

It doesn't change anything is the point. It's still a goof.

It's not even a huge deal, but it is pretty funny that they managed to screw this up again.

It must be a huge deal, because quite a few people are acting like it is.

[ZDPhoenix]

Baryonic_Member wrote...
Anyone else bothered how unserious BioWare seem to be about consistency? 

I'm more bothered by your snarkiness, honestly.

They're the tellers of this tale. They're allowed to change whatever they want to.

[Inquisitor Recon]

The question of if a dreadnought could hover in atmosphere like that is moot. The real question is why the hell an experienced captain commanding one of the System Alliance's few capital warships decide to bring it down in atmosphere, right in the middle of a city, and then slug it out with a reaper head on?

As for the claim that a single hit from a reaper could destroy a dreadnought, clearly their lethality was overstated. If reapers could kill any warship like that there would simply be no chance to defeat them.

The bigger question is how the hell did the reapers destroy what could possibly be upwards of 50% of the Systems Alliance Navy in seconds. Quickly enough where Hackett or somebody couldn't send message down stating the obvious "we are getting our asses kicked". Even for the reapers that whole sequence of events moved too fast IMHO. Moving from the edge of the solar system, destroying a large fleet, and starting to vaporize some random city has got to take more than three minutes.

Even without comms from Hackett how could this naval station/military base/wherever Shepard was on the ground have no idea what's going on in orbit and in the immediate space around Earth. If they don't have the slightest idea of what's going on in this massive battle above them, how the hell can the Systems Alliance do simple air control duties and track the routine movements of hundreds of cargo, passenger, and military ships?

Maybe the battle took place farther out from Earth, but the cutscene at the start of the demo made it looked like the fleet was assembled damn close.

Conclusion: The Systems Alliance is incompetent. Senior commanders who made minimum preperations almost shat themselves before the reapers crushed them with their own oversized desk.

Modifié par ReconTeam, 16 février 2012 - 07:38 .

[InvincibleHero]

ZDPhoenix wrote...

Baryonic_Member wrote...
Anyone else bothered how unserious BioWare seem to be about consistency? 

I'm more bothered by your snarkiness, honestly.

They're the tellers of this tale. They're allowed to change whatever they want to.

While I agree with your sentiment they should not abuse the trust overmuch. If they were too inconsistent and made huge changes then people should be rightly upset and or turned off of the property.

Modifié par InvincibleHero, 16 février 2012 - 07:51 .

[Gonder]

Meh, atleast that oversized explosion made up for It.

[Lotion Soronarr]

Saphra Deden wrote...

Gemini1179 wrote...

And yet none of the Barney Fife investigation teams were able to find the half-kilometre in diameter crater at any of the other planets where colonists were taken. Or Collector footprints either. I didn't seen anyone sweeping up after themselves in Veetor's footage... but ME2 was great if you didn't think about the plot and story... maybe that's a good way to go into ME3 after all...

I was trying to throw the devs a bone and you had to go and ruin it.

The dreadnought thing is stupid, as I've said many times before. Does it break the game? No. It's one line of dialog and then we can forget about it.

Agreed. You cna even SEE it's a cruiser. No biggie.
There ar FAR bigger problems to tackle.

[Hunter of Legends]

Lotion Soronnar wrote...

Saphra Deden wrote...

Gemini1179 wrote...

And yet none of the Barney Fife investigation teams were able to find the half-kilometre in diameter crater at any of the other planets where colonists were taken. Or Collector footprints either. I didn't seen anyone sweeping up after themselves in Veetor's footage... but ME2 was great if you didn't think about the plot and story... maybe that's a good way to go into ME3 after all...

I was trying to throw the devs a bone and you had to go and ruin it.

The dreadnought thing is stupid, as I've said many times before. Does it break the game? No. It's one line of dialog and then we can forget about it.

Agreed. You cna even SEE it's a cruiser. No biggie.
There ar FAR bigger problems to tackle.

Agreed.

[Kakistos_]

Mistakes happen and I'm glad that Bioware acknowledged it. I am more worried that other glaring discrepancies like Asari mind control and the thermal clips explanation bleeding over into ME3.

[Labrev]

I thought they were referring to the Reaper as the dreadnought tbh.

[Denethar]

I think that when they give an honest answer and explains what went wrong, people could perhaps stop jumping down their throat about it. Lore is important, sure, but things go wrong at times in productions this big....get over it people.

[Lotion Soronarr]

Again, Bioware explain it's an error (similar to the lack of DN's in the Citadel fleet), we cna SEE ti's a different model (cruiser). No biggie.

Thus, canonicly, that's a cruiser, not a dreadnought.
Problem solves, crysis averted...

Let's focus on more serious issues.

Like the Alliance having no clue about a reaper fleet in orbit???
Normandy howering for an eternity sorounded by reapers.
Cheesy writing.
Idiot balls and so forth.

Modifié par Lotion Soronnar, 16 février 2012 - 08:59 .

[StarcloudSWG]

The ship model is actually a cruiser, isn't it? Then again, it's hard to tell, because Alliance capital ships seem to be built to the same plan, just at different scales.

[Candidate 88766]

Saphra Deden wrote...

InvincibleHero wrote...

Anyway it is a minor issue to me as technically it didn't land until it was blown up.

Being anywhere near the surface/within the atmosphere should be impossible. Dreadnoughts just aren't designed for that kind of thing. There's no way it would have enough thrust to stay in the air and not just crash down to the surface.

One of the things ME2 actually got right was the way the Collector ship took off from Horizon. It was basically a big rocket-ship.

For once, mass effect fields really are the answer. Dreadnoughts can generate a field strong enough to lower the ship's mass to the point that it can travel faster than light. There's no reason ME fields can't lower the ships mass enough that its engines can support it - it would take far less energy to lower a ship's mass to this point than to lower it enough that it can travel at FTL speeds.