When used, the flag refers to the absolute texel location within a texture, rather than being bound by the traditional values of 0 and 1. The new Agility SDK's non-normalized sampling feature moves away from typical sampling methods, instead allowing developers to place a sampler using the D3D12_SAMPLER_FLAG_NON_NORMALIZED_COORDINATES flag. Texture sampling refers to the method used to retrieve data from a specific texture, which is later combined or processed to create the sample. The second feature, non-normalized sampling, provides developers with a more absolute method to obtain texture sampling data.
While the impact is currently unknown and requires further testing, the reduction in resources and required data could very well translate to new available efficiencies for developers and performance enhancements for end users. This access eliminates the need for data to be copied from VRAM to DRAM for CPU access and use. The first of the new features, known as GPU upload heaps, decreases dynamic random access memory (DRAM) utilization by allowing the CPU to access the GPU's video RAM (VRAM). The updates, in conjunction with VRAM resizable base address register (BAR), provide more efficient VRAM data handling across the CPU and GPU, as well as enhancements improving texture-related information management and use. The new version brings developers two new features, GPU upload heaps and non-normalized sampling. Why it matters: On Thursday, Microsoft's Agility SDK development team announced the preview release of Agility SDK version 1.7.10.0.
0 kommentar(er)
