That RDNA 1.8 Consoles Rumor *spawn*

Well MS did file this patent, which is explicitly related to increasing the efficiency of tiled resources via improvements (including potential hardware implementation) in the handling of residency maps.

 

Not going to be all that much drama here. We know which console is more powerful. I guess the interesting part will be how much of DF wins it translates to and how much is in not a big deal territory.

 

What advantages might those be ?

And it is an orthogonal issue as far as I'm concerned. How much data you can compress (whether using ML or not) is independent of how much data you can stream from your drive ...(both can impact texture streaming system but they're very much separate variables)

Texture compression can be used achieve the same effect and increasing resolution means a potential tradeoff with lower frametimes or vice versa so your texel density budget doesn't really change regardless ...

I very much doubt that native 4K resolution will even come close to being the standard for AAA games as they have other important matters like ray tracing to deal with which will almost certainly make it impossible for them to target very high resolutions or framerates ...

Texture compression can have artifacts but for the most part developers can more easily control their output compared to artifacts from ML-based solutions. With ML you're at the mercy of how good your data will be while training this model but with texture compression you're at the mercy of an algorithm which is far more reasonable since they're more likely to work from a general standpoint these days ...

Just in case you've been living under a rock, developers have been using MIP maps to this optimize the scenario of distant textures that you speak of so ML doesn't really offer anything new here either ...

That patent only covers a feedback loop system. It doesn't go into the specifics of how the tile mappings are updated in memory so this patent is pretty much outside of that scope. This leads me to believe that RDNA2 just like it's predecessors before it doesn't actually have a different implementation of how tile mappings are updated ...

 

these patents were only recently made public and im thinking they're the final design of RDNA2 CU's

Each CU has RT units parallel to simd units (that execute shaders) .. thats what i interpret 13 (RT) + 12 (shader) = 25 ..

If you've designed your scheduled calls correctly, the scheduler can feed both SIMD and RT units in parallel per CU ..



ref: https://pdfpiw.uspto.gov/.piw?PageN...0692271.PN.%26OS=PN/10692271%26RS=PN/10692271

 

This "residency map" is just the "MinMip texture" that was described in the D3D sampler feedback spec. I want to know how the hardware will update the tile mappings itself. This patent is pretty useless in trying to describe that process ...

I don't think you've really got all that much of a grasp on how on what exactly sampler feedbacks are or how they interact with tiled resources so let me explain. Feedback maps can only be either a committed or a placed resource. A tiled resource is normally created as a reserved resource. The UpdateTileMappings API specifically needs to be called to change the tile mappings in a reserved resource. Just having a feedback map alone won't automatically do this for you like you seem to keep implying ...

Feedback maps are a totally different type of resource compared to a reserved/tiled resource and are separate from each other ...

 

Maybe clock speed conversation will start to shift to feature support.

https://respawnfirst.com/sony-engineer-confirms-ps5-rdna2/

 

Hmm yea Sony needs to get out infront and deal with this. This will be a burden if they don’t deal with this leading up to launch.

 

Well they're basically the same as the last time I stated them (in a post of mine which I think you quoted from). Also the same as the ones that the MS Game Stack GM himself talked about, quoted by @eastmen (which I think you also replied to).

C'mon bro, no-one has time to go running in circles.

The post you had responded to was about one of the potential benefits of real time upresing, namely the impact on a texture streaming system of being able to stream smaller textures and ML upres in real time. Basically, about the direct relationship between a hypothetical ML uprezzer and texture streaming requirements.

You responded "And texture streaming is an orthogonal issue altogether", leading me to think you were saying that ML upressing in real time is unrelated to a game's texture streaming requirements.

If what you meant was "streaming requirements are independent of a given drives capabilities", then yeah. But that, ironically, is independent of the point I was trying to make...

I know this quote was directed to eastmen, but I wanted to point out that the training data could easily be uncompressed 24-bit 8K asset textures (or higher for future compatibility), with the machine tuned on a per-game or even a per-level or per-material basis (whatever you want). So static images with definite states. Far more optimal than the situation for DLSS, or MS's own ML HDR for backwards compatibility (ML is everywhere!!) which both have to work on very dynamic frame-buffers.

 

Same idea. Sony need to explain....

 

Needs? Sony can overclock the ps4 pro, call that ps5 sweet silence and anybody would buy it without making any question.
If they lack vrs they will just say that their image quality is always to the max, and any outlet will shit on xsx because of reduced quality.
Sony doesn't need to do anything.

 

Why? Most people that care about this info are console trolls.

 

Articles add up over time. There comes a point where if enough people are armed with the information and it’s never corrected, then it becomes knowledge for everyone. It would have an effect if they are the same price for instance.

 

Yes, like the ps4 pro that was a failure because was 2TF less e 50$ more than the one x.

 

I can't imagine most console buyers knowing what RDNA or even a GPU is. They did care about the UE5 demo or the PS5 reveal event tho.

Let console concern trolls be concerned and show COD running on a PS5 next month.

 

Users get informed, things can shift. That’s just part of the way customers are. You are going to get the person that does research and that travels down too.

I’m just stating my opinion of things. It’s not detrimental but I think it deserves some attention.

 

Depends on what people consider important.

Will the average Joe be more likely to notice a 20% resolution drop and VRS omission, or a 100% increase in loading speed?

I'm certain that Sony are going to smash records this year with the PS5 regardless of it usage of a feature that the competitor uses (and is likely covered by *other* unique features).

 

Well...

 

Over the time with the DF articles about multiplat games performances this lack (if it's there) can have quite an impact... maybe not so huge but clearly visible... and myself for instance this time I'm considering XSX (last time did not give a cent to Xbox One)...