protonscr

PRAGMATA (AppID 3357650): Persistent PSO compatibility hash mismatch on RDNA 4 (GFX1201) causing micro-stutters

vkd3dopen
HansKristian-Work/vkd3d-proton#2962 · opened 2026-04-25 by lugipfupf · updated 2026-04-28 · 7 comments · github
Llugipfupf 2026-04-25 github

PRAGMATA (AppID 3357650): Persistent PSO compatibility hash mismatch on RDNA 4 (GFX1201) causing micro-stutters

Summary

PRAGMATA (Capcom, RE Engine, DX12) produces continuous d3d12_cached_pipeline_state_validate: PSO compatibility hash mismatch warnings on AMD RX 9070 XT (RADV GFX1201) throughout gameplay. These mismatches persist even with VKD3D_CONFIG=no_pipeline_cache, indicating the game's own shipped PSO blobs are being rejected every session with no fallback caching. The result is recurring micro-stutters every 1–10 seconds that do not improve over time or across sessions.

Disclosure

I have spent hours debugging and analyzing the issue, with the help of forums and AI. This report was generated using AI.

System

Component Version
GPU AMD Radeon RX 9070 XT (RADV GFX1201)
CPU AMD Ryzen 7 9800X3D
RAM 32 GB DDR5 @ 5600 MHz
OS Arch Linux, kernel 6.19.13
Compositor Hyprland (Wayland)
Mesa / RADV 26.0.5
vkd3d-proton 3.0.0
Proton experimental-11.0-20260417
Steam App ID 3357650

The fact that no_pipeline_cache does not eliminate the mismatches confirms they originate from the game's own internal D3D12 PSO blob, not from vkd3d-proton's cache layer. vkd3d-proton is correctly rejecting them, but there is no recovery path — the game re-submits the same broken blobs every session.

Pipeline compilation times (with pipeline_library_log)

All observed pipeline compilations completed in under 2ms (max observed: ~1.98ms). Individual compilations are not the stutter cause. The stutter correlates with the frequency of mismatch events forcing repeated fallback recompilation.

Application workaround detection

vkd3d-proton identifies the executable but applies no specific workaround:

info:vkd3d-proton:vkd3d_instance_apply_application_workarounds: Program name: "PRAGMATA.exe" (hash: 2a3c1afb3b904ef6)

Steps to reproduce

  1. Install PRAGMATA (AppID 3357650) via Steam on Linux with any recent Proton version
  2. Launch with PROTON_LOG=1 and VKD3D_CONFIG=pipeline_library_log
  3. Enter gameplay and move around any area for 2–3 minutes
  4. Observe repeated PSO hash mismatch warnings and Fossilize unregistered pipeline warnings in the log
  5. Note micro-stutters correlating with mismatch frequency

What has been ruled out

  • Shader compilation stutter (stutter is consistent in the same room with no new assets)
  • CPU frequency scaling (governor is performance)
  • DNS/network latency (Denuvo domains fully whitelisted and tested with direct DNS)
  • Filesystem CoW overhead (disabled on btrfs for game directory)
  • fTPM, C-States, ReBAR (all disabled in BIOS)
  • Proton version differences (tested Experimental, GE-Proton10-34, Proton 11 beta)

Suggested fix

An application-specific workaround in vkd3d-proton for PRAGMATA.exe (hash: 2a3c1afb3b904ef6) to ignore or gracefully handle the game's shipped PSO compatibility blobs, similar to workarounds applied for other RE Engine titles, would likely resolve or significantly reduce the stutter.

Logs

Full PROTON_LOG sessions available:

  • Baseline log (no extra VKD3D_CONFIG)
  • VKD3D_CONFIG=no_pipeline_cache log
  • VKD3D_CONFIG=pipeline_library_log log

steam-3357650.log
steam-3357650-no_pipeline_cache.log
steam-3357650-pipeline_library_log.log

Eemilnymann 2026-04-26 github

VKD3D_CONFIG=no_pipeline_cache is invalid. VKD3D_CONFIG=pipeline_library_log is invalid. Disclosing the use of AI is pointless when you can't even be bothered to verify easily verifiable things like that.

Mmbriar 2026-04-26 github

All these AI "analysis" people post recently here just add noise. 95% is plain nonsense and then the actual information is hidden in a wall of nonsense text. Just describe what your issue is and how to reproduce it and post a log..

Llugipfupf 2026-04-26 github

I am sorry, if anyone feels like I have wasted their time.

My goal was to give as much information as possible, but maybe I was wrong with the method I chose.
What do you mean with the logs being invalid? I just downloaded all 3 of them from this issue and can open them without issues. It's just hard for me to make much sense of the contents ;-)

As for the possible bug, maybe this is a bit more concise: Symptom is stuttering every now and then with varying time between stutters (1-10 seconds). And there are a lot of those in the logs:

5738.689:0158:01ac:warn:vkd3d-proton:d3d12_cached_pipeline_state_validate: PSO compatibility hash mismatch.

Maybe it has something to do with the stutters, maybe not. I have tried many things but could not get rid of the stutters.

If you consider this report to be noise, then feel free to close.

Either way, thank you for the work your're doing, I really appreciate it.

cheers

Eemilnymann 2026-04-26 github

What do you mean with the logs being invalid?

It's not that the logs are invalid, but the environment variables I mentioned are invalid. They do nothing.

Llugipfupf 2026-04-26 github

Oh, ok :-/ I am truly sorry. I should have verified more thoroughly before filing the issue. Learned something. Besides that, if the issue at hand may not have anything to do with vkd3d, this may be closed. Or, if on the other hand you need more/other info, let me know.

HHansKristian-Work maintainer 2026-04-27 github

Wall of text of AI nonsense just hides the actual useful information.

5738.689:0158:01ac:warn:vkd3d-proton:d3d12_cached_pipeline_state_validate: PSO compatibility hash mismatch.

is worth some triaging, but there's zero reason why it would cause "microstutters" that wouldn't already happen on native.

Llugipfupf 2026-04-28 github

is worth some triaging

Well, that's something at least. I guess, I can rule this one out as well then and hope for a patch from Capcom.

I can edit the original issue and remove whatever is irrelevant/invalid, if that helps.

Proton versions

Launch options