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

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

Proelite

Member
BTW of course Tim Lottes hates DirectX, especially when the comparison is with LibGCM. PC APIs are a necessary evil, and nothing you'd want on a console. It also clarifies his position on Durango, which he sees running a full version of Windows with DirectX.

I am not sure how an unbiased technical guy would jump to that conclusion, unless he is just fucking with us.
 
If you're talking about the rumored specs those are the rumored specs.

VGLeaks 1:

- 8 cores (x64 CPU)
- 12 GB RAM (8 + 4)

The Alpha kit has 12 GB of RAM, rather than the 8 GB in the final design. The extra 4 GB of RAM facilitates development of console system software.

- DirectX 11.x GPU

The Alpha kit uses a discrete graphics card similar in capability and speed to the GPU that will be included in the final design. The card does not have the ESRAM that the final design GPU will.

- 50GB Blu-ray Disk drive
- HDD, etc

VGLeaks 2:

GPU:

- custom D3D11.1 class 800-MHz graphics processor
- 12 shader cores providing a total of 768 threads
- each thread can perform one scalar multiplication and addition operation (MADD) per clock cycle
- at peak performance, the GPU can effectively issue 1.2 trillion floating-point operations per second

How can you to conclude it is based on 7000?
 
BTW of course Tim Lottes hates DirectX, especially when the comparison is with LibGCM. PC APIs are a necessary evil, and nothing you'd want on a console. It also clarifies his position on Durango, which he sees running a full version of Windows with DirectX.
I could see it. Windows 8, but locked out of desktop with a modified Metro interface. Why not.
 
Also thinking....


The 720 needs 3 gig and a runs non specialized Windows 8 even though MS has a specialized and very temporary version of Windows 8 created just for Surface RT that uses 2 or less than 2 gigs of RAM while doubling as a tablet/desktop OS?

Windows 8 PC's minimum RAM requirement is 1gig.


Gonna have to hold off on assuming anything about the OS foot print.
 

Erasus

Member
Also thinking....


The 720 needs 3 gig and a runs non specialized Windows 8 even though MS has a specialized and very temporary version of Windows 8 created just for Surface RT that uses 2 or less than 2 gigs of RAM while doubling as a tablet/desktop OS?

Windows 8 PC's minimum RAM requirement is 1gig.


Gonna have to hold off on assuming anything about the OS foot print.

Yea, with 0 apps running. I think they want people to be able to run also every app and sort of multi task while having a game up. Also OS might incluse Kinect usage?
 
Yea, with 0 apps running. I think they want people to be able to run also every app and sort of multi task while having a game up. Also OS might incluse Kinect usage?

I think windows 8 footprint with no apps running is less than 200 MB (depending on various settings and hardware configuration of course but generally).

EDIT: I believe the kernel overhead is much less. Remember Windows is designed to use up as much memory as reasonably possible for cache but what it actually uses for active memory is less in a clean state. When you remove window managers, UI, desktop OS services, extra drivers for PnP devices, etc... you get down to very low usage thresholds really fast.
 
What evidence do you have to support this? If the target specs are similar to the leaked specs, this isn't the case.

Developers assured him that the nonexistent special sauce would magically surpass Orbis, but only to the tune of 5-10%, just so Proelite could make the claim that Durango > Orbis.
 
RSX = 400GFLOPs, Xenos = 250GFLOPs... yes, flops flops everywhere...

The 400GFLOPs number in reference to RSX is inaccurate as that is counting texture unit ALUs which are completely separate architecturally on Xenos and thus cannot be added in the same way.

The correct apples to apples comparison of the shading power between them is :
RSX = 232GFLOPs, Xenos = 240GFLOPs

And of course Xenos is unified shaders so it can kill RSX in vertex ops by dynamically allocating more resources, it's overall just a lot more efficient.

But the graphics logic in Orbis and Durango are probably extremely similar if not identical.
 
And what if the balance of power shifts dramatically and third parties choose Orbias as their lead platform ?

I could see that happening.

I dont know what balance of power shift you're speaking of. I'm saying whichever of the two is the lowest common denominator is most likely the console devs will lead on, and then port. Just like this gen. Unless of course there's a world of difference between the two as there was between the Wii and the 360/PS3.
 
Yea, with 0 apps running. I think they want people to be able to run also every app and sort of multi task while having a game up. Also OS might incluse Kinect usage?

I have had Windows 8 running on an ancient Pentium Dual Core and only use up to roughly a gig in memory.
 
The 400GFLOPs number in reference to RSX is inaccurate as that is counting texture unit ALUs which are completely separate architecturally on Xenos and thus cannot be added in the same way.

The correct apples to apples comparison of the shading power between them is :
RSX = 232GFLOPs, Xenos = 240GFLOPs

And of course Xenos is unified shaders so it can kill RSX in vertex ops by dynamically allocating more resources, it's overall just a lot more efficient.

But the graphics logic in Orbis and Durango are probably extremely similar if not identical.

Thanks for pointing this out. I knew the 400 GFLOP number of RSX was inflated.

In the end PS3 was marginally more powerful than 360, because CELL made up for the deficiencies with RSX versus Xenos...but at the end of the day it was marginal and extremely hard to extract. So it wasn't obvious unless you looked at certain exclusive titles, and even then who knows if that was more a function of talent versus hardware prowess.

But, with Durango and Orbis sharing the same vendor and basic architecture, the comparisons are a lot more straightforward.
 

THE:MILKMAN

Member
proelite said:
Specs where finalized sometime in late 2011 / earlier 2012.
Only minute changes such as clocks can be tweaked this late in the cycle.

I would be more worried about the shittiness of the January Orbis devkits revealed today in VGLeaks than a very reactive blog post by a known hater of Directx.



Please feel free to explain why they are shitty.

Quoting for Proelite.
 

spisho

Neo Member
I am not sure how an unbiased technical guy would jump to that conclusion, unless he is just fucking with us.

I agree he seems to be jumping to the worst case scenario, but DDR3 with ~3GB reserved for the OS is rather suggestive of a full Windows experience, and if not it's definitely sacrificing bandwidth for whatever OS ends up shipping on there.
 

Proelite

Member
Quoting for Proelite.

8 core dozer at 1.6 ghz, 8gb of ram, and a 18 CU modified Southern Islands just doesn't sound impressive to me.

I'll be very disappointed if that was the kit that's supposed to emulate final Orbis performance.

But according to Thuway, dev kits shown marked improvement every iteration, so final kit performance should be great.
 

Proelite

Member
I agree he seems to be jumping to the worst case scenario, but DDR3 with ~3GB reserved for the OS is rather suggestive of a full Windows experience, and if not it's definitely sacrificing bandwidth for whatever OS ends up shipping on there.

Full Windows experience has support for billions of legacy apps, and drivers. It also has memory paging, complicated task manager, dos, apis for dozens of languages, and thousands of hot fixes.

I am only scratching the surface of what Windows is.
 
8 dozer at 1.6 ghz, 8gb of ram, and a 18 CU modified Southern Islands just doesn't sound impressive to me.

I'll be very disappointed if that was the kit that's supposed to emulate final Orbis performance.

But a modified 12 CU Southern Islands Cape Verde card with 8 Jaguar Cores @ 1.6 Ghz and 8 GB of DDR3 RAM does sound impressive to you?
 

THE:MILKMAN

Member
8 dozer at 1.6 ghz, 8gb of ram, and a 18 CU modified Southern Islands just doesn't sound impressive to me.

I'll be very disappointed if that was the kit that's supposed to emulate final Orbis performance.

As I read it the January devkit is actual early final silicon, not a powerful PC emulating it. But I may be wrong?
 
You dared to say that Durango may be more powerful. You're obviously on the payroll. May I borrow a dollar?

He is going against the prevailing opinion from the sliver of spec info we have on both systems, and even provided percentage estimates for the difference. No real way to know yet what credibility he has in this, since he hasn't provided any significant insider info before that I can think of.
 
That's what's supposed to be in the box, not the devkit.

The semi-final devkit for Orbis is as follows:

SoC Based Devkit

Available January 2013
CPU: 8-core Jaguar
GPU: Liverpool GPU
RAM: unified 8 GB for devkit (4 GB for the retail console)
Subsystem: HDD, Network Controller, BD Drive, Bluetooth Controller, WLAN and HDMI (up to 1980×1080@3D)
Analog Outputs: Audio, Composite Video
Connection to Host: USB 3.0 (targeting over 200 MB/s),
ORBIS Dualshock
Dual Camera
 

nib95

Banned
But a modified 12 CU Southern Islands Cape Verde card with 8 Jaguar Cores @ 1.6 Ghz and 8 GB of DDR3 RAM does sound impressive to you?

Hate to mention it again....but special sauce mang. That's essentially what his argument equates to. That unknown features will make up the difference. Which would be perfectly appreciable, if he had evidence to back it. Having said that, it is a possibility, there's just nothing out there to suggest it yet.

I guess it will boil down to what special sauce (i.e customisations) Orbis and Durango will have, plus the GDDR5 and DDR3 plus Sram differences. You never know, faster ram might still come with Durango, and slower ram with Orbis. Don't think it's set in stone yet.
 

Pistolero

Member
Proelite seems to know very little for someone who indulges in a know-it all attitude (winks, vaguely assertive comments, flip-flop stances...), me thinks...
 

Mindlog

Member
Hate to mention it again....but special sauce mang. That's essentially what his argument equates to. That unknown features will make up the difference. Which would be perfectly appreciable, if he had evidence to justify it. Having said that, it is a possibility, there's just nothing out there to suggest it yet.
Why even bother vigorously defending amateur technical assessments? We're going to find out soon.

If anything argue the Orbis is even stronger given the known memory differentiation. Go big or go home. None of this half-measure crap.

To arms and whatnot.
 

i-Lo

Member
Hate to mention it again....but special sauce mang. That's essentially what his argument equates to. That unknown features will make up the difference. Which would be perfectly appreciable, if he had evidence to back it. Having said that, it is a possibility, there's just nothing out there to suggest it yet.

I guess it will boil down to what special sauce (i.e customisations) Orbis and Durango will have, plus the GDDR5 and DDR3 plus Sdram differences. You never know, faster ram might still come with Durango, and slower ram with Orbis. Don't think it's set in stone yet.

Honestly, I am less resentful that secret recipe and more curious. Given llhere said it is a wash, it has to have had some impact to narrow the TF gap.


I got through Honors just fine; not being overly tech savvy shouldn't subject me to my mathematic abilities being called out by internet douches.


It's surprising that you trivialize the difference of 0.6TF, because you are not "overly tech savvy" hence, did not have enough information to pass such a judgement. Yet when you are called out on it, you get defensive and compensate by showing off your credentials and resort to name calling.

Ah, the beauty of internet forum.
 

derFeef

Member
The semi-final devkit for Orbis is as follows:

SoC Based Devkit

Available January 2013
CPU: 8-core Jaguar
GPU: Liverpool GPU
RAM: unified 8 GB for devkit (4 GB for the retail console)
Subsystem: HDD, Network Controller, BD Drive, Bluetooth Controller, WLAN and HDMI (up to 1980×1080@3D)
Analog Outputs: Audio, Composite Video
Connection to Host: USB 3.0 (targeting over 200 MB/s),
ORBIS Dualshock
Dual Camera

It's nice and all, but still rumored leaks.
I will judge the systems when I play games on them :p
 
Top Bottom