my expectation for the wii u is that nsmbu won't do what people expect it to, and for the system to struggle to hit 200k a month in the us and japan (much like the early 3ds).
I think it will have a much bigger impact in Japan. We'll see though.
my expectation for the wii u is that nsmbu won't do what people expect it to, and for the system to struggle to hit 200k a month in the us and japan (much like the early 3ds).
That would be incredibly dumb. Nintendo's entire point in developing NSMB U is to have a system seller day 1.
As rabid as Nintendo and even NSMB fans are i think Nintendo are making a huge mistake releasing two games from the series in the space of 3 months, esp expecting them both to shift hardware.
I couldn't believe my ears when i heard the 3DS XL was being released such a small time frame before Wii U, it has the potential to canabalize the Wii U hardware and software sales imo.
How many people have enough money in this economy to buy both a 3DS XL, NSMB 2, a Wii U and NSMB U in the space of three months, i doubt many, esp the mass market audience Nintendo seem to be targeting with Wii U launch software.
Agreed. I see Nintendo treating WiiU like 3DS in terms of first party support. If so Id be so happy. The 3DS has been getting great after great game non stop since december last year.I doubt that. Nintendo is willing to release two NSMB games within 3 freaking MONTHS of eachother. We'll see Mario Kart U in 2013.
The mass market will see the difference just fine, but I'm not sure they'll care as much. Both games are a case of "we want to shift units, so lets ship a hardware moving game". The market wants NSMB, but I'm not sure the market is desperate for two NSMB titles released in short succession.
That's true. It's mostly the crazy variety of assets in Prime that would hike production costs.
How many people have enough money in this economy to buy both a 3DS XL, NSMB 2, a Wii U and NSMB U in the space of three months, i doubt many, esp the mass market audience Nintendo seem to be targeting with Wii U launch software.
This might be true in begining..but NSMBU is a console lifetime selling game. Itll prolly hit 20+ million by the end off WiiUs life span.The thing about the mass market, though, is that it's such a large potential audience. Even if some people decide to go the 3DS XL route, there's still plenty more left who didn't buy anything and can still purchase a Wii U. I think the real problem for Nintendo is the possibility that people will simply get tired of the NSMB formula.
This might be true in beginning..but NSMBU is a console lifetime selling game. It'll probably hit 20+ million by the end off WiiUs life span.
From here on out itll be like that from every Nintendo console. The Wii and DS has had so much success that people who dont follow Nintendo think that any thing less than was Nintendo being lucky with DS and Wii, and that everything else is a failure if it fails to meet Wii DS numbers.I'm sure it'll be a lifetime seller, it's not like Nintendo are milking the franchise to Activision levels. It'll be hard to match the DS and Wii versions. They were both hardware-shifters, but they were also buoyed by being attached to consoles that were already extremely successful.
As rabid as Nintendo and even NSMB fans are i think Nintendo are making a huge mistake releasing two games from the series in the space of 3 months, esp expecting them both to shift hardware.
I couldn't believe my ears when i heard the 3DS XL was being released such a small time frame before Wii U, it has the potential to canabalize the Wii U hardware and software sales imo.
How many people have enough money in this economy to buy both a 3DS XL, NSMB 2, a Wii U and NSMB U in the space of three months, i doubt many, esp the mass market audience Nintendo seem to be targeting with Wii U launch software.
Heat is the usual reason to downclock hardware. Heat can damage components and decrease stability, which is the absolute last thing you want in a closed hardware environment. Nintendo is extremely cautious about product reliability, and I could totally see them pulling back on hardware components if they felt there was any risk of heat and stability issues popping up.
Relying on the GPU is a bit crazy, but kinda understandable in a crazy logic given the compute support. But these are all maybes and speculation, a lot of which unfounded. We simply don't know what the hardware can and cannot do, nor how efficient it is. Maybe the CPU is terrible, maybe it's manageable. Maybe they are indeed relying on the GPU compute functions, but maybe the compute functions are poor or the GPU too is poorly clocked. Or maybe the GPU is great. Or maybe nothing is wrong. We just don't know.
Personally, I fully believe there is some kind of architectural 'issue' developers are facing with the Wii U, relative to the 360/PS3. If they wasn't, we/I wouldn't have reports of teams facing issues. This doesn't mean the issues are fixable or without solutions, but it does mean issues exist, issues that likely will not be evident in both Sony and Microsoft's next generation machines (in terms of porting current gen titles).
But I also feel that Metroid won't be a truly gigantic franchise ever.
I think Metroid needs to go straight up against Halo.
Why the hell would they be so stingy/anal/stupid to gimp their CPU? Heat? Costs? I wish they weren't so worried about those things. They seems to be a bit OCD on it all.
Relying on the GPU is mental, especially if it means you think you should gimp your CPU out of any reasonable standard of acceptability which is what it seems they have done. They could have the best of both worlds for a little more power/heat or cost.
Heat is the usual reason to downclock hardware. Heat can damage components and decrease stability, which is the absolute last thing you want in a closed hardware environment. Nintendo is extremely cautious about product reliability, and I could totally see them pulling back on hardware components if they felt there was any risk of heat and stability issues popping up.
Relying on the GPU is a bit crazy, but kinda understandable in a crazy logic given the compute support. But these are all maybes and speculation, a lot of which unfounded. We simply don't know what the hardware can and cannot do, nor how efficient it is. Maybe the CPU is terrible, maybe it's manageable. Maybe they are indeed relying on the GPU compute functions, but maybe the compute functions are poor or the GPU too is poorly clocked. Or maybe the GPU is great. Or maybe nothing is wrong. We just don't know.
Personally, I fully believe there is some kind of architectural 'issue' developers are facing with the Wii U, relative to the 360/PS3. If they wasn't, we/I wouldn't have reports of teams facing issues. This doesn't mean the issues are fixable or without solutions, but it does mean issues exist, issues that likely will not be evident in both Sony and Microsoft's next generation machines (in terms of porting current gen titles).
Not confusing them. The way I understand it is this: Flipper has access to both the texture cache and frame buffer at 6.2 ns. It would be hard for an off-die cache to achieve this. If you give me examples, I'd be interested to read. Further, the texture cache in particular is 64kb wide, reducing the necessary amount of page switches and thereby reducing the total latency. Looking at the setup for this supposed RV770 spin off, AMD don't seem to give particulars of their cache, but it's unlikely there's access to 64 out of around 128 total L1 texture cache at once.
So now we're looking at fattening the total SRAM cache, which seems expensive in both cost and transistors. With the CPU, it looks as if Nintendo are shying away from SRAM, going so far as to not use it for CPU L2. So perhaps they replaced the GPU L2 with eDRAM, which is something we haven't heard, as opposed to the unified 32 MB framebuffer. Or they've just struck the L2 cache from the GPU, maybe fattened the L1 caches to 32 kb SRAM each, and gotten the eDRAM on there, Power7 style. There is that talk of a "blank substrate" SoC going on with the 360 CPU so I don' think it's outside the realm of possibility IBM and AMD worked that closely together. I don't see much point in the small CPU being able to access the eDRAM, when its own L2 is quite nice and the latency would probably be just as bad as to main memory. It seems it would be much more useful for gpu physics and gpu compute functions in addition to framebuffer. And there's definitely more to use than as just a framebuffer. In Xenos, only the ROPS had high bandwidth access to the eDRAM, as they were on the same chip. Increasing the bus between chips to make it much more beneficial than main memory would probably start getting pricey.
I think Metroid needs to go straight up against Halo. Meaning they need to add a huge emphasis on adding in a great online competitive multiplayer system. I know there are a lot of folk who would burn me at the stake for saying that, but if they ever want Metroid to be as big as it should, that is what it needs.
Metroid competes against Halo on the Single player part and probably to a lot of people it wins. But without the multiplayer, the HD twin people don't see it as anything to beat an eyelash at.
Nintendo fans will disagree, but I would place bets that if it got multiplayer on level with Halo/CoD it would be a 5-8 million seller on it's first Wii-U entry instead of a 1-2 million seller and only grow with each installment.
I think Metroid needs to go straight up against Halo. Meaning they need to add a huge emphasis on adding in a great online competitive multiplayer system. I know there are a lot of folk who would burn me at the stake for saying that, but if they ever want Metroid to be as big as it should, that is what it needs.
Metroid competes against Halo on the Single player part and probably to a lot of people it wins. But without the multiplayer, the HD twin people don't see it as anything to beat an eyelash at.
Nintendo fans will disagree, but I would place bets that if it got multiplayer on level with Halo/CoD it would be a 5-8 million seller on it's first Wii-U entry instead of a 1-2 million seller and only grow with each installment.
The problem with the rumor is that it's implying that the initial "unprecedented" relationship is based on the outcome of the offer in the future that hasn't happened yet. That and I don't see Nintendo going to EA for network help in the first place.This! Starting to believe EA Origin rumor:
-showing major support at last years E3
-Moore visiting NoJ
-things go south from there
-shockingalbertos leaking details about BF3 being canned and other projects
- announcement of ME3, but no ports of first two games
-ME3 U being done by different 3rd party with more effort
-gimped madden with subpar graphics
-no sims franchise insight (Possible next year when sims 4 is announced)
2 years between GBA, GC, and DS releases, then 3 between DS, Wii, and 3DS. Going back to 2 years would be 2013. If you go with just the console releases it's 5 years between the last two releases, another 5 years would also be 2013.there's a 3 year gap between each installment. Mario Kart 7 came out late 2011 so I'm not expecting the next one till 2014 at the earliest.
They got around that in the 3DS by sticking the safety thing in as a separate app. And the Wii did have that a startup sequence...it was just really brief and plain.Do anyone else hope that Wii U has an actual startup sequence unlike the Wii? I always hated the warning message that shows up when you turn the console on.
Does NSMBU have the Miis in it from the old E3 showing? If so there's your difference maker! Make a cheesy commercial with people transforming into similar looking Miis and joining Mario in the game.Will the 'mass market' be able to tell that NSMB U is not the same game as NSMB 2, esp so close after release.
They should keep NSMB U for Jan / Feb 2013 for this very reason imo and go with Nintendo Land, Pikmin 3 and ZombiU as the three most advertised launch day games.
Free to play Metroid Prime Hunters: Federation vs Space Pirates, bonus tie ins/items when you buy Aliens: Colonial Marines or any other random game that can add in stuff.The only way I want to see Metroid go against Halo is if they follow the Halo 4 model (and Halo 4 is already looking REALLY Metroid Prime-ish in terms of stylization...).
Do not fuck with primary Samus concept of exploration / platforming. Do not have multiplayer involve Samus in any way. No 16 Chozo Power Suits running around in deathmatch.
Instead bring in the Federation space navy and have a detachment of marines be the multiplayer and co-op characters who are on their own parallel missions. Essentially like the Infinity in Halo 4. This also creates an excuse to not try and work in power suit gameplay like the morphball if it doesn't fit. The marines aren't Samus and don't have all the same gear. But they could have variations of it, such as weapons that the Federation has reverse engineered from Chozo ruins.
game of the show
The problem with the rumor is that it's implying that the initial "unprecedented" relationship is based on the outcome of the offer in the future that hasn't happened yet. That and I don't see Nintendo going to EA for network help in the first place.
.. go on
This. X's 2.. go on
game of the show
This! Starting to believe EA Origin rumor:
-showing major support at last years E3
-Moore visiting NoJ
-things go south from there
-shockingalbertos leaking details about BF3 being canned and other projects
- announcement of ME3, but no ports of first two games
-ME3 U being done by different 3rd party with more effort
-gimped madden with subpar graphics
-no sims franchise insight (Possible next year when sims 4 is announced)
Can't see it.
game of the show
game of the show
What image was it?
I don't understand how people get that as him saying that they'll drop motion controls. He says they want to evolve them? Most probably they will drop it for shit like goddamn swimming, but keep it for combat.
The slightly different architecture was in reference to the Wii U's potential, as in devs wont have to spend 6 years to fully understand the hardware because the environment isn't too foreign to what they're use to. It's no different to when Team Ninja alluded a similar thing before.
Says access denied for me
game of the show
Ok, I re-read it and it wasn't talking about dev time.You need to read that again. That's not what Iwata was saying at all.
I always took that as meaning it won't rely to much on Motion+ for everything. Use the IR pointer for the bow and what not while keeping swordplay the same.I don't understand how people get that as him saying that they'll drop motion controls. He says they want to evolve them? Most probably they will drop it for shit like goddamn swimming, but keep it for combat.
I don't understand how people get that as him saying that they'll drop motion controls. He says they want to evolve them? Most probably they will drop it for shit like goddamn swimming, but keep it for combat.
I thought that MotionPlus fixed swimming: you had total control in the water. I can't believe there wasn't a swimming mini-game in the underused Lake Floria.
What reason is there to believe the eDRAM in GPU7 will be on package rather than on-chip? Has someone actually said that to you or are you making an assumption based on some piece of info I've missed?
Ok, I re-read it and it wasn't talking about dev time.
Still, I'm not seeing any vibes of 'weaker than average parts' despite the architecture being different (which has been vague to this point).
I thought that MotionPlus fixed swimming: you had total control in the water. I can't believe there wasn't a swimming mini-game in the underused Lake Floria.
I agree. If next generation engines are compute heavy it should be theoretically less of a problem than porting current gen engines, but it's still a whole bundle of maybes and speculation, none of which particularly reliable. There's absolutely some difficulty with the hardware though, and if leaks are correct then it's the CPU. Which is pretty dumb.
In what way did EA's support for Wii U "take a hit"? The Wii U is getting some of EA's biggest franchises right at launch.
If they did so it's probably cost. When you're as big as Nintendo you have to think about the long-term impact of costs - you know what kept the Wii from rendering natively to HD resolutions, like the original XBox did? Probably $5 worth of video RAM. But guess what, by the end of the Wii's lifetime that decision will have gained Nintendo $500 million in extra profits.
It was from the post quoting eatchildren although I could of been interpreting the last part wrong.We were talking about the architecture not dev time in those posts, though that does affect it. And where are you getting the "weaker" part from when that wasn't a part of the discussion?
Iwata was saying that devs have had six years to learn the other hardware (PS360), not "devs wont have to spend 6 years to fully understand the hardware because the environment isn't too foreign to what they're use to." He's saying that devs are only using half of Wii U's potential and the slightly different architecture is a part of the reason why.
Given the case size they probably couldn't have both.Yeah I do think that the GPGPU stuff in the Wii U will set them in good stead but they could have had GPGPU AND a good CPU.
Given the case size they probably couldn't have both.
I don't really understand why Nintendo cares so much about having a small console, the PS2 wasn't small and it sold 150 million so people really don't care about how big a console is.
I don't really understand why Nintendo cares so much about having a small console, the PS2 wasn't small and it sold 150 million so people really don't care about how big a console is.