Nsight fails to open text editor with shader source

Developer Tools Nsight Visual Studio Edition
1

NSight Version 2019.1.1
NSight Build Number 2019.1.1.19056
Visual Studio Community 2019 Version 16.0.2
GPU Gefore GTX 1060 Driver Version 419.17
Windows 10 64-bit

I am trying to use the shader debugging feature. When I capture a frame and scrub to the event I am interested in, I can see the shader I am interested in with a hyperlink on the source in the API Inspector:

[url]https://lh3.googleusercontent.com/czOQdHRq7ARqJRtZ9oUS_zMnICfRIrNamd0s0Bxoz6ezX1puwx9j34dcUAaDlHA_usRK0hE6TrjfSIDlo_zZJTlOxwEovZUJHaVpaER22LnTuHtGnyuZH3_4J5rjREtB94UX50dhcebYOSNhRrprTTaQNDNH0CnYOvmSikzQ8F7dbOzRH8N2q1SKtObVhx5JPvbP05SPY2v5IvVrL_-YIKX8bfnio5cDZXaSaPo_B6-rS4tHLo6N4RvYynPymxtKaWniYSya0pDtTYUapA37x4apaj1ub_Qhb_a-NnCXy2S72y31iGj_e0dLryl7Ktd_PWVH5IY2zxvbnv2BRBZ_Xf9ET0coEtY347M4vlUNfziuC7H9f8YdThgaUO4hnD5RG2Ny4RpFZCUShB46hzeDVs4yvXeXHZqza-ICq9XxzY-M-5KUNB5WMLJPEFsiSr-T4QhlwL8-NEAVhwc4_aWZQvThWIxN15YvRSx5bkm1WGC3ry2kYQcA0N_r-XWfjZ6L-RdpV1xKJupL8y7Il08D_Ma9XT_ZOURtP36Jt4LZsmKX7tQ508AbIoFg6jMalqmJd7XVUrYnRF3_BPa2Fmrh2CtrRuZ2NGZM6Jg1LsszVid0R4h0CPBZzg8G4raZu9DBqqAT31_zigeoOTZ962EKHOXCIPlVSsFH=w1470-h828-no[/url]

But, when I click on the hyperlink, I am presented with an empty text editor panel:

[url]https://lh3.googleusercontent.com/cGAH3e9t8r1Ru2CpEuf0hs6p-3Et2T5OQ6hTSpe1xAMIf4KI--HxwGyXe3A9aIg_CHjqIn-ZGdS6CXVykKGXoUaxt0ATDDC2njnkoBbtTEL3Dx2EHSkw5W1cwZYFDeQnfAoAGtvYNPXM1FfnBQLnb-V2mg1k-7FV_9rl1l6vRHZ4fxwQXug5LsV5PHlpT64V8NBIFqbC4PntIKRvEdmKCbnHyVWlpOQojYmg8UabaHbdx8Zfdo2b8YUFEq-hgxdnb5Kz58X94yIowQVJSXY76c7-XehlIKifisEmDW9qwm5sZOLoKbyCnnD62cyKirt4aRgOPptX60ixGrIEGwVa-yjaTdBAy8WBws24u4URFRbjhS05Ax-ER6Ghfgg2bKOiQSj3EtBtFaml4ChNqLo-OxZbo_PNb9sPvcX2R4dlGkE9_sGOKeGLHQyZwCrG_Ap8fH9z97y8K7jP-0nO4ZPt9T0vfgLzQsv1eaEJ7R5HjR5u9Z-r6YgNRDpvyafPBviTeU0_kLsFdELyXDsJwR16m7rhajRCWAqtjK8oZYXMHQ_5VVsQqMpsN4ydXu-aBmaOx2YTTPHUABH3G_R_2QuX_ZNAG1Y5j39GTCgjxsR6kmoFCWRRropQM_-6w56g6VaipjJshzcUFOlde9INXAM9ptTCOPds0d4R=w1470-h828-no[/url]

If I right-click on the panel tab and click on “Open Containing Folder”, I can see that the file has contents:

[url]https://lh3.googleusercontent.com/ZV9u8BzpFjMbWF8QpobSLHmRxp3cNCqvyiV8ApazSeMlWZ8VxbIDHbFEmvot2TBWo901JrpjTzdWzOr3UAWre5737RnBMo98WHjQtIHHvT2cVzbEAdQlAim4OH1Z5sXpJpERaU6jwcV9zyVug7pVmMWTpReiuLnw4iOyHWpixlSAvueDLh1QiV9JVtU_JbEAQAh-LbBoaE90bqdu15qt4OT78F2CoYNxRAcw2ENtbBVP6RyOe6lQFhW9Fo2yPjIvkqrWhPfYWncUwAh_6ndC-5zGsredqeU9i4Ho2y0FaAZiWftpiXD4RzlKWfQBSdAZot2Xib2Xa-Ukj8DwU12S86Gayb27D7rGiWNW10T8NDO7tBn1U7mRd_2ClPC81c8oVCZnv1fHTeGeFVq1JxRO0V8QBehe4x8rSTuu9RWBEpqM_kYj4stlE4VLKvLTAfg89S4X_ihumkFm2pfDtNc_FpwXn5UQWF0sIBEFXqOlDTT4IDQ1mhAkXIyqZ0svQ1NczszP_5ep-EnSSBLgve1ninlivSfBCIjr5Ewo4sg-shL08v3JVhnaDAjGsxxgtOSEL1qtexpVg-MFgcAu408z68o4o1S4Hq_BxB2WBOEpiLRZ_SvZ2aCkPEj5yS8KDa1NXqyNhS_i7VO97g_9iJBLKsEOefaMsTJt=w1470-h828-no[/url]

I can also open this temp file in a normal text editor to see contents:

[url]https://lh3.googleusercontent.com/s0xpI9r_dyCCXCM7Ca0TJYx4vSspJS13p_83zhnOrvhI4bZOxL2H5FlVfZCI6z-kyyhh8f1g2HMI6-kPTTwTID4ZPWBzs_cKWj93462Q8vibDGOC9CqcrmtTtS6yi3aXk5L71lmOarC3lQZV9Kw1R0CBN3rj8aR45GAjmEFRyQA5jPo2GpfSpznKHuyX09JSpYwXpk2iJBIaWGwJn4I5eImzGZ2sLiTJbbWyvqLRhz66xSlx-kEivVa_1twm2M6INrYWHGtHZ6A0I2C_EXHnQ0UuqsX_zrxQ2sd1HU2tSK89uxgjPIoscGyMPVIGw4s-G-9v7r84Fs4CuGpQb0KBcJD2ZfEEabwDDSmjuTcOG7iP9y3sWUYeMhiEOBn-Us0AWL2xWaptd1YXnYziZMSnfsxBDiGL3tBxdU1Lp2omgZuUARc6ieqFLAbLTdeG1ybGW9NfvsBBRZV3Fy0laYKdcSTdbgSm3lPU_8TKuqSpwUQZmxALOyAKXrAuCoB8PRRLazQsT2tDpbLctkgHbRy-PtQ_z4CmIAmqMhGmnQQ1po-XIsXsD-LaPwnYTKC-ichR3PIfhk2dCkzr4ialq-2IO4SELuEEmCnZOLojug5eXYczuBfEaZcXcSg7n2Ng6uxuwhQQgUqgUvTk6d7zT4UHUIGo7inaUWHA=w1470-h828-no[/url]

but I can’t toggle breakpoints in the external editor.

2

I’m sorry to say that NsightVSE no longer support shader debugging.

See [url]https://developer.nvidia.com/nsight-visual-studio-edition-features[/url]
[5] Not shown: Note that shader debugging (previously only supported on Kepler GPUs and for D3D11 and Open GL (4.2-4.5)) has been removed as of version 2019.1.

3

Is there some alternative tool that you would like to recommend? Shader debugging seems just as important as viewing renderer states when tracking down bugs.

4

RenderDoc has some basic shader debugging. You could try that.

As a note, we will be supporting Shader Debugging again in the future! But for now, it is unfortunately deprecated.