Quote:
|
Originally Posted by Duke_Wellington_1st
Great Thread.
I do not uderstand those voices that seem to support companies that sell faulty and unfinished products. Sure the Sub simulation genre is fairly bare.... but no reason to support publishers that rush release dates and fail to deliver what they advertise. That sort of behaviour should not be tolerated in any industry.
|
Look, the thing is, how do you know they "rushed" the release date? Do you think they contracted the dev team without a time shedule set out beforehand and then all of a sudden one day broke through the door saying "All right, everyone STOP! We are going to publish now."? Publishing a software product on a worldwide scale, with buying shelf space in advance etc. is not something you do over a weekend. And sure enough when the publisher asks "So, when will it be done? We would like to see it on shelves in a year." the notion the devs could just answer back "It'll be done when it's done." is laughable. You won't find any publisher by doing so. This is what modders can do when there is no money involved, but not when you are in business.
So you gota make contracts and set priorities in developement to ensure you STICK to what you SIGNED and be able to deliver a working product on release date. Features described in the manual but totally absent in the product (like properly working radar, chronometer, map notes, and may I say convoys NOT stopping waiting to be torpedoed is also essential for a subsim and shouldn't even need to be mentioned, and bugs that weren't there in SHIII) is NOT acceptable and surely NOT the fault of the publisher. The devs build the game, not the publisher. And now, the publisher has already allowed for two more patches. The devs had two more patches to fix things, but were unable to complete it.
Of course Ubisoft gets the blame and rage of the customer for that - which is proper from the customer's perspective, since the publisher is his direct other contracting party - but the only thing the publisher will do when being "dropped" by the customer is drop HIS contracting party, the dev team. And it doesn't matter whether that's an in-house or external team.
So, all this "BOYCOTT / SUE UBI!" is not only half of the story, but if you think the devs are not to blame for any of that and want to see them stay in business it won't be helpfull to that cause at all.