Low FPS DX12

So my specs are a i7-6700k CPU, 32GB of memory, and 2 980 Ti's running on Windows 10. I ran the benchmark multiple times with different settings and here are the results. The DirectX 12 tests are with SLI turned off and using the multi-GPU option in the game settings and the DirectX 11 tested are with SLI turned on. All tests were done with Shadowplay and the Steam overlay turned off.

 

DirectX 12 - Fullscreen - 1 GPU - High Settings - 32.7 fps average.

DirectX 12 - Fullscreen - 2 GPUs - High Settings - 33.1 fps average.

DirectX 12 - Borderless Windowed - 1 GPU - High Settings - 52.1 fps average.

DirectX 12 - Borderless Windowed - 2 GPUs - High Settings - 52.0 fps average.

 

DirectX 11 - Fullscreen - 1 GPU - High Settings - 68.7 fps average.

DirectX 11 - Fullscreen - 2 GPUs(SLI) - High Settings - 70.1 fps average.

DirectX 11 - Borderless Windowed - 1 GPU - High Settings - 68.0 fps average.

DirectX 11 - Borderless Windowed - 2 GPU(SLI) - High Settings - Crashed

 

11,801 views 4 replies
Reply #1 Top

Something is definitely wrong there. I get 46 fps on a single GTX 970 on high (1080p) DX12 while I have tonnes of crap running in the background.

 

What is your CPU usage like when running the benchmark?

I would recommend trying setting AsyncComputeOff=1 in the Settings.ini in the "Documents\My Games\Ashes of the Singularity" directory.

As a last resort maybe try physically removing one of the GPUs and see if it makes any difference, I would expect your single GPU DX12 performance to be the same as DX11.

 

If you aren't able to improve your performance I would recommend submitting a support ticket (instructions at bottom of general troubleshooting).

https://esupport.stardock.com/index.php?/default_import/Knowledgebase/Article/View/530/175/general-ashes-troubleshooting

Reply #2 Top

So I reran the benchmark after turning off AsyncCompute and the results were the same. I did everything on the troubleshooting page and my fps is still terrible.

Reply #3 Top

I see you are using the high preset. What resolution are your fullscreen tests at? Borderless Windowed will use the desktop resolution... what's that set to?