Phaelducan wrote...
CulturalGeekGirl wrote...
Phaelducan wrote...
SennenScale wrote...
Phaelducan wrote...
Again, you are metagaming. Bioware would not have programmed lesbian = ok and gay = not ok. Male shep was not gay at the time of ME1 and ME2. If he was, the option would have been there, period. It's not an omission on the behalf of the programmers. No whoops moment here. If it was so, it would be coded, period.
They recorded the lines for it. Male Shepard had s/s lines.
They recorded S/S lines again in ME2, with male Shepard.
They've been asked why it wasn't included in the final product. They've said it was time constraints, I believe.
TIme constraints my left fore-tentacle. If it was recorded, they would have put it in the game if they wanted it there. Hence why it took modders so little time to get those scenes in the game.
You obviously known absolutely nothing about game design and release.
If something isn't 100% implemented, it doesn't go live. Period. If it's 78% done, it doesn't go in. I've seen CITIES burned to the ground, cities with months of work put into them, because they were only 50% done. Cities that were in the design document from day one, cast aside because you needed their teams to work on other content, content that was 90% done, and higher on the priorities list.
Time is time. If something's not finished, it can't go in. Time constraints are very real things. And deciding what gets crossed off that feature list is devastating and painful. So don't tell me "they would have put it in the game if they wanted it there." Game design does not work that way! Assuming that it does is... just beyond maddening. When a game comes out with partially implemented features, it's usually not because the devs "didn't want to put in" the full features. It's because of time.
Fail and fail. Things go in ALL THE TIME that aren't ready in AAA games. Look at the cinematics in ME2 when you go through the Omega-4. No way was that completely done, it was choppy as all hell.
In this case we are talking about a 2 minute cinematic with one character.... which was already animated for the other gender. The lines were recorded... and the animations were complete..... if you honestly say they cut s/s romances because they didn't have time, you are rocking the ganj.
Do the cinematics in ME2 cause your game to crash? Do they just suddenly stop for no reason? Implemented does not mean "completely perfect" it means
functional. Implementation comes first, then polish; while the cinematics in ME2 may not be polished, they were sure as heck
implemented. Sometimes things are released that are implemented but not polished. Sometimes QA misses bugs. it happens.
Fully implemented doesn't mean 100% perfect. It means "can be played through entirely without crashing, and has at least made it through a desultory QA test without any catastrophic bugs." This can include content that has bugs which QA missed. It often does. Sometimes QA would need 50 or hours to test every single possible permutations of a quest (Ok, what happens if I do this quest right after doing quest A? quest B? quest C? What if I go to town H before town G?) Some studios are more notorious for launching with gamestopping bugs than others, but pretty much everything in game probably went through QA at least once, and got approved.
Sometimes there are things cut from a game at launch that would take a developer only five or six days to finish implementing. The problem is, you can't pull five or six days out of nowhere, when you're already working 80 hour weeks. Having to scrap something that is tantalizingly close to being done is painful, but you can't work more than 120 hours a week without doing serious injury to yourself, and you can only work more than 100 hours a week for so long before you can feel your body start to die. Sometimes "5 days" or "40 hours" might as well be forever.
So yes, I can believe that getting Kaidan's m/m romance and Ash's f/f romance fully implemented might have taken one developer a week or so, and they just couldn't spare anyone for the extra week. It's also possible that midway through implementation, they discovered "Crap! The confrontation scene was only coded for two LIs. We'd have to completely redo that scene if we all three LIs are available. Crap crap crap! Guess we'll have to confine players to 2 LIs." And then someone facepalmed and s/s LIs were cut. There are a thousand possibilities, and I don't presume to tell you which one actually happened. But if you had ever worked in game development, you'd know how many things can contribute to a feature cut.
When a developer tells me something was cut because they didn't have time? And they invested enough cash in that feature to record VO lines for it? I believe them. If they never intended to put it in, having VAs record those lines would be a ludicrous waste of money. If there's VO for it, it was on the design document for a long, long time.
Modifié par CulturalGeekGirl, 18 mai 2011 - 11:40 .