Hello,

I've been browsing through the samples here, and I noticed some weird behavior on the "RaytracingMiniEngineSample," looks like something strange is happening with the texture filtering, but only in specific areas.

This may already be known, but I didn't see mention of it in the issues.

I'm on an RTX 2060, i7 3770k, 18362.778

All the best, Nico.

I have modified the HelloTriangle sample to read vertex positions from HLSL constants, and while rendering works as expected attempting to analyze the DrawInstanced() call in Visual Studio Graphics Analyzer causes the analyzer to crash. I attempted to submit feedback using Microsoft Connect and I get the following error message: "You are not authorized to submit the feedback for this connection.".

I have a diagsession that can help reproduce the issue, and I have the modified code that I can share. Where to go to get this fixed?

Hi,

I'm getting the error

D3D12 ERROR: ID3D12Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). [ EXECUTION ERROR #232: DEVICE_REMOVAL_PROCESS_AT_FAULT] 

at the following callstack:

D3D12RaytracingMiniEngineSample.exe!PostEffects::Render() Line 511	C++
D3D12RaytracingMiniEngineSample.exe!GameCore::UpdateApplication(GameCore::IGameApp & game) Line 77	C++
D3D12RaytracingMiniEngineSample.exe!GameCore::RunApplication(GameCore::IGameApp & app, const wchar_t * className) Line 356	C++
D3D12RaytracingMiniEngineSample.exe!wmain(int argc, wchar_t * * argv) Line 278	C++

Even after commenting out all code within the PostEffects::Render() function (other than context.begin() and context.finish()) the crash still occurs. With the d3d debug layer enabled I get the following output

D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 1 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 2 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 3 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 4 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 5 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 6 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 7 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 8 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]
D3D12 ERROR: CGraphicsCommandList::SetComputeRootDescriptorTable: Specified GPU Descriptor Handle (ptr = 0x13a79035420 at 9 offsetInDescriptorsFromDescriptorHeapStart) of type SRV, for Root Signature (0x0000013A0A687230:'Unnamed ID3D12RootSignature Object')'s Descriptor Table (at Parameter Index [4])'s Descriptor Range (at Range Index [0] of type D3D12_DESCRIPTOR_RANGE_TYPE_UAV) have mismatching types. All descriptors of descriptor ranges declared STATIC (not-DESCRIPTORS_VOLATILE) in a root signature must be initialized prior to being set on the command list. [ EXECUTION ERROR #646: INVALID_DESCRIPTOR_HANDLE]

at

	D3D12RaytracingMiniEngineSample.exe!D3D12RaytracingMiniEngineSample::RaytraceDiffuse(GraphicsContext & context, const Math::Camera & camera, ColorBuffer & colorTarget) Line 1588	C++
 	D3D12RaytracingMiniEngineSample.exe!D3D12RaytracingMiniEngineSample::Raytrace(GraphicsContext & gfxContext) Line 1692	C++
 	D3D12RaytracingMiniEngineSample.exe!D3D12RaytracingMiniEngineSample::RenderScene() Line 1396	C++
 	D3D12RaytracingMiniEngineSample.exe!GameCore::UpdateApplication(GameCore::IGameApp & game) Line 75	C++
 	D3D12RaytracingMiniEngineSample.exe!GameCore::RunApplication(GameCore::IGameApp & app, const wchar_t * className) Line 356	C++
 	D3D12RaytracingMiniEngineSample.exe!wmain(int argc, wchar_t * * argv) Line 278	C++

I'm not sure if any of this is helpful, but I'm running this on a GTX1050 on 411.70 drivers. For what it's worth all of the other samples in this solution work as expected.

D3D12 WARNING: ID3D12Resource::ID3D12Resource::Map: pReadRange is NULL and the heap page property is WRITE_BACK. This can be an indicator of inefficiencies that will result on mobile systems, as the range should be as tight as possible. But, it is also possible the range must encompass the whole subresource.A NULL pReadRange parameter indicates all resource memory will be read by the CPU.  [ EXECUTION WARNING #930: MAP_INVALID_NULLRANGE]

D3D12 WARNING: ID3D12Resource::ID3D12Resource::Unmap: pWrittenRange is NULL and the heap page property is WRITE_BACK. This can be an indicator of inefficiencies that will result on mobile systems, as the range should be as tight as possible. But, it is also possible the range must encompass the whole subresource.A NULL pWrittenRange parameter indicates all resource memory was written to.  [ EXECUTION WARNING #931: UNMAP_INVALID_NULLRANGE]

I am trying to execute two command lists at once to see if gpu cores, and heaps are being used properly and I can't debug it because this pops up and crashes the debugger. When I execute without graphics debugger everything works perfectly, both command lists are rendering their draw commands and everything looks fine.

Dear Microsoft Team,

I attached two files, which contain a modified version of the HelloTexture sample.

The major change is, that I create an unordered access view to the texture in addition to the shader resource view in the LoadAssets method of the sample:

D3D12_UNORDERED_ACCESS_VIEW_DESC uavDesc = {};
uavDesc.Format = textureDesc.Format;
uavDesc.ViewDimension = D3D12_UAV_DIMENSION_TEXTURE2D;
uavDesc.Texture2D.MipSlice = 0;
uavDesc.Texture2D.PlaneSlice = 0;

handle.ptr += m_srvDescriptorSize;

m_device->CreateUnorderedAccessView(m_texture.Get(), nullptr, &uavDesc, handle);

Also I change the resource state of the texture from COPY_DEST to UNORDERED_ACCESS instead to PIXEL_SHADER_RESOURCE:

m_commandList->ResourceBarrier(1, &CD3DX12_RESOURCE_BARRIER::Transition(m_texture.Get(), D3D12_RESOURCE_STATE_COPY_DEST, D3D12_RESOURCE_STATE_UNORDERED_ACCESS));

I did not change anything in the rendering method, so the texture is still used there as a pixel shader resource. Now my question: Why is this working? Why can the texture be used as a pixel shader resource so its resource state is UNORDERED_ACCESS?

Is it because UNORDERED_ACCESS is a read/write state and the set read flag automatically includes read-only states? On the other hand, changing the state to or-combined UNORDERED_ACCESS | PIXEL_SHADER_RESOURCE is not allowed, cause read/write states cannot or-combined with read-only states. So to be honest, I am a bit confused.

I did not find an option in the Visual Studio Graphics Debugger (and neither in NSight) to check the current state of a resource. Did I have overseen something?

Kind regards,

Joerg Sahm

D3D12HelloTexture.zip

I have been trying to compile the example stated in the title, however DXC keeps erroring out with pretty much no debug information on compile - all other samples work fine.

1>dxc failed : cannot specify entry point for a library
1>E:\Visual Studio 2019\IDE\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(1532,5): error MSB6006: "dxc.exe" exited with code 1.
1>Done building project "D3D12RaytracingRealTimeDenoisedAmbientOcclusion.vcxproj" -- FAILED.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

It seems that there is a library with an invalid entry point somewhere, but I have absolutely no clue where. Is there any further debugging for DXC or is there a shader error somewhere ?

In line 78, CommandListManager::m_CommandQueue is NULL when running the Debug and Profile builds. This bug is found in CommandQueue::Create of CommandListManager.cpp, part of the Core library. Does not trigger when running Release configuration.

Fix: Commenting out line 100 pDevice->SetStablePowerState(TRUE); seems to fix this bug. Forcing low GPU clocks seems to put the hardware in a state that fails creation of the CommandQueue.

My system is NVIDIA Geforce 1070, Intel i6500K

Capturing a frame that renders a single triangle (Based on the HelloTriangle) sample crashes the graphics debugging tools with or without the debug SDK layer enabled. To reproduce, open the attached diag session in crashing frame.zip and double click the single captured frame. Output from dxcap -info also attached. Let me know if you need more information.

crashing frame.zip

dxcap_info.txt

I wasn't sure where else to ask this so feel free to remove if this isn't the appropriate place. I noticed the samples are all using Win32 instead of the new UWP API's. Is that the recommended approach of making DX12 applications? Or was it just an arbitrary decision for the samples?

I brought this up the other day in a closed thread, so I am creating a new one. Feel free to tell me to close this one if needed.

Has there been any update on the DX12+XAML for UWP template? I am currently developing a C#/C++ Direct2D application and have run into an issue creating my SwapChainPanel.

Compiler crashes when building MiniEngine (VS2015Update1 default cmplr.).

"1> GraphicsCore.cpp 1> Generating Code... 1>c:\program files (x86)\microsoft visual studio 14.0\vc\include\xmemory0(909): fatal error C1001: An internal error has occurred in the compiler. 1> (compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 246) 1> To work around this problem, try simplifying or changing the program near the locations listed above. 1> Please choose the Technical Support command on the Visual C++ 1> Help menu, or open the Technical Support help file for more information 1> CL!InvokeCompilerPass()+0x2d4bd 1> CL!DllGetC2Telemetry()+0xae663 1> "

Failed normal Download ZIP

When I click the [<> Code] button and "Download ZIP", then I got a corrupted file (Windows cannot open the folder). Note that I repeated the same process so many times since many months ago because DirectX 12 is very important, but still failed. I tried 7-Zip to force extract but there are a lot of missing files then.

Failed when using git clone

The latest percentage I remember stuck on 27% (500 MB+), because it's too slow, not normal, but when I came back then it's suddenly 100% (failed). The reason I download from Linux is the normal Download ZIP from Windows didn't work, and I was hoping that it will work on Linux but it doesn't work.

Questions

Is it possible to fix that problem? Should the administrator reupload the DirectX Samples? Or should I wait for the release of DirectX 13 because it's impossible to learn DirectX 12?

I asked the question in this link but a community expert said that the issue is more related to GitHub and my machine: https://learn.microsoft.com/en-us/answers/questions/1112283/how-to-use-the-d3d12-raytracing-fallback-layer.html

I might be wrong but it seems like the m_renderContextFenceValues array is not indexed correctly in the WaitForGpu() function. m_renderContextFenceValues is an array of size ThreadCount but it is indexed using frame-index which might lead to access violation. I couldn't reproduce the issue as the WaitForGpu is only called when DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_RESET but I thought it might worth someone double checking it.

• According to official docs(https://learn.microsoft.com/en-us/windows/win32/api/d3d12/nf-d3d12-id3d12commandqueue-updatetilemappings?redirectedfrom=MSDN), UpdateTileMappings is only taking a pointer to a single heap(allowing multiple offsets into this heap, but not multiple heaps). The sample is iterating over multiple heaps and tries to map tiles to them in a single UpdateTileMappings call. While this doesn't break the functionality of the sample, in a real world applications with more complicated heap usage patterns, this wouldn't work.

Unhandled exception at 0x00007FFAABD706BC (KernelBase.dll) in D3D12RaytracingProceduralGeometry.exe: 0xC000041D

Callstack:

• KernelBase.dll!00007ffaabd706bc() Unknown
• DXGIDebug.dll!00007ffa5cbd3059() Unknown
• d3d12SDKLayers.dll!00007ffa49c57731() Unknown
• d3d12SDKLayers.dll!00007ffa49b745ea() Unknown
• d3d12SDKLayers.dll!00007ffa49b744a3() Unknown
• d3d12SDKLayers.dll!00007ffa49be499e() Unknown
• d3d12SDKLayers.dll!00007ffa49be00c1() Unknown
• D3D12RaytracingProceduralGeometry.exe!DX::DeviceResources::ExecuteCommandList() Line 556 C++
• D3D12RaytracingProceduralGeometry.exe!DX::DeviceResources::Present(D3D12_RESOURCE_STATES beforeState) Line 518 C++
• D3D12RaytracingProceduralGeometry.exe!D3D12RaytracingProceduralGeometry::OnRender() Line 1297 C++
• D3D12RaytracingProceduralGeometry.exe!Win32Application::WindowProc(HWND__ * hWnd, unsigned int message, unsigned __int64 wParam, __int64 lParam) Line 232 C++
• [External Code]
• D3D12RaytracingProceduralGeometry.exe!Win32Application::Run(DXSample * pSample, HINSTANCE__ * hInstance, int nCmdShow) Line 73 C++
• D3D12RaytracingProceduralGeometry.exe!WinMain(HINSTANCE__ * hInstance, HINSTANCE__ * __formal, char * __formal, int nCmdShow) Line 19 C++
• [External Code]

Windows 11 25206.1000 nVidia GeForce RTX 3070 (31.0.15.3004)

I just got a question regarding the Direct3D 12 HDR sample app. Actual metadata is only transmitted when the app is in fullscreen. I confirmed this with a hdfury arcana that shows the HDMI stream information. Is this behavior intended, where metadata is only forwarded in fullscreen mode, or is this a bug? Or to ask it differently what is needed for the windows compositor to actually forward HDR metadata?

This behavior is also present in other apps, like the video player mpv, that rely on the same api calls (like IDXGISwapChain4_SetHDRMetaData). The mpv video player transmits metadata only in fullscreen mode, like the HDR samples app.

(tested on Windows 10 21H2, with a RTX3050 and a RX 580)

Hello!

I was looking at the HDR sample here: https://github.com/microsoft/DirectX-Graphics-Samples/blob/master/Samples/Desktop/D3D12HDR/src/D3D12HDR.cpp#L994

And it seems to treat MaxMasteringLuminance and MinMasteringLuminance as the same range/scale.

Whereas the docs say:

MaxMasteringLuminance

The maximum number of nits of the display used to master the content. Values are in whole nits.

MinMasteringLuminance

The minimum number of nits of the display used to master the content. Values are 1/10000th of a nit (0.0001 nit).

Is the sample wrong, are the docs wrong, or am I just misunderstanding?

Thanks for your time!