- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
My DX11 app has recently stopped capturing pixels written to all Render Target Views - they are all rendering as black (despite being touched and not depth rejected). I've culled out all the code from my Pixel Shader so it only emits red colour - but no affect.
Once the deferred render pass is complete, I render semi-transparent pixels as a forward pass, and these render OK - despite using the same shader code.
This started happening about 5 weeks ago - could it be related to a GPA release ? If not, any idea what could be causing it ?
This is only evident in frame capture - trace and stream capture seems fine.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Answering my own query:
I reworked the code to use DirectX11 Immediate Context for all rendering, and this enabled GPA to capture the frame successfully again. When I swap to using Deferred Contexts + Command Lists GPA no longer captures the frame. Its a workaround, but it works.
コピーされたリンク
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Answering my own query:
I reworked the code to use DirectX11 Immediate Context for all rendering, and this enabled GPA to capture the frame successfully again. When I swap to using Deferred Contexts + Command Lists GPA no longer captures the frame. Its a workaround, but it works.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hey PhilippH,
I'm glad you were able to resolve your issue!
We like to document and investigate issues encountered in order to improve GPA. Reviewing your application's source code could help us track down why using Deferred Contexts and Command Lists caused undesired behavior in the Render Target View of Frame Analyzer. If this is something you are interested in sharing with us, please feel free to reply and/or send us an email at [email protected].
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hello PhillipH,
Thank you for your post, and we appreciate you bringing this frame capture issue to our attention.
We'd like to investigate this further. To accurately diagnose and address this problem, reviewing your application's source code would be very beneficial. This will allow us to better understand of the circumstances surrounding the crash.
We'd also like to ask for the system information from Graphics Monitor on your machine to help us better understand the context of this problem (accessible using the (i) icon in the top right hand corner of the screen, see picture below)
Thank you and looking forward to hearing from you.