A good portion of that comes from how the teams are treated by EA and how many resources they’re granted though. I’m not about to assign a percentage to the blame, but of course the DA folks will be resentful of the ME folks if EA listens to one of them and gives them the time and money they ask for at the expense of the other. “Knowing how to negotiate” can often just come down to how much one game sold versus another, which isn’t really something the developers are responsible for.
But even that is a mess of causality for blame. EA wants to save money and mandates a nightmare of an engine for development; managers get incentives from EA to build a type of game that their studio doesn’t usually make; etc.
I could argue in favour of EA’s decision regarding the engine. Their previous engine was also a mess, but they mishandled the change. They didn’t give the studios the necessary time or support to implement it properly. But at the time of Veilguard they already had plenty of experience, the game performs really well and they release the game practically bug free.
The part of EA forcing them to build a type of game that they didn’t usually make I’m particularly not inclining to believe it’s was a problem. Bioware developed and maintain Star Wars Old Republic, an MMO, MMOs have many similarities to live services(it’s a type of live service), they already had experience with that. They also released Anthem, and looks like the idea of a multiplayer for Anthem came from Bioware.
The idea of a multiplayer Dragon age to finish the story is completely stupid but Bioware had the expertise to work on it. It’s a different case for Fallout 76 as Bethesda has never developed a multiplayer game before, TESO is a completely different studio with its own team, SWTOR is from a team within Bioware.
A good portion of that comes from how the teams are treated by EA and how many resources they’re granted though. I’m not about to assign a percentage to the blame, but of course the DA folks will be resentful of the ME folks if EA listens to one of them and gives them the time and money they ask for at the expense of the other. “Knowing how to negotiate” can often just come down to how much one game sold versus another, which isn’t really something the developers are responsible for.
I could believe that if they didn’t have a history of poor management and lack of leadership and unified vision as demonstrated during the Anthem development.
But even that is a mess of causality for blame. EA wants to save money and mandates a nightmare of an engine for development; managers get incentives from EA to build a type of game that their studio doesn’t usually make; etc.
I could argue in favour of EA’s decision regarding the engine. Their previous engine was also a mess, but they mishandled the change. They didn’t give the studios the necessary time or support to implement it properly. But at the time of Veilguard they already had plenty of experience, the game performs really well and they release the game practically bug free.
The part of EA forcing them to build a type of game that they didn’t usually make I’m particularly not inclining to believe it’s was a problem. Bioware developed and maintain Star Wars Old Republic, an MMO, MMOs have many similarities to live services(it’s a type of live service), they already had experience with that. They also released Anthem, and looks like the idea of a multiplayer for Anthem came from Bioware.
The idea of a multiplayer Dragon age to finish the story is completely stupid but Bioware had the expertise to work on it. It’s a different case for Fallout 76 as Bethesda has never developed a multiplayer game before, TESO is a completely different studio with its own team, SWTOR is from a team within Bioware.