The primary goal for Mortal Kombat 1 shader optimization is Cache Persistence and Multithreaded Warming. MK1 uses a background process to “warm” shaders. If this process is interrupted or if the shader cache size is restricted by your GPU drivers, you will experience micro-stutters. This configuration focuses on increasing the driver-level cache size and manually resetting the “Warming” flag in the configuration files to force a clean, fast compile.
File Location
MK1 stores its local DirectX 12 configuration and shader cache data in the AppData folder. Ensure the game and Steam/Epic are closed before editing:
- Config Folder:
%LocalAppData%\MK12\Saved\Config\WindowsNoEditor\ - Shader Cache Folder:
%LocalAppData%\MK12\Saved\Steam\(or\Epic\)
Technical Configuration (The 2026 “No-Stutter” Template)
While the game does not always generate a visible DX12Config.ini by default, you can often find these parameters within GameUserSettings.ini or by adding an Engine.ini override to force Unreal’s DX12 behavior:
[SystemSettings]
# MK1 Shader Speed Optimization - GameEngineer.net
r.ShaderCompiler.JobPriority=1
r.Shaders.Optimize=1
r.Shaders.FastMath=1
r.D3D12.ShaderCacheMode=1
r.D3D12.PSO.DiskCache=1
r.D3D12.PSO.WarmupTimeAmount=0.0
Parameter Breakdown:
- r.D3D12.PSO.DiskCache=1: Forces the game to write the Pipeline State Objects (PSOs) directly to the disk, preventing the game from re-compiling them every single time you launch.
- r.ShaderCompiler.JobPriority=1: Sets the shader compiler to a higher CPU priority. This makes the “Preparing Shaders” bar at the main menu move significantly faster.
- r.D3D12.PSO.WarmupTimeAmount=0.0: Removes the artificial “wait” time for shader warmup. Note: Use this only if you have a high-end SSD (NVMe Gen4/5), as it forces the engine to load shaders as fast as the hardware allows.
Strategy for 2026 Shader Stability
- The NVIDIA/AMD Cache Rule: In 2026, the most effective “tweak” isn’t in the game files, but in your GPU control panel. Set your Shader Cache Size to Unlimited (or at least 10GB). MK1’s shader library is massive; if the cache is set to “Default,” Windows will delete old MK1 shaders to make room for other games, causing the “Preparing Shaders” loop to repeat.
- Force Re-compilation: If you are experiencing stutters after a patch, go to
%LocalAppData%\MK12\Saved\Steam\and delete all files with the.ushaderprecacheextension. This forces the game to do a “Fresh Warmup,” which is safer than playing with a corrupted or mismatched cache. - E-Core Management: If you are using an Intel 13th/14th/15th Gen CPU, MK1’s shader compiler sometimes struggles with “E-Cores.” Using a tool like Process Lasso to force
MK12.exeto only use P-Cores during the warmup phase can prevent the process from hanging at 99%. - SSD Priority: Never install MK1 on an HDD. The DX12 shader streaming system relies on the random-read speed of an SSD. On an HDD, the “Shader Warming” process can take up to 20 minutes; on an NVMe, it should take less than 2.
Key Performance Parameters
| Parameter | Recommended Value | Impact |
| Shader Cache Size | Unlimited / 10GB | Prevents the game from re-compiling every boot. |
| Disk Type | NVMe SSD | Drastically reduces initial “Shader Warming” time. |
| V-Sync (In-game) | Off | Reduces latency once shaders are loaded. |
| Upscaling (DLSS/FSR) | Quality | Reduces the complexity of the initial shader pass. |
Frequently Asked Questions (FAQ)
Why does my “Preparing Shaders” get stuck at 95%?
This is usually a disk-write conflict. Check if your Antivirus is scanning the %LocalAppData%\MK12 folder. Whitelisting this folder often allows the final 5% of the compression to finish instantly.
Does “Shader Warming” affect online play?
Absolutely. If you skip the warmup and go straight to the Kombat League, your game will stutter every time a character uses a move for the first time in that session. This can lead to “Desync” errors and losses.
I updated my drivers and it’s slow again!
This is normal for DX12. Every GPU driver update changes how the hardware communicates with the API, making the old cache obsolete. Always allow the full 100% completion after a driver update.
No. Shader caches are unique to your specific GPU model, driver version, and CPU architecture. Using someone else’s file will cause immediate crashes.
Conclusion and Expected Results
By prioritizing the Shader Compiler Job and setting your GPU Shader Cache to Unlimited, you are effectively telling your PC to “remember” Mortal Kombat 1’s complex visual data forever. You can expect near-instant game boots after the initial compile and zero micro-stutters during high-intensity Fatalities or Kameo assists.