iamvin22
Industry Verified
Wow. complete meltdown.
Where is all the proof about the "origin deals"? He acts like its a fact. Crazy....
thats nothing compared to some other tube members. i can link if you can stomach it.
Wow. complete meltdown.
Where is all the proof about the "origin deals"? He acts like its a fact. Crazy....
CPU-wise, probably. GPU wise, in real-world performance, likely not for years.Mobiles are probably going to outpower Wii U very soon.
..For a certain definition of 'very soon'.Mobiles are probably going to outpower Wii U very soon.
Just saw that, hilarious and sad. Should've duct tapped a cell phone to it, would've ran frostbite.
This is hyperbole. EA is making a mobile port of Frostbite, but we have no idea what that engine will be capable of. What EA said about WiiU was that Frostbite engine on the WiiU did not run current or next-gen console games feasibly. And obviously, the WiiU install base does not warrant a ground-up redevelopment of titles to fit WiiU.
The Mobile situation couldn't be more different. Not only is the install base huge, but they are not expected to 1-to-1 port current or next gen games to mobiles (it's not even possible due to input constraints). They won't have to test and see whether BF3 runs on Nexus 4 or not. They'll port the engine and make the best game they can. And they have enough customers to do that.
..For a certain definition of 'very soon'.
Argyle, I posted the PPE SMT results. Improvement is ~29%. Yes, I did overlook one 'small' detail when assessing the original code, which made me undeservedly skeptical re SMT@PPE.
Yes. Basically the multiplier goes from 2.7 (single-threaded) to 3.47 (SMT) per core. Just keep in mind the (projected) Espresso results are not optimal either (remember we're testing the compiler's performance as much as the CPU's), whereas the SMT boost that PPE gets is pretty much what IBM's own manual projects as SMT gain.Interesting - so it comes out around 3.47x faster than the projected performance of an Espresso core?
I believe it was in the old WUST when we still had little idea what UCPU was, back then a few posters were discussing the meaning of the rumors that nintendo was aiming for easy ps360 portability. There I said that in my eyes those rumors implied UCPU had to meet Xenon's sustainable SIMD throughout. Fast forward to today. Clearly nintendo got the GPU covered (the jury is still out about the margins), but CPU FLOPS-wise they fell short. They could have addressed that via wider SIMD or more cores, if we assume upclocking Espresso further was not viable. Does that make WiiU less of a console? I don't think so - I judge hw mostly on its own merits, how well it meets its own bar, what hurdles devs have to go through to get it to do this or that advertised metric. Does it affect WiiU's reception of ps360 flagman ports, though? It likely does. Do I think that the original statement of FB2 not running well on WiiU was actually justified? No. If they meant to say such-and-such game they should have said that.I really wish Nintendo had at least decided to match 360 level performance on the CPU - I would have seriously considered picking up a WiiU last year and been reasonably happy with the best version of any multiplatform game (and it probably would have gotten more ports if there was enough performance to make ports from 360 trivial). Honestly I thought that was going to be their strategy for the WiiU when they announced it...at least it made sense to me
Do I think that the original statement of FB2 not running well on WiiU was actually justified? No. If they meant to say such-and-such game they should have said that.
I don't feel like explaining what an engine running well on a hw means. Engines are software and as any software they get ported, are subject to evaluation how well they run, etc. As for the rest, what they obviously did and what they obviously said are apparently different things in this thread. Perhaps why semantics is fairly essential part of human communication. Good luck trying to communicate anything without caring about semantics.What the hell does it even mean that an engine 'runs well' on a hardware? They did not have to specify games, there are a handful of FB2 games on the market and they obviously tried porting one, and did not like the result. What's up with the semantics argument here?
I don't feel like explaining what an engine running well on a hw means. Engines are software and as any software they get ported, are subject to evaluation how well they run, etc. As for the rest, what they obviously did and what they obviously said are apparently different things in this thread. Perhaps why semantics is fairly essential part of human communication. Good luck trying to communicate anything without caring about semantics.
Consider yourself spared. I'm not in an educational mood today.Oh please spare me. You know very well that an engine 'running well' on a hardware in a vacuum means shit.
And yet you come back to argue some more. Oh the irony.You take something they said, isolate it from the context, argue for pages on this thread that what they say is wrong, then try to wash your hands clean of it by conceding solely that they should have explained their context better (which was pretty evident as is)? Thank you but I don't need the good luck, I just know when to stop arguing with this kind of behaviour.
So if CoD and the like sold a bajillion EA still would have skipped the Wii U because they hate Nintendo more than they love money?
Wii U owners would probably settle for up-ports of phone games, though, given the game situation.Eh. Its Frostbite Mobile, not Frostbite 3. Its like comparing UE 3 web CE 3 Mobile to U4 or CE 3.5.
Indeed. About that context:I agree with hooijdonk17: FB, as in the engine, could probably "run well" on cell phones, and also on Wii U. However, this fact is meaningless in context -- which is also a very important factor in human communication.
Which entries from DICE's lineup of PC and console games do you expect to run well on the just announced FB mobile (assuming the latter is actually meant for mobiles)?And the only meaningful context for porting FB to a new home console platform is porting home console games based on FB to that platform. Thus, if they don't run well, then neither does the engine, for all meaningful purposes.
None. But it's not the same context. They aren't planning to port console games to mobiles, and they weren't trying to run mobile games on Wii U.Which entries from DICE's lineup of PC and console games do you expect to run well on the just announced FB mobile (assuming the latter is actually meant for mobiles)?
None. But it's not the same context. They aren't planning to port console games to mobiles, and they weren't trying to run mobile games on Wii U.
But it seems like it is meaningless to discuss this topic with you, for some reason you seem to have a major hangup about it.
Ok, perhaps I asked you the wrong question. Let me try again: can you guarantee that any FB2 game, present and future, originating from the PC and console alike, will not be technically portable to the WiiU? And I didn't catch your response re the apparent context in that twitter exchange.None. But it's not the same context. They aren't planning to port console games to mobiles, and they weren't trying to run mobile games on Wii U.
Perhaps my 'hangup' stems from the fact from my POV evaluating an engine and evaluating a title on a candidate platform are not the same thing.But it seems like it is meaningless to discuss this topic with you, for some reason you seem to have a major hangup about it.
Ok, perhaps I asked you the wrong question. Let me try again: can you guarantee that any FB2 game, present and future, originating from the PC and console alike, will not be technically portable to the WiiU? And I didn't catch your response re the apparent context in that twitter exchange.
Ok, perhaps I asked you the wrong question. Let me try again: can you guarantee that any FB2 game, present and future, originating from the PC and console alike, will not be technically portable to the WiiU? And I didn't catch your response re the apparent context in that twitter exchange.
My question wasn't about what EA might or might not decide, though. It was about technical feasibility.For Frostbite 2 yes we can probably guarantee that Unless EA decides to release ports of MOH Warfighter and Army of Two this fall...
"The game"? Which game is that?What defines an engine running well on a system is if it could run games well without major cut backs or massive rewriting to bypass something the hardware does slowly.
Trying to take the game out of the question pointless, you might as well claim that anything that has enough RAM to load the engine binaries is running the engine, no matter if all it can at interactive frame rates is rasterize a single polygon!
My question wasn't about what EA might or might not decide, though. It was about technical feasibility.
its odd that they'll bring Frostbite to iOS and other mobile devices but not nintendo
It's not the same as FB2 or 3.
EA decide what games are technically portable to the WiiU?Well, it kinda does depend on what EA might or might not decide, as they are the ones who decide what games get made (present and future!) on Frostbite 2, don't you think?
Just a question. So what happens then IF they decide to make a Wii U version of a game that runs on Frostbite 3.
What engine will they use, and if that less expensive to strip an engine out and replace it, rather then actually make sure the engine they are going to use for their games also works on Wii U.
"The game"? Which game is that?
Engine feasibility on a given platform is a subject of and in itself. Every function or feature in an engine has an associated cost, which might or might not be constant. We used to collect megabytes of statistical data on my prev job entirely focusing on our engine's associated perf costs on new platforms. That could tells us if feature X is perfectly fine, while feature Y is prohibitively expensive, or feature Z is a simple no-no. That data was never collected from any given game - that data was collected from engine unit tests.
Wii U owners would probably settle for up-ports of phone games, though, given the game situation.