That RDNA 1.8 Consoles Rumor *spawn*
- Thread starter Ronaldo8
- Start date
Alessio1989
Regular
Meaningless gossip... They will probably have some custom BUS between CPU and system memory, like any other recent console..
Are you just trying to confuse DSoup?
Alessio1989
Regular
We do not have a single public technical information to talk about. So it's gossip. So it's meaningless.
And it's perfectly reasonable that the ISA of the upcoming consoles are not 100% equal to the ISA of the future AMD RDNA2 PC GPUs. As any other past console.
EDIT: by a developer point of view, a possible lack of a new geometry pipeline in a mesh+amplification shader stage-like form and the lack of a programmable sampler/sampelr feedback would be a big lack. And yes, I do not care about ray-tracing as I do not care if we can make a colony on Mars.
And it's perfectly reasonable that the ISA of the upcoming consoles are not 100% equal to the ISA of the future AMD RDNA2 PC GPUs. As any other past console.
EDIT: by a developer point of view, a possible lack of a new geometry pipeline in a mesh+amplification shader stage-like form and the lack of a programmable sampler/sampelr feedback would be a big lack. And yes, I do not care about ray-tracing as I do not care if we can make a colony on Mars.
Last edited:
I feel pretty bad for the dude who's DMs got shared. Sucks to be in the spotlight at such an important time. If your friends tell you stuff that might be sensitive, best to keep it to yourself for their sake.
Between the Github leak naming, and the radio silence on VRS and Sampler feedback, I've been considering it a distinct possibility for a while now. So much so that this doesn't actually surprise me.
That's a good point. MS may not have the full suite of "PC RDNA2" technology either, for one reason or another. Though so far, they seemed to have ticked all the publicly revealed boxes. Hotchips in a couple of weeks might offer more insight...
This is a really interesting point. If they chose 36 CUs for BC reasons it figures that there may be other aspects of the PS5 hardware determined by it. Even MS have made mention of having to do work at the hardware level for BC, despite the extra hardware abstraction that they've built into their systems.
Other possible reasons might be:
- Was planned for 2019, but slipped
- Extensive customisation meant having to branch from available RDNA technologies sooner
... but I have to say I like the possibility you've raised here the most. Actually ... you know those rumours about "AMD building RDNA for Sony"? Maybe some aspects of RDNA 1 actually were determined by Sony's needs.
1. There are zero scenarios where a naive solution like checkerboarding will yield better results than VRS. MS's solution in particular enables the calling of a shader per primitive with an almost infinite amount of ways of calculating the shading rate. Lack of VRS is a huge miss.
2. Virtual texture streaming is old news and, as the SIE engineer said, was already being done using shaders on the PS4. However, the old way of doing things cannot determine with certainty what level of a given mip was being sampled. Also, sampler feedback streaming, or at least MS implementation, will provide gains in latency, granularity and efficiency which are crucial when targeting textures on a per frame basis in a JIT system. The PS5 does away with this possible setback by having an incredibly fast throughput such that it can well afford to be more inefficient.
3. I am not familiar with the differences (if any) between the geometry engines of RDNA 1 and the putative mesh shaders of RDNA 2. So won't comment on this.
Not at all strange if there was a year delay.
Featuresets are not pedantry. Will indicate whether performance of the two platorms are comparable.
HBRU
Regular
Of course... BC
I never said they were. I spoke to the version labeling of the featuresets, as in 1.5 vs 1.9 vs 2.0.
I don't really buy the 2019 release theory. Can a one year delay cause such paucity of features? VRS and mesh shaders were not developed in one year time.
Sorry. I misunderstood your post.
Nothing is released yet we don’t know if they haven’t announced thing because they don’t want to. Or they SDK is not ready. Or they do not have it. Etc
only benchmarking can compare the performance of the two systems. This is speculation of have and have nots and relaying that to game performance before either has been released.
Yeah, I think @Pixel has come up with a really sensible possibility there.
BC can put real constraints on the evolution of systems.
I mean, if all goes to plan for AMD you're looking at less than 18 months between the release of RDNA 1 and RDNA 2 for PC. GPUs are highly modular and there's always going to be a time when a feature isn't available, or it is.
That said, AMD have to serve a number of markets and customers. Bringing VRS and Sampler Feedback (useful for more than just efficient, low overhead texture streaming!) to their latest architecture was essential. Simultaneously backporting it to a single-customer design based off an older RDNA derivative may not have been viable even if Sony was prepared to pay for it
Delays, BC, or even a combination of both could be an entirely realistic reason for such a feature disparity. And if BC helps Sony gain more momentum early on than SF or VRS, can you honestly say it was a bad idea?
True, but speculation is a blast. It lets the mind run free! I still remember fondly being one of the very first people ON EARTH to suggest that the Wii had 192 shaders. Woop woop!*
*I've also suggested many things that turned out to be oh so wrong.
Since when was a radio ever silent, except when switched off/down?
Since the FM radio.Since when was a radio ever silent, except when switched off/down?
Alessio1989
Regular
In some countries FM radio is still a thing, especially since Covid-19
But Github wasn't true?
Big difference between being true and being the complete picture...
None of us outsiders have the complete picture at this point.
