In the games stack presentation he makes a specific point that the data wasn't exposed before. Unless I'm mis remembering, but I'm pretty sure he said that.
Current Generation Games Analysis Technical Discussion [2020-2021] [XBSX|S, PS5, PC]
- Thread starter Shortbread
- Start date
- Status
thank you. This is what I wanted. I'll go back to the SFS presentation and see if I can find this part.
edit: I cannot find it. @Jay help?
Implications are pretty large here, it pretty much means even though not exposed on DirectX12 for PC, this type of feature would have been available on PS4 and XBO forward as their own APIs let them bypass any sort of alignment required with PC.
Last edited:
I'll try to find it, as I watched 2021 and went back and watched some previous SFS talks afterwards, so it may have been in one of those.
Can't look right now, but I'll try scrubbing through a couple today
Edit : here you go @iroboto
The first 6:30min she explains that it's opaque then goes on to explain that SF exposes what was a black box.
Worth watching it all, but that's as much as I could do at mo.
Last edited:
Unless vulkan exposed the data prior to DX12U. That's the only chance you have to work out if the data could've been exposed.
As I said unsure where the data was being blocked in the stack.
But in DX12U compared to DX12 this is a new feature of it being exposed. Vulkan is your only chance to find out the specific your looking for I suspect.
Hasn't it already been confirmed that SF is only supported on Turing/Ampere/RDNA2? If older hardware was capable and the functionality simply wasn't exposed before DX12U then why don't RDNA and Pascal at least support it too under that API?
senis_kenis
Newcomer
I ran @DmitryKo DX checker on my vega 56:
Maximum feature level : D3D_FEATURE_LEVEL_12_1 (0xc100)
TiledResourcesTier : D3D12_TILED_RESOURCES_TIER_3 (3)
ResourceBindingTier : D3D12_RESOURCE_BINDING_TIER_3 (3)
...
MeshShaderTier : D3D12_MESH_SHADER_TIER_NOT_SUPPORTED (0)
SamplerFeedbackTier : D3D12_SAMPLER_FEEDBACK_TIER_NOT_SUPPORTED (0)
Thank you. If I could give you 50 upvotes I would here.
And texture space shading is a possibility since Direct X 11 GPU
https://gpuopen.com/learn/texel-shading/
Yes and is streaming virtual textures. Sampler feedback isn’t an enabler of those systems. I don’t think that has been an implication.
regardless I have the information I want.
Last edited:
From the article about SF, its not that SF enables texture space shading, it makes it a lot more practical and much less expensive. Just as SF makes texture streaming/tiles resources a lot more feasible/practical as a result of its ability to give devs feedback so they make better/more accurate decisions and less guesswork and make more optimal use of available resources.
But if it doesn't support DX12U, would you expect it to be exposed?
So the hardware itself may actually be able to send the data but not exposed by DX12.
Tiled resources is rarely use by devs. All virtual resources system use software indirection.
https://gpuopen.com/performance/
Hardware tiled resources aren't recommanded by AMD because of performance problem. At least sampler feedback seems to have much better performance.
And SF has the same problem than hardware tiled resource there is no UpdateTileMappingsIndirect doesn't exist in DirectX and it means you need to use the CPU for updating tile. This is why devs use compute for doing this.
https://forum.beyond3d.com/posts/1868601/
Some dev wait it since a very long time. But it seems it has a security problem.
Last edited:
Hmm. I don’t think SF is a DX12U only feature. It’s has a flag and tier level like any other feature part of Direct3D. For a GPU to be DX12U certified it must among other things has support SF Tier 1.
AMD would be the ones to expose SF on their cards now that SF is a direct3d feature. No reason why they shouldn’t.
https://en.wikipedia.org/wiki/Feature_levels_in_Direct3D#cite_note-57
according to wikipedia dx feature matrix only rdna2 support SF tier1. However i cannot find clear answer if the same functionality can be enabled/exposed on previous gen gpu via other/custom graphics apis.
according to wikipedia dx feature matrix only rdna2 support SF tier1. However i cannot find clear answer if the same functionality can be enabled/exposed on previous gen gpu via other/custom graphics apis.
"
Software-based residency checks can implement arbitrarily small granularities, but applications that implement software-based residency checks must perform a traversal of the residency structure (which includes at least one command/response exchange between the application and the residency structure) for every texture sampling operation. Thus, a software-based residency check could be required to traverse the residency structure for every rendered pixel, which would reduce the performance of the graphics pipeline and increase latency.
Residency checks for texture blocks of arbitrary granularity can be performed in hardware, and therefore without the command/response overhead of software-based residency checks, by storing metadata that encodes compression parameters of a texture block and a residency status of the texture block. The metadata is stored in a GPU memory that is also used to store the texture block for access by a graphics pipeline implemented by the GPU. A shader in the graphics pipeline accesses the metadata for the texture block in conjunction with requesting the texture block to perform a shading operation. For example, the metadata can be accessed concurrently with requesting the texture block. If the metadata indicates that the texture block is resident in the GPU memory, the request for the data in the texture block is returned to the shader. Thus, no additional overhead is incurred by the residency check if the texture block is resident in the GPU memory. If the metadata indicates that the texture block is not resident in the GPU memory, a signal is fed back to the shader to indicate that the requested data is not resident in the GPU memory. The shader can populate the non-resident texture block (e.g., by loading the texture block from disk or procedurally generating the data for the texture block) in response to receiving the feedback. The shader can then re-access the metadata in conjunction (e.g., concurrently) with the texture block. The additional overhead required to perform the residency check in the event that the texture block is not resident in the GPU memory is minimal because it is performed in the flow of the sampling operation, e.g., in conjunction with or concurrently with attempting to access the texture block."
- Status
Similar threads
- Locked
