Directx 12 problem.

[Flaren]

Hello,

I tried to do test on PerformanceTest 10.0, but DirectX 12 causes problems.

+36.625s - DEBUG: DX12 Render call failed - code: -2003238900
+36.640s - ERROR: Asteroids::RenderUI mD2DDeviceContext->EndDraw HRESULT (0x8899000c)
+36.640s - DEBUG: DX12 Render call failed - code: -2003238900
+36.672s - ERROR: Asteroids::RenderUI mD2DDeviceContext->EndDraw HRESULT (0x8899000c)
+36.672s - DEBUG: DX12 Render call failed - code: -2003238900
+36.687s - ERROR: Asteroids::RenderUI mD2DDeviceContext->EndDraw HRESULT (0x8899000c)
+36.687s - DEBUG: DX12 Render call failed - code: -2003238900
+36.703s - ERROR: Asteroids::RenderUI mD2DDeviceContext->EndDraw HRESULT (0x8899000c)
+36.719s - DEBUG: DX12 Render call failed - code: -2003238900
+36.719s - DEBUG: stop test, send close message
+36.937s - DEBUG: Exited Main Loop

This is the debug mode logs.
You may also find the error given at the end of the test on the screenshots.

[David (PassMark)]

Microsoft Error codes are here
https://docs.microsoft.com/en-us/win...error-codes-10

D2DERR_RECREATE_TARGET
0x8899000C, There has been a presentation error that may be recoverable. (in decimal that error code is, -2003238900)

So Microsoft were not very helpful in describing the cause of this error on that page.

However digging a bit deeper we find this detail.
"While your program is running, the graphics device that you are using might become unavailable. For example, the device can be lost if the display resolution changes, or if the user removes the display adapter. If the device is lost, the render target also becomes invalid, along with any device-dependent resources that were associated with the device. Direct2D signals a lost device by returning the error code D2DERR_RECREATE_TARGET from the EndDraw method. If you receive this error code, you must re-create the render target and all device-dependent resources."

So the device disappeared in the middle of the test. If it comes back we could do all the setup again, and try again, but for a benchmark it doesn't really make sense to spend time doing this.

These problems are typically video card device driver bugs, or 3rd party software causing problems (screen sharing, overlays, etc..)