Closed mapmapbear closed 1 month ago
It's not an NRI issue. Most likely shaders do not include debug information. At least all my projects, using NRI, have debug info stripped out (it can be changed by modifying "ShaderMake" command line in the CMake files).
It's not an NRI issue. Most likely shaders do not include debug information. At least all my projects, using NRI, have debug info stripped out (it can be changed by modifying "ShaderMake" command line in the CMake files).
Maybe getting shader's PDB solves that problem?
Debug information can be embedded into a shader binary or come in a separate PDB file (recommended by MS). So, yes.
Debug information can be embedded into a shader binary or come in a separate PDB file (recommended by MS). So, yes.
I compiled the shader of NRISampler using dxc and shademake respectively, and found that this constant buffer display exception only occurs in D3D12. The following image shows some flags of dxc, which proves that it does indeed work under debug, I look forward to hearing from you
Debug information can be embedded into a shader binary or come in a separate PDB file (recommended by MS). So, yes.
I compiled the shader of NRISampler using dxc and shademake respectively, and found that this constant buffer display exception only occurs in D3D12. The following image shows some flags of dxc, which proves that it does indeed work under debug, I look forward to hearing from you
Update!!!, my doubts about FP16 have been ruled out. FP16 has nothing to do with errors -enable-16bit-types
In a common graphics debugger, there is a problem with the display of constant buffers eg:Renderdoc, Nsight, Pix