I think the Lottes' blog post deserves its own thread.
Your posts are confusing.
I think the Lottes' blog post deserves its own thread.
Your posts are confusing.
It's no fun when you're not in the dark anymore.
But watching people squirm at the what you know to be vague / false / misleading / accurate news is amusing.
It's no fun when you're not in the dark anymore.
But watching people squirm at the what you know to be vague / false / misleading / accurate news is amusing.
What has changed from the point where the developers were excited about the possibilities of the durango and were telling game journalists such as Arthur the good things about the Durango to now?
If nothing of note has changed why is everyone sweating this?
1.8 teraflops to 1.2 teraflops.
1.8 teraflops to 1.2 teraflops.
It's a decimal difference ffs. Seems highly unnecessary to fret over.
1.8 teraflops to 1.2 teraflops.
It's a decimal difference ffs. Seems highly unnecessary to fret over.
What has changed with the Durango itself? was it downgraded at some point?
Or is everyone just enamored with the new shiny ball in the room?
It's a decimal difference ffs. Seems highly unnecessary to fret over.
MS goes to 16GB DDR3 and 16MB eSRAM, thanks Sweeny!
It's 50%.
Those numbers don't really mean much...
I mean, for all we know (unless you've been given information the rest of us haven't), the Orbis Floating Point throughput of 1.86 could be Single Precision and the Durango's 1.2 could be Double Precision (1.2 TFLOPS double is unlikely, but not out of the question)...
Also, I am not convinced this alone will have a particularly huge impact on the performance difference of the two systems, being just one single metric in a whole system full of them.
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 Orbis devkits revealed today in VGLeaks than a very reactive blog post by a known hater of Directx.
PS3 in Gflops too.
This mean almost nothing.
LOL
Oh god, my sides.
Those numbers don't really mean much...
I mean, for all we know (unless you've been given information the rest of us haven't), the Orbis Floating Point throughput of 1.86 could be Single Precision and the Durango's 1.2 could be Double Precision (1.2 TFLOPS double is unlikely, but not out of the question)...
Also, I am not convinced this alone will have a particularly huge impact on the performance difference of the two systems, being just one single metric in a whole system full of them.
Those numbers don't really mean much...
I mean, for all we know (unless you've been given information the rest of us haven't), the Orbis Floating Point throughput of 1.86 could be Single Precision and the Durango's 1.2 could be Double Precision (1.2 TFLOPS double is unlikely, but not out of the question)...
Also, I am not convinced this alone will have a particularly huge impact on the performance difference of the two systems, being just one single metric in a whole system full of them.
Not really. But when you have Bkilian (ex-Microsoft) and ERP (current SCEA dev) on b3d both saying flops don't mean anything, I think it's safe to say that flops don't mean everything.
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.
Even Tim claims FLOPS don't mean everything.Not really. But when you have Bkilian (ex-Microsoft) and ERP (current SCEA dev) on b3d both saying flops don't mean anything, I think it's safe to say that flops don't mean everything.
However, few noticed.If PS4 has a real-time OS, with a libGCM style low level access to the GPU, then the PS4 1st party games will be years ahead of the PC simply because it opens up what is possible on the GPU.
Those numbers don't really mean much...
I mean, for all we know (unless you've been given information the rest of us haven't), the Orbis Floating Point throughput of 1.86 could be Single Precision and the Durango's 1.2 could be Double Precision (1.2 TFLOPS double is unlikely, but not out of the question)...
Also, I am not convinced this alone will have a particularly huge impact on the performance difference of the two systems, being just one single metric in a whole system full of them.
They're both AMD. Those numbers are based on very similar hardware.
It is a significant difference.
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.
It is a significant difference.
Oh for the love of...
I can tell my ignore list is going to swell massively as E3 approaches.
They're both AMD. Those numbers are based on very similar hardware.
It is a significant difference.
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.
This post is sad
Yes.
Some people are ignoring stupidity better than others. For me, I just use to tools this forum provides.
Pretty sure you will come across your share of insanity come the next few months.
I don't think a sane person would define that post as stupid, this is a complicated area.
Based on the rumors, there is nothing similar about the hardware other than being made by the same company sharing a CPU. It's like saying 360 and PS3 are similar hardware because they share the PPE and both have a GPU. The PS4 is designed around a moderate amount high bandwidth memory and the 360 is designed around a large amount of slow memory supplemented with esram. They're very different approaches and these differences will be reflected in every part of the design as they were almost certainly decided on early in the process.
Claiming 1.2TF double precision in a closed box with TDP of less than 200W and 28nm fabrication is sane? Not even AMD Radeon HD7970 GHz edition produces that.
Not really. But when you have Bkilian (ex-Microsoft) and ERP (current SCEA dev) on b3d both saying flops don't mean anything, I think it's safe to say that flops don't mean everything.
ROFL
I won't call it stupid, because he honestly may not know but it reeks of spin.I don't think a sane person would define that post as stupid, this is a complicated area.
I won't call it stupid, because he honestly may not know but it reeks of spin.
I won't call it stupid, because he honestly may not know but it reeks of spin.
I really feel for anybody who reads posts from the developer types and come away with the conclusion that flops or raw power don't mean anything.
They're both based on 7000 series AMD GPUs. One is better.
This makes me hopeful for x-play between the new Xbox and PC at least GFWL games.The guy says Durango is gonna be a cheap PC with off the shelf Windows on it, focused on DVR and delivering games for the casual market. It will also make profit day 1.
He might know about tech, but he doesn't seem to know anything that isn't out there.
As far as I know, the latest versions of USB and firewire still keep the same drawbacks and benefits... there's more to a protocol than max bandwidth, especially when latency is important.
But then I don't pretend that MS should use firewire, just that using USB is not a given to connect a camera, especially if you're considering a proprietary connector. There are other options, and some of them can provide lower latency and not require additional CPU.
RSX = 400GFLOPs, Xenos = 250GFLOPs... yes, flops flops everywhere...
We don't know that.