• Breaking News

    CopyDescriptors between different heaps How does CopyDescriptors work when copying from a CPU-only heap to a Shader-Visible one? The D3D12_CPU_DESCRIPTOR_HANDLE structure is just a size_t, but if I use CD3DX12_CPU_DESCRIPTOR_HANDLE to create it then it uses the result of GetCPUDescriptorHandleForHeapStart() to offset those size_t's to be specific to that heap. Is CopyDescriptors from one heap to another going to make all the descriptors be specific to that new heap? Also, calls like CreateConstantBufferView and CreateShaderResourceView take a descriptor as one of their parameters (which points to a specific location in a heap). How is that going to get updated for the new heap location? https://ift.tt/eA8V8J

    How does CopyDescriptors work when copying from a CPU-only heap to a Shader-Visible one? The D3D12_CPU_DESCRIPTOR_HANDLE structure is just a size_t, but if I use CD3DX12_CPU_DESCRIPTOR_HANDLE to create it then it uses the result of GetCPUDescriptorHandleForHeapStart() to offset those size_t's to be specific to that heap. Is CopyDescriptors from one heap to another going to make all the descriptors be specific to that new heap? Also, calls like CreateConstantBufferView and CreateShaderResourceView take a descriptor as one of their parameters (which points to a specific location in a heap). How is that going to get updated for the new heap location?

    from GameDev.net http://bit.ly/2DCDFU0

    ليست هناك تعليقات

    Post Top Ad

    ad728

    Post Bottom Ad

    ad728