Whatever it takes to save a few cents. I was actually surprised that they even added HDMI.TunaLover said:Why Nintendo doesn't add a optical audio output? I don't want to buy a new receiver with HDMI in/out. Nintendo always is pretty restrictive with Audio and Video options =/
I'm pretty sure that it has something to do with licensing fees for optical output although it's not like I would be reaching to assume that since practically every decision Nintendo makes about its hardware is directly tied to saving costs wherever they can.TunaLover said:Why Nintendo doesn't add a optical audio output? I don't want to buy a new receiver with HDMI in/out. Nintendo always is pretty restrictive with Audio and Video options =/
Saint Gregory said:I'm pretty sure that it has something to do with licensing fees for optical output although it's not like I would be reaching to assume that since practically every decision Nintendo makes about its hardware is directly tied to saving costs wherever they can.
Since HDMI is capable of streaming uncompressed audio Nintendo will tout that as HD audio output and leave it on everyone else to come up with the extra money to upgrade their receivers. Now while I don't condone them making that move I did get a new Marantz receiver last year that supports HDMI in/out and I can't say enough about how clean it looks having all of my sources running into the TV on one HDMI cable - sounds great too.
In all seriousness a really good option depending on the type of TV you have it to run everyything into the set over HDMI and then run a single optical out from the TV back into your receiver. That's what I was doing before I bought the Marantz although you need a TV with opticial output that can carry 5.1.TunaLover said:more cheap options? Like a HDMI in splitter with HDMI and Optical output?
Saint Gregory said:In all seriousness a really good option depending on the type of TV you have it to run everyything into the set over HDMI and then run a single optical out from the TV back into your receiver. That's what I was doing before I bought the Marantz although you need a TV with opticial output that can carry 5.1.
I never understood why but until recently very few TVs supported anything higher than 2.1 for audio passthrough.TunaLover said:The problem is my TV doesn't carry DPLII signal, it convert to stereo sound only, at least that happens when I connect analog audio cables to my TV and transfer the sound via optical to my HTS. I think the same could happen with Dolby Digital...
The problem is my TV doesn't carry DPLII signal, it convert to stereo sound only, at least that happens when I connect analog audio cables to my TV and transfer the sound via optical to my HTS. I think the same could happen with Dolby Digital...
bgassassin said:^ Exactly Ace. So sometime next year we'll have a legitimate thread about the hardware.
Only other plausible idea I can think of at this point is that the GPU is based on a Juniper like some have posed before.
StevieP said:Even if it was based on evergreen, or hell northern islands, I don't see why they should be having overheating problems in a giant devkit box.
From what we know, the dev kit is the size of a 360.StevieP said:Even if it was based on evergreen, or hell northern islands, I don't see why they should be having overheating problems in a giant devkit box.
Cube did have a digital out via Component Cables, but no dedicated digital audio out. Factor 5 and their German superscience made 5.1 possible on the Cube despite that though.BocoDragon said:I guess a Nintendo console is finally getting some sort of digital audio cable through HDMI... I remember wanting that back on Cube....
sfried said:Cube did have a digital out via Component Cables, but no dedicated digital audio out. Factor 5 and their German superscience made 5.1 possible on the Cube despite that though.
From what we know, the dev kit is the size of a 360.
BurntPork said:What I mean is that it's so heavily customized that it's very different from any existing R700 chips. It's probably some type of Frankenstein monster of a chip, taking various elements of R700 and Evergreen; perhaps even something from Northern Islands. Something is making it hard for devs to determine its power, and the only thing I can think of is that it's a chip that can't be compared to anything else on the market without testing.
StevieP said:Even if it was based on evergreen, or hell northern islands, I don't see why they should be having overheating problems in a giant devkit box.
Scoops said:Probably old but Amazon is taking pre-orders for some of the announced games for $49.99.
The only way that could happen is if Nintendo drastically cut their third party license fees. That would actually make me believe for the first time ever that they are really serious about wanting to make inroads with third parties.AceBandage said:Oh, that would be awesome if Nintendo was telling devs to launch games at $50.
It would really put them in a good position.
Um, are we seriously going to believe that Nintendo and third-parties told Amazon the prices of games that are like 12-16 months away from release? They probably haven't even decided that yet.Scoops said:Probably old but Amazon is taking pre-orders for some of the announced games for $49.99.
bgassassin said:Cool. Even though you obviously can't give us specifics, I feel that I'm at least getting a better idea of the situation being presented to you.
Are you still on the first version of the dev kit that was talked about before or are you on the second version we've heard about recently like from Vigil? I ask this because you mention you will see in the next revision if the info changes, meaning that you would possibly be getting a third version sooner or later. Also again in your opinion could it be argued that it's not an RV770 (or R700 for that matter) as much as it can be argued that it is one due to the lack of complete information you have? I hope how that sounded in my brain translated properly to this post for you to understand that question. With the problems of the GPU that you mention, I'd kind of gather that you wouldn't be able to firmly say that it is a variant of an R700 and that the ones who said it before were speculating almost as much as some of us are.
Someone told me that an early devkit supposedly used an off-the-shelf RV770LE. But that chip would certainly not be used in the final hardware either way.AceBandage said:The RV700 came from 01net. The French site that originally leaked the Wii U (Project Cafe).
Say what! I thought devs were meant to know the exact specs of the hardware they're developing for even though it's non final. Doesn't not knowing the specs make it extremely hard to develop for the console?lherre said:First I want to know why the people think about R7XX family all the time. I'm not sure if it was press people or where this rumor comes from but I think any dev said nothing about a R7XX model or any particular model. I can't said too much about it (specific details) but in the docs exists a detail that people can interpret that is a R7XX card, but it can be anything at all. But nothing in the documentation (as I said before) speaks about any specific models, clocks speeds, etc. So at this moment is a bit premature to say one thing or another.
I'm sure my info comes from the second version of the devkits at least (third if we count internal-alpha hardware in nintendo quarters that didn't go to licensees). I'll try to gather new info (i'm curious too XD).
Sorry to be so vague.
Mr_Brit said:Say what! I thought devs were meant to know the exact specs of the hardware they're developing for even though it's non final. Doesn't not knowing the specs make it extremely hard to develop for the console?
Given that the previous console CPU design by IBM was POWER6-based, I think it's a bit premature for 'most of us' to be past the notion this round IBM went with a POWER7-based design.BurntPork said:What I posted wasn't a Power7, though, and I think most of us are past that.
They don't need exact specs this early on in development. Sure, I guess it would be nice, but it's not something that would be a factor until much later. As long as they have the controllers and something approximating the Wii U environment, they can get started. Besides, I doubt final specs even exist yet.Mr_Brit said:Say what! I thought devs were meant to know the exact specs of the hardware they're developing for even though it's non final. Doesn't not knowing the specs make it extremely hard to develop for the console?
Mike Capps, president, Epic GamesAs a middleware provider and as a game developer it sure would be nice if all the different platforms were really similar for us it would make it easier to work between them with maybe just a few differentiating features we could take advantage of. I'd hate to say that the Wii U is late; in fact, you could almost argue that it's early,
[Nintendo is] aiming for a point beyond the current generation they're just not leapfrogging it. One can certainly envision a future a couple years down the road where we have some significantly leapfrogged generation and then the Wii U again becomes a system that's not easily portable between the other platforms. But honestly, I think the bigger challenge for us is mobile.
wsippel said:
One can certainly envision a future a couple years down the road where we have some significantly leapfrogged generation and then the Wii U again becomes a system that's not easily portable between the other platforms.
I'm not talking about final specs but about the specs in the dev kits. Without knowing things like frequencies, number of ROPs, bandwidth, number of TMUs, latency, amount of RAM, bus width etc. it makes it very hard to develop for the console. In a sense it makes it similar to developing on PC where you have no idea about the hardware being used so have a non definite performance target which means that the games will end up looking awful/ running badly.lednerg said:They don't need exact specs this early on in development. Sure, I guess it would be nice, but it's not something that would be a factor until much later. As long as they have the controllers and something approximating the Wii U environment, they can get started. Besides, I doubt final specs even exist yet.
Well, for a certain definition of 'portable' the ps360 duo was a portability nightmare. But unless a miracle happens, WiiU will never be in the position of its predecessor portability-wise.lherre said:This is the way I think now too.
wsippel said:
lherre said:For me this is more important
This is the way I think now too.
Well, that basically confirms that that it's closer to 2-3x the current gen. So the max is definitely 640SPs. That said, it also means that is can't be a 500MHz RV740 like Mr. Brit thinks. It has to be something more.lherre said:For me this is more important
This is the way I think now too.
Well, since that's not what's happening, you're obviously wrong.Mr_Brit said:I'm not talking about final specs but about the specs in the dev kits. Without knowing things like frequencies, number of ROPs, bandwidth, number of TMUs, latency, amount of RAM, bus width etc. it makes it very hard to develop for the console. In a sense it makes it similar to developing on PC where you have no idea about the hardware being used so have a non definite performance target which means that the games will end up looking awful/ running badly.
Or they'll make the case a bit bigger. Though, wasn't that solved with the new dev kit?EatChildren said:A couple of years isn't long in the course of a generation, and Epic's vision is how I see it.
The main concern is if Nintendo can iron out the hardware issues, such as the overheating problem. If they cant, they'll be declocking that GPU.
Not at all. They work based on "minimun specs" so they can upgrade, lot easier than downgrading. It's like G5 Xbox devkits, that proved to be much slower than final specs, but something good to have an idea an adapt easily what was already done.Mr_Brit said:Say what! I thought devs were meant to know the exact specs of the hardware they're developing for even though it's non final. Doesn't not knowing the specs make it extremely hard to develop for the console?
I think that's basically what Capps meant when he said mobile is a bigger challenge. Porting might not be easy, but not really a big deal, either.Effect said:I think this depends on how scalable the various middleware engines are.
lherre said:I mean that:
- first 2 years: x360-ps3 ports (easy money because porting is cheap)
- ps4-Xbox next arrive: some ports but each time less frequent, 3rd party support goes to the new machines because the gap in power with Wii u is too big so port will be expensive too much compromises to downport games (Wii situation)
Is my personal bet. I can be mistaken of course.
EatChildren said:A couple of years isn't long in the course of a generation, and Epic's vision is how I see it.
The main concern is if Nintendo can iron out the hardware issues, such as the overheating problem. If they cant, they'll be declocking that GPU.
That and a good online system is all it really needs. If they can put out some hardware that is a noticeable step up from what we've got now they've got me. If I can't tell the difference between WiiU games and 360 games at all then it's right back to uncertainty for me.Smiles and Cries said:If Nintendo has an edge for 2 years thats pretty huge to me, losing it will suck but to think Nintendo would be top tech for 2 years is almost hard to believe
DaSorcerer7 said:In the first 2 years, there will be new games for the system.
UE3 will continue to be Epic's engine on all next gen systems. PS4 and Xbox3 won't be that radically different, just more of the same - no reason to develop a whole new engine.theBishop said:Well, of course Epic is happy about it. They can keep licensing UE3 to WiiU developers for the life of the system. With PS4 and Xbox3, Epic has to develop a whole new base of technology.
SolarPowered said:That and a good online system is all it really needs. If they can put out some hardware that is a noticeable step up from what we've got now they've got me. If I can't tell the difference between WiiU games and 360 games at all then it's right back to uncertainty for me.
dcdobson said:Assuming that Sony and Microsoft's next systems end up significantly more powerful than the Wii-U (and I'm not convinced this will be the case), then whether or not the Wii-U continues to receive ports will be based mainly on how core games sell on the system up to that point. If they sell well, I can't imagine a rational publisher deciding to abandon development. If they don't, well, who knows?
wsippel said:UE3 will continue to be Epic's engine on all next gen systems. PS4 and Xbox3 won't be that radically different, just more of the same - no reason to develop a whole new engine.