Bug Report: Performance Issues with DirectX 12 and Vulkan on High-End Hardware
I had a similar problem.
Asrock taichi b650e+7800x3d+RTX4090+nwme_PCIE4.0+nwme_PCIE5.0. With any graphics settings in any resolution, the frame rate on directx12 and vulcan was at around 50fps. The frame rate was higher on directx11, but the game was unstable. The problem was the automatic distribution of PCI lines between the graphics card and the drives. I have set settings 8x4x4 lines and forced usage on a PCIE 4.0 graphics card. Now 8 PCIE4.0 lanes are allocated to the video card. in 4K at maximum graphics settings, I get about 140 frames on directx12. I blocked the frequency at 120 fps with rivatuner and I like the result. |
![]() |
If the fix is to actually tampering with the PC that could be a turn off for users who are inexperience or afraid to open up the case (Given if other games dont have the same issue, while runs on a higher spec demand, what if they accidentally broke a PC out of trying to gain FPS and now instead of low FPS gaming, now no gaming at all
Last edited by Subzidite#6624 on Dec 25, 2024, 10:31:19 AM
|
![]() |
" PROBLEM FINALLY SOLVED: As someone mentioned earlier updating BIOS might help. I updated my bios (previous was 2023 version) and chipset for motherboard, no lags since then, game runs good and stable. P.S. Motherboard -- Asus TUF b650m plus wifi |
![]() |
I have the same issue: FPS on DX12 and Vulkan stays around 45. I’ve tried various recommendations, but nothing helped. My NVIDIA drivers are up-to-date, and I’ve also updated the BIOS. The game is installed on an SSD. Here are my system specs:
Operating System: Windows 11 Pro GPU: NVIDIA GeForce RTX 3070 (newest driver) CPU: AMD Ryzen 5 5600 RAM: 16 GB DDR4 Storage: Installed on a PCIe NVMe SSD |
![]() |
Switching to Vulkan fixed explosion fps issues for me. I'd probably update BIOS as a last resort
Last edited by goodsine#0033 on Jan 4, 2025, 2:33:52 PM
|
![]() |
Just attempting to bump this thread since it appears to have died. Has anyone found additional fixes beyond what has been listed already? I've tried everything so far, and still have the same issues.
|
![]() |