Game engine limitations?
Apologies in advance if this I has already been answered or is obvious but I haven’t played the game since before Xmas nor can I bring myself to boot the game back up. I’m genuinely curious as ...
Forum Discussion
@CountSero At its core it’s still just a frostbite engine that was not particularly great when it first came out.
BioWare stated many times when working with the engine that it was “poorly documented and hacked together,
BioWare stated many times when working with the engine that it was “poorly documented and hacked together,
@emerson1975 Yeah, the name is still a Frostbyte engine and yes, it is a complex engine but it is not the engine from Bad Company anymore. (As Unreal Engine ist not the Unreal Engine back from 1998...)
Yeah, i know what BioWare has stated but Poor Documentation and Structure don't say that this is a bad engine. It shows a problem of bad management and the fluctuation in employees which causes such problems. If you give the developers the freedom to create a documentation and tutorials then the next generation of developers have much easier task to work with it.
But the problem there is that EA give the DICE enough time or money for a good development for an engine.
Also, that EA has given the Order to use the Frostbyte for every game was a bad decision.
And after Mass Effect: Andromeda and Anthem they should pull the plug because at this point the development of additional feature needed for RPGs games has pulled to many resources from DICE or other studios which where more needed for the development of the games.
Also, after Mass Effect Andromeda people left BioWare and they lost track of many things and then things getting worse.
The same problem had DICE with BF 1 and BF V (to many resources bound for different EA projects instead of their own)
So, the engine itself is OK but complex and to make good games with it, you need time and capable people. So, EA made the wrong decision and didn’t build a good structure to handle all projects with the Frostbyte engine.
Yeah, i know what BioWare has stated but Poor Documentation and Structure don't say that this is a bad engine. It shows a problem of bad management and the fluctuation in employees which causes such problems. If you give the developers the freedom to create a documentation and tutorials then the next generation of developers have much easier task to work with it.
But the problem there is that EA give the DICE enough time or money for a good development for an engine.
Also, that EA has given the Order to use the Frostbyte for every game was a bad decision.
And after Mass Effect: Andromeda and Anthem they should pull the plug because at this point the development of additional feature needed for RPGs games has pulled to many resources from DICE or other studios which where more needed for the development of the games.
Also, after Mass Effect Andromeda people left BioWare and they lost track of many things and then things getting worse.
The same problem had DICE with BF 1 and BF V (to many resources bound for different EA projects instead of their own)
So, the engine itself is OK but complex and to make good games with it, you need time and capable people. So, EA made the wrong decision and didn’t build a good structure to handle all projects with the Frostbyte engine.
