Honestly, was expecting a little more. Maybe not Tomb Raider, but Epic Mickey 2 port from the PS360, or from the Wii (Wii U HD Version for example) using still the Wiimote instead of the Upad is what I expect. Why? Junction Point seems very happy with the sales of the first one and it's using the Wii as the lead platform. Even the 3DS is getting its exclusive game (which looks awesome).

Also, announcing RE6 version at E3 will make people roll eyes rather than be surprised. So, why waste time on E3 while it can be used to show other games? If there's actually a NDA and everything is unveiled until then, expect some big backlash and not a warm reception like the Wii.

You didn't read the second part of my post, did you?

Do you mean this?

"I supposed I should also make a logical point of reference and that the avaiability of a new console's SDK's in the first year leading to release are pretty limited therby making it impossible for every game to be released on the new console.   Many studios may have a couple of SDK's but that's enough for prelimenary R&D only, not full blown software development."

So, you are saying that few companys have enough SDK's to develop games? And that's why not every game will be released on Wii U? Is this something normal to evey console launch, or in this particular case?

You will say wow.

Every console launch.  This is why I was asking if you guys are new to console launches.   Expecting there to be the same number of Wii U SDK's floating out there (final revisions at that) as there are PS3 or X360 SDK's isn't reality.   Hell, it was well after the Wii itself launched that many devs started to finally get the final SDK.

Select developers always receive the kits first.  These are early R&D kits to get engines running and becoem familiar with the hardware.   Then you get more revisions but you have to split those with the Tier A developers that received the alpha kits and Tier B developers.   Console makers will probably have a list of multiple tiers and they'll have to allocate those SDK's (and their subsequent revisions) to whichever developers they think will best be able to sevre them at or just after launch.

SDk's are expensive and not mass manufactured like the console itself is so you don't have several thousand to go out a year before launch.  Remember all those stories about Suda51 still waiting to get a development kit?   Well, that's actually the case for lots of studios.

Another factor is general resources.   Say you budget a game at $25 million and 100 people for about 3 years.   Now if a game is to be released near the same tiem as the upcoming console and you didn't get enough SDK's early enough nor budget the money and manpower for the upcoming console in time for the games release, you largely cannot develop that SKU.  Companies that do get such early launch support must have received SDK's early enough and are flexible enough with their budget and man power to allocate for the new SKU.

true but it will be full of sarcasm and disappointment.

The list continues growing:

No Crysis 3 for Wii U CONFIRMED (No wait until E3 for god's sake)

http://www.destructoid.com/-fat-chance-of-crysis-3-coming-to-the-wii-u-226413.phtml

Tought EA was very close to Nintendo this time.