Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
i have BIG frametime spikes and games just freeze on these 566.36 and 566.14
. I installed 566.14 and 566.03 with NVSlimmer. 1 min 1 second latency mon screenshots:kyube wrote: ↑03 Sep 2025, 18:02“Why is LatencyMon not desirable to objectively measure DPC/ISR driver performance?”
Your test data only covers 1 scenario: idle on desktop, which isn't representative of what you feel in-game.
Oh, right. I can test DOOM Eternal for Vulkan workload, D3D11 Borderlands GOTY Remastered, DX9 S.T.A.L.K.E.R. Shadow of Chernobyl and CoD1 for OGL. What time per testing session should I go for? 30 mins? more? less? right now I don't have time to test.kyube wrote: ↑04 Sep 2025, 09:00Your test data only covers 1 scenario: idle on desktop, which isn't representative of what you feel in-game.
The DPC/ISR performance values significantly change once you introduce D3D9-12 3d workloads (games) or OpenGL/VK 3d workloads.
You can take a look at this article, which dissects how Intel ARC cards behave VS AMD cards in D3D11: https://chipsandcheese.com/p/digging-in ... -on-intels
You need a repeatable test environment in a specific graphics API to be able to evaluate 2 driver releases in 1 specific workload (game).
so, 566.03 working for you?crack wrote: ↑04 Sep 2025, 14:47Oh, right. I can test DOOM Eternal for Vulkan workload, D3D11 Borderlands GOTY Remastered, DX9 S.T.A.L.K.E.R. Shadow of Chernobyl and CoD1 for OGL. What time per testing session should I go for? 30 mins? more? less? right now I don't have time to test.kyube wrote: ↑04 Sep 2025, 09:00Your test data only covers 1 scenario: idle on desktop, which isn't representative of what you feel in-game.
The DPC/ISR performance values significantly change once you introduce D3D9-12 3d workloads (games) or OpenGL/VK 3d workloads.
You can take a look at this article, which dissects how Intel ARC cards behave VS AMD cards in D3D11: https://chipsandcheese.com/p/digging-in ... -on-intels
You need a repeatable test environment in a specific graphics API to be able to evaluate 2 driver releases in 1 specific workload (game).
You don't need to do long sessions, shorter intervals are sufficient.
yes, better than 566.14, although 566.14 did not show the big frametime spikes you speak of, this absolutely feels better off straight away after the shader caching finishes.Slender wrote: ↑04 Sep 2025, 14:55so, 566.03 working for you?crack wrote: ↑04 Sep 2025, 14:47Oh, right. I can test DOOM Eternal for Vulkan workload, D3D11 Borderlands GOTY Remastered, DX9 S.T.A.L.K.E.R. Shadow of Chernobyl and CoD1 for OGL. What time per testing session should I go for? 30 mins? more? less? right now I don't have time to test.kyube wrote: ↑04 Sep 2025, 09:00Your test data only covers 1 scenario: idle on desktop, which isn't representative of what you feel in-game.
The DPC/ISR performance values significantly change once you introduce D3D9-12 3d workloads (games) or OpenGL/VK 3d workloads.
You can take a look at this article, which dissects how Intel ARC cards behave VS AMD cards in D3D11: https://chipsandcheese.com/p/digging-in ... -on-intels
You need a repeatable test environment in a specific graphics API to be able to evaluate 2 driver releases in 1 specific workload (game).