VGLeaks Durango specs: x64 8-core CPU @1.6GHz, 8GB DDR3 + 32MB ESRAM, 50GB 6x BD...

That is flat out wrong.

Most of these titles are being developed with the consoles in mind first and foremost.

Sir, would you mind reading my post again? It pertains to PC exclusives.

As a PC gamer I find it sad to find so few titles that are willing to really push the hardware.

Well, top-of-the-line tech is expensive. Crysis had poor sales at first because noone could run it at anything close to maximum specs. It just doesn't make sense to put out a game that only relatively few people can play. This is why Diablo III has modest system requirements even though it had a very big budget.

Maybe the Steambox can change this by establishing a higher baseline spec even for PC exclusives, or maybe the bar will be raised by better-performing integrated graphics. If not, system requirements will stay low for PC games because companies want the biggest possible audience.
 
It will not matter though, we already know the basis. Orbis will be pure gaming based, but brute force. Durango will be an all-rounder with media capabilities, but will be more efficient. That's pretty much the jist of it.

Its not that simple. We still don't know everything.
 
The thing is people run with the current rumored specs (even if we do not know everything) and make purchase decisions and recommendations based on them - stupid imho.
 
AAA games that are PC exclusive? as a PC gamer I find it sad to find so few titles that are willing to really push the hardware. the original Crysis was a good example, however it's been watered down for consoles, because that's where the majority of video game sales come from; their is just more money to be made there. if you consider superior hardware to be one of the main advantages of PC gaming, lacking software to take advantage of said hardware is very much a shame.

Star Citizen should be next generations equivalent of Crysis. Also Crysis was an outlier in regards to visuals last generation, it bit off way more than it could chew, people should be giving more props to the Total War series, which has consistently been at the cutting edge since 2005.
 
The thing is people run with the current rumored specs (even if we do not know everything) and make purchase decisions and recommendations based on them - stupid imho.

these consoles won't be launching for like 10+ months. no one will be making their purchase decisions based on current rumored specs. we will have definitive final specs and screenshots and videos before launch.

Star Citizen should be next generations equivalent of Crysis.

Star Citizen runs on the Crysis engine; don't expect it to look any better than Crysis.
 
It will not matter though, we already know the basis. Orbis will be pure gaming based, but brute force. Durango will be an all-rounder with media capabilities, but will be more efficient. That's pretty much the jist of it.

Where exactly does the efficiency claim stem from? Orbis seems alot more efficient of a machine looking at the specs..
 
Star Citizen runs on the Crysis engine; don't expect it to look any better than Crysis.

It runs on CryEngine 3 and its specification is demanding a GTX680, which is a stunningly powerful card even compared to rumored next generation console specs, and it scales up from there (I assume to accommodate the next generation of cards). We've already seen it in a pre-alpha state and it does indeed look better than Crysis.
 
It will not matter though, we already know the basis. Orbis will be pure gaming based, but brute force. Durango will be an all-rounder with media capabilities, but will be more efficient. That's pretty much the jist of it.

Why do you think the machine that 1. has a much larger portion of system memory locked away from games developers 2. has a divided memory structure requiring devs to feed a small segment of higher speed ram independently and 3. is widely accepted to have a much larger background footprint is the more efficient one?
 
It runs on CryEngine 3 and its specification is demanding a GTX680, which is a stunningly powerful card even compared to rumored next generation console specs, and it scales up from there (I assume to accommodate the next generation of cards). We've already seen it in a pre-alpha state and it does indeed look better than Crysis.

I doubt it will hold the crown for very long next gen.
 
It doesn't look like the guy knows what he's talking about, when he mentions the "learning set". The learning set is never in the device, it i used offline to program/configure the recognition tools. And it can be much bigger than 1G by the way.

Ah, I seem to recall reading about that, crowd sourcing and such. It's been a year or two though. Isn't there a collection of poses still on the system though? Which is used for the pose matching.
 
Why do you think the machine that 1. has a much larger portion of system memory locked away from games developers 2. has a divided memory structure requiring devs to feed a small segment of higher speed ram independently and 3. is widely accepted to have a much larger background footprint is the more efficient one?
Like I said earlier, I do not believe it will be better than Orbis. I do believe that the tools will make a difference (purely speculating) on helping what seems to be a very limited console looking at the specs.
 
I doubt it will hold the crown for very long next gen.

Eh, it depends on a lot of things. Namely on when AMD/Nvidia plan on releasing their next generation of GPUs, which look like absolute beasts going by rumors. If it does scale up to them (from a GTX680 baseline) I can see it being like a next gen equivalent of Crysis.
 
The thing is people run with the current rumored specs (even if we do not know everything) and make purchase decisions and recommendations based on them - stupid imho.

The "imho" qualifier is unnecessary, it is stupid, although I would perhaps use a less charged word. Even if we had the full specs - which we don't - and we knew all the implications of how the two different architectures were supposed to be utilized - which, again, we don't - the specs can still change, and they often do keep changing until the very last moment, whether that's because of production difficulties or for other reasons (at E3 2005 Microsoft still didn't have anything resembling the final Xbox 360 hardware in the devkits; going by the rumors, Orbis specs have changed drastically over the past few months). And then there's the all-important matter of tools and software support.

The only reasonable thing to do would be to wait until both Orbis and Durango are presented to us in full detail, probably at this E3 (again, changes could still occur even after that, but I think they'll both want to enter full production a bit sooner this time around, in order to avoid launch period shortages), but people are impatient.
 
Like I said earlier, I do not believe it will be better than Orbis. I do believe that the tools will make a difference (purely speculating) on helping what seems to be a very limited console looking at the specs.

I didn't say you said it would be better. You said Durango looked to be more efficient. I can't see why.

Orbis has:
- a clearly defined CPU - APU - GPU alignment with a healthy APU that can take a lot of the load off the GPU.
- high speed memory that will keep all of this silicon fed quite well.
- unified memory so no additional hoops for developers to jump through in memory management.
- the smaller, sleeker OS, with only 512MB of system memory locked away from developers. This dovetails perfectly with Sony's track record case in point the Vita, which dramatically reduces it's OS footprint in games with a scaling OS that still manages to function very quickly.
- strong rumors pointing to OpenGL as a non-layered, native API alternative to LibGCM.

Meanwhile on Durango:
- only rumored "secret sauce" to take workload off the GPU, will that "secret sauce" be in as accessibly a form factor as Sony's APU?
- split memory architecture requiring devs to manage the 8 GB system memory while also feeding the 32MB EsRam.
- a much larger OS footprint in terms of both CPU and memory that strongly suggests a non-scaling OS.
- at best it will have DirectX at parity with LibGCM and if the rumors prove to be true OpenGL.

If all of the unknown things about Durango were answered in the most realistically positive way we would still be talking about slower overall memory with a divided supply line and a larger OS footprint over what Orbis is doing. The Durango being equally efficient to the Orbis is extremely idealistic, being more efficient is pie in the sky dreaming.

"Tools" alone can't bridge those gaps. If Sony really does have OpenGL as native then that claim also goes completely out the window. Even if it doesn't, Sony has made huge leaps to closing the gap in the dev tools arena this generation, and that is on more obtuse hardware, which is a major reason why the PS3's tools had to start out so obtuse. More streamlined hardware inherently leads to more streamlined dev tools.
 
I didn't say you said it would be better. You said Durango looked to be more efficient. I can't see why.
I think you misunderstood me wrong or I worded it wrong. It will be efficient with what it has to work with, I did not mean to imply that it was more efficient than Orbis.
 
Ah, I seem to recall reading about that, crowd sourcing and such. It's been a year or two though. Isn't there a collection of poses still on the system though? Which is used for the pose matching.

There may be reference poses indeed, but that wouldn't amount to a big volume of data. A static pose is only a few dozens of position angles (assuming a more complex skeleton model) ; even if a gesture is considered as a sequence of static positions through time (which would be the less efficient way to do it), a complete reference gesture would be a few kB in size.
I'm less familiar with speech recognition, though. I wouldn't be surprised if those required more memory. It's hard to tell, when most recent device use the cloud to process it.
 
It runs on CryEngine 3 and its specification is demanding a GTX680, which is a stunningly powerful card even compared to rumored next generation console specs, and it scales up from there (I assume to accommodate the next generation of cards). We've already seen it in a pre-alpha state and it does indeed look better than Crysis.

should have put an IMO in that statement. judging from the early videos, I have not seen Star Citizen doing anything that Crysis 3 cannot do. which makes sense, since they are both using the exact same engine. also AFAIK Star Citizen has its minimum specification claimed as a GTX 460.
 
The "imho" qualifier is unnecessary, it is stupid, although I would perhaps use a less charged word. Even if we had the full specs - which we don't - and we knew all the implications of how the two different architectures were supposed to be utilized - which, again, we don't - the specs can still change, and they often do keep changing until the very last moment, whether that's because of production difficulties or for other reasons (at E3 2005 Microsoft still didn't have anything resembling the final Xbox 360 hardware in the devkits; going by the rumors, Orbis specs have changed drastically over the past few months). And then there's the all-important matter of tools and software support.

The only reasonable thing to do would be to wait until both Orbis and Durango are presented to us in full detail, probably at this E3 (again, changes could still occur even after that, but I think they'll both want to enter full production a bit sooner this time around, in order to avoid launch period shortages), but people are impatient.

The discussion of the specs were interesting initially, but it has boiled down to warz and metacritic lists.

There may be reference poses indeed, but that wouldn't amount to a big volume of data. A static pose is only a few dozens of position angles (assuming a more complex skeleton model) ; even if a gesture is considered as a sequence of static positions through time (which would be the less efficient way to do it), a complete reference gesture would be a few kB in size.
I'm less familiar with speech recognition, though. I wouldn't be surprised if those required more memory. It's hard to tell, when most recent device use the cloud to process it.

Yeah, that was what I was thinking. When I loaded up the Windows 8 English voice recognizer(it wasn't the Kinect one that the tutorials said to use, because for some reason it isn't on my system, but it worked without issues anyway) for speech recognition in my little Kinect program I am screwing around with, it only added about 20 - 30 mb of RAM. I am assuming this would be a rather large set.
 
I doubt it will hold the crown for very long next gen.

A space game won't hold the crown at all most likely. Granted I have no idea just how much is showing in this particular game to warrant a friggin 680, but most space games don't render very much at once which is why they always look so great.
 
should have put an IMO in that statement. judging from the early videos, I have not seen Star Citizen doing anything that Crysis 3 cannot do. which makes sense, since they are both using the exact same engine. also AFAIK Star Citizen has its minimum specification claimed as a GTX 460.

The pre-alpha demo could scale down to a 460, but not noted for the final 2014 release. I imagine that'll be able to scale down as well, but the target baseline specs, minimum for the 'full experience' of the project include a 670/680, and they plan to scale up from there to what I assume are next generation cards depending on release. And yeah I probably should specify it was my opinion, but I thought the pre-alpha gameplay demo looked insanely impressive despite being two years from release and rushed to the showfloor.

A space game won't hold the crown at all most likely. Granted I have no idea just how much is showing in this particular game to warrant a friggin 680, but most space games don't render very much at once which is why they always look so great.

Boarding ships, traversing though spaceports are going to be a major part of the mechanics for this game.
 
Is there a chance that (other than turning out to be false in the first place) the rumored specs are subject to dramatic change now that the two competirs have leaked their hand?

Based on what I read through this and other similar threads, vocal majority supports Orbis >> Durango conclusion. As both next-gen consoles probably have devs working on them for a few years already, if these really are true, they are unlikely to be altered in a significant way, right?
 
Is there a chance that (other than turning out to be false in the first place) the rumored specs are subject to dramatic change now that the two competirs have leaked their hand?

Based on what I read through this and other similar threads, vocal majority supports Orbis >> Durango conclusion. As both next-gen consoles probably have devs working on them for a few years already, if these really are true, they are unlikely to be altered in a significant way, right?

It is highly unlikely that anything changes and no possible way anything drastic changes without delays at this point. Durango is rumored to already be complete.
 
The pre-alpha demo could scale down to a 460, but not noted for the final 2014 release. I imagine that'll be able to scale down as well, but the target baseline specs, minimum for the 'full experience' of the project include a 670/680, and they plan to scale up from there to what I assume are next generation cards depending on release. And yeah I probably should specify it was my opinion,

I can't have a discussion let alone a debate over what is your opinion. your opinion will always be right, that's why its called an opinion.

http://dictionary.reference.com/browse/opinion
1. a belief or judgment that rests on grounds insufficient to produce complete certainty.
2. a personal view, attitude, or appraisal.
 
I didn't say you said it would be better. You said Durango looked to be more efficient. I can't see why.

Orbis has:
- a clearly defined CPU - APU - GPU alignment with a healthy APU that can take a lot of the load off the GPU.
- high speed memory that will keep all of this silicon fed quite well.
- unified memory so no additional hoops for developers to jump through in memory management.
- the smaller, sleeker OS, with only 512MB of system memory locked away from developers. This dovetails perfectly with Sony's track record case in point the Vita, which dramatically reduces it's OS footprint in games with a scaling OS that still manages to function very quickly.
- strong rumors pointing to OpenGL as a non-layered, native API alternative to LibGCM.

Meanwhile on Durango:
- only rumored "secret sauce" to take workload off the GPU, will that "secret sauce" be in as accessibly a form factor as Sony's APU?
- split memory architecture requiring devs to manage the 8 GB system memory while also feeding the 32MB EsRam.
- a much larger OS footprint in terms of both CPU and memory that strongly suggests a non-scaling OS.
- at best it will have DirectX at parity with LibGCM and if the rumors prove to be true OpenGL.

If all of the unknown things about Durango were answered in the most realistically positive way we would still be talking about slower overall memory with a divided supply line and a larger OS footprint over what Orbis is doing. The Durango being equally efficient to the Orbis is extremely idealistic, being more efficient is pie in the sky dreaming.

"Tools" alone can't bridge those gaps. If Sony really does have OpenGL as native then that claim also goes completely out the window. Even if it doesn't, Sony has made huge leaps to closing the gap in the dev tools arena this generation, and that is on more obtuse hardware, which is a major reason why the PS3's tools had to start out so obtuse. More streamlined hardware inherently leads to more streamlined dev tools.

Interesting to see it all laid out like that. Almost feels like Durango is the PS3 this time around, only without the hardware advantage. I hope Microsoft's alternative aspirations with regards to Kinect, Windows or mobile app platform convergence are worth all this. But you never know, there's time left. For all we know Microsoft might still pull out the more efficient console, just doesn't seem that way yet.
 
Where is Proelite when you most need him? And why doesn't Aegies divulge the information he's garnered? The latter's been bandishing the sorry excuse of not understanding the technical mumbo jambo he was fead. Well, easy solution : Just share whatever info you have, guys, and let us discuss it, for god's sake!

Sorry for the outburst : Been having some pre-next gen hysteria syndroms for the last couple of weeks, and my nerves show signs of degradation!
 
Where is Proelite when you most need him? And why doesn't Aegies divulge the information he's garnered? The latter's been bandishing the sorry excuse of not understanding the technical mumbo jambo he was fead. Well, easy solution : Just share whatever info you have, guys, and let us discuss it, for god's sake!

Proelite @ B3D:

Sweetvar26 also said that AMD felt the Xbox was a super computer and was "more" powerful. In hind sight, I think he mistakenly switched the platforms.

From the looks of it, Orbis fits the super computer descriptor better.

This comment is from second half of 2012. AMD already knew the ram expansion from 2 to 4 gb, as it already happened.

It's more likely Sweetvar26 go the two consoles mixed up.
 
Where is Proelite when you most need him? And why doesn't Aegies divulge the information he's garnered? The latter's been bandishing the sorry excuse of not understanding the technical mumbo jambo he was fead. Well, easy solution : Just share whatever info you have, guys, and let us discuss it, for god's sake!

aegies posted some next gen talk on his twitter earlier today.
 
Read Aegies tweets : Same vague, hazy claims...
Proelite changes opinions as I do underwears...

Am I correct in advancing that neither of them has signed any NDA whatsoever? Why the secrecy?
 
Read Aegies tweets : Same vague, hazy claims...
Proelite changes opinions as I do underwears...

Am I correct in advancing that neither of them has signed any NDA whatsoever? Why the secrecy?

Because they don't want to get their source(s) in trouble lol. A few people have had access to stuff they should not have... but I'm pretty sure that stuff was old. Whether they have up to date info or a source with fresh new tidbits is unknown to me.
 
Proelite @ B3D: "From the looks of it, Orbis fits the super computer descriptor better."


I'm not sure how he came to that?


I think it was Xbox 3 that looked like a Super Computer to people from the Devkits because they was using powerful CPUs /GPUs to emulate the special chips that are going to be in the final hardware.
 
I didn't say you said it would be better. You said Durango looked to be more efficient. I can't see why.

Orbis has:
- a clearly defined CPU - APU - GPU alignment with a healthy APU that can take a lot of the load off the GPU.
- high speed memory that will keep all of this silicon fed quite well.
- unified memory so no additional hoops for developers to jump through in memory management.
- the smaller, sleeker OS, with only 512MB of system memory locked away from developers. This dovetails perfectly with Sony's track record case in point the Vita, which dramatically reduces it's OS footprint in games with a scaling OS that still manages to function very quickly.
- strong rumors pointing to OpenGL as a non-layered, native API alternative to LibGCM.

Most of the efficiency claims come from the expectation of ESRAM being used as a large low latency input cache for GPUs. Many are expecting it to have lower latency than L1 cache on other AMD GPUs. This doesn't sound feasible to me.

BTW I'm betting most developers will stick with LibGCM since it's really not an API but a way of directly issuing instructions to the GPU command buffer. OpenGL will be higher level and less efficient.
 
Well, if you look at vgleaks, the durango leak said "x64 cpu" and Orbis said "8 cores jaguar"...

I really think people are making precipitated judgments

EDIT:

jKZaIvgkyoCnB.png
 
Why only 32MB ESRAM?

10MB eDRAM to 32MB ESRAM seems like it's not enough when they went from 512MB GDDR3 RAM to 8GB DDR3 RAM.

They increased the unified system RAM by 16x but only increased the embedded RAM by 3x.

IIRC the 10MB eDRAM was used to give nearly free 2xAA for 640p games or something like that. What can the tiny 32MB of ESRAM be used for?
 
Why only 32MB ESRAM?

10MB eDRAM to 32MB ESRAM seems like it's not enough when they went from 512MB GDDR3 RAM to 8GB DDR3 RAM.

They increased the unified system RAM by 16x but only increased the embedded RAM by 3x.

IIRC the 10MB eDRAM was used to give nearly free 2xAA for 640p games or something like that. What can the tiny 32MB of ESRAM be used for?

$$$
 
I didn't say you said it would be better. You said Durango looked to be more efficient. I can't see why.

Orbis has:
- a clearly defined CPU - APU - GPU alignment with a healthy APU that can take a lot of the load off the GPU.
- high speed memory that will keep all of this silicon fed quite well.
- unified memory so no additional hoops for developers to jump through in memory management.
- the smaller, sleeker OS, with only 512MB of system memory locked away from developers. This dovetails perfectly with Sony's track record case in point the Vita, which dramatically reduces it's OS footprint in games with a scaling OS that still manages to function very quickly.
- strong rumors pointing to OpenGL as a non-layered, native API alternative to LibGCM.

Meanwhile on Durango:
- only rumored "secret sauce" to take workload off the GPU, will that "secret sauce" be in as accessibly a form factor as Sony's APU?
- split memory architecture requiring devs to manage the 8 GB system memory while also feeding the 32MB EsRam.
- a much larger OS footprint in terms of both CPU and memory that strongly suggests a non-scaling OS.
- at best it will have DirectX at parity with LibGCM and if the rumors prove to be true OpenGL.

If all of the unknown things about Durango were answered in the most realistically positive way we would still be talking about slower overall memory with a divided supply line and a larger OS footprint over what Orbis is doing. The Durango being equally efficient to the Orbis is extremely idealistic, being more efficient is pie in the sky dreaming.

"Tools" alone can't bridge those gaps. If Sony really does have OpenGL as native then that claim also goes completely out the window. Even if it doesn't, Sony has made huge leaps to closing the gap in the dev tools arena this generation, and that is on more obtuse hardware, which is a major reason why the PS3's tools had to start out so obtuse. More streamlined hardware inherently leads to more streamlined dev tools.

The xenos was the first compute capable gpu, it was out before dx10, let alone dx11. You're talking to the company who controls D3D and you expect them not to be introducing features and instruction sets and architecture in their gpu that wont be a stop gap for dx12? You're blowing smoke.

Also, the memory effeciency and latency is much better on the 360, the way it's laid out means that developers can write to both ram and esram (which also means that you can use slower memory for tasks which you know will take more time instead of waiting for cycles), which means that you're going to be able to fetch from anywhere in memory, perform arbitrary ALU operations and write the results back to memory at extremely high speeds, in conjunction with the raw floating point performance of the large shader ALU array.

There's a clear reason why MS is going about their design the way they are. Dont think for a moment that it's not intentional and that it's somehow not benefecial. They're getting bandwidth yields are roughly 170gb/s with more and cheaper memory then the ps3 which is roughly 180gb/s.

The consoles will have parity between systems, if anything it's delusional to think there will be recognizable gap between them. Strengths and weaknesses, of course, but parity for the most part.
 
Why do we have to constantly remind people that you can't just add bandwidth together? It doesn't work like that.

Durangos bandwidth is not 170 GB/s by adding 68 + 102. The latter is only pulling from 32 MB.

Microsoft's design is an attempt to mitigate the bandwidth issues by choosing a large pool of ddr3, but its still significantly below the projected bandwidth of Orbis
 
Also, the memory effeciency and latency is much better on the 360, the way it's laid out means that developers can write There's a clear reason why MS is going about their design the way they are. Dont think for a moment that it's not intentional and that it's somehow not benefecial. They're getting bandwidth yields are roughly 170gb/s with more and cheaper memory then the ps3 which is roughly 180gb/s.

This is a bit misleading. That bandwidth is applicable to only 32MB on Durango, whilst it's applicable to the entire 4GB on Orbis.
 
So if Durango has a lot less memory bandwidth than Orbis, how will that affect game performance? Slower loading textures and more pop-in?
 
Why do we have to constantly remind people that you can't just add bandwidth together? It doesn't work like that.

Durangos bandwidth is not 170 GB/s by adding 68 + 102. The latter is only pulling from 32 MB.

Microsoft's design is an attempt to mitigate the bandwidth issues by choosing a large pool of ddr3, but its still significantly below the projected bandwidth of Orbis

you don't just add them together, what are you talking about. You access them simultaneously.
 
Top Bottom