TheMoon
Member
"What will release first, Kimishima-San? Mother 3 or NX?"
*Kimi puts on serious face*
"The NX is Mother 3."
Well, Mother 3 will be out come E3 so that question can be skipped
"What will release first, Kimishima-San? Mother 3 or NX?"
*Kimi puts on serious face*
"The NX is Mother 3."
I agree waiting until E3 would only make things worse, I would rather have them show it off early so I could try to gauge how much I should save.If Nintendo were to say these things, then that would be good enough for me, since i will have a date to look forward to other than E3 which is too far at the moment
Me too, when I'm not busy with school work.A timeline would be lovely. I've been checking GAF way too often lately hoping for some sort of drop.
Not sure considering that they're two completely different architectures.Is it possible that both of AMD's design wins due in 2016 (arm & x86 radeon apus) could both be for NX flavours? It was described as 'at least one being beyond gaming' but I have no idea what that means specifically.
Is it possible that both of AMD's design wins due in 2016 (arm & x86 radeon apus) could both be for NX flavours? It was described as 'at least one being beyond gaming' but I have no idea what that means specifically.
Is it possible that both of AMD's design wins due in 2016 (arm & x86 radeon apus) could both be for NX flavours? It was described as 'at least one being beyond gaming' but I have no idea what that means specifically.
Well, Mother 3 will be out come E3 so that question can be skipped
Not sure considering that they're two completely different architectures.
A 'design win' in the context of AMD's comments refers to them signing a contract to design one or more semi-custom chips. If Nintendo had hired them for both the handheld and console, they wouldn't announce it as two separate design wins (as they almost certainly would have both been covered in the same negotiations and contract).
It'll be a full year since M1 released. Makes sense to me. I wonder what the NWC games will be this year. Maybe they can have a Fed Force showdown.
Wait so according to that article, VentureBeat say the 2nd x86 one is for the home console... wonder if they know that for sure.
"What will release first, Kimishima-San? Mother 3 or NX?"
*Kimi puts on serious face*
"The NX is Mother 3."
Well, Mother 3 will be out come E3 so that question can be skipped
The VentureBeat article seems to be largely speculation of the "PS4 and XBO are x86, therefore Nintendo should use x86 as well" variety.
The three "design wins" seem likely to be the following:
ARM - Nintendo (home console, portable, or both)
x86 - Server or HPC custom chip
x86 - Apple (iMac custom APU)
makes sense... I think I remember that VB article now, they get a bit obsessed with powerpc BC. Feels like it was much longer than 6 months ago though.
TK1 (in a TDP-lax enclosure such as a tablet) performs roughly the same as an iPad Air 2, and AMD, while clearly delivering similar goods, does not have a competitive power/perf part @ 28nm. So yes, there are TK1-alternatives out there, but it's out of the question in a 28nm hh SoC.Interesting, and the Tegra K1 is already 2 years old (early 2014) and Tegra X1 was last year.
Blu, do you feel there's any possibility the handheld NX might have TK1 equivalent graphics performance from AMD, PowerVR, or whoever provides the GPU?
How many hours away is the presentation with the good stuff.
Time: Feb. 3, 10.00 AM (JST) / Feb. 2, 08.00 PM (EST) / Feb. 2, 05.00 PM (PST)
That's not to say that x86 for the home console is impossible (who the hell knows with Nintendo), just that ARM seems to make a lot more sense for a variety of reasons. Some journalists just seem to think that x86 is a big deal for ports, perhaps under some sort of delusion that games are still written entirely in assembly language.
But given Nintendo's goal of unifying their consoles & handhelds to be "like brothers", it doesn't make sense for them to have two completely different architectures. And it's not like porting to ARM from x86 would be that bad for third parties. ARM across the board makes the most sense for what Nintendo supposedly wants for the NX Platform.Indeed but no; The question is to know if popular game engines supports ARM. After a quick check, it seems it may not be the case sometimes. At least x86/x64 is the primary architecture, without a doubt.
And with Nintendo's current relationship with developers, every bit of things that makes them look marginal plays against them. And IMO, that sort of problem should be changed from the go on NX.
How many hours away is the presentation with the good stuff.
I guess the other question is do AMD actually have a working design for a mobile arm based apu? They have Mullins for x86 Puma cores but I don't know about ARM.
3,205 hours. (Till June 14 2016, when I assume Nintendo's E3 presentation will occur.)
Indeed but no; The question is to know if popular game engines supports ARM. After a quick check, it seems it may not be the case sometimes. At least x86/x64 is the primary architecture, without a doubt.
And with Nintendo's current relationship with developers, every bit of things that makes them look marginal plays against them. And IMO, that sort of problem should be changed from the go on NX.
Indeed but no; The question is to know if popular game engines supports ARM. After a quick check, it seems it may not be the case sometimes. At least x86/x64 is the primary architecture, without a doubt.
And with Nintendo's current relationship with developers, every bit of things that makes them look marginal plays against them. And IMO, that sort of problem should be changed from the go on NX.
E3 is gonna be hype.3,205 hours. (Till June 14 2016, when I assume Nintendo's E3 presentation will occur.)
Which are those engines?Indeed but no; The question is to know if popular game engines supports ARM. After a quick check, it seems it may not be the case sometimes. At least x86/x64 is the primary architecture, without a doubt.
And with Nintendo's current relationship with developers, every bit of things that makes them look marginal plays against them. And IMO, that sort of problem should be changed from the go on NX.
Soon NX will be within ARM's reach!
Ducktaped. They got him too!
Ha, fantastic posts!
First Ideaman, now him... Nninjas, Nninjas everywhere!
That would make sense, except that June seems late for a first reveal? Can they get enough momentum and interest if they only show it for the first time at E3? Maybe the combination of the first reveal plus concrete launch details will be enough?
But the Sony tactic of a February reveal and June blowout seemed to do well - why not copy that? (I just want to find out ASAP!)
Well, Mother 3 will be out come E3 so that question can be skipped
First Ideaman, now him... Nninjas, Nninjas everywhere!
Handheld is a different matter, though, as they don't have any experience at 28nm in the ~2W kind of power envelope you'd have to hit for handheld. That's not to say that they can't make something under 2W, but it probably wouldn't compete with companies for whom such low power envelopes are their day-to-day business (e.g. Imagination Technologies).
It was just a joke about supposedly (?) tight NDAs in place for NX.What happened to Rosti? I don't understand Mochi's tweet.....something going on?
All right, who gave them ninjas the duct tape?
I guess they took it from the NX hardware engineers.
Indeed but no; The question is to know if popular game engines supports ARM. After a quick check, it seems it may not be the case sometimes. At least x86/x64 is the primary architecture, without a doubt.
Unreal is the big one, and supports ARMv8, frostbite, CryEngine, Euphoria, GameMaker, Source, UbiArt and Unity do as well. Most importantly: ARM is a well documented platform where a lot of stakeholders are involved in having middleware run good on it.
5W is tablet territory. Try 2W, max 3W (with throttling). Remember the Shield hh with Tegra4 and active cooling? Yeah, nintendo would never do that.Hmm but that Tegra K1 is ~5w if I'm reading right, with Mullins supposedly lower. would a large form handheld make the difference or is it out of the question? A pocket version could be lined up once 14nm is affordable if so.
I see a lot of mid-tier-less-than-199 smartphones have been released recently with octa core A-53 SoCs (mostly from mediatek), albeit with low clocks. Could Nintendo be aiming at something like that with AMD for the "supposed" handheld in terms of price/specs?
Hmm but that Tegra K1 is ~5w if I'm reading right, with Mullins supposedly lower. would a large form handheld make the difference or is it out of the question? A pocket version could be lined up once 14nm is affordable if so.
First Ideaman, now him... Nninjas, Nninjas everywhere!
I always thought Ideaman was French.
In theory Nintendo should be able to out-do a less-than-$199 smartphone in terms of the SoC, as it's likely to have a cheaper, lower-res screen, no cellular modem, etc. etc. Octo-core A53's would also be entirely possible, as they're very power efficient, and tiny even on a 28nm process (as far as I can recall about 1mm² per core and about 8mm² for a quad-core module with L2 cache). The performance we'll actually get is anyone's guess, though, as we don't know what Nintendo's goals are when choosing a SoC. Are they happy with something that's just a noticeable step-up from the 3DS now that they don't have any direct competition? Will they go high-performance on the handheld to get it as close as possible to the console to ease cross-development? Is there anything expensive like a free-form display on there? What are they looking to charge for it? Will they be willing to take a loss on early units, and if so how much? Lots of things that we don't know are going to have a play in things, so all we can really do is look at the options open to Nintendo and make a few guesses from there.
A handheld is more likely to use a smartphone-class power envelope than tablet-class (i.e. 2W vs 5W). You could try a "large form factor" handheld with a tablet SoC, but the last device to attempt that was the Nvidia Shield, which was a monstrous device by Nintendo's standards and even ended up needing active cooling to boot.
Edit: Beaten by Blu, and with a Shield reference too, no less.