none
VS 2015: Failure to debug shader RRS feed

  • Question

  • Hi,

    We are on vs2015 & windows10 and if we call OMSetRenderTargetsAndUnorderedAccessViews anywhere in the code, even if it's just with NULL's and do nothing, the shader debugging within Visual Studio Graphics Analyzer errors with "The Graphics Diagnostics engine failed to build the shader trace and therefore is unable to debug the shader". If we remove that API call from the code, everything works fine. 

    If I were to take a simple "HelloWorld" like sample which works with shader debugging and add this supposedly "no-op" code block in there:

    {
        ID3D11RenderTargetView *cv[1] = { NULL };
        ID3D11UnorderedAccessView *uavs[1] = { NULL };
        context->OMSetRenderTargetsAndUnorderedAccessViews(1, cv, NULL, 1, 1, uavs, NULL);
    }

    The shader debugging will fail. Any thoughts why?

    EDIT: Forgot to add that we are on VS2015 Version 14.0.25431.01 Update 3

    Thanks!




    • Edited by zh1983 Tuesday, June 13, 2017 5:51 PM
    Tuesday, June 13, 2017 1:11 AM

All replies

  • Any ideas/suggestions here on what could be wrong?

    Thanks!

    Monday, June 19, 2017 8:48 PM
  • Did you ever find a solution or workaround to this? I've been having the same problem for weeks, except that the graphics debugger won't even show me the frame details. It just gets stuck at "Waiting for the application to draw a DirectX frame..."
    Tuesday, February 6, 2018 9:40 PM