• Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.

What we know so far about the Nintendo NX with sources

Status
Not open for further replies.
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
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.
A timeline would be lovely. I've been checking GAF way too often lately hoping for some sort of drop.
Me too, when I'm not busy with school work.
 
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.
 

Neoxon

Junior Member
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.
Not sure considering that they're two completely different architectures.
 

Thraktor

Member
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.

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).
 
Not sure considering that they're two completely different architectures.

If they are going android-y it might not matter, but I don't know much about Dalcik or jit.

Wait so according to that article, VentureBeat say the 2nd x86 one is for the home console... wonder if they know that for sure.

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).

Ah, makes sense.
 

TheMoon

Member
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.

Fed Force Blind Co-Op Let's Play Race, winning team gets to see Metroid 5 demonstration by Sakamoto. :D
 

Thraktor

Member
Wait so according to that article, VentureBeat say the 2nd x86 one is for the home console... wonder if they know that for sure.

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)
 

deriks

4-Time GIF/Meme God
"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 :p
Mother-3-Good-News-and-Bad-News-620x1.jpg
 
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, might have been something else from the same author.
 

Thraktor

Member
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.

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.
 

blu

Wants the largest console games publisher to avoid Nintendo's platforms.
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?
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.
 
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.
Forgive my ignorance on how these things are made but I assume 'semi custom' wouldn't cover changing one cpu architecture for another.
 
R

Rösti

Unconfirmed Member
I assume Mochizuki will be live tweeting from the Third Quarter Financial Results Briefing. If I am not mistaken, he did so for Nintendo's Corporate Management Policy Briefing/Second Quarter Financial Results Briefing on October 29 last year.
 

Jackano

Member
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.

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.
 

Neoxon

Junior Member
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.
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.
 

Thraktor

Member
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.

Well, that's what makes it semi-custom. They have shipped lots of APUs, and they're now shipping ARM-based processors as well, so it's not an extraordinary leap for them, especially with ~2 years between design start and product launch.

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).

I still think it's feasible, as I believe Nintendo would be willing to make the trade-off of performance in order to have the same tech in both handheld and home console to make cross-development as simple as possible, but I'm sure Blu is about to disagree with me on that :p

There's also the possibility of 14nm, and AMD have been making a big deal about their gains in perf/W with their 14nm Polaris architecture, but it would probably be too expensive for Nintendo for a late 2016 launch.
 

thefro

Member
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.

That's only going to be an issue if the NX console's processor doesn't clearly outperform PS4's.

You're still going to have to recompile your code for NX even if the console is a just a "souped-up" PS4.
 

Thraktor

Member
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.

Game engines aren't programmed in assembly any more than games are. If there's a new platform to support then compiling for ARM would be much less of an issue than, say, supporting a new, proprietary graphics API.
 

blu

Wants the largest console games publisher to avoid Nintendo's platforms.
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.
Which are those engines?
 

Josh5890

Member
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!)

While I liked that approach from Sony, the biggest reason for their success was the trolling of Microsoft at their E3 press conference that year.

Well, Mother 3 will be out come E3 so that question can be skipped :p

I'm waiting for the "We have no plans to bring any of the Mother games to the NX Virtual Console"
 

Litri

Member
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?
 
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).

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. (the inevitable 18 month later hh revision)
 

E-phonk

Banned
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.

I listed the major engines that should support ARM a few weeks ago:

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.
 

blu

Wants the largest console games publisher to avoid Nintendo's platforms.
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.
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.
 
Yeah anyone invested in mobile will support arm, so pretty much everyone.


blu:
active cooling is a no no, but maybe tablet territory is where Nintendo want to be. I am expecting something on the relatively large size either way.
 

Thraktor

Member
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?

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.

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.

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.
 

Somnid

Member
We're back to "architecture" misconceptions again? Look, the CPU platform doesn't matter from a software standpoint, assuming there is a console and a handheld they actually don't gain that much by making them the same. That's what a compiler does, it compiles code to a particular instruction set. It makes more sense to make logical choices about architecture based on other factors, like what is a reasonable get from that market. There aren't really any x86 chips getting ARM-like power/thermal efficiency (despite what Intel would have you believe), and certainly not from AMD. That said, there aren't really any ARM chips getting x86 power (despite what Apple would have you believe), and certainly not from AMD. I assume that if they made a switch at the console level, it's to x86 with an AMD GPU, and at the portable level they are likely happy with ARM and will license a GPU design from ARM/Imagine etc. since AMD doesn't make one for ARM SoCs. Now they could do a console SoC with ARM but considering how little exists in that space they'd pay a lot of R&D to get something of parity.
 

orioto

Good Art™
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.

So.. You're telling me there won't be a snapdragon 820 in the portable NX :(
 
Status
Not open for further replies.
Top Bottom