| MDMAlliance said: I believe that quote came after he made the comment, but I cannot be too sure. However it is very likely that they're just making excuses because I don't know what UE3 has that MT Frameworks doesn't that makes it so difficult to make at least the version the phones use to put the UE3 on it. You're bringing up the programmable shaders, but I'll just come right out and say I have no idea what that means or how that seriously impacts the capability of making an engine work on a piece of hardware. Especially since the 3DS is such a big system now (sales wise), I don't know why the resources wont be worth using since it really can't be that much of a big deal. |
I'm pretty sure there's no technical reason that can't be overcome by enough economic incentives.
MT Frameworks is probably a skewed comparison, as it's an internal engine that Capcom could tailor exactly around their games and expand strictly along their requirements. Whereas UE tries to have a broader appeal and thus has to offer a more ductile feature set. For what we know, the MT Framework mobile used in 3DS might be an almost integral rewrite and does not even try to offer the same features - as a general purpose engine- of its bigger sibling.
i would not read too much into it: Epic come from the PC and they tend to stick to standard, general solutions. They might be wrong in their business choices when it comes to something like the 3DS that requires a dirtier, peculiar approach. But it's probably more about their experience and company culture than about any irrational resentment against Nintendo.
