protonscr

Validation errors on Windows: index buffer creation flags

dxvkclosed bug
doitsujin/dxvk#61 · opened 2018-02-05 by GabrielMajeri · updated 2018-02-05 · 3 comments · github
GGabrielMajeri 2018-02-05 github

I've run d3d11-triangles.exe on Windows 10 with the validation layers enabled.

Errors

Standard output is flooded with the following warning:

MEM(ERROR): object: 0x3 type: 10 location: 2985 msgCode: 400556898:
Invalid usage flag for Buffer 0x3 used by vkCmdBindIndexBuffer().
In this case, Buffer should have VK_BUFFER_USAGE_INDEX_BUFFER_BIT set during creation.
The spec valid usage text states 'buffer must have been created with the VK_BUFFER_USAGE_INDEX_BUFFER_BIT flag'
(https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html#VUID-vkCmdBindIndexBuffer-buffer-00433)

System information

  • GPU: NVIDIA GTX 960
  • DXVK version: latest master / 26ef59d
Ooscarbg 2018-02-05 github

hope this helps in clearing all Nvidia issues..
right now crash is fixed a few days ago..
but for example ComputeMark renders black screen on all tests:
run on Windows putting dxgi.dll and d3d11.dll on program folder..
basically getting
info: D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info: D3D11CreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn: DxbcOptions: Using FMin/FMax/FClamp instead of NMin/NMax/NClamp
warn: DxbcOptions: Packing depth reference value into coordinate vector
warn: D3D11Device: No matching border color found for (0.5,0.5,0.5,0.5)
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
err: DxvkComputePipeline: Failed to compile pipeline
info: D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_1
info: D3D11CreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info: D3D11CreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn: DxbcOptions: Using FMin/FMax/FClamp instead of NMin/NMax/NClamp
warn: DxbcOptions: Packing depth reference value into coordinate vector
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
warn: DxbcCompiler: Unhandled VS SV output: DxbcSystemValue::ClipDistance
full log ComputeMark_d3d11.log

Ddoitsujin maintainer 2018-02-05 github

Can't reproduce. Which version of the Vulkan SDK are you running?

The validation layers are independent of the GPU, driver, and platform used as long as the application runs the same code path, which DXVK mostly does, so this message is a bit werid.

Please try 0437e5652b650a70d2232ec3e035f88ec5c1c1a2, if that doesn't fix it, I have no idea what is going wrong. I double-checked the code, and anything that is used as an index bufffer in D3D11 is also created with the index buffer flag in Vulkan.

GGabrielMajeri 2018-02-05 github

Can confirm the latest commit does fix the issue.

DLLs