16 Gbyte is not enough, no HbM2 or other Wide I/O Solutions is also very dissapointing, cleary not a generational Leap. Busarchitecture/Memorysystem is a big Bottleneck.
You're off your rocker and lost your marbles.
16 Gbyte is not enough, no HbM2 or other Wide I/O Solutions is also very dissapointing, cleary not a generational Leap. Busarchitecture/Memorysystem is a big Bottleneck.
He can see these SOC layouts.Btw do you guys remember taiwan insider aquariuszi, he ended up pretty accurate about the SoC for XSX at least(he guessed ~350mm2), i was thinking he's wrong due to most people(including DF) guessed ~400mm2 for XSX, but nah.
Now let's wait for the PS5(he guessed ~300mm2).
https://pttweb.tw/s/3We5x
I think 11.6 is pretty new one, here is the TF stocks of PS5:Was the 11.6TF before or after Spencer confirmed 12 TFs at VGA (2 * OneX)?
Well....my theory of Lockhart being primarily for Xcloud was wrong. Apparently the XSX chip can be used to virtualize 4 Xbox One S instances in Xcloud....
So have any donation bets now completed? As a result of the release?
I remember reading people who were pretty adamant xsx was <10TF due to only being 2x xb1x, too bad there wasn't a bet.I don't think so, I only remember them being made on Sony PS5 side. But then again I'm old and have slept since then. *shrug*
SSD speed (I/O) is 2GB/s rounded as the insider correctly predicted. So now, since a few hours, we must all use compressed (marketing) numbers even if we have being using actual I/O BW numbers (the real amount of bytes that pass by the controller) for years ?
Are we going to use the 25tf number announced by Microsoft (and happily printed by DF) too ?
To clarify, I'm not saying the Github data is wrong - just that it was wrongly used to prove PS5 is 9TF as it's incomplete data. You know this thread is full of people using the Github data in this way, Shifty even had to tell people to stop using it this way. And (again) I'm not discounting this guy just guessed right - but it's interesting he guessed almost exactly the correct speed, he could have just said 1.8. Not only that, he said RDNA 2.So guy who posted 10 wrong things for 1 right, after 12TF number was already confirmed, was more correct then document which showed :
56CU chip (which it technically is)
Actual confirmed chip codename - Arden
560GB/s
320bit bus
RT/VRS
Same 2.0GHz clock for PS5
Actual codename for PS5 chip - Oberon
Now, I already said this, with Xbox One X MS used full chip for dev kit and cut 4CUs for retail, so it could have easily happen again. But to throw away one leak because data from it was incorrectly assumed (because hey, there still are 3584 shader cores in XSX), and go with guy that posted 10 more wrong things for one correct one is...interesting.
Btw, if we are being pedantic - chip is 1.825MHz.
See my reply above. Either way, I'm not saying it proves anything, just that we should keep an open mind - the truth is likely out there, it's just spotting it in the noise.Also, read his post, explains everything regarding the insider who guessed XSX specs.
https://www.resetera.com/threads/ps...se-read-03-16-staff-post.173318/post-29949494
From DrKeo
''I have to say, he had like 50% chance of guessing that. If you take 12TF for granted (because of the windows central leak), there aren't many ways of achieving that. You basically have two options:
1) 52CU @1.81Ghz.
2) 56CU @1.675Ghz.
Anything else doesn't make much sense. I mean, you can add two less likely options, 48CU @1.95Ghz, and 60CU @1.562Ghz but that's still well over 25% chance (considering the last two options aren't that likely). A lot of numbers have been thrown around, I mean I made a post about XSX memory having two speeds, 10GB @560GB/s and 6GB @336GB/s back in December which is spot on, but you don't see me claiming to be an insider. I just take the rumors and leaked numbers and play with them according to my technical knowledge and still I've provided better and more accurate "insider" information.''
It’s as valid as any of the 10000 assumptions posted here based on zero facts.That's not a valid argument (if it was, I wouldn't have asked for one ). That hype brought customers to the fight - bums on seats. Explain to me how a lack of PS5 info now means a lack of 'bums on seats' when it launches. If PS5 wasn't advertised at all, then yes, you'd have a point. "PS5? I didn't even know it was out. That's why I bought an Xbox." Clearly though, PS5 will be fully covered when it's time to. So it's not an issue of no coverage, but coverage timing. You're saying that XBSX is gaining an advantage. In this business, that means unit sales. So, how are PS5's unit sales going to be affected by a lack of information 8 months in advance as opposed to, say, only 4 months in advance? How many people are going to have their mind made up now for XBSX who can't then be influenced to consider PS5 in some months' time because the info is too late? Or is your argument something else? Please explain what Sony loses with this silence.
See my reply above. Either way, I'm not saying it proves anything, just that we should keep an open mind - the truth is likely out there, it's just spotting it in the noise.
What's this based on, just wanting more?
What do you think would be min?
Yes, ps5 could very well be 12, 13 or 15TF. It could also be sub 10. Or anything between. Nothing is off the cards untill official specs drop. Wouldn’t it be for all the leaks, common sense would be it is around what xbox is, for me atleast. I personally choose to believe in what another doesn’t. If it turns out to be 15tf of rdna2 monster, then well we have some real monster of a console there.
I guess sony won’t be having to wait too long for them to show something?
Now that we know that devs can choose to run the XsX CPU with SMT on or off does that lend more credibility to this thing being an upgraded Lockhart?