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

Next-Gen PS5 & XSX |OT| Console tEch threaD

Status
Not open for further replies.

Rheon

Member
I'm just happy the 9.2TF thing is more less dead now.

Both consoles being more less the same in terms of power is really exciting. It means games/services will be the deciding factor of who wins this gen and that's a great thing.
 

Gamernyc78

Banned
Nothing proven yet Ps5 could still be 9.2tf to many people certain it will be 13tf wait until it's 100% confirmed by sony then belive until then take all the info with a pinch of salt.

Nothing proven yet but best believe shit isn't 9tf lol well he happy if it's 12 it isn't tht serious like it is for others that keep pushing 9tf narrative.
 
Last edited:

hemo memo

You can't die before your death
So it looks like the news coming from Kojima Productions was the PC port of Death Stranding.



tenor.gif
 

44alltheway

Member
This is likely not the only news from Kojima Productions this week.
I'd make a bet saying it is. Assuming by news you mean something that has to do with next-gen

No this only solidifies something new for the 3rd. Today is the 2nd
No it doesn't! when did Kojima Productions say anything about March 3rd? That picture posted earlier today only had the number 3 because march is the 3rd month in the year.
 
Last edited:
Tommy Fisher has been criticized by some people, even I had my weak days, but it is obvious that he was telling the truth. Tommy Fisher is going to cover many mouths.
Tommy Fisher was caught in the past sharing supposed PS5 specs with per CU L1 cache memory numbers. In RDNA architecture the L1 cache is per shader array, not per CU. I won't trust anything he says until he actually leaks something that is proven correct which, at this point in time, hasn't yet happened.
 
Last edited:

DeepEnigma

Gold Member
Tommy Fisher was caught in the past sharing supposed PS5 specs with per CU L1 cache memory numbers. In RDNA architecture the L1 cache is per shader array, not per CU. I won't trust anything he says until he actually leaks something that is proven correct which, at this point in time, hasn't yet happened.

You mean like the XSX 12TF RNDA2 that everyone ridiculed, even other supposed insiders on other sites?
 
Last edited:
Because github.




No, seriously, if this winds up being true for PS5, yes I still remain skeptical until officially confirmed....

It was probably because of the way Sony is doing BC. And focusing on nailing it. Also, with the questions surrounding github after folks started digging into the info, it should have been taken with a grain of salt for PS5.

Matched Series X to a tee tho.

I've said before it should have been treated on the same level as an insider. I really think some thought it was the same thing as the SuperDae hack. Its not IMO.

What made me sit up and take notice recently is a post on another forum saying it's possible the github data was a mix of 2 gpu's... older and newer version. Ariel vs Oberon.

There was too much smoke around the data being incomplete, off, etc

But there's no more smoke around that than what the insiders have been saying the past few months. Some have even wavered between the systems being 9-10, then 12, then 11, then 13 etc. I've been doing some reading on the Beyond3D forums as well and they have a lot of good analysis on the data.

And tbf, I haven't been using Github exclusively whatsoever. My thing is moreso on the GPU data and benchmarks that have been coming up. There are several products matching those data/benchmarks that have either been officially announced or practically confirmed to be real, and again Oberon steppings have been found there.

If Oberon (in any stepping) is not the PS5 chip, why would Sony spend so much time on testing it? If Ariel is still in contention why hasn't it gone through any recent steppings? These are also valid questions imho.

At this point since the beginning of last week TF-wars rumors have been growing at a fever pitch. So it's probably more than time Sony actually come out with some official information.

Not in Japan. It's March 3rd there.

PS headquarters is in California now, so I thought such an announcement would come from them?
 
Last edited:

xPikYx

Member
So there we are, I was predicting back in December RDNA2 14tf ps5, I was quite right after all... Hahaha call me insider XD

All these rumours coming up mean tomorrow something is really happening?
 

Sinthor

Gold Member
Better question is why has no silicon surfaced in testing results indicating a PS5 chip fitting specifications to reach that number? I mean it definitely sounds like a great target to hit but we have GPU database entries on many, many other AMD GPUs and APUs that have been officiated in one way or another and, more importantly, we have actually datamined information for.

And it still doesn't answer why a certain other chip has been tested as recently up to December from last year. Unless the base/Pro plans are actually holding some validity, or there is another PS5-related APU with data that will show up very soon (if Sony's actually going to talk of specs or specs somehow get leaked out this soon, it shouldn't take more than a month for such a chip's data to be found in AMD's database bank), be it another Oberon stepping or a revision chip.

Because given what PS5 chips exist that we have actual evidence of existence on, there's but a few ways to reach the numbers Osiris mentioned in their post:

-Full active 40CU Oberon E0 clocked @ 2600MHz (13.3)

-Full active 40CU Oberon E0 clocked @ 2550MHz (13.05)

- Oberon E0* with 48CUs clocked @ 2125MHz (13.05)

- Oberon E0* with 54CUs clocked @ 1890MHz (13.06)

- Oberon E0* with 56CUs clocked @ 1815MHz (13.009)

- Unknown Chip

Highlighted that specific option because it mirrors the butterfly setup, 18 x 3 = 54. However, the E0* ones are scenarios where E0 is a larger Oberon chip than the others. We don't actually have data yet on the CU setup for Oberon E0, so it's possible it could have additional units. After all, it had a fix for the memory controller on it as well. However, one thing working against this, is that steppings with that large a change between previous ones usually get a full revision. IIRC that usually means a different codename to go with it.

So E0 could fit the criteria the whole time and we just don't know it yet, or there's another chip on the database (by now it would absolutely be recorded onto the database, it's already early March) fitting the criteria. But if it's another chip altogether, why was E0 tested as late as December 2019? Wouldn't it actually be more hopeful that E0 is this "other chip" and has the means of providing the higher numbers sanely?

We also have to ask what chip is in the latest devkit that was supposedly sent out. The V-shaped devkit had one of the pre-E0 Oberon steppings in it, and that devkit was sent roughly around the time of E3 2019 (or shortly after). Given the timing insiders were claiming the new devkit was sent and E0's logging, I'm going to assume the latest devkit has the E0 stepping in it. We already know E0 upped the bandwidth some, but we don't know if it has additional CUs on it (being a bigger chip than the previous steppings). If it does, would such an addition still fit in giving it a stepping designation, or fall more in line with a full revision?

I mean, I'd like to believe it, but as you say there's still too many other things of valid concern to prevent that just yet. But that's just my opinion. Either way we'll be finding out soon where PS5 actually is in terms of at least some of the major specs, and probably get additional details on XSX like the storage and memory amount/bandwidth. All leading up to E3 of course.

I don't know how people put such stock in the GitHub "leaks" to begin with. Sure they're solid data..seemingly, but what are the chances some low level intern is trusted with top tier and top security data? I can tell you in MY industry that chance is virtually nil and any intern making that mistake would be canned immediately.

Also, people like to point to the supposed XBX chip showing the same results MS just announced (12TF). So what does that mean for the arguments that XBX dev kits were so far behind that Developers were saying a 9TF PS5 dev kit was ahead in performance? That just doesn't make logical sense. If they had 12TF silicon available, they would be having developers use that as their target for performance. Not magically stepping up the silicon in power over tons of different revisions till they hit their target, whatever that was.

I mean, seriously. Time will tell what the truth is, but those GitHub numbers, which seeming to be real data are also VERY suspect IMHO for those reasons. We shall see....
 
I'm going to help dig yourself out of this hole, remember when someone (I have no idea who) said they heard the machines were 11.6 and 12.4 sometime last year? That number was SPOT ON at that time with PSV having a slight lead but also having heat and sound issues. (Heat and sound are no longer issues) MS announces 12 TF hey look a .4 increase not bad at all they made it. BOTH are > 10 (said this last year) with PSV still having a slight advantage. (Said this last year also.) Both were aiming for a very high number (13) and from what I can gather one of them may have actually hit that number. (Its not MS) Either way BOTH consoles are stupidly powerful and still very close. 12 vs 12.4 or 13.2 (Within 1TF of the numbers with a . up in both cases not down) isn't bad at all.

This last part is completely my opinion
I think the main reason we arent hearing about Lockheart is because MS KNOW Sony is going all in for a premium console. Their is no PSV is the mid range system rhetoric to play at launching both simultaneously would cannibalize their XseX sales.
Somehow I see a lot of crow being eaten on your behalf.

Sony isn't going to eat losses, and they won't price themselves out of their expected market range. There's a catch 22 here with what you're saying.
 
Last edited:

DeepEnigma

Gold Member
Who was first to confirm XSX 12 TF RDNA, wasn't it kleegamefan?

Klee did not say RDNA2, and when asked I am pretty sure he said "no" to it. :pie_thinking:

Everyone knew it was at least RDNA1.0 since it was Navi, and Navi is the departure of GCN to RDNA1.0 on.
 
Last edited:

Md Ray

Member
Last edited:

44alltheway

Member
For what?!?!?!? He's is one of the most polite and unbiased users here - does he turn into some kind of maniac over at the asylum?
I mean he did post a private conversation. If I were in the same situation than I probably would have taken action as well.
 

LED Guy?

Banned
Who was first to confirm XSX 12 TF RDNA, wasn't it kleegamefan?
No Kleegamefan confirmed that both are RDNA and both being double digits before basically anyone, and then when the news broke out about Xbox Series X being 12 TF, everyone was saying that it is GCN and whatnot, Klee at that time said that he already knew it would be 12 TF and he confirmed that it’ll be in RDNA when almost everyone was betting it would be GCN TFs, and then Klee said that it didn’t change anything, PS5 is still a bit more powerful, so more than 12 TFs.
 
Last edited:

MadAnon

Member
Nobody will obviously focus on Tommy Fisher posting his 12TF "info" several days after Windowscentral broke the news. Convenietly he didn't post his numbers before. :pie_roffles:

Also Series X being 52CUs when we have more legit data pointing towards 56CUs at 1675mhz (exactly 12TF). And who can forget the whole RDNA cache debacle.
 
Last edited:

Mriverz

Member
Playing the Ff remake and shyt this game looks amazing On 4.2 tf I cant even imagine it running at 9.2tf let alone 11-13 with a oled or qled. We should all be happy ^_^
 

saintjules

Member
For what?!?!?!? He's is one of the most polite and unbiased users here - does he turn into some kind of maniac over at the asylum?

We will let him explain if/when he wants to. I was wondering considering he shared private messages from Mods publicly, but not sure if those Mods even saw that and considered the ban.
 

DeepEnigma

Gold Member
Nobody will obviously focus on Tommy Fisher posting his 12TF info several days after Windowscentral broke the news. Convenietly he didn't post his numbers before. :pie_roffles:

Also Series X being 52CUs when we have more legit data pointing towards 56CUs at 1675mhz (exactly 12TF). And who can forget the whole RDNA cache debacle.

Not a single insider or website mentioned RDAN2 (they all just said RDNA which is obvious and known for over a year because it's Navi). In fact, they all denied it or claimed it would be at most "1.5".

He stuck to RDNA2, and yet here we are. RDNA2 confirmed.
 
Last edited:

MadAnon

Member
Not a single insider or website mentioned RDAN2 (they all just said RDNA which is obvious and known for over a year because it's Navi). In fact, they all denied it or claimed it would be at most "1.5".

He stuck to RDNA2, and yet here we are. RDNA2 confirmed.
You mean he made a guess based on AMD RDNA2 = RT slides?

By the way, PS5 will be clocked at 2ghz according to him. Guess where he got this info? Github? :pie_roffles:
 
Last edited:

FacelessSamurai

..but cry so much I wish I had some
Not a single insider or website mentioned RDAN2 (they all just said RDNA which is obvious and known for over a year because it's Navi). In fact, they all denied it or claimed it would be at most "1.5".

He stuck to RDNA2, and yet here we are. RDNA2 confirmed.
If you throw so much stuff at the wall I guess you can expect at least 1 thing to stick in the end, doesn’t mean he is legit.
 

DeepEnigma

Gold Member
You mean he made a guess based on AMD RDNA = RT slides?

We all guessed. He stuck to it. Not long after it was confirmed.

Other verified insiders on other sites denied it though, so what do you make of that shit?

If you throw so much stuff at the wall I guess you can expect at least 1 thing to stick in the end, doesn’t mean he is legit.

giphy.gif
 
Last edited:
Status
Not open for further replies.
Top Bottom