Previous update’s results can be seen here

Benchmark template spreadsheet: https://docs.google.com/spreadsheets/d/1hnERNVvrv8lJfkAZtgE4V0afo90bh0_zPrX4Ep7aJZI/

Please put (or edit) your results here: https://forms.gle/mv3DW6MtDcnJNN3h6

Users’ results can be seen here: https://docs.google.com/spreadsheets/d/17gsJtW5QrcSMNCbyQbIt09XlOusrvIluS_8Esg0S6s4/

Purpose of Benchmarking

To my understanding, Valve intends to eventually drop DX11 support in one of their in-development games: Deadlock (source). Because Deadlock doesn’t have a benchmark map or program, I decided that the next best option would be to benchmark CS2 in both DX11 and Vulkan every time an update has anything related to performance improvements in the changelogs.
The goal is to document if any improvements or regressions have occurred in Vulkan or DX11 performance in CS2, and to see if this could indicate any progress towards a full transition to Vulkan in later Source 2 games. A link to the template spreadsheet can be seen above, and my benchmarking results will be provided below along with a commentary.

My Non-Game Specs

• CPU: AMD Ryzen 7 9700X
• GPU: Nvidia Geforce RTX 5070 Ti
• Operating System: Windows 11 25H2
• GPU Driver Version: 596.36

Benchmark Results

Link:
– Mean DX11 Average FPS: 826.09 (Standard Deviation: 9.11)
– Mean DX11 1% FPS: 228.15 (Standard Deviation: 4.50)
– Mean Vulkan Average FPS: 697.94 (Standard Deviation: 9.35)
– Mean Vulkan 1% FPS: 199.05 (Standard Deviation: 4.35)

Discussion

Another regression in Vulkan catching up to DX11. Valve please fix.