Next gen EA games will skip the Wii U due to Frostbite Engine

[ZaeZae64]

oh no all those games I wasn't going to buy in the first place )':

I'm sure you know better than the EA Techies.






(What I actually mean is that you're accusing them without proof, and that's slander)

Aint the first time EA lied about something.

 

[KingVamp]

I'll just place this here.

 

[Coto]

EA VS Wii U, who's doomed first

 

[2ndApex]

RIP Nintendo

 

[WiiUBricker]

What's up with those nazi puns lately?

 

[Deleted_171835]

I'm sure you know better than the EA Techies.






(What I actually mean is that you're accusing them without proof, and that's slander)

>Frostbite 3 supports the PS3/360
>Wii U is more powerful than the PS3/360

Ergo, Frosbite 3 can run on the Wii U. The only sensible reason to skip out on the platform is because of the install-base.

 

[Joe88]

next gen ea games are skipping wii u because its not next gen

 

[Snailface]

2011-The 3ds is Dead
2013-OMG its coming back, best year ever!

2013-The WiiU is Dead
2015-OMG its coming back, best year ever!

Conclusion:
Gamers = Historical Amnesia + Micheal Pachter's vision

 

[DiscostewSM]

next gen ea games are skipping wii u because its not next gen

Yet many of those games utilizing FB3 are coming to last-gen systems? Besides, I wonder how many people have looked back at E3 2011 when EA wholeheartedly supported the Wii U, which they did mention as next-gen.

 

[Foxi4]

>Frostbite 3 supports the PS3/360
>Wii U is more powerful than the PS3/360

Ergo, Frosbite 3 can run on the Wii U. The only sensible reason to skip out on the platform is because of the install-base.

That's the most upside-down logic I've ever heard - there can be an inheritent flaw in the WiiU's SDK that makes it impossible to port the engine, hardware has nothing to do with this.

 

[DiscostewSM]

Does FB2 not work on Wii U? Perhaps, but seeing EA's rather potent flip-flopping over the past year with regards to Nintendo and Wii U, I'm not so sure about it anymore.

 

[Deleted_171835]

That's the most upside-down logic I've ever heard - there can be an inheritent flaw in the WiiU's SDK that makes it impossible to port the engine, hardware has nothing to do with this.

Even if there was somehow a major flaw in the SDK that prevented them from bringing over the engine, they could have contacted Nintendo for support in overcoming the issue or updating the SDK to resolve it. Something like that could easily be rectified.

Fact of the matter is, if EA wanted to bring Frostbite 3 to the Wii U, they could. They simply decided that it wasn't worth putting time and money into, likely because of how the Wii U is selling right now.

 

[Foxi4]

Even if there was somehow a major flaw in the SDK that prevented them from bringing over the engine, they could have contacted Nintendo for support in overcoming the issue or updating the SDK to resolve it. Something like that could easily be rectified.

Fact of the matter is, if EA wanted to bring Frostbite 3 to the Wii U, they could. They simply decided that it wasn't worth putting time and money into, likely because of how the Wii U is selling right now.

...or they cannot for technical reasons and you cannot prove otherwise without proof - what you're saying is conjuncture. They're not coding for the system in binary - they're using the kit and if the kit doesn't have certain functionality, they're not working on porting the engine. Sure, there maybe some more to it, but we don't know what that might be - we're just speculating.

 

[Rizsparky]

I'll just place this here.

This man talk the truth!

 

[Eerpow]

It's probably not worth the investment they need to put in to optimize the engine, if just putting it on the system as is isn't possible then they're obviously not going to put in money and effort looking deeper into it. As a developer you make your games multiplatform to generate profit, however in the case of the Wii U the margin between porting costs and sales isn't good enough to invest in the system, this is something that won't change until Nintendo manages to change the Wii U sales situation.

EA already put out some games for the system to serve as sales tests, seeing the currently low sales of the system it wouldn't surprise me if they didn't generate much if any profit with those titles. This decision won't change unless the install base of the platform grows or Nintendo decides to give them a hand by either sending them their own teams who knows the hardware or by simply giving them money so that EA themselves can make good ports for the system. A lot is up to Nintendo to show if they're capable of turning things around.

 

[Deleted_171835]

...or they cannot for technical reasons and you cannot prove otherwise without proof - what you're saying is conjuncture. They're not coding for the system in binary - they're using the kit and if the kit doesn't have certain functionality, they're not working on porting the engine. Sure, there maybe some more to it, but we don't know what that might be - we're just speculating.

Like what?

It's not an issue with horsepower as the Wii U is at least more powerful than the PS3/360.
It's not an issue with the feature set as the Wii U has a more modern feature set than the PS3/360.
It's not an issue with the SDK as EA could easily rectify such a problem by contacting Nintendo for support if they were really deadset on bringing the engine over.

So unless the Wii U is lacking in some special sauce that the PS3/360 have and we're not aware of, common-sense says that they're not bringing it over because of sales. That's pretty much it.

 

[shakirmoledina]

nintendo has dropped support for wii u because its engine cannot support its own hardware...

ea ... lazy devs, all of them

 

[Foxi4]

Like what?

It's not an issue with horsepower as the Wii U is at least more powerful than the PS3/360.
It's not an issue with the feature set as the Wii U has a more modern feature set than the PS3/360.
It's not an issue with the SDK as EA could easily rectify such a problem by contacting Nintendo for support if they were really deadset on bringing the engine over.

So unless the Wii U is lacking in some special sauce that the PS3/360 have and we're not aware of, common-sense says that they're not bringing it over because of sales. That's pretty much it.

You can have the best components in the world but if you put them together with spit, it's just not going to work. Do take into account the way the WiiU's CPU works - it's a custom architecture that does lack several contemporary features - it's by no means a beefy processor.

 

[DSGamer64]

This makes no sense. The current gen consoles can run the frostbite engine (very poorly tho), so why can't the wiiu? Is EA implying that the WiiU is inferior to those consoles hardware-wise?

Because EA fucking sucks and they are crybabies who don't want to utilize the hardware at their disposal. Nintendo told them to fuck off with Origin integration into their infrastructure as well. EA required you to log into Origin when you first created a new game in Mass Effect 3 on the Wii U. Question, why would a game that doesn't have both it's predecessors on the platform, have to have an Origin log in? Do they expect you to carry over non existent save files from the previous games? Because those games aren't available and it just screamed DRM to me. You don't have to log into Origin on the Wii U version in order to play the game, though to access the DLC you might, I didn't own the game long enough to even try.

 

[Eerpow]

To believe that it's actually a technical issue is the far more far fetched theory. There's no way EA would have put that kind of money towards Wii U hardware/infrastructure/SDK research when they know that it doesn't turn into profit with how things currently are going with the system. It's an excuse to not develop for the system, that said it's an understandable one.