As of this season’s patch I can no longer change my render API. The game feels much worse for me on DX11 than DX12 but it’s stuck on DX11. I can change other video settings fine through the in game settings menu and settings_v0.ini has GraphicsAPI = “Dx12” but when I open the game it still goes to DX11. I’ve tried setting -dx12 and -d3d12 in the command line arguments in battle.net and I’ve tried deleting settings_v0.ini and making it read-only after changing the GraphicsAPI line but nothing has worked so far.
1 Like
I suggest you’d better use dx11 although dx12 can get better performance but dx12 gonna cuz game crushing not working,and Blizzard only lets you seek help on forums, there’s no real customer service.
Same problem here and tried editing the ini file. I want to use FSR4 upscaling, but stuck on DX11.
Game was fine yesterday, I was using DX12 and FSR 4.1 on my Radeon and today game got small update which screwed up all of this. Now I’m forced to play on crappy DX11 with FSR 2.2. Thanks Blizzard. sigh
1 Like
+1 same here with a 9070 on linux no matter what i try it reverts back to dx11 which is a stuttery mess for me !
This is in known issues at the moment:
“Temporarily disabled DX12 Beta for some video cards due to stability concerns.”
May have been leading to some crashes. Hopefully it’s resolved in the next patch so you can return to your preferred render pipeline. I hope they continue to update it.
I didn’t have any crashes, but now i have to deal with horrible image because I’m forced to use FSR 2.2 and DX11 stutters and lags and has such horrid framerate in general. Sigh. But I guess it’s hard when such small company as Blizzard is managing the game.
They likely disabled it for more GPUs than was actually necessary, just to be “safe”.
Gee, if only there was a thing called A PATCH NOTE. You know, so people don’t spend literal HOURS figuring out why the F it doesn’t work and reinstalling the entire frigging 76 GB game just to find out hours and tens of inquiries later that they screwed up the game somehow and disabled it. You know, if only such a thing ever existed… but again, it’s a small company with limited resources, what can you do, right?
1 Like
I think the change was deployed after the patch due to crash report telemetry, hence it not being in the patch notes - the known issues list should be viewable in game at least though.
You know what feature PATCH NOTES have? That you can add MORE NOTES to it. It’s literally the whole point of patch notes. If anything pisses me off it’s either no patch notes or patch notes that say “Fixes and improvements” with no specification of what they are fixing or improving.