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

AMD Exec Wants In on Handheld Market; Hints at 3DS Successor Deal?

nikatapi

Member
People expecting Nintendo's next handheld to be a powerful media device are going to be so disappointed. I think Vita showed us that handhelds can't be people's main media device, unlike PSP back in the day. Cheap system, cheap good games, lots of them - that's what can make Nintendo's next handheld a success. No one is going to trade his/her iPad / iPhone for a Nintendo device, ever.

Yeah i agree, even though i expected some more multimedia functions on the 3DS (of course the screen resolution is not great, but i'd watch a 3D movie).

As far as ppi goes, i think over 200 is good, i mean my Nexus 7 1st gen has 216ppi and it looks fine. As people said, the games need to be in native resolution, otherwise it looks even worse than a low resolution screen.
 

Nikodemos

Member
I think Vita showed us that handhelds can't be people's main media device, unlike PSP back in the day.
Problem with that is Sony didn't bother putting any real effort to turn the Vita into one. Otherwise we'd have PS Mobile as Sony's own PlayStore/AppStore on the Vita.
 

z0m3le

Banned
I've been thinking about this for a while now. The simple answer is that they will use an AMD APU. 2016 for their handheld and 2017 for their console. Here is how it would work and carry over BC as well as their current Wii U library of VC titles/eshop titles.

First some realities:
Nintendo's oldest partner in console making is the S3/ARTX/ATI/AMD team where they have hired over some of the staff themselves and have a very strong working relationship.

AMD's "Mullins" is a 28nm APU with 128 ALUs @ 500MHz (Wii U has 160 @ 550MHz = 172 GFLOPs) and a quad core 2GHz Puma core, these APUs run at 2.8 watts (which is lower than psp, but of course this is just the SoC and not the complete system)

AMD is moving to 20nm next year and 16/14nm in 2016 as well as new architecture for their cores (k12 arm/x86)

Wii U uses about 28watts without the disc drive, ~20% of that is likely PSU power efficiency loss, so you are closer to 22 watts, USB, Wifi, Wifi(gamepad signal), bluetooth, ram and other misc components will use up another ~8watts, this system is built on 45nm process for the CPU/GPU (GPU is possibly 40nm) these are drastically old parts that could be reduced as much as 3 times to reduce their power draw. Infact there is little in the Wii U that couldn't of literally been done in 2009 from a technical standpoint. This entire system can be created in a handheld size with 20nm process under the formfactor's power restrictions

The simple setup:

3DS uses 2 CPUs, one used in games and one used in the DS for BC and to power the OS, this was the key to where Nintendo is most likely going with their absorption of Wii U architecture, NNID and VC going forward.

They are likely to use an AMD APU for their handheld, possibly only 2 cores but I'd venture to guess a quad core is just as likely. For the GPU side you could see 3CUs running at 450MHz (192 ALUs @ 450MHz = 172 GFLOPs) with Espresso cores for OS/BC/VC compatibility with Wii U.

This is also the likely answer for Wii U's successor as well, Espresso as a co-processor makes a lot of sense.

Handheld: ~2016
[polygon performance is actually higher on GCN afaik, you get 2m poly per mhz, so a higher clock can push more polygons but more "shaders" or ALUs gives a better GFLOPs performance and is also more likely considering higher clocks effect battery more]

Pessimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) APU Dual core 1.6GHz on 20nm process
GPU: AMD APU 2CU (128 ALUs GCN2 @ 670MHz for 172GFLOPs) on 20nm process
RAM: 2GB
Screen: 2x ~4 inch 480p screens (Lower resolution gives a better performance so this might not be a huge negative)

Optimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) APU Quad core 2GHz on 20nm process
GPU: AMD APU 4CU (256 ALUs GCN2 @ 500MHz for 256GFLOPs) on 20nm process
RAM: 4GB
Screen: 2 ~5 inch 540p screens (qHD gives the best reduction of 1080p graphics which we would see a lot of in Nintendo's next console)

Console: ~2017

Pessimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) 8 core 2GHz on 20nm process.
GPU: AMD APU 14CUs (896 ALUs GCN2 @ 1GHz for 1792GFLOPs | ~PS4 spec) on 20nm process.
RAM: 8GB DDR4 ~150GB/s + 35MB edram

Optimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) 8 core 3GHz on 16/14nm process
GPU: AMD APU 20CUs (1280 ALUs GCN2 @ 1.2GHz for 3072GFLOPs)
RAM: 16GB DDR4 ~150GB/s + 35MB edram

[note: Sorry if the listed specs above is more of a range than some might be expecting, but the truth is I don't know the future and so speculating on specifications of a device without intimate knowledge is really just guess work, so rather than that, I looked at AMDs future products and selected likely candidates from 2 view points for both devices.]

This allows Nintendo to legacy their software through a service, connect both devices going forward into 1 dev cycle and allows the OS to become quite a bit more capable with background services (system wide voice chat, gameplay recording/uploading) all while keeping their current tools and apps alive.
 
Why is anybody defending heavily multimedia focused handhelds when N-Gage was a thing? Let game playing systems just play games. Leave all the other bullshit out
 

disap.ed

Member

If I would be Nintendo I wouldn't give a fuck about BC and let out the Espresso cores.
They can always rerelease the main games on the eShop ("Remastered").

I also find the use of an ARMv8 processor highly likely, more so than a x86 architecture.

Don't agree they should use 2 screens on the handheld, just one quality screen would be my choice.

And I think K12 will be a 14/16nm chip, I may be wrong though, also it probably won't be ready for the handheld, they could use a standard A57 instead though with the same instruction set.
 

z0m3le

Banned
If I would be Nintendo I wouldn't give a fuck about BC and let out the Espresso cores.
Espresso as a co-processor does a lot more good than harm, it wouldn't be part of game development and would be available only for OS, VC and BC, all of those things would be greatly appreciated for Nintendo's hardware going forward, accounts would sync up better, you'd be able to play old games, including games from Wii U on your handheld.

They can always rerelease the main games on the eShop ("Remastered").
This requires dev time, and would seriously be a lack of foresight, especially when they are adding any Wii U architecture to these devices at all. It would be better to start "a new" but we know they aren't doing that.

I also find the use of an ARMv8 processor highly likely, more so than a x86 architecture.
Yes, AMD's ARM would make the most sense, also APU would be a certain choice for this.

Don't agree they should use 2 screens on the handheld, just one quality screen would be my choice.
I think 2 screens allows for more opportunities, gives people more creative freedom (including the players) it also has a great benefit of allowing the clamshell design which Nintendo should definitely stick with, but these are all opinions, the main reason is BC/VC going forward.

And I think K12 will be a 14/16nm chip, I may be wrong though, also it probably won't be ready for the handheld, they could use a standard A57 instead though with the same instruction set.
Yes, I believe you are right, AMD would be able to create a 20nm ARM chip, I'm sorry I didn't refer to this.
 

Marco1

Member
I'm sure it's been said but what if the handheld was a streamlined version of the wiiu game-pad but with the same functions for the next home console?
Maybe using an sdcard or memory to store games to be played anywhere as well as on the TV. When played on the TV the extra power of the wiiu would then add extra graphical capabilities.
 

Tetranet

Member
I know people are expecting a very powerful handheld for the 3DS successor, but... the more powerful the handhelds get, the more expensive it becomes to develop games for them and the less "risky" games we get. The DS had a lot of weird and creative low budget games, same goes to the PSP (kinda). The 3DS, while it has a lot of good games, is severely lacking in new and different experiences, so I am afraid the successor would be even more lackluster in this aspect. Don't even get me started on the Vita...

Indeed.

This notion that the hardware needs to be exploited in every imaginable way needs to leave in an age where development costs are becoming heavier and heavier.

I know the core/middle-ground audience will not mind a game with simpler graphics, and I think the wide audience won't care that much anyway considering that people are obsessing over nonsensical Android/iOS games.

You can have both simple and incredibly complex technically games on the same system, creating artificial plateaus isn't good for anyone.
 

z0m3le

Banned
Indeed.

This notion that the hardware needs to be exploited in every imaginable way needs to leave in an age where development costs are becoming heavier and heavier.

I know the core/middle-ground audience will not mind a game with simpler graphics, and I think the wide audience won't care that much anyway considering that people are obsessing over nonsensical Android/iOS games.

You can have both simple and incredibly complex technically games on the same system, creating artificial plateaus isn't good for anyone.
All the more reason for Nintendo to push the same hardware architecture into both devices so that their game development is more seamless between their platforms.
 

kinggroin

Banned
Odds of Wii U staying the course for 5 more years and the new handheld is built on the exact same architecture and OS, just less powerful. Account system enabled systems wide and we get a sort of shared library going forward.
 

QaaQer

Member
I've been thinking about this for a while now. The simple answer is that they will use an AMD APU. 2016 for their handheld and 2017 for their console. Here is how it would work and carry over BC as well as their current Wii U library
...

going forward into 1 dev cycle and allows the OS to become quite a bit more capable with background services (system wide voice chat, gameplay recording/uploading) all while keeping their current tools and apps alive.

very interesting post...

I assume you are also interested in the non-tech side of console. How do you think they are going to try to position their handheld in the West? I.e., what demographic are they going to target and business strategies do you think they will pursue in terms of getting that deom to bite?

My prediction is that they are going to make and sell a laser focused "keep your kid entertained with a tuff, child safe device--plus there is some educational shit too!" They know that virtually nobody will carry 2 potable devices, which means the remaining market is non-phone toting kids, hence they will have to serve that market to the best of their ability.

There will be a curated app store that developers will find friendly and easy to create content for, with an in-app purchase mechanism thus allowing f2p. they will also find a way to deliver some media, including books etc. And of course, Nintendo games like Luigi's Mansion, Mario, etc.

How they go about monetizing that will be a cut of app store purchases, their retail game profits, cut of other retail games, and possibly a subscription service. Maybe something like Amazon offers, where kids get a certain number of books/movies/shows/games per month. Although, Amazon's deal in the US is pretty unbeatable for any company that has to make a profit on their activities. Amazon is a fucking shark.
 

blu

Wants the largest console games publisher to avoid Nintendo's platforms.
Pessimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) APU Dual core 1.6GHz on 20nm process
GPU: AMD APU 2CU (128 ALUs GCN2 @ 670MHz for 172GFLOPs) on 20nm process
RAM: 2GB
Screen: 2x ~4 inch 480p screens (Lower resolution gives a better performance so this might not be a huge negative)

Optimistic view:
CPU: Espresso co processor for VC/BC/OS; AMD ARM (k12) APU Quad core 2GHz on 20nm process
GPU: AMD APU 4CU (256 ALUs GCN2 @ 500MHz for 256GFLOPs) on 20nm process
RAM: 4GB
Screen: 2 ~5 inch 540p screens (qHD gives the best reduction of 1080p graphics which we would see a lot of in Nintendo's next console)
K12 is not targeted at this segment at all. And won't be ready in a while. So it's out of the question.
 
Interestingly enough, if we look at Apple's custom ARM A57 implementation, the core seems quite large. The best estimation I can come up with is Chipworks, who put the dual cores and cache at 17% of the overall die. So for two cores and L2, that's 17.34 mm2 on 28nm. Seems like an awful lot considering a Jaguar core at the same node is close to 3 mm2.

Granted that's a custom design, but it does seem to reinforce what I've read about RISC and CISC growing more like each other as the years go by.

Edit: Digging further, it looks like Apple core I referenced (Cyclone) doubles or even triples some of the units over the stock ARM A57, so it's not really an apt comparison. A57s should be showing up in the wild soon enough, though, so we should be able to get a better picture.
 

Papacheeks

Banned
Indeed.

This notion that the hardware needs to be exploited in every imaginable way needs to leave in an age where development costs are becoming heavier and heavier.

I know the core/middle-ground audience will not mind a game with simpler graphics, and I think the wide audience won't care that much anyway considering that people are obsessing over nonsensical Android/iOS games.

You can have both simple and incredibly complex technically games on the same system, creating artificial plateaus isn't good for anyone.

Cost's come into play when the studio doesn't make smart decisions when developing software.

Unity is great for making games and from what I'v heard is mobile friendly.
3DS games are not that graphical intensive, minus RE:Relations which was pushing the hardware a lot.

Some of the best games on DS were 2d, so it really comes down to the developer to be smart in how they approach their vision for a game.

Don't create your own engine, when there's ones out there that can save your money and time.

Indie games have shown you can create great games that can wow an audience with a small team, and small impact on development budget.
 

blu

Wants the largest console games publisher to avoid Nintendo's platforms.
Just how behind has AMD been in terms of mobile tech? Are they embarrassing themselves?
They dug themselves under when they sold their mobile division to Qualcomm, and then when they lost key engineer figures to the same company. It's amazing how much damage a certain AMD CEO did to the company's future - he literally set them back with respect to some markets if not by a decade, then by quite a few years.

If nintendo uses AMD x86 for their handheld. Odds are that the wii u successor will too.
Well, duh. The question is, what are the chances for a x86-based nintendo handheld?
 

AmyS

Member
GPU: AMD APU 20CUs (1280 ALUs GCN2 @ 1.2GHz for 3072GFLOPs)


Yeah, I think a roughly ~3 TFLOPs GPU in the console would be pretty nice, considering PS4 GPU is ~1.8 TFLOPs, XBone GPU is ~1.3 TFLOPs.

Just for a reference point, PC graphics cards reached 1.2 TFLOPs in '08 with the introduction of Radeon HD 4870 (RV770). HD 4850 was 1.0 TFLOPs.

HD 4870 X2 (two GPUs, CrossFire on a single card, codenamed R700) was 2.4 TFLOPs. So two 4870 X2s CrossFire'd had 4.8 TFLOPs peak shader performance.

Obviously that's very inefficient having 4 GPUs on 2 cards, and RV770 used Shader Model 4.1, very similar to the generation of shaders Wii U uses if not the same. Not as efficient as Shader Model 5.X. with DX11. And yes I know Nintendo does not use DirectX but shaders are shaders.

While Wii U's GPU has more advanced shaders (SM 4.1) than Xbox 360's Xenos (SM 3.0+) or PS3's RSX (SM 3.0) the fact that Latte has lower performance certainly does not help it. If Wii U's successor has a reasonable amount of graphics performance (north of PS4), it could only be a good thing, developers might be more happy to work with it, if the other aspects of Nintendo's entire next gen effort are in place (price, marketing, name etc).

Wii U's hardware specs are not the real cause of its failure, but they're also not helping matters. Sure Mario Kart 8 looks amazing, just think how much more amazing Mario Kart 9 would look like if running on hardware that's somewhat above PS4 :)
 
Specs speculation

Your pessimistic specs look pretty good to me (minus swapping out the K12s for stock ARM A57s). I don't think they need to worry about matching Wii U on the handheld, though. Yes, it would probably help for VC games, but who knows what type of abstraction layer they have those games running on. I can see them putting the major 3DS SoC blocks on the handheld die and Espresso on the console die.

One thing that must be acknowledged, however, is that Nintendo still haven't fundamentally changed their philosophy on hardware. Certain things are part of their "DNA" as Genyo Takeda would put it. Just looking at die size, the Xbone/PS4 SoCs are massive - Xbone's being 363mm2 and PS4's only slightly smaller. Nintendo believe in efficiency over sheer horsepower. I'd expect the Wii U successor's SoC to be roughly half the size of their competitors' and somewhere between the two in GPU GFLOPs.

There's also the reality that eDRAM is not available at the foundries they would be using at the 20nm node. They'll have to use eSRAM, which will take up a great percentage of die space, as it does on Xbone.

DDR4 can probably happen given the timeframe, but I personally doubt Nintendo will opt for a 256-bit bus like the others. They can get something like 50 GB/s with a 128-bit bus, maybe more if faster clocked DDR4 becomes readily available. The narrower bus would help reduce board complexity and cost. The eSRAM will have to pick up the rest of the slack.

If nintendo uses AMD x86 for their handheld. Odds are that the wii u successor will too.

I think the more interesting question is: If they went with ARM in their next handheld, would they necessarily have to for their next home console?

They dug themselves under when they sold their mobile division to Qualcomm, and then when they lost key engineer figures to the same company. It's amazing how much damage a certain AMD CEO did to the company's future - he literally set them back with respect to some markets if not by a decade, then by quite a few years.

Kinda reminds one of the present situation at another certain three letter company...
 

z0m3le

Banned
Fourth Storm said:
the pessimistic specs look pretty good to me (minus swapping out the K12s for stock ARM A57s). I don't think they need to worry about matching Wii U on the handheld, though. Yes, it would probably help for VC games, but who knows what type of abstraction layer they have those games running on. I can see them putting the major 3DS SoC blocks on the handheld die and Espresso on the console die.

One thing that must be acknowledged, however, is that Nintendo still haven't fundamentally changed their philosophy on hardware. Certain things are part of their "DNA" as Genyo Takeda would put it. Just looking at die size, the Xbone/PS4 SoCs are massive - Xbone's being 363mm2 and PS4's only slightly smaller. Nintendo believe in efficiency over sheer horsepower. I'd expect the Wii U successor's SoC to be roughly half the size of their competitors' and somewhere between the two in GPU GFLOPs.

There's also the reality that eDRAM is not available at the foundries they would be using at the 20nm node. They'll have to use eSRAM, which will take up a great percentage of die space, as it does on Xbone.

DDR4 can probably happen given the timeframe, but I personally doubt Nintendo will opt for a 256-bit bus like the others. They can get something like 50 GB/s with a 128-bit bus, maybe more if faster clocked DDR4 becomes readily available. The narrower bus would help reduce board complexity and cost. The eSRAM will have to pick up the rest of the slack.



I think the more interesting question is: If they went with ARM in their next handheld, would they necessarily have to for their next home console?



Kinda reminds one of the present situation at another certain three letter company...
Yeah they might go with 128bit memory, that could even go as high as what? 90GB/s.

I do think that it is worth it for them to bring espresso for the seamlessness of the ecosystem they are trying to build, it could handle the os and that would be a big help to them imo, not to mention they have been spending all this extra resources on emulators that work with Espresso, eshop titles they could keep selling as well as their history with the processor for all sorts of future applications, if they put it in one device they will likely put it in another, it's also ridiculously tiny and cheap for them.

AMD is the obvious partner going forward, they have just caught up with HD development, they intimately know that hardware family and AMD is the most price aware of the companies they could use. As for the pessimistic view, I simply took an already existing product on the low end for each device, in 2016 the handheld will be a bit behind their newer apus in this formfactor (Mullins is a 2014 part afterall)

I've been reasonable before, over 3 years ago I thought Nintendo would use a trinity apu quad core 3ghz with 384 shaders @ 800MHz (gpu) for project café, and would just use their gecko cpu for bc, it sounded fairly reasonable as does this.

However I think there is a clear change between what they were doing then and what they are trying to do now. I wouldn't say they were completely oblivious to the market changes with mobile, it just moved faster than they could anticipate, plan for and execute. I imagine that Wii U was actually suppose to come sooner. I'd say what they eventually brought to market isn't even their full vision for the device, Iwata hinted in his wii u ask piece that Wii U was originally going to be more powerful but they thought the power envelope was more important. Japan's console market crashed completely during Nintendo's planning of the Wii U and they didn't under spend on the components, they just focused on tdp far too much.

Their goals with these next devices are different which is why I think they will go with AMD, and the relative power in both platforms is more of a byproduct of AMD than Nintendo's goals. I also think they are planning a more immediate and closer answer to mobile than their handheld, I think when Iwata was talking about combining their architecture going forward and that it would lead to a 3rd pillar, they were thinking of a platform that could more readily compete with mobile, something lacking most buttons and in a single screen formfactor that is small and sleek while still offering inputs that mobile can't.

Also it's not true that people don't have room on them for a dedicated gaming device, people on average carry about 3 tech devices on them according to the research so Nintendo needs a device people are more willing to carry around. I personally believe that their handheld won't fill this void but a smaller device similar to an iPod touch, could.

Edit: the 3rd device I imagine would come after the other 2, have 2 shoulder buttons that look like volume rockers, a dpad that functions like an iPhone home button, and possibly a couple action buttons, a stylus wouldn't hurt. Releasing a device like this under $100 that can also run mobile games but is sort of a undercover gaming device would have a fair chance in the market to end up in every gamer's pocket, casual or core.
 

QaaQer

Member
Also it's not true that people don't have room on them for a dedicated gaming device, people on average carry about 3 tech devices on them according to the research so Nintendo needs a device people are more willing to carry around. I personally believe that their handheld won't fill this void but a smaller device similar to an iPod touch, could.

What research?

There was thing on NakedSecurity which was an online poll of their readers, but that was an online poll of readers of a tech security firm's website. It's like having a gaf poll on # of consoles owned and extrapolating to the general population.
 
All the more reason for Nintendo to push the same hardware architecture into both devices so that their game development is more seamless between their platforms.

What about the 3rd party devs who will be contending with x86 for the other platforms sans Vita?
 

Snakeyes

Member
They know that virtually nobody will carry 2 potable devices, which means the remaining market is non-phone toting kids, hence they will have to serve that market to the best of their ability.
That's not true at all. Several surveys have shown that the average person carries close to 3 portable devices when on the go. What people are unwilling to carry is a clunky, thick and inelegant piece of tech like the 3DS and all of its revisions.

Zomle, I think you're on the right track but also agree with those who think Nintendo will ditch the dual screen.
 

LordOfChaos

Member
Exciting, if true! I wonder if they will provide the full solution, or just the GPU portion (shrunken espresso/latte theory). Being unified with AMD APUs would have been nice. Perhaps the next stationary console in turn will be based off a nextDS compatible APU.


I just hope the next handheld has some decent guts as of its launch date, not some head scratchingly underpowered hardware.
 
This might be kind of crazy, but could Nintendo attempt to compete in the mobile space? This is what I'm thinking in this regard. The mobile space is kind of analogous to the situation in the 80s before Nintendo introduced the NES. What I mean is, people always talk about how X can't compete because they don't have an established app store, but think about it. Who really plays any of that crap or uses more than maybe 1% of all of the apps on the app store or google play? I mean if you go to the Games section of Google Play, it's all garbage, nothing that I'd want to play personally. Sure you might download one to play if you need to kill some time, but you don't really expect to get a quality experience.

With the unified architecture concept you could have a premium Nintendo device with high quality content that can also be played on Nintendo's other devices. Not only that but it would have the virtual console plus Wii U games possibly as well.

The one question I have is could the Wii U SoC be shrunken down to an acceptable power consumption level for a phablet form factor?
 

z0m3le

Banned
What about the 3rd party devs who will be contending with x86 for the other platforms sans Vita?
All 3rd parties use ARM, all Middleware engines support ARM as well, the next consoles from both companies also might go ARM. In the end, 3rd parties are gonna 3rd party. Wii U was never supported properly by any major 3rd party, but if Nintendo can produce 50% more titles a year and blend titles like mg1&2 or oot and mm, to release across both consoles, they will be in the best position with software for a long time and not be completely at the mercy of 3rd parties like they were in the first year of 3ds and wii u's life.
 

Log4Girlz

Member
That's not true at all. Several surveys have shown that the average person carries close to 3 portable devices when on the go. What people are unwilling to carry is a clunky, thick and inelegant piece of tech like the 3DS and all of its revisions.

Zomle, I think you're on the right track but also agree with those who think Nintendo will ditch the dual screen.

I don't believe you.
 

StevieP

Banned
What about the 3rd party devs who will be contending with x86 for the other platforms sans Vita?

The current major 3rd parties don't feel there's money to be made on an ecosystem that falls outside of their focus of the16-30yo male. They will continue to feel that way no matter the hardware on the table. Even if they were exactly the same as other console makers. It's best if you seperate the hardware from that equation, as it has very little to do with it. Some people here are barking up the right trees in that regard.
 
There's no way they're getting rid of touch. I expect they'll go back to one screen, but I highly highly doubt it'll just be a normal screen. They'll want touch for their own stuff, and to get some mobile ports on there

Get rid of touch? wtf

That's really a bad idea though. Touch is convenient, necessary for mobile ports and can be used in Nintendos own games for interesting new gameplay.

How many mobile ports does the 3DS get that would make this a worthwhile pursuit in a successor?

I own a Vita, a 3DS, an iPhone, a 2013 Nexus 7, and I'm a former Android phone user.

The Vita and the 3DS don't make touch something I enjoy using like I do on my Android and iOS devices. The way they use touch in their operating system is slow and cumbersome to use relative to mobile devices.

Disregarding any discussion of specifications in a 3DS successor, Nintendo needs to make a device (and operating system) that's enjoyable to use. I enjoy using my phone. When I know I can bring an extra device with me, I enjoy taking my tablet or Kindle. My Vita and 3DS stay at home.

It's 2014. If you want a 3DS or Vita successor to have media functionality (Netflix, Hulu, music/video player) and a web browser, then Nintendo and Sony need to make much stronger efforts to keep up with Apple and Google. Their web browsers are a pain to use even to browse GAF.
 
I think the more interesting question is: If they went with ARM in their next handheld, would they necessarily have to for their next home console?

They don't necessarily have to, but it does make creating a unified os and platform easier which is one of the goals Iwata has spoken of. Otherwise, there has to be some common virtual machine or something of that sort for games, applications, etc to run across different cpu architectures without forcing a recompile and having to test on both platforms.
 

z0m3le

Banned
They don't necessarily have to, but it does make creating a unified os and platform easier which is one of the goals Iwata has spoken of. Otherwise, there has to be some common virtual machine or something of that sort for games, applications, etc to run across different cpu architectures without forcing a recompile and having to test on both platforms.

This is another reason I think they will put espresso in their devices going forward, they can always add more cores and increase the clock rate of that chip as they shrink it to fit their need, they bought the full license from IBM years ago and never have to drop their backlog again if they do.

I'm really looking forward to the next hardware cycle from Nintendo but I really hope that they bring my current growing library with them, it's a great way to carry customers forward and if what they said about bringing nnid forward to their future consoles is true, this would be the best way to keep people's digital library and loyalty to an ecosystem rather than a device. They are late to this game of course, but when they do eventually come, they have always proven themselves worthy of their customers.
 
How many mobile ports does the 3DS get that would make this a worthwhile pursuit in a successor?

I own a Vita, a 3DS, an iPhone, a 2013 Nexus 7, and I'm a former Android phone user.

The Vita and the 3DS don't make touch something I enjoy using like I do on my Android and iOS devices. The way they use touch in their operating system is slow and cumbersome to use relative to mobile devices.

Disregarding any discussion of specifications in a 3DS successor, Nintendo needs to make a device (and operating system) that's enjoyable to use. I enjoy using my phone. When I know I can bring an extra device with me, I enjoy taking my tablet or Kindle. My Vita and 3DS stay at home.

It's 2014. If you want a 3DS or Vita successor to have media functionality (Netflix, Hulu, music/video player) and a web browser, then Nintendo and Sony need to make much stronger efforts to keep up with Apple and Google. Their web browsers are a pain to use even to browse GAF.

I'm just saying, with the ubiquity of phones and daily devices, any device coming out WITHOUT a touch screen is going to be a step back, no doubt about it.

And even ignoring that, Nintendo would be stupid to ignore mobile devs anyway. The 3DS gets small mobile ports on the eShop, and sometimes even bigger games like retail releases of Angry Birds or Puzzle and Dragons (which is INSANELY popular in Japan, hopefully we get it ;D). They should be encouraging all developers to make games, not just those that meet some touchless pedigree. They could absolutely make the touch better used in the UI, but when it comes to games, they can't give it up. Imagine a phone that comes out today without a touchscreen, a flagship phone. It would be worthless.

(Your comments on OS I agree with. They need to step it up in that regard. I can't even imagine using my 3DS browser for anything, it's a joke).
 
I'm just saying, with the ubiquity of phones and daily devices, any device coming out WITHOUT a touch screen is going to be a step back, no doubt about it.

And even ignoring that, Nintendo would be stupid to ignore mobile devs anyway. The 3DS gets small mobile ports on the eShop, and sometimes even bigger games like retail releases of Angry Birds or Puzzle and Dragons (which is INSANELY popular in Japan, hopefully we get it ;D). They should be encouraging all developers to make games, not just those that meet some touchless pedigree. They could absolutely make the touch better used in the UI, but when it comes to games, they can't give it up. Imagine a phone that comes out today without a touchscreen, a flagship phone. It would be worthless.

(Your comments on OS I agree with. They need to step it up in that regard. I can't even imagine using my 3DS browser for anything, it's a joke).

I'm not against Nintendo using a touch screen in the "4DS," but as a long-time DS and 3DS owner, I didn't feel like enough games used the touch screen meaningfully.

I'm not even against mobile ports, but Nintendo's tendency to use uncommon or unique hardware (PICA GPU, asychronous CPUs, low-resolution dual screens) show that's not a priority. On the eShop, a bigger concern should be tying games to your account and day-and-date releases of major retail games. And I say this as someone that loves playing Ollie Ollie and Pinball Arcade in short bursts on my Vita.

They could absolutely make the touch better used in the UI, but when it comes to games, they can't give it up. Imagine a phone that comes out today without a touchscreen, a flagship phone. It would be worthless.

I understand why Nintendo made the choices they did. The OS keyboard makes sense when you design a software keyboard for small, square resistive touchscreens. By extension, most of my complaints in how the touchscreen is used in the OS and games stem from the resistive touchscreen.

If Nintendo's content to follow a 4DS/4DSXL hardware path and not kill resistive touch, it's not going to matter. We're just going to see the same issues crop up again.
 

z0m3le

Banned
I'm not against Nintendo using a touch screen in the "4DS," but as a long-time DS and 3DS owner, I didn't feel like enough games used the touch screen meaningfully.

I'm not even against mobile ports, but Nintendo's tendency to use uncommon or unique hardware (PICA GPU, asychronous CPUs, low-resolution dual screens) show that's not a priority. On the eShop, a bigger concern should be tying games to your account and day-and-date releases of major retail games. And I say this as someone that loves playing Ollie Ollie and Pinball Arcade in short bursts on my Vita.



I understand why Nintendo made the choices they did. The OS keyboard makes sense when you design a software keyboard for small, square resistive touchscreens. By extension, most of my complaints in how the touchscreen is used in the OS and games stem from the resistive touchscreen.

If Nintendo's content to follow a 4DS/4DSXL hardware path and not kill resistive touch, it's not going to matter. We're just going to see the same issues crop up again.

They can leave resistive touchscreens and just use an active stylus, something pressure sensitive much like the Galaxy Note uses. I just hope they build out from their current Wii U OS, Nintendo isn't Microsoft, building on an old OS new features much like Android does, is better for them than scrapping the OS every generation and since they are bringing forward something from Wii U, Espresso would mean all these things going forward. I just think that it will be a co-processor and not be tethered to all future products / development cycles, leave it for a seemless OS experience that can build on all their current Wii U titles and all the ones they will make going forward.
 

nikatapi

Member
They can leave resistive touchscreens and just use an active stylus, something pressure sensitive much like the Galaxy Note uses. I just hope they build out from their current Wii U OS, Nintendo isn't Microsoft, building on an old OS new features much like Android does, is better for them than scrapping the OS every generation and since they are bringing forward something from Wii U, Espresso would mean all these things going forward. I just think that it will be a co-processor and not be tethered to all future products / development cycles, leave it for a seemless OS experience that can build on all their current Wii U titles and all the ones they will make going forward.

Sounds like an interesting idea, hopefully they'll improve the OS both on the next console and handheld, because their current efforts are both slow, especially on the 3DS (which is understandable with such low specs).
 

z0m3le

Banned
Sounds like an interesting idea, hopefully they'll improve the OS both on the next console and handheld, because their current efforts are both slow, especially on the 3DS (which is understandable with such low specs).

By leave, I meant move to a Capacitive touchscreen and add a Stylus much like the Note (I currently use the Note II as my phone and this works beautifully) and I to hope they work on the OS going forward, I don't think they need multiple OS for the different devices, it would be best if both platforms could run the OS natively and using the same CPU again would allow this, would also allow a seemless experience when moving from device "x" to device "y". Having access to your digital titles would also be very nice going forward.
 

nikatapi

Member
By leave, I meant move to a Capacitive touchscreen and add a Stylus much like the Note (I currently use the Note II as my phone and this works beautifully) and I to hope they work on the OS going forward, I don't think they need multiple OS for the different devices, it would be best if both platforms could run the OS natively and using the same CPU again would allow this, would also allow a seemless experience when moving from device "x" to device "y". Having access to your digital titles would also be very nice going forward.

Yes exactly, i meant that if they mean to use the same OS they need to make some substantial improvements going forward, in terms of features and especially in terms of responsiveness and speed, currently it takes too much time to jump from one feature to another on the 3DS (browser, friend list, miiverse is the most slow), i'm not sure how fast it is on the WiiU.

Having the same OS on both the console and the portable would be a great move, having the same familiar experience (and possibly downloadable games being playable on both), i'm just arguing that they need to step up their game as far as speed and features are concerned.
 

Log4Girlz

Member
How many mobile ports does the 3DS get that would make this a worthwhile pursuit in a successor?

Buttons is death. The next handheld has to be nothing but screen. Sure, it can have a sliding controller area to use for many games. Buttons are a layer of complexity that will put off MANY people. Kids are already being raised on touch only. Getting rid of touch would be one of the all-time dumbest decisions in this industry.
 

z0m3le

Banned
Buttons is death. The next handheld has to be nothing but screen. Sure, it can have a sliding controller area to use for many games. Buttons are a layer of complexity that will put off MANY people. Kids are already being raised on touch only. Getting rid of touch would be one of the all-time dumbest decisions in this industry.

I really think this is why they will bring back the "3rd pillar" strategy, just make a 4inch 540p ipod touch type device, (275dpi) give it 2 shoulder buttons disguised as volume rockers and a dpad or slide pad that clicks like a home button. throwing in another button or 2 on the other side of the display could work if it looked fine, I think the entire diamond input (abxy) could be pulled off. This would be more a VC/BC device, could even play 3DS games possibly. Would come in under $100 and be a single screen device.
 

Jinko

Member
This is another reason I think they will put espresso in their devices going forward, they can always add more cores and increase the clock rate of that chip as they shrink it to fit their need, they bought the full license from IBM years ago and never have to drop their backlog again if they do.

I think this a bad idea, but its Nintendo and they seem happy to coast along with old tech and architecture so wouldn't be surprised if it happened.
I would much prefer them to switch to ARM. (or X86 for their next home console so they can get better multi platform support,something they are desperate for)

I'm really looking forward to the next hardware cycle from Nintendo but I really hope that they bring my current growing library with them, it's a great way to carry customers forward and if what they said about bringing nnid forward to their future consoles is true, this would be the best way to keep people's digital library and loyalty to an ecosystem rather than a device. They are late to this game of course, but when they do eventually come, they have always proven themselves worthy of their customers.

Well if they do bring it over I hope they make it a shit load more user friendly, when transferring your accounts/games and the rest of it.
NNID just seems like a bandaid to me, they need a much more robust system in place for their next systems, if they want to be taken seriously.

People expecting Nintendo to drop touch capabilities in their hand-held need their heads looked at, at this point in technology a hand-held without touch will look antiquated.
 
I may be in the minority, but I hope to god the next DS keeps the resistive touchscreen. A capacitive screen would ruin it for me.

Also, I generally carry at least two mobile devices, sometimes three. I realize I'm an outlier, but all gamers are.
 

Principate

Saint Titanfall
TBF to state people are unwilling to carry more than one mobile device is completely fallacious when tablets (which don't actually replace mobile phones) are all the rage. They probably don't want to carry single purpose and likely clunky devices but a tablet will still often require a bag so they certainly still willing to sometimes go out of their way to have a second device.
 

Jinko

Member
TBF to state people are unwilling to carry more than one mobile device is completely fallacious when tablets (which don't actually replace mobile phones) are all the rage. They probably don't want to carry single purpose and likely clunky devices but a tablet will still often require a bag so they certainly still willing to sometimes go out of their way to have a second device.

Exactly both tablets and phones are multiple purpose where as a ganmes system is just a games system.

Maybe people who carry both a phone and tablet either use them for work or reading/browsing both of which are non existent or inferior on current handheld games systems.

There is also a negative stigma to using a game system in public that I am sure many people get embarrassed about, I know I sure do.
 

japtor

Member
Interestingly enough, if we look at Apple's custom ARM A57 implementation, the core seems quite large. The best estimation I can come up with is Chipworks, who put the dual cores and cache at 17% of the overall die. So for two cores and L2, that's 17.34 mm2 on 28nm. Seems like an awful lot considering a Jaguar core at the same node is close to 3 mm2.

Granted that's a custom design, but it does seem to reinforce what I've read about RISC and CISC growing more like each other as the years go by.

Edit: Digging further, it looks like Apple core I referenced (Cyclone) doubles or even triples some of the units over the stock ARM A57, so it's not really an apt comparison. A57s should be showing up in the wild soon enough, though, so we should be able to get a better picture.
Yeah Apple's cores (both Swift and Cyclone) were custom ISA implementations of their own design rather than modified ARM designs.
I think the more interesting question is: If they went with ARM in their next handheld, would they necessarily have to for their next home console?
Nope.
They don't necessarily have to, but it does make creating a unified os and platform easier which is one of the goals Iwata has spoken of. Otherwise, there has to be some common virtual machine or something of that sort for games, applications, etc to run across different cpu architectures without forcing a recompile and having to test on both platforms.
Unless everything is completely identical devs will have to test for both platforms regardless.

The issue I have with the idea about needing the same hardware to ease software development is that it just leads down the same path that they've been on, which is what I think they're ultimately trying to avoid (hopefully/finally). Having software dev tied to hardware forces their hardware choices rather than picking potentially better solutions, not just between portable/console but every future generation. Major changes within the same architecture would screw them too as far as optimizations.

All that I could see Espresso sticking around as a coprocessor of some sort for their next home console too (depending on die shrinks/efficiency/cost), although I'd be surprised if it got used in a portable just cause the tighter tolerances and limited benefit.
 

z0m3le

Banned
I think this a bad idea, but its Nintendo and they seem happy to coast along with old tech and architecture so wouldn't be surprised if it happened.
I would much prefer them to switch to ARM. (or X86 for their next home console so they can get better multi platform support,something they are desperate for)
I think you misunderstood, they should bring Espresso as a co-processor that handles OS, BC and VC, it's 12mm^2 on 45nm process, it's absolutely tiny and I'm talking about shrinking it to 20nm process which would allow it to fit inside the GPU die.

They should go with an AMD APU using ARM or X86 (ARM is preferred because it's better and more forward thinking IMO)
 
Top Bottom