If you are encountering Gotham Knights D3D12 error while playing the Mission Heist at STAR Labs, we have a workaround.
Gotham Knights has been out for a while, and it’s been receiving mixed reviews from critics and gamers alike. One of the main reasons why Gotham Knights was not well received is because of its bugs and glitches.
Although the devs have fixed major bugs like the failed to join session error, there are still glitches such as the Gotham Knights D3D12 error which has been making some people stuck at a particular mission.
The good news is a Reddit user has found a workaround for this issue. Let's get into it!
How to fix the Gotham Knights D3D12 error
Many players have reported that on the Mission Heist at STAR Labs during the fight the game consistently crashes with a DXGI_Device_Hung error, making it impossible to progress past this point.
According to the support website, the error is under investigation and we can expect a fix soon. In the meantime, you can try the following workaround suggested by this Reddit user. Before that, make sure your graphics drivers are fully updated, as mentioned in the error message.
"When the encounter starts, start powering up the railgun and immediately run up the stairs to the right and kill the goons as they come up the steps, then run down and fire the gun and grapple back up to where you were."
This little trick will help you avoid crashing in the game, and thereby, you will not encounter the Gotham Knights D3D12 error.
- Read more: How to fix Gotham Knights crashing
What is Gotham Knights D3D12 error?
The Gotham Knights D3D12 error happens during the Mission Heist at STAR Labs where you need to rotate the Railgun to free the scientists. At a certain point in the mission, the game crashes to the desktop and you are presented with a message that says:
A call to a D3D12 API Failed with D3D HRESULT error code: 887A0005
DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG.
Please try updating your GPU drivers. Exiting...
By the looks of it, a bug in the game code is causing the D3D12 error. As we mentioned earlier, the error has been acknowledged by the devs and is under investigation. Hopefully, they will patch the issue soon.